draft-ietf-roll-unaware-leaves-28.txt   draft-ietf-roll-unaware-leaves-29.txt 
ROLL P. Thubert, Ed. ROLL P. Thubert, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 6550, 6775, 8505 (if approved) M. Richardson Updates: 6550, 6775, 8505 (if approved) M. Richardson
Intended status: Standards Track Sandelman Intended status: Standards Track Sandelman
Expires: 21 June 2021 18 December 2020 Expires: 15 July 2021 11 January 2021
Routing for RPL Leaves Routing for RPL Leaves
draft-ietf-roll-unaware-leaves-28 draft-ietf-roll-unaware-leaves-29
Abstract Abstract
This specification updates RFC6550, RFC6775, and RFC8505. It This specification updates RFC6550, RFC6775, and RFC8505. It
provides a mechanism for a host that implements a routing-agnostic provides a mechanism for a host that implements a routing-agnostic
interface based on 6LoWPAN Neighbor Discovery to obtain reachability interface based on 6LoWPAN Neighbor Discovery to obtain reachability
services across a network that leverages RFC6550 for its routing services across a network that leverages RFC6550 for its routing
operations. operations.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 21 June 2021. This Internet-Draft will expire on 15 July 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
skipping to change at page 27, line 20 skipping to change at page 27, line 20
is redistributing an external target into the RPL network is redistributing an external target into the RPL network
4. The Path Lifetime in the TIO is computed from the Registration 4. The Path Lifetime in the TIO is computed from the Registration
Lifetime in the EARO. This operation converts seconds to the Lifetime in the EARO. This operation converts seconds to the
Lifetime Units used in the RPL operation. This creates the Lifetime Units used in the RPL operation. This creates the
deployment constraint that the Lifetime Unit is reasonably deployment constraint that the Lifetime Unit is reasonably
compatible with the expression of the Registration Lifetime; compatible with the expression of the Registration Lifetime;
e.g., a Lifetime Unit of 0x4000 maps the most significant byte of e.g., a Lifetime Unit of 0x4000 maps the most significant byte of
the Registration Lifetime to the Path Lifetime. the Registration Lifetime to the Path Lifetime.
In that operation, the Path Lifetime must be rounded, if needed, In that operation, the Path Lifetime must be set to ensure that
to the upper value to ensure that the path has a longer lifetime the path has a longer lifetime than the registration and covers
than the registration. in addition the round trip time to the Root.
Note that if the Registration Lifetime is 0, then the Path Note that if the Registration Lifetime is 0, then the Path
Lifetime is also 0 and the DAO message becomes a No-Path DAO, Lifetime is also 0 and the DAO message becomes a No-Path DAO,
which cleans up the routes down to the RUL's address; this also which cleans up the routes down to the RUL's address; this also
causes the Root as a proxy to send an EDAR message to the 6LBR causes the Root as a proxy to send an EDAR message to the 6LBR
with a Lifetime of 0. with a Lifetime of 0.
5. the Path Sequence in the TIO is set to the TID value found in the 5. the Path Sequence in the TIO is set to the TID value found in the
EARO option. EARO option.
skipping to change at page 37, line 39 skipping to change at page 37, line 39
This specification creates a new Subregistry for the RPL Rejection This specification creates a new Subregistry for the RPL Rejection
Status values for use in the RPL DAO-ACK and DCO messages with the Status values for use in the RPL DAO-ACK and DCO messages with the
'A' flag set to 0, under the RPL registry. 'A' flag set to 0, under the RPL registry.
* Possible values are 6-bit unsigned integers (0..63). * Possible values are 6-bit unsigned integers (0..63).
* Registration procedure is "IETF Review" [RFC8126]. * Registration procedure is "IETF Review" [RFC8126].
* Initial allocation is as indicated in Table 5: * Initial allocation is as indicated in Table 5:
+-------+-----------------------+-----------+ +-------+-----------------------+-------------------+
| Value | Meaning | Reference | | Value | Meaning | Reference |
+-------+-----------------------+-----------+ +-------+-----------------------+-------------------+
| 0 | Unqualified rejection | THIS RFC | | 0 | Unqualified rejection | THIS RFC |
+-------+-----------------------+-----------+ +-------+-----------------------+-------------------+
| 1..63 | Unassigned | | | 1 | No routing entry | [EFFICIENT-NPDAO] |
+-------+-----------------------+-----------+ +-------+-----------------------+-------------------+
| 2..63 | Unassigned | |
+-------+-----------------------+-------------------+
Table 5: Rejection values of the RPL Status Table 5: Rejection values of the RPL Status
13. Acknowledgments 13. Acknowledgments
The authors wish to thank Ines Robles, Georgios Papadopoulos and The authors wish to thank Ines Robles, Georgios Papadopoulos and
especially Rahul Jadhav and Alvaro Retana for their reviews and especially Rahul Jadhav and Alvaro Retana for their reviews and
contributions to this document. Also many thanks to Eric Vyncke, contributions to this document. Also many thanks to Eric Vyncke,
Erik Kline, Murray Kucherawy, Peter Van der Stok, Carl Wallace, Barry Erik Kline, Murray Kucherawy, Peter Van der Stok, Carl Wallace, Barry
Leiba, Julien Meuric, and especially Benjamin Kaduk and Elwyn Davies, Leiba, Julien Meuric, and especially Benjamin Kaduk and Elwyn Davies,
skipping to change at page 39, line 38 skipping to change at page 39, line 38
[RFC8928] Thubert, P., Ed., Sarikaya, B., Sethi, M., and R. Struik, [RFC8928] Thubert, P., Ed., Sarikaya, B., Sethi, M., and R. Struik,
"Address-Protected Neighbor Discovery for Low-Power and "Address-Protected Neighbor Discovery for Low-Power and
Lossy Networks", RFC 8928, DOI 10.17487/RFC8928, November Lossy Networks", RFC 8928, DOI 10.17487/RFC8928, November
2020, <https://www.rfc-editor.org/info/rfc8928>. 2020, <https://www.rfc-editor.org/info/rfc8928>.
[USEofRPLinfo] [USEofRPLinfo]
Robles, I., Richardson, M., and P. Thubert, "Using RPI Robles, I., Richardson, M., and P. Thubert, "Using RPI
Option Type, Routing Header for Source Routes and IPv6-in- Option Type, Routing Header for Source Routes and IPv6-in-
IPv6 encapsulation in the RPL Data Plane", Work in IPv6 encapsulation in the RPL Data Plane", Work in
Progress, Internet-Draft, draft-ietf-roll-useofrplinfo-42, Progress, Internet-Draft, draft-ietf-roll-useofrplinfo-43,
12 November 2020, <https://tools.ietf.org/html/draft-ietf- 10 January 2021, <https://tools.ietf.org/html/draft-ietf-
roll-useofrplinfo-42>. roll-useofrplinfo-43>.
[EFFICIENT-NPDAO] [EFFICIENT-NPDAO]
Jadhav, R., Thubert, P., Sahoo, R., and Z. Cao, "Efficient Jadhav, R., Thubert, P., Sahoo, R., and Z. Cao, "Efficient
Route Invalidation", Work in Progress, Internet-Draft, Route Invalidation", Work in Progress, Internet-Draft,
draft-ietf-roll-efficient-npdao-18, 15 April 2020, draft-ietf-roll-efficient-npdao-18, 15 April 2020,
<https://tools.ietf.org/html/draft-ietf-roll-efficient- <https://tools.ietf.org/html/draft-ietf-roll-efficient-
npdao-18>. npdao-18>.
15. Informative References 15. Informative References
 End of changes. 7 change blocks. 
17 lines changed or deleted 19 lines changed or added

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