Mode of Operation extension and Capabilities
draft-ietf-roll-mopex-cap-00
ROLL R. Jadhav, Ed.
Internet-Draft Huawei Tech
Intended status: Standards Track P. Thubert
Expires: February 10, 2020 Cisco
August 9, 2019
Mode of Operation extension and Capabilities
draft-ietf-roll-mopex-cap-00
Abstract
RPL allows different mode of operations which allows nodes to have a
consensus on the basic primitives that must be supported to join the
network. The MOP field in RFC6550 is of 3 bits and is fast
depleting. This document extends the MOP field specification and
adds a notion of capabilities using which the nodes can further
advertise their support for, possibly optional, capabilities.
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 February 10, 2020.
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
Jadhav & Thubert Expires February 10, 2020 [Page 1]
Internet-Draft MOP extension August 2019
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language and Terminology . . . . . . . . . . 3
2. Requirements for this document . . . . . . . . . . . . . . . 3
3. Extended MOP Control Message Option . . . . . . . . . . . . . 4
3.1. Final MOP . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Handling MOPex . . . . . . . . . . . . . . . . . . . . . 5
4. Capabilities . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Capability Control Message Option . . . . . . . . . . . . 5
4.2. Capabilities Handshake . . . . . . . . . . . . . . . . . 5
5. Implementations Consideration . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7.1. Mode of operation: MOPex . . . . . . . . . . . . . . . . 6
7.2. New options: MOPex and Capabilities . . . . . . . . . . . 7
7.3. New Registry for Extended-MOP-value . . . . . . . . . . . 7
7.4. New Registry for Capabilities Flags . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Capability Handshake Example . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
RPL [RFC6550] specifies a proactive distance-vector based routing
scheme. The protocol creates a DAG-like structure which operates
with a given "Mode of Operation" (MOP) determining the minimal and
mandatory set of primitives to be supported by all the participating
nodes.
MOP as per [RFC6550] is a 3-bit value carried in DIO messages and is
specific to the RPL Instance. The receipient of the DIO message can
join the specified network as a router only when it can support the
primitives as required by the mode of operation value. For example,
in case of MOP=3 (Storing MOP with multicast support) the nodes can
join the network as routers only when they can handle the DAO
advertisements from the peers and manage routing tables. The 3-bit
value is already exhausted and requires replenishment. This document
introduces a mechanism to extend mode of operation values.
Show full document text