[ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marc Blanchet
marc.blanchet at viagenie.ca
Tue Jul 19 14:30:09 CEST 2011
Le 11-07-19 08:17, Jan Zorz @ go6.si a écrit : > On 7/19/11 1:44 PM, Ahmed Abu-Abed wrote: >> I am not proposing a change with respect to existing RFCs; we must to >> live with existing /64 subnets as a minimum allocation. >> >> My comments apply for future networks beyond the current 2000::/3 range >> used by all RIRs. Beyond this range all options are still open. > > I don't think so. IPv6 as protocol applies over all ::/0, not only 2000::/3 > > Why do you think ND and SLAAC would behave differently in 4000::/3 ? > I think Ahmed is referring to: <RFC4291> Future specifications may redefine one or more sub-ranges of the Global Unicast space for other purposes, but unless and until that happens, implementations must treat all addresses that do not start with any of the above-listed prefixes as Global Unicast addresses. </RFC4291> > Cheers, Jan -- ========= IETF81 Quebec city: http://ietf81.ca IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca DTN Implementation: http://postellation.viagenie.ca NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca Space Assigned Number Authority: http://sanaregistry.org
- Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]