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

remove camelcase for AutoConfiguration

Browse source
This commit is contained in:
Nick Hilliard 2017-05-13 16:48:06 +01:00
parent 32f624f69c
commit 940d4bfeb9
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -132,7 +132,7 @@ rate is low enough.
<t>To state it simply, IPv6 unicast subnetting is based on prefixes <t>To state it simply, IPv6 unicast subnetting is based on prefixes
of any valid length up to 128 except for links where an Internet of any valid length up to 128 except for links where an Internet
Standard that has nothing to do with routing may impose a Standard that has nothing to do with routing may impose a
particular length. Examples are Stateless Address AutoConfiguration particular length. Examples are Stateless Address Autoconfiguration
(SLAAC) <xref target="RFC4862"/>, or Using 127-Bit IPv6 Prefixes on (SLAAC) <xref target="RFC4862"/>, or Using 127-Bit IPv6 Prefixes on
Inter-Router Links <xref target="RFC6164"/>.</t> Inter-Router Links <xref target="RFC6164"/>.</t>
@ -166,7 +166,7 @@ rate is low enough.
target="RFC7136"/>.</t> target="RFC7136"/>.</t>
<t>The length of the Interface Identifier in Stateless Address <t>The length of the Interface Identifier in Stateless Address
AutoConfiguration <xref target="RFC4862"/> is a parameter; its Autoconfiguration <xref target="RFC4862"/> is a parameter; its
length SHOULD be sufficient for effective randomization for privacy length SHOULD be sufficient for effective randomization for privacy
reasons. For example, a /48 might be sufficient. But operationally reasons. For example, a /48 might be sufficient. But operationally
we recommend, barring strong considerations to the contrary, using we recommend, barring strong considerations to the contrary, using