From 4786e3b8bffc08707205388e46ef12d2250cca2e Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Mon, 17 Jul 2017 14:18:13 +0200 Subject: [PATCH] joel, nick, and nbourbaki change --- draft-nbourbaki-6man-classless-ipv6.xml | 184 ++++++------------------ 1 file changed, 46 insertions(+), 138 deletions(-) diff --git a/draft-nbourbaki-6man-classless-ipv6.xml b/draft-nbourbaki-6man-classless-ipv6.xml index 18731b3..7bd70d6 100644 --- a/draft-nbourbaki-6man-classless-ipv6.xml +++ b/draft-nbourbaki-6man-classless-ipv6.xml @@ -16,7 +16,6 @@ IPv6 is Classless - - - - Internet Initiative Japan -
- - 5147 Crystal Springs - Bainbridge Island - Washington - 98110 - US - - randy@psg.com -
- - - - -
- - Department of Computer Science - University of Auckland - PB 92019 - Auckland - - 1142 - New Zealand - - brian.e.carpenter@gmail.com -
- - - - SI6 Networks / UTN-FRH -
- - Evaristo Carriego 2644 - 1706 - Haedo - Provincia de Buenos Aires - Argentina - - +54 11 4650 8472 - fgont@si6networks.com - http://www.si6networks.com -
- - - - INEX -
- - 4027 Kingswood Road - Dublin - 24 - Ireland - - nick@inex.ie -
- - - - -
- gih@apnic.net -
- - - - Google, Inc. -
- - 1600 Ampitheatre Parkway - Mountain View - California - United States of America - - morrowc@google.com -
- - - - NTT Communications -
- - Theodorus Majofskistraat 100 - 1065 SZ - Amsterdam - The Netherlands - - job@ntt.net -
- @@ -221,51 +127,44 @@ rate is low enough. length, previously fixed at 64 bits , is in fact a variably-sized parameter as explicitly acknowledged in Section 5.5.3(d) of which states: - - - Note that a future revision of the address architecture [RFC4291] - and a future link-type-specific document, which will still be - consistent with each other, could potentially allow for an - interface identifier of length other than the value defined in the - current documents. Thus, an implementation should not assume a - particular constant. Rather, it should expect any lengths of - interface identifiers. - - + + Note that a future revision of the address architecture + [RFC4291] and a future link-type-specific document, which will + still be consistent with each other, could potentially allow for + an interface identifier of length other than the value defined in + the current documents. Thus, an implementation should not assume + a particular constant. Rather, it should expect any lengths of + interface identifiers. + - +
- - As IPv6 usage has evolved and grown over in recent years, it has - become evident that it faces several scaling and coordination problems. - These problems are analogous to allocation and coordination problems - that motivated IPv4 CIDR allocation and later abundant IPv4 PAT, they - include: - - - - Address allocation models for specific counts of fixed length subnets - to downstream networks or devices from /48 down to /64 are based - on our imagination of how subnets are or should be allocated within - ipv4 networks. - - - Hierarchical allocation of fixed-length subnets requires coordination - between lower / intermediate / upper network elements and has implict - assumption that policies and size allocation at the top of the hierarchy - will accomidate all use cases with fixed lenth subnet allocation. - - - Coordination with upstream network elements for the allocation of - fixed length subnets reveals topology and intent that may be private - in scope and which amounts to permission to build a particular topology. - - -
+ As IPv6 usage has evolved and grown over in recent years, it has + become evident that it faces several scaling and coordination + problems. These problems are analogous to allocation and coordination + problems that motivated IPv4 CIDR allocation and later abundant IPv4 + PAT, they include: + + Address allocation models for specific counts of fixed length + subnets to downstream networks or devices from /48 down to /64 are + based on our imagination of how subnets are or should be allocated + within ipv4 networks. + Hierarchical allocation of fixed-length subnets requires + coordination between lower / intermediate / upper network elements + and has implict assumption that policies and size allocation at the + top of the hierarchy will accomidate all use cases with fixed lenth + subnet allocation. + Coordination with upstream network elements for the allocation of + fixed length subnets reveals topology and intent that may be private + in scope and which amounts to permission to build a particular + topology. + + + -
+
IPv6 unicast interfaces may use any subnet length up to 128 except for situations where an Internet Standard document may impose a @@ -355,11 +254,20 @@ rate is low enough.
-