5 Apr
2021
5 Apr
'21
2:20 p.m.
I'd use the actual RFC5737 address space and make the assumption that the
reader has enough intelligence to replace those with their own allocation
after they realize the defaults don't work because they skipped that step.
On Mon, Apr 5, 2021, 13:16 Alistair Mackenzie via 44Net <
44net(a)mailman.ampr.org> wrote:
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:
--
The content of this email is confidential and intended for the
recipient
specified in message only. It is strictly forbidden to share
any part of
this message with any third party, without a written consent
of the
sender. If you received this message by mistake, please reply to
this
message and follow with its deletion, so that we can ensure such a
mistake
does not occur in the future.
Please do not print this email unless it is
necessary. Every unprinted email helps the environment.
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