Configuration option for RFC 8138
draft-thubert-roll-turnon-rfc8138-00
The information below is for an old version of the document.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Author | Pascal Thubert | ||
| Last updated | 2019-05-23 | ||
| Replaced by | draft-ietf-roll-turnon-rfc8138, draft-ietf-roll-turnon-rfc8138, draft-ietf-roll-turnon-rfc8138, RFC 9035 | ||
| Stream | (None) | ||
| Formats | plain text xml htmlized pdfized bibtex | ||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-thubert-roll-turnon-rfc8138-00
ROLL P. Thubert, Ed.
Internet-Draft Cisco Systems
Updates: 6550 (if approved) May 23, 2019
Intended status: Standards Track
Expires: November 24, 2019
Configuration option for RFC 8138
draft-thubert-roll-turnon-rfc8138-00
Abstract
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.
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 November 24, 2019.
Copyright Notice
Copyright (c) 2019 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
Thubert Expires November 24, 2019 [Page 1]
Internet-Draft Enabling RFC 8138 May 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . . 2
4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . 3
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
8.1. Normative References . . . . . . . . . . . . . . . . . . 3
8.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
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.
Thubert Expires November 24, 2019 [Page 2]
Internet-Draft Enabling RFC 8138 May 2019
4. Operation
A node that supports this specification SHOULD source packets in the
compressed form using [RFC8138] if the new T flag is set in the RPL
configuration option from its parents. Failure to do so will result
in larger packets, yields higher risks of loss and may cause a
fragmentation.
A node that supports this specification SHOULD refrain from sourcing
packets in the compressed form using [RFC8138] if the T flag is
reset. This behaviour can be overridden by a configuration of the
node in order to cope with intermediate implementations of the root
that support [RFC8138] but not this specification and cannot set the
T flag.
Regardless of the setting of the bit, the node MUST forward a packet
in the form it was received, compressed or uncompressed.
5. IANA Considerations
This specification updates the "Registry for the DODAG Configuration
Option Flags" that was created for [RFC6550] as follows:
+---------------+---------------------------------+-------------+
| Bit number | Suggested value | Defined in |
+---------------+---------------------------------+-------------+
| 2 (suggested) | Turn on RFC8138 Compression (T) | This RFC |
+---------------+---------------------------------+-------------+
Table 1: New DODAG Configuration Option Flag
6. Security Considerations
No specific threat was identified with this specification.
7. Acknowledgments
8. 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>.
Thubert Expires November 24, 2019 [Page 3]
Internet-Draft Enabling RFC 8138 May 2019
[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
Low-Power and Lossy Networks", RFC 6550,
DOI 10.17487/RFC6550, March 2012,
<https://www.rfc-editor.org/info/rfc6550>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References
[RFC8138] Thubert, P., Ed., Bormann, C., Toutain, L., and R. Cragie,
"IPv6 over Low-Power Wireless Personal Area Network
(6LoWPAN) Routing Header", RFC 8138, DOI 10.17487/RFC8138,
April 2017, <https://www.rfc-editor.org/info/rfc8138>.
Author's Address
Pascal Thubert (editor)
Cisco Systems, Inc
Building D
45 Allee des Ormes - BP1200
MOUGINS - Sophia Antipolis 06254
FRANCE
Phone: +33 497 23 26 34
Email: pthubert@cisco.com
Thubert Expires November 24, 2019 [Page 4]