From 28578623cf77ab84ea4ba76415cf40e2e41a68b8 Mon Sep 17 00:00:00 2001 From: becarpenter Date: Wed, 10 May 2017 17:04:38 +1200 Subject: [PATCH] minor suggestions, updated a reference --- draft-nbourbaki-6man-classless-ipv6.xml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/draft-nbourbaki-6man-classless-ipv6.xml b/draft-nbourbaki-6man-classless-ipv6.xml index 2e21b36..b64d47c 100644 --- a/draft-nbourbaki-6man-classless-ipv6.xml +++ b/draft-nbourbaki-6man-classless-ipv6.xml @@ -1,4 +1,4 @@ - + @@ -77,7 +77,7 @@ Some confusion has been caused by the IP Version 6 Addressing Architecture, , and the proposed changes in - with respect to the + with respect to the minimum subnet size. Meanwhile, link prefixes of varied lengths, /127, /126, /124, @@ -100,7 +100,8 @@ It is also assumed that the reader understands IPv6 , the IP Version 6 Addressing Architecture , the proposed changes to RFC4291 , and the recent + target="I-D.ietf-6man-rfc4291bis"/> and RFC2464 + , and the recent recommendations for the generation of stable Interface Identifiers . @@ -132,9 +133,10 @@ rate is low enough. To state it simply, IPv6 unicast subnetting is based on prefixes of any valid length up to 128 except for links where an Internet - Standard such as, for example, Stateless Address AutoConfiguration + Standard that has nothing to do with routing may impose a + particular length. Examples are Stateless Address AutoConfiguration (SLAAC) , or Using 127-Bit IPv6 Prefixes on - Inter-Router Links is in use. + Inter-Router Links . Nodes must always support routing on any valid network prefix length, even if SLAAC or other standards are in use, because routing @@ -252,7 +254,8 @@ rate is low enough. - + +