randy/draft-classless6
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

part of brian's comments

Browse source
This commit is contained in:
Randy Bush 2017-04-03 17:57:53 -07:00
parent 46ef205150
commit 5f7ecf251a
1 changed files with 19 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

23
draft-nbourbaki-6man-classless-ipv6.xml
View file

@ -66,14 +66,22 @@
<section anchor="background" title="Background"> <section anchor="background" title="Background">
<!--
<t>To quote Lorenzo Colitti in the working group meeting at IETF 98, <t>To quote Lorenzo Colitti in the working group meeting at IETF 98,
"Just because this is being elevated to full standard does not mean "Just because this is being elevated to full standard does not mean
it can not be changed tomorrow." Tomorrow is here.</t> it can not be changed tomorrow." Tomorrow is here.</t>
-->
<t>Link prefixes of varied lengths, /127, /126, /124, /120, ... /64 <t>Some confusion has been caused by the IP Version 6 Addressing
have been successfully deployed for many years. Having the formal Architecture, <xref target="RFC4291"/>, and the proposed changes in
specification say otherwise risks potential mis-implementation by <xref target="I-D.hinden-6man-rfc2464bis"/> with respect to allowed
the naive, resulting in operational disasters.</t> maximum prefix lengths and the minimum host part on a link.</t>
<t>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
disasters.</t>
</section> </section>
@ -92,6 +100,13 @@
<t>For historical reasons, when a prefix is needed on a link, <t>For historical reasons, when a prefix is needed on a link,
barring other considerations, a /64 is traditional.</t> barring other considerations, a /64 is traditional.</t>
<t>The length of the prefix identifier in Stateless Address
Configuration, <xref target="RFC4862"/> 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.</t>
</section> </section>
<section anchor="security" title="Security Considerations"> <section anchor="security" title="Security Considerations">