Configuration option for RFC 8138
draft-ietf-roll-turnon-rfc8138-03
ROLL P. Thubert, Ed.
Internet-Draft L. Zhao
Updates: 6550, 8138 (if approved) Cisco Systems
Intended status: Standards Track 22 January 2020
Expires: 25 July 2020
Configuration option for RFC 8138
draft-ietf-roll-turnon-rfc8138-03
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 25 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 25 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 . . . . . . . . . . . . . . . . . . . . . . 2
4. Updating RFC 8138 . . . . . . . . . . . . . . . . . . . . . . 3
5. Transition Scenarios . . . . . . . . . . . . . . . . . . . . 3
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 to [RFC8138] in a network can only be done when all
nodes support the specification. In a mixed case with both
RFC8138-capable and non-capable nodes, the compression should be
turned off.
This document complements RFC 8138 and dedicates a bit in the RPL
configuration option to indicate whether RFC 8138 compression should
be used within the RPL Instance. 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.
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.
3. Updating RFC 6550
RPL defines a configuration option that is registered to IANA in
section 20.14. of [RFC6550]. This specification defines a new flag
"Enable RFC8138 Compression" (T) that is encoded in one of the
reserved control bits in the option. The new flag is set to turn on
the use of the compression of RPL artifacts with RFC 8138. The bit
position of the "T" flag is indicated in Section 6.
Thubert & Zhao Expires 25 July 2020 [Page 2]
Internet-Draft Enabling RFC 8138 January 2020
Section 6.3.1. of [RFC6550] defines a 3-bit Mode of Operation (MOP)
in the DIO Base Object. The new "T" flag is defined only for MOP
value between 0 to 6. For a MOP value of 7 or above, the flag MAY
indicate something different and MUST NOT be interpreted as "Enable
Show full document text