drop 2119 language
This commit is contained in:
parent
e8b242134c
commit
b230b3b452
1 changed files with 8 additions and 2 deletions
|
|
@ -43,6 +43,8 @@
|
|||
|
||||
</abstract>
|
||||
|
||||
<!--
|
||||
|
||||
<note title="Requirements Language">
|
||||
|
||||
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
|
||||
|
|
@ -54,6 +56,8 @@
|
|||
|
||||
</note>
|
||||
|
||||
-->
|
||||
|
||||
</front>
|
||||
|
||||
<middle>
|
||||
|
|
@ -156,14 +160,14 @@ rate is low enough.
|
|||
<section anchor="notes" title="Recommendations">
|
||||
|
||||
<t>For historical reasons, when a prefix is needed on a link,
|
||||
barring other considerations, a /64 is RECOMMENDED <xref
|
||||
barring other considerations, a /64 is recommended <xref
|
||||
target="RFC7136"/>.</t>
|
||||
|
||||
<t>The length of the Interface Identifier in Stateless Address
|
||||
AutoConfiguration <xref target="RFC4862"/> is a parameter; its
|
||||
length SHOULD be sufficient for effective randomization for privacy
|
||||
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
|
||||
64-bits for SLAAC in order not to discover bugs where 64 was
|
||||
hard-coded, and to favor portability of devices and operating
|
||||
systems.</t>
|
||||
|
|
@ -230,7 +234,9 @@ rate is low enough.
|
|||
<back>
|
||||
|
||||
<references title="Normative References">
|
||||
<!--
|
||||
<?rfc include="reference.RFC.2119"?>
|
||||
-->
|
||||
<?rfc include="reference.RFC.2450"?>
|
||||
<?rfc include="reference.RFC.2460"?>
|
||||
<?rfc include="reference.RFC.4291"?>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue