Geoff Huston wrote:
You are looking for 2001:0DB8::/32
The IANA IPv6 registry
[http://www.iana.org/assignments/ipv6-unicast-address-assignments]
says:
2001:0DB8::/32 has been assigned as a NON-ROUTABLE
range to be used for documentation purpose [RFC3849].
RFC3849 is the reference
"IPv6 Address Prefix Reserved for Documentation", June 2004
Thanks Geoff, that's it.
What I'm looking for now is a 2nd documentation prefix, that would
differ in the first bit. Such that nobody could say that this prefix X
has an aggregation relationship with 2001:db8::/32. Such that I can
picture a Router with two non-hierarchical non-aggregated prefixes on
its two interfaces.
The Router on my paper would not ROUTE anything, it's on paper. But
some deployed Router may ROUTE between two such prefixes differing on
the first bit.
Alex
Geoff
Alexandru Petrescu wrote:
Hi 6MAN,
I remember having seen a draft or a section in a draft/rfc that
suggested a certain value for IPv6 addresses in example architectures
(those used only for explanation purposes, not actually deployed
addresses). Something like this:
------ 3ffe:1:2:1::1/65 ------
|Router|-------------------|Router|
------ ------
Is that document alive existing somewhere? Something along the lines of
section 2.2 Text Representation of Addresses of RFC4291 "IPv6 Addressing
Architecture" which says an example of unicast address is
"2001:DB8::8:800:200C:417A"; but something that indicates which values
exactly to use in a document describing an example (non-deployed)
addressing architecture.
Thanks,
Alex
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
