From 06cb09405ca8effc04a0ceaf6ba961671b3e44e4 Mon Sep 17 00:00:00 2001 From: Nick Hilliard Date: Sun, 14 May 2017 12:27:08 +0100 Subject: [PATCH] refactor formal statement - clarify that there are two cases - interface subnetting is now classless - routing prefixes were always classless, but this is now explicitly stated --- draft-nbourbaki-6man-classless-ipv6.xml | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/draft-nbourbaki-6man-classless-ipv6.xml b/draft-nbourbaki-6man-classless-ipv6.xml index 5cd8c96..92bfd00 100644 --- a/draft-nbourbaki-6man-classless-ipv6.xml +++ b/draft-nbourbaki-6man-classless-ipv6.xml @@ -78,6 +78,9 @@ risk of mis-implementation, which can easily result in serious operational problems. + This document also clarifies that IPv6 routing subnets may be of any + length up to 128. +
@@ -130,20 +133,19 @@ 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 that has nothing to do with routing may impose a - particular length. Examples are Stateless Address Autoconfiguration + IPv6 unicast interfaces may use any subnet length up to 128 except + for situations where an Internet Standard document may impose a + particular length, for example Stateless Address Autoconfiguration (SLAAC) , or Using 127-Bit IPv6 Prefixes on 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 - could choose to differentiate at a different granularity than is - used by any such automated link local address configuration - tools. + Additionally, this document clarifies that a node or router MUST + support routing of any valid network prefix length, even if SLAAC or + other standards are in use, because routing could choose to + differentiate at a different granularity than is used by any such + automated link local address configuration tools.