Configuration option for RFC 8138
draft-ietf-roll-turnon-rfc8138-04
ROLL P. Thubert, Ed.
Internet-Draft L. Zhao
Updates: 6550, 8138 (if approved) Cisco Systems
Intended status: Standards Track 24 January 2020
Expires: 27 July 2020
Configuration option for RFC 8138
draft-ietf-roll-turnon-rfc8138-04
Abstract
This document complements RFC 8138 and dedicates a bit in the RPL
configuration option defined in RFC 6550 to indicate whether RFC 8138
compression is used within the RPL Instance.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 27 July 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Thubert & Zhao Expires 27 July 2020 [Page 1]
Internet-Draft Enabling RFC 8138 January 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . . 3
4. Updating RFC 8138 . . . . . . . . . . . . . . . . . . . . . . 3
5. Transition Scenarios . . . . . . . . . . . . . . . . . . . . 4
5.1. Inconsistent State While Migrating . . . . . . . . . . . 5
5.2. Single RPL Instance Scenario . . . . . . . . . . . . . . 5
5.3. Double RPL Instances Scenario . . . . . . . . . . . . . . 6
5.4. Rolling Back . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
9. Normative References . . . . . . . . . . . . . . . . . . . . 7
10. Informative References . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The transition of a RPL [RFC6550] network to activate the compression
defined in [RFC8138] can only be done when all routers in the network
support it. A non-capable node acting as a router would drop the
compressed packets and black-hole its subDAG. In a mixed case with
both RFC8138-capable and non-capable nodes, the compression may be
turned on only if all the non-capable nodes act as leaves and their
RPL parents handle the compression/decompression on their behalf.
This document complements RFC 8138 and dedicates a flag in the RPL
configuration option to indicate whether RFC 8138 compression should
be used within the RPL Instance. The setting of new flag is
controlled by the Root and propagates as is in the whole network.
When the bit is not set, source nodes that support RFC 8138 should
refrain from using the compression unless the information is
superseded by configuration.
This specification provides scenarios that force a legacy node to
become a RPL-Aware-Leaf (RAL). In that case, the 6LR must be aware
by means out of scope that it must uncompress the packets before
delivering to the RAL.
2. BCP 14
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119][RFC8174] when, and only when, they appear in all
capitals, as shown here.
Thubert & Zhao Expires 27 July 2020 [Page 2]
Internet-Draft Enabling RFC 8138 January 2020
3. Updating RFC 6550
This specification defines a new flag "Enable RFC8138 Compression"
Show full document text