Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-update-00.txt

[waldemar <[e-mail]>]

I think I'll record my comment about private networks here. Indeed, 
sometimes it is important to make a point that a network is not globally 
reachable. It helps to have a doc address block making it apparent.

I will also make an off-the-wall suggestion that maybe doc blocks could 
use a non-hex letter in their addresses which will make it easily 
shorter for readability and will guarantee no router will ever forward 
it.  For example a TR00 prefix looks perfect to me. I would also add 
another prefix TN00 for non-global address blocks.


On 11/7/23 04:21, Erik Nygren wrote:
> Should we ask for multiple prefixes while we're doing this?
> Both a small prefix (eg, another /32) in addition to the /20, trying 
> to make sure that there is enough visual difference between them?
> It would be good if neither was in 2001::/16.
> Having a few that are clearly distinct helps with readability of 
> documents talking about distinct entities.
> Similar to the multiple IPv4 documentation prefixes that are visually 
> different, it would be more readable.
> (Some other people made this same comment at the mic while I was 
> writing this.)
>
> Regardless, we should also have a clear statement in the draft that 
> documentation prefixes
> MUST NOT be used for actual traffic , MUST NOT be advertised, and 
> SHOULD NOT be routed?
> (There was a comment in some other thread about ULA with someone 
> talking about using
> 2001:db8::/32 in production rather than ULA because it had higher 
> preference in source address selection.)
>
> Thanks for pulling this together!  I keep wishing there was more than 
> one IPv6 doc prefix.
>
> Erik
>
>
>
> On Mon, Oct 23, 2023 at 10:49 AM <[e-mail]> wrote:
>
>     Internet-Draft draft-ietf-v6ops-rfc3849-update-00.txt is now
>     available. It is
>     a work item of the IPv6 Operations (V6OPS) WG of the IETF.
>
>        Title:   Expanding the IPv6 Documentation Space
>        Authors: Geoff Huston
>                 Nick Buraglio
>        Name:    draft-ietf-v6ops-rfc3849-update-00.txt
>        Pages:   4
>        Dates:   2023-10-20
>
>     Abstract:
>
>        The document describes the reservation of an additional IPv6
>     address
>        prefix for use in documentation.  The reservation of a /20 prefix
>        allows documented examples to reflect a broader range of realistic
>        current deployment scenarios.
>
>     The IETF datatracker status page for this Internet-Draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc3849-update/
>
>     There is also an HTML version available at:
>     https://www.ietf.org/archive/id/draft-ietf-v6ops-rfc3849-update-00.html
>
>     Internet-Drafts are also available by rsync at:
>     rsync.ietf.org::internet-drafts
>
>
>     _______________________________________________
>     I-D-Announce mailing list
>     [e-mail]
>     https://www.ietf.org/mailman/listinfo/i-d-announce
>
>
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops