From cdc1c268fc4b5dd0342f3da74c7c79caf603a3cd Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Sat, 8 Apr 2017 10:07:06 -0700 Subject: [PATCH] spelling and a bit of wording --- draft-nbourbaki-6man-classless-ipv6.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/draft-nbourbaki-6man-classless-ipv6.xml b/draft-nbourbaki-6man-classless-ipv6.xml index a0fa14e..4faa90a 100644 --- a/draft-nbourbaki-6man-classless-ipv6.xml +++ b/draft-nbourbaki-6man-classless-ipv6.xml @@ -20,7 +20,7 @@ The Intertubes
- 42 Rue le Jour + 42 Rue du Jour Sophia-Antipolis ::1 @@ -36,8 +36,8 @@ Over the history of IPv6, there have been many classful address models; TLA and NLA being outstanding examples. They have all been - shown to be mistakes. The last is a magic boundary at /64. This - document removes that last bit of useless magic. + shown to be mistakes. The last remaining is a magic boundary at + /64. This document removes that last bit of useless magic. @@ -49,8 +49,8 @@ Over the history of IPv6, there have been many classful address models; TLA and NLA being outstanding examples. They have all been - shown to be mistakes. The last is a magic boundary at /64. This - document removes that last bit of useless magic. + shown to be mistakes. The last remaining is a magic boundary at + /64. This document removes that last bit of useless magic. @@ -80,7 +80,7 @@ In the meantime, link prefixes of varied lengths, /127, /126, /124, /120, ... /64 have been successfully deployed for many years. Having the formal specification be unclear risks potential - mis-implementation by the naive, which coulf result in operational + mis-implementation by the naive, which could result in operational disasters. @@ -104,8 +104,8 @@ Configuration, is a parameter; its length needs to be sufficient for effective randomization for privacy reasons. For example, a /48 would be sufficient. But we recommend, - barring strong considerations to the contrary, using 64-bits in - order not to discover where 64-bits was hard-coded. + barring strong considerations to the contrary, using 64-bits for + SLAAC in order not to discover where 64-bits was hard-coded.