draft-ietf-v6ops-cpe-slaac-renum-02.txt   draft-ietf-v6ops-cpe-slaac-renum-03.txt 
IPv6 Operations Working Group (v6ops) F. Gont IPv6 Operations Working Group (v6ops) F. Gont
Internet-Draft SI6 Networks Internet-Draft SI6 Networks
Updates: 7084 (if approved) J. Zorz Updates: 7084 (if approved) J. Zorz
Intended status: Informational Go6 Institute Intended status: Informational Go6 Institute
Expires: November 19, 2020 R. Patterson Expires: November 28, 2020 R. Patterson
Sky UK Sky UK
B. Volz B. Volz
Cisco Cisco
May 18, 2020 May 27, 2020
Improving the Reaction of Customer Edge Routers to Renumbering Events Improving the Reaction of Customer Edge Routers to Renumbering Events
draft-ietf-v6ops-cpe-slaac-renum-02 draft-ietf-v6ops-cpe-slaac-renum-03
Abstract Abstract
In scenarios where network configuration information becomes invalid In scenarios where network configuration information becomes invalid
without any explicit signaling of that condition (such as when a without any explicit signaling of that condition (such as when a
Customer Edge Router crashes and reboots without knowledge of the Customer Edge Router crashes and reboots without knowledge of the
previously-employed configuration information), hosts on the local previously-employed configuration information), hosts on the local
network will continue using stale network configuration information network will continue using stale network configuration information
for an unacceptably long period of time, thus resulting in for an unacceptably long period of time, thus resulting in
connectivity problems. This document specifies improvements to connectivity problems. This document specifies improvements to
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 19, 2020. This Internet-Draft will expire on November 28, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Improved Customer Edge Router Behavior . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
2.1. Interface Between WAN-side and LAN-side . . . . . . . . . 3 3. Improved Customer Edge Router Behavior . . . . . . . . . . . 3
2.2. LAN-side Option Lifetimes . . . . . . . . . . . . . . . . 4 3.1. Interface Between WAN-side and LAN-side . . . . . . . . . 4
2.3. Signaling Stale Configuration Information . . . . . . . . 6 3.2. LAN-side Option Lifetimes . . . . . . . . . . . . . . . . 5
3. Recommended Option Lifetimes Configuration Values . . . . . . 8 3.3. Signaling Stale Configuration Information . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. Recommended Option Lifetimes Configuration Values . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
In scenarios where network configuration information becomes invalid In scenarios where network configuration information becomes invalid
without any explicit signaling of that condition, nodes on the local without any explicit signaling of that condition, nodes on the local
network will continue using stale information for an unacceptably network will continue using stale information for an unacceptably
long period of time, thus resulting in connectivity problems. This long period of time, thus resulting in connectivity problems. This
problem is documented in detail in [I-D.ietf-v6ops-slaac-renum]. problem is documented in detail in [I-D.ietf-v6ops-slaac-renum].
This document specifies improvements to Customer Edge (CE) Routers This document specifies improvements to Customer Edge (CE) Routers
that help mitigate the aforementioned problem for residential and that help mitigate the aforementioned problem for residential and
small office scenarios. This document updates RFC7084. small office scenarios. It specifies recommendations for the default
behavior of CE Routers, and does not preclude the availability of
configuration knobs that might allow an operator or user to manually-
configure the CE Router to deviate from these recommendations. This
document updates RFC7084.
2. Improved Customer Edge Router Behavior 2. Requirements Language
Take careful note: Unlike other IETF documents, the key words "MUST",
"MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are not used as
described in [RFC2119]. This document uses these keywords not
strictly for the purpose of interoperability, but rather for the
purpose of establishing industry-common baseline functionality. As
such, the document points to several other specifications (preferable
in RFC or stable form) to provide additional guidance to implementers
regarding any protocol implementation required to produce a
successful CE router that interoperates successfully with a
particular subset of currently deploying and planned common IPv6
access networks.
Note: the aforementioned terms are used in exactly the same way as in
[RFC7084], with the above explanation copied verbatim from
Section 1.1 of [RFC7084].
3. Improved Customer Edge Router Behavior
This section specifies and clarifies requirements for Customer Edge This section specifies and clarifies requirements for Customer Edge
Routers that can help mitigate the problem discussed in Section 1, Routers that can help mitigate the problem discussed in Section 1,
particularly when they employ prefixes learned via DHCPv6-Prefix particularly when they employ prefixes learned via DHCPv6-Prefix
Delegation (DHCPv6-PD) [RFC8415] on the WAN-side with Stateless Delegation (DHCPv6-PD) [RFC8415] on the WAN-side with Stateless
Address Autoconfiguration (SLAAC) [RFC4862] or DHCPv6 [RFC8415] on Address Autoconfiguration (SLAAC) [RFC4862] or DHCPv6 [RFC8415] on
the LAN-side. The recommendations in this document help improve the LAN-side. The recommendations in this document help improve
robustness at the Customer Edge Router (on which the user or ISP may robustness at the Customer Edge Router (on which the user or ISP may
have no control), and do not preclude implementation of host-side have no control), and do not preclude implementation of host-side
improvements such as those specified in [I-D.gont-6man-slaac-renum]. improvements such as those specified in [I-D.gont-6man-slaac-renum].
This document specifies additional LAN-side requirements to This document specifies additional LAN-side requirements to
requirements L-1 through L-14 specified in [RFC7084]: requirements L-1 through L-14 specified in [RFC7084]:
o L-15: CE routers MUST NOT advertise prefixes via SLAAC or assign o L-15: CE routers MUST NOT advertise prefixes via SLAAC or assign
addresses or delegate prefixes via DHCPv6 on the LAN-side, addresses or delegate prefixes via DHCPv6 on the LAN-side,
employing lifetimes that exceed the remaining lifetimes of the employing lifetimes that exceed the remaining lifetimes of the
corresponding prefixes learned from the WAN-side via DHCPv6-PD. corresponding prefixes learned from the WAN-side via DHCPv6-PD.
For more details, see Section 2.1. For more details, see Section 3.1.
o L-16: CE routers SHOULD advertise capped SLAAC option lifetimes o L-16: CE routers SHOULD advertise capped SLAAC option lifetimes
and capped DHCPv6 IA Address Option and IA Prefix Option and capped DHCPv6 IA Address Option and IA Prefix Option
lifetimes, as specified in Section 2.2. lifetimes, as specified in Section 3.2.
o L-17: CE routers MUST signal stale configuration information as o L-17: CE routers MUST signal stale configuration information as
specified in Section 2.3. specified in Section 3.3.
o L-18: CE routers SHOULD NOT automatically send DHCPv6-PD RELEASE o L-18: CE routers SHOULD NOT automatically send DHCPv6-PD RELEASE
messages upon reboot events. messages upon reboot events.
2.1. Interface Between WAN-side and LAN-side 3.1. Interface Between WAN-side and LAN-side
The "Preferred Lifetime" and "Valid Lifetime" of Prefix Information The "Preferred Lifetime" and "Valid Lifetime" of Prefix Information
Options (PIOs) [RFC4861] corresponding to prefixes learned via Options (PIOs) [RFC4861] corresponding to prefixes learned via
DHCPv6-PD MUST NOT span past the remaining preferred and valid DHCPv6-PD MUST NOT span past the remaining preferred and valid
lifetimes of the corresponding DHCPv6-PD prefixes. This means that lifetimes of the corresponding DHCPv6-PD prefixes. This means that
the advertised "Preferred Lifetime" and "Valid Lifetime" MUST be the advertised "Preferred Lifetime" and "Valid Lifetime" MUST be
dynamically adjusted such that they never span past the remaining dynamically adjusted such that they never span past the remaining
preferred and valid lifetimes of the corresponding prefixes delegated preferred and valid lifetimes of the corresponding prefixes delegated
via DHCPv6-PD on the WAN-side. via DHCPv6-PD on the WAN-side.
skipping to change at page 4, line 39 skipping to change at page 5, line 14
* The lifetime values of prefixes advertised on the LAN-side via * The lifetime values of prefixes advertised on the LAN-side via
SLAAC must be dynamically updated (rather than static values), SLAAC must be dynamically updated (rather than static values),
since otherwise the advertised lifetimes would eventually span since otherwise the advertised lifetimes would eventually span
past the DHCPv6-PD lifetimes. past the DHCPv6-PD lifetimes.
* The same considerations apply for the valid-lifetime and * The same considerations apply for the valid-lifetime and
preferred-lifetime of IA Address Options and IA Prefix Options preferred-lifetime of IA Address Options and IA Prefix Options
employed with DHCPv6 on the LAN-side. employed with DHCPv6 on the LAN-side.
2.2. LAN-side Option Lifetimes 3.2. LAN-side Option Lifetimes
CE Routers SHOULD override the default PIO "Preferred Lifetime" and CE Routers SHOULD override the default PIO "Preferred Lifetime" and
"Valid Lifetime" values from [RFC4861], and employ shorter lifetime "Valid Lifetime" values from [RFC4861], and employ shorter lifetime
values to improve the robustness to renumbering events, while values to improve the robustness to renumbering events, while
complying with the requirements from Section 2.1 of this document and complying with the requirements from Section 2.1 of this document and
the recommendations in [RFC7772]. the recommendations in [RFC7772].
This document RECOMMENDS that CE router set the Router Lifetime to This document RECOMMENDS that CE router set the Router Lifetime to
ND_PREFERRED_LIMIT. This document also RECOMMENDS that the CE router ND_PREFERRED_LIMIT. This document also RECOMMENDS that the CE router
set the PIO Preferred Lifetime to the lesser of the remaining set the PIO Preferred Lifetime to the lesser of the remaining
preferred lifetime (see Section 2.1) and ND_PREFERRED_LIMIT, and the preferred lifetime (see Section 3.1) and ND_PREFERRED_LIMIT, and the
PIO Valid Lifetime to the lesser of the remaining valid lifetime and PIO Valid Lifetime to the lesser of the remaining valid lifetime and
ND_VALID_LIMIT. Additionally, this document RECOMMENDS that the ND_VALID_LIMIT. Additionally, this document RECOMMENDS that the
Route Lifetime of Route Information Options (RIOs) [RFC4191], the Route Lifetime of Route Information Options (RIOs) [RFC4191], the
Lifetime of Recursive DNS Search Options (RDNSSO) [RFC8106], and the Lifetime of Recursive DNS Search Options (RDNSSO) [RFC8106], and the
Lifetime of DNS Search List Options (DNSSLO) [RFC8106] be set to the Lifetime of DNS Search List Options (DNSSLO) [RFC8106] be set to the
lesser of the longest valid-lifetime in a DHCPv6 IA Prefix Option lesser of the longest valid-lifetime in a DHCPv6 IA Prefix Option
(received via DHCPv6 on the WAN-side) and ND_VALID_LIMIT, if any of (received via DHCPv6 on the WAN-side) and ND_VALID_LIMIT, if any of
these options are included in Router Advertisement messages. these options are included in Router Advertisement messages.
This document RECOMMENDS that a CE Router providing stateful address This document RECOMMENDS that a CE Router providing stateful address
configuration via DHCPv6 set the DHCPv6 IA Address Option preferred- configuration via DHCPv6 set the DHCPv6 IA Address Option preferred-
lifetime to the lesser of the remaining preferred lifetime (see lifetime to the lesser of the remaining preferred lifetime (see
Section 2.1) and ND_PREFERRED_LIMIT, and the valid-lifetime of the Section 3.1) and ND_PREFERRED_LIMIT, and the valid-lifetime of the
same option to the lesser of the remaining valid lifetime and same option to the lesser of the remaining valid lifetime and
ND_VALID_LIMIT. ND_VALID_LIMIT.
This document RECOMMENDS that a CE Router providing DHCPv6-PD on the This document RECOMMENDS that a CE Router providing DHCPv6-PD on the
LAN-side set the DHCPv6 IA Prefix Option preferred-lifetime to the LAN-side set the DHCPv6 IA Prefix Option preferred-lifetime to the
lesser of the remaining preferred lifetime (see Section 2.1) and lesser of the remaining preferred lifetime (see Section 3.1) and
ND_PREFERRED_LIMIT, and the valid-lifetime of the same option to the ND_PREFERRED_LIMIT, and the valid-lifetime of the same option to the
lesser of the remaining valid lifetime and ND_VALID_LIMIT. lesser of the remaining valid lifetime and ND_VALID_LIMIT.
RATIONALE: RATIONALE:
* The Valid Lifetime and Preferred Lifetime of PIOs have direct * The Valid Lifetime and Preferred Lifetime of PIOs have direct
impact on three different aspects: impact on three different aspects:
+ The amount of time hosts may end up employing stale network + The amount of time hosts may end up employing stale network
configuration information (see configuration information (see
skipping to change at page 6, line 12 skipping to change at page 6, line 36
same effective lifetimes as specified by the WAN-side DHCPv6-PD same effective lifetimes as specified by the WAN-side DHCPv6-PD
lifetimes. lifetimes.
* Similarly, CE Routers need not employ the (possibly long) * Similarly, CE Routers need not employ the (possibly long)
DHCPv6-PD lifetimes for the valid-lifetime and preferred- DHCPv6-PD lifetimes for the valid-lifetime and preferred-
lifetime of IA Address Options and IA Prefix Option employed by lifetime of IA Address Options and IA Prefix Option employed by
DHCPv6 on the LAN-side, since the renewal of bindings by DHCPv6 DHCPv6 on the LAN-side, since the renewal of bindings by DHCPv6
clients will lead to the same effective lifetimes as specified clients will lead to the same effective lifetimes as specified
by the WAN-side DHCPv6-PD lifetimes. by the WAN-side DHCPv6-PD lifetimes.
2.3. Signaling Stale Configuration Information 3.3. Signaling Stale Configuration Information
In order to phase-out stale SLAAC configuration information: In order to phase-out stale SLAAC configuration information:
o A CE router sending RAs that advertise dynamically-learned o A CE router sending RAs that advertise dynamically-learned
prefixes (e.g. via DHCPv6-PD) SHOULD record, on stable storage, prefixes (e.g. via DHCPv6-PD) SHOULD record, on stable storage,
the list of prefixes being advertised on each network segment, and the list of prefixes being advertised on each network segment, and
the state of the "A" and "L" flags of the corresponding PIOs. the state of the "A" and "L" flags of the corresponding PIOs.
o Upon changes to the advertised prefixes, and after bootstrapping, o Upon changes to the advertised prefixes, and after bootstrapping,
the CE router advertising prefix information via SLAAC SHOULD the CE router advertising prefix information via SLAAC SHOULD
proceed as follows: proceed as follows:
* Any prefixes that were previously advertised via Router * Any prefixes that were previously advertised via Router
Advertisement (RA) messages, but that have now become stale, Advertisement (RA) messages, but that have now become stale,
MUST be advertised with a "Valid Lifetime" and a "Preferred MUST be advertised with a "Valid Lifetime" and a "Preferred
Lifetime" set to 0, and the "A" and "L" bits unchanged. Lifetime" set to 0, and the "A" and "L" bits unchanged.
* The aforementioned advertisement SHOULD be performed for at * The aforementioned advertisement SHOULD be performed for at
least the "Valid Lifetime" previously employed for such prefix. least the "Valid Lifetime" previously employed for such prefix.
Note: If requirement L-16 (Section 2.2) is followed, the Valid Note: If requirement L-16 (Section 3.2) is followed, the Valid
Lifetime need not be saved and the prefix can simply be Lifetime need not be saved and the prefix can simply be
advertised for a period of ND_VALID_LIMIT. advertised for a period of ND_VALID_LIMIT.
o CE Routers receiving DHCPv6 Prefix Delegations with a 0 valid- o CE Routers receiving DHCPv6 Prefix Delegations with a 0 valid-
lifetime MUST advertise the corresponding sub-prefixes (as they lifetime MUST advertise the corresponding sub-prefixes (as they
would be generated for the same leased prefix with a non-zero would be generated for the same leased prefix with a non-zero
lifetime) with a PIO with both the Preferred Lifetime and the lifetime) with a PIO with both the Preferred Lifetime and the
Valid Lifetime set to 0, for at least the WAN-side DHCPv6-PD Valid Lifetime set to 0, for at least the WAN-side DHCPv6-PD
valid-lifetime, or for period of ND_VALID_LIMIT if the recommended valid-lifetime, or for period of ND_VALID_LIMIT if the recommended
lifetimes from Section 2.2 are employed. lifetimes from Section 3.2 are employed.
This document RECOMMENDS that if a CE Router provides LAN-side DHCPv6 This document RECOMMENDS that if a CE Router provides LAN-side DHCPv6
(address assignment or prefix delegation), the following behavior be (address assignment or prefix delegation), the following behavior be
implemented: implemented:
o The CE Router SHOULD record, on stable storage, the DHCPv6 address o The CE Router SHOULD record, on stable storage, the DHCPv6 address
and delegated-prefix bindings corresponding to the LAN-side. and delegated-prefix bindings corresponding to the LAN-side.
o If the CE Router finds that the prefix to be employed for address o If the CE Router finds that the prefix to be employed for address
assignment and/or prefix delegation has changed (e.g., upon a assignment and/or prefix delegation has changed (e.g., upon a
crash-and-reboot event) or the CE Router receives DHCPv6 Prefix crash-and-reboot event) or the CE Router receives DHCPv6 Prefix
Delegations with 0 lifetimes, the CE Router MUST: Delegations with 0 lifetimes, the CE Router MUST:
* In Replies to DHCPv6 Request, Renew, Rebind messages, send 0 * In Replies to DHCPv6 Request, Renew, Rebind messages, send 0
lifetimes for any address assignments or prefix delegations for lifetimes for any address assignments or prefix delegations for
the deprecated prefixes for at least the valid-lifetime the deprecated prefixes for at least the valid-lifetime
previously employed for them, or for a period of ND_VALID_LIMIT previously employed for them, or for a period of ND_VALID_LIMIT
if the recommended lifetimes from Section 2.2 are employed. if the recommended lifetimes from Section 3.2 are employed.
* Initiate sending Reconfigure messages (if possible - i.e., * Initiate sending Reconfigure messages (if possible - i.e.,
client requests Reconfigure support and the CE Router offers client requests Reconfigure support and the CE Router offers
it) to the those clients with address assignments or prefix it) to the those clients with address assignments or prefix
delegations for the deprecated prefixes. delegations for the deprecated prefixes.
RATIONALE: RATIONALE:
* IPv6 network renumbering is expected to take place in a planned * IPv6 network renumbering is expected to take place in a planned
manner, with old/stale prefixes being phased-out via reduced manner, with old/stale prefixes being phased-out via reduced
skipping to change at page 8, line 9 skipping to change at page 8, line 30
* The requirement in this section is conveyed as a "SHOULD" (as * The requirement in this section is conveyed as a "SHOULD" (as
opposed to a "MUST"), since we acknowledge that the requirement opposed to a "MUST"), since we acknowledge that the requirement
to store information on stable storage may represent a to store information on stable storage may represent a
challenge for some implementations. challenge for some implementations.
* Advertising DHCPv6-leased prefixes with zero lifetimes on the * Advertising DHCPv6-leased prefixes with zero lifetimes on the
LAN-side would handle the case where a CE Router has no stable LAN-side would handle the case where a CE Router has no stable
storage but receives the prefixes via DHCPv6 with 0 lifetimes. storage but receives the prefixes via DHCPv6 with 0 lifetimes.
3. Recommended Option Lifetimes Configuration Values 4. Recommended Option Lifetimes Configuration Values
o ND_PREFERRED_LIMIT: 2700 seconds (45 minutes) o ND_PREFERRED_LIMIT: 2700 seconds (45 minutes)
o ND_VALID_LIMIT: 5400 seconds (90 minutes) o ND_VALID_LIMIT: 5400 seconds (90 minutes)
4. IANA Considerations 5. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
5. Security Considerations 6. Security Considerations
This document discusses a problem that may arise in scenarios where This document discusses a problem that may arise in scenarios where
dynamic IPv6 prefixes are employed, and proposes improvements to dynamic IPv6 prefixes are employed, and proposes improvements to
Customer Edge Routers [RFC7084] to mitigate the problem for Customer Edge Routers [RFC7084] to mitigate the problem for
residential or small office scenarios. It does not introduce new residential or small office scenarios. It does not introduce new
security issues. security issues.
6. Acknowledgments 7. Acknowledgments
The authors would like to thank Owen DeLong, Philip Homburg, and Ted The authors would like to thank Owen DeLong, Philip Homburg, and Ted
Lemon, for their valuable help in improving this document via Lemon, for their valuable help in improving this document via
successive detailed reviews. successive detailed reviews.
The authors would like to thank Mikael Abrahamsson, Brian Carpenter, The authors would like to thank Mikael Abrahamsson, Brian Carpenter,
Lorenzo Colitti, Alejandro D'Egidio, Fernando Frediani, Erik Kline, Lorenzo Colitti, Alejandro D'Egidio, Fernando Frediani, Erik Kline,
Olorunloba Olopade, Mark Smith, Job Snijders, Sander Steffann, Ole Olorunloba Olopade, Mark Smith, Job Snijders, Sander Steffann, Ole
Troan, Loganaden Velvindron, Timothy Winters, and Chongfeng Xie, for Troan, Loganaden Velvindron, Timothy Winters, and Chongfeng Xie, for
providing valuable comments on earlier versions of this document. providing valuable comments on earlier versions of this document.
skipping to change at page 9, line 5 skipping to change at page 9, line 23
Hilliard, Philip Homburg, Lee Howard, Christian Huitema, Ted Lemon, Hilliard, Philip Homburg, Lee Howard, Christian Huitema, Ted Lemon,
Albert Manfredi, Jordi Palet Martinez, Richard Patterson, Michael Albert Manfredi, Jordi Palet Martinez, Richard Patterson, Michael
Richardson, Mark Smith, Job Snijders, Tarko Tikan, and Ole Troan, for Richardson, Mark Smith, Job Snijders, Tarko Tikan, and Ole Troan, for
providing valuable comments on [I-D.gont-6man-slaac-renum], on which providing valuable comments on [I-D.gont-6man-slaac-renum], on which
this document is based. this document is based.
Fernando would also like to thank Brian Carpenter who, over the Fernando would also like to thank Brian Carpenter who, over the
years, has answered many questions and provided valuable comments years, has answered many questions and provided valuable comments
that has benefited his protocol-related work. that has benefited his protocol-related work.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and
More-Specific Routes", RFC 4191, DOI 10.17487/RFC4191, More-Specific Routes", RFC 4191, DOI 10.17487/RFC4191,
November 2005, <https://www.rfc-editor.org/info/rfc4191>. November 2005, <https://www.rfc-editor.org/info/rfc4191>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
DOI 10.17487/RFC4861, September 2007, DOI 10.17487/RFC4861, September 2007,
<https://www.rfc-editor.org/info/rfc4861>. <https://www.rfc-editor.org/info/rfc4861>.
skipping to change at page 9, line 39 skipping to change at page 10, line 16
"IPv6 Router Advertisement Options for DNS Configuration", "IPv6 Router Advertisement Options for DNS Configuration",
RFC 8106, DOI 10.17487/RFC8106, March 2017, RFC 8106, DOI 10.17487/RFC8106, March 2017,
<https://www.rfc-editor.org/info/rfc8106>. <https://www.rfc-editor.org/info/rfc8106>.
[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A., [RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
Richardson, M., Jiang, S., Lemon, T., and T. Winters, Richardson, M., Jiang, S., Lemon, T., and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 8415, DOI 10.17487/RFC8415, November 2018, RFC 8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>. <https://www.rfc-editor.org/info/rfc8415>.
7.2. Informative References 8.2. Informative References
[I-D.gont-6man-slaac-renum] [I-D.gont-6man-slaac-renum]
Gont, F., Zorz, J., and R. Patterson, "Improving the Gont, F., Zorz, J., and R. Patterson, "Improving the
Robustness of Stateless Address Autoconfiguration (SLAAC) Robustness of Stateless Address Autoconfiguration (SLAAC)
to Flash Renumbering Events", draft-gont-6man-slaac- to Flash Renumbering Events", draft-gont-6man-slaac-
renum-07 (work in progress), April 2020. renum-08 (work in progress), May 2020.
[I-D.ietf-v6ops-slaac-renum] [I-D.ietf-v6ops-slaac-renum]
Gont, F., Zorz, J., and R. Patterson, "Reaction of Gont, F., Zorz, J., and R. Patterson, "Reaction of
Stateless Address Autoconfiguration (SLAAC) to Flash- Stateless Address Autoconfiguration (SLAAC) to Flash-
Renumbering Events", draft-ietf-v6ops-slaac-renum-02 (work Renumbering Events", draft-ietf-v6ops-slaac-renum-02 (work
in progress), May 2020. in progress), May 2020.
[RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic [RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic
Requirements for IPv6 Customer Edge Routers", RFC 7084, Requirements for IPv6 Customer Edge Routers", RFC 7084,
DOI 10.17487/RFC7084, November 2013, DOI 10.17487/RFC7084, November 2013,
 End of changes. 27 change blocks. 
37 lines changed or deleted 66 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/