Hi,
What is your plan for when this prefix ends up coming in to use? There will
potentially be networks using this and break reachability elsewhere due to
this.
There is also the fact that people often copy documentation exactly and use
it which can cause problems. This has been seen with CloudFlare[1] and
Cisco's documentation on ERSPAN.
it is not worth the possible problems and clean up operation required by
using a prefix outside of RFC5737. This RFC was created to avoid the issues
that I have mentioned and we should use it as intended wherever possible,
including in AMRP/44net.
[1]
On Mon, Apr 5, 2021 at 7:44 PM G1FEF via 44Net <44net(a)mailman.ampr.org>
wrote:
Hi Jason,
44.128.0.0/16 is reserved for testing and will never be allocated to
anyone, unless we run out of space ;-)
I see no reason why you can’t use addresses from that block.
73,
Chris
On 5 Apr 2021, at 19:19, 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:
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
_________________________________________
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