6 Apr
2021
6 Apr
'21
1:31 a.m.
I would use the RFC space for this still. It's what it is for, using AMPR
space is just wasteful in this case.
On Mon, Apr 5, 2021 at 7:18 PM Jason McCormick via 44Net <
44net(a)mailman.ampr.org> wrote:
To clarify where something is "AMPRNet" vs
"Interent". For example, the
code I was going to post was specifically for handing out 44Net addresses
for an OpenVPN IP pool. It seems confusing and odd to use the RFC5737 to
document something specifically about AMPRNet like that.
-----Original Message-----
From: 44Net <44net-bounces+jason=mfamily.org(a)mailman.ampr.org> On
Behalf Of Alistair Mackenzie via 44Net
Sent: Monday, April 5, 2021 2:15 PM
To: 44Net general discussion <44net(a)mailman.ampr.org>
Cc: Alistair Mackenzie <magicsata(a)gmail.com>
Subject: Re: [44net] IP Ranges for Documentation
Jason,
Is there any reason that you are opposed to using the RFC5737 space? This
seems like exactly the kind of thing the RFC is for.
Thanks,
Alistair
On Mon, Apr 5, 2021 at 7:11 PM Jason McCormick via 44Net <
44net(a)mailman.ampr.org> wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Is there an allocation for documentation similar
to RFC 5737? I was
going to upload some stuff to the GitLab server but I wanted to
generalize it so people didn't just copy/paste deploy stuff with my IP
allocations in it. I looked on the portal but couldn't find anything.
If there isn't, I'd like to propose that two /24s get set aside for
documentation out of 44.0.0.0/9 that don't seem ripe for future use
such as 44.0.192.0/24 and 44.1.255.0/24.
Jason
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net