[bcop] Fwd: [Bcop-gc] documentation ipv6 prefix

Hi

All these are really good points.

> I personally think we must be careful to make documentation examples too
> different from the real world, as people tends to use examples as
> templates in their real network designs. So keeping just the 2001:db8::/32
> for documenting examples for ones own network is more than enough.

I totally agree with this.

> I personally think we must be careful to make documentation examples too
> different from the real world, as people tends to use examples as
> templates in their real network designs. So keeping just the 2001:db8::/32
> for documenting examples for ones own network is more than enough.

Also strongly agree with this.
And I think this is one reason why we see more 3ffe:: and fd00::
usage in documents.

Thanks!

-Seiichi


(2014/08/27 17:54), Anfinsen, Ragnar wrote:
> On 25.08.14 16:21, "Seiichi Kawamura" <kawamucho at mesh.ad.jp> wrote:
> 
> 
>> OK. I joined the list so you don't have to cc me anymore.
>> I noticed on a MyNOG presentation last week that someone
>> was using 2001:db8:: to describe one network and 3fff::
>> to describe another. Not sure if he meant to use 3ffe::
>> but it certainly took me by surprise.
> 
> I personally think we must be careful to make documentation examples too
> different from the real world, as people tends to use examples as
> templates in their real network designs. So keeping just the 2001:db8::/32
> for documenting examples for ones own network is more than enough.
> 
> However, I do see the problem when an example shows connectivity between
> two different resource holders.
> 
> IMHO, I think we should consider finding a method of differentiating
> different network in examples, either by assigning one or more /32
> prefixes documentation prefixes, or allow the 2001:db8::/32 to become
> 2001:db8::/29.
> 
> Changing RFC3849 to reflect the changes done in the RIPE region, where an
> LIR can get a /29 without any further documentation. This will allow for a
> more real world documentation both for large networks and multiple
> networks.
> 
> I.E.
> 
> NET A = 2001:db8::/32
> 	Subnet a = 2001:db8:1::/48
> 	Subnet b = 2001:db8:2::/48
> 	Subnet c = 2001:db8:3::/48
> 
> NET B = 2001:dba::/32
> 	Subnet a = 2001:dba:1::/48
> 	Subnet b = 2001:dba:8000::/48
> 	Subnet c = 2001:dba:a000::/48
> 
> 
> NET C = 2001:dbf::/32
> 	Subnet a = 2001:dba:1::/48
> 	Subnet b = 2001:dba:10::/48
> 	Subnet c = 2001:dba:20::/48
> 
> OR
> 
> NET A = 2001:db8::/29
> 	Subnet a = 2001:db8::/48
> 	Subnet b = 2001:dba::/48
> 	Subnet c = 2001:dbf::/48
> 
> 
> 
> BR
> Ragnar
> 
>