Hi, Jan and all,<br><br>As RFC3849 specified, the prefix reserved for documentation is a /32 <!-- begin sanitized html -->
block, <br> 2001:DB8::/32<br>while people can use the following:<br> net A = 2001:db8:1::/48<br> net B = 2001:db8:2::/48<br> net C = 2001:db8:3::/48
<br><div id="signEditor"></div>we can also use <br> net A = 2001:db8:1::/48<br> net B = 2001:db8:8000::/48<br> net C = 2001:db8:a000::/48
<br>for being easy recognized as separated networks.<br>The only shortcoming that I can think of is, because 2001:db8::/32 is one big block, when being used to describe<br>inter-domain network topology, /32 address block may easily be considered as all networks belong to one organization.<br>Any comment?<br><br>I also cc:ed this email to the co-author of RFC3849, G.Huston, Chief Scientist from APNIC, for further discussion.<br><br>Best regards,<br>--MA Yan<br><br><div style="FONT: 9pt ">----- reply email -----<div style="BACKGROUND: #e4e4e4; font-color: black"><b>Sender:</b>Jan Zorz @ go6.si <jan@go6.si></div><div><b>Recipient:</b>bcop <bcop@ripe.net></div><div><b>Time:</b>08/21/2014 22:11:55</div><div><b>Subject:</b>[bcop] Fwd: [Bcop-gc] documentation ipv6 prefix</div></div><br><blockquote style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0mm; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0mm; MARGIN: 5pt 0mm 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0mm; BORDER-BOTTOM: medium none"><div class="bodyclass"><br>
Dear RIPE BCOP community,<br>
<br>
I got a question from Seiichi Kawamura, JANOG BCOP co-chair and I think <br>
this suggestion/question would be best if discussed here on this mailing <br>
list (and maybe also on IPv6 WG ml).<br>
<br>
Please read below.<br>
<br>
Cheers, Jan<br>
<br>
-------- Original Message --------<br>
Date: Tue, 19 Aug 2014 10:04:56 +0900<br>
From: Seiichi Kawamura <kawamucho@mesh.ad.jp><br>
<br>
Fellow BCOPers<br>
<br>
Hi there.<br>
Some folks in Japan, especially tech<br>
bloggers and tech documentation producers<br>
are saying that we need more ipv6 documentation<br>
prefix than just 2001:db8::/32<br>
<br>
When describing a classic 3 prefix<br>
network topology they would use<br>
<br>
net A = 2001:db8:1::/48<br>
net B = 2001:db8:2::/48<br>
net C = 2001:db8:3::/48<br>
<br>
where as with v4,<br>
<br>
net A = 192.0.2.0/24<br>
net B = 198.51.100.0/24<br>
net C = 203.0.113.0/24<br>
<br>
The 3 IPv6 prefixes are too similar and it's<br>
intuitively hard to tell if the 3 prefixes are<br>
talking about a network, or is it 3 separate networks.<br>
I guess this is bad especially for educational<br>
tutorial documentation.<br>
<br>
So I'm thinking that if there are 2 more prefixes<br>
defined as documentation, I would say that's enough.<br>
We can maybe even revive 3ffe:: and make that documentation purpose.<br>
<br>
However, I'm intersted in hearing opinions from other regions.<br>
Do you think there are any such needs in your region?<br>
<br>
-Seiichi<br>
<br>
_______________________________________________<br>
Bcop-gc mailing list<br>
Bcop-gc@elists.isoc.org<br>
https://elists.isoc.org/mailman/listinfo/bcop-gc<br>
<br>
<br>
<br>
</div></blockquote>
<!-- end sanitized html -->