]> Huawei Tech

Kundalahalli Village, Whitefield, Bangalore Karnataka 560037 India +91-080-49160700 rahul.ietf@gmail.com

Cisco Systems, Inc

Building D 45 Allee des Ormes - BP1200 MOUGINS - Sophia Antipolis 06254 France +33 497 23 26 34 pthubert@cisco.com

General ROLL RPL, mesh, MOP, extension 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.

RPL 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 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 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. MOP: Mode of Operation. Identifies the mode of operation of the RPL Instance as administratively provisioned at and distributed by the DODAG root. DAO: DODAG Advertisement Object. An RPL message used to advertise the target information in order to establish routing adjacencies. DIO: DODAG Information Object. An RPL message initiated by the root and is used to advertise the network configuration information. Current parent: Parent 6LR node before switching to the new path. NPDAO: No-Path DAO. A DAO message which has target with lifetime 0. MOPex: MOP extension as defined in this document. This document uses terminology described in . For the sake of readability all the known relevant terms are repeated in this section.

Following are the requirements considered for this documents: MOP extension. Current MOP of 3-bit is fast depleting. An MOP extension needs to extend the possibility of adding new MOPs in the future. Optional capabilities handshake. Capabilities are features, possibly optional, which could be handshaked between the nodes and the root within an RPL Instance. Backwards compatibility. The new options and new fields in the DIO message should be backward compatible i.e. if there are nodes which support old MOPs they could still operate in their own instances. Capabilities handshake could be optionally added with existing MOPs. Capabilities been optional in nature could be put to use with existing MOPs. Capabilities and MOP-extension is mutually independent i.e. a DIO can have a capabilities option, MOP-extension option or both in the same message.

This document reserves existing MOP value 7 to be used as an extender. DIO messages with MOP value of 7 MUST refer to the Extended MOP (MOPex) option in the DIO message. If the MOPex option is absent in the DIO whose MOP is 7, then the DIO message MUST be silently discarded.

An implementation supporting this document MUST calculate the final MOP value as the sum of base MOP (as supported in Section 6.3.1. of ) plus the MOPex value. Thus if the MOPex value is 0, it means the final MOP is 7 since the base MOP in this case will be set to 7. Base MOP MOPex Final MOP 0 NA 0 1 NA 1 : : : 6 NA 6 7 0 7 7 1 8 7 2 9 : : :

Currently RPL specification does not have a mechanism whereby a node can signal the set of features that are available on its end. Such a mechanism could help the root to advertise its capabilities and in response also determine some advanced information about the capabilities of the joining nodes. The Mode of Operation field in RPL mandates the operational requirement and does not allow loose coupling of additional capabilities. This document defines Capabilities as additional features which could be supported by the nodes and handshaked as part of RPL signaling. Capabilities are embedded as RPL control message option as defined Section 6.7 of in the base messages of DIO, DAO and DAO-ACK signaling.

There are no capability flags defined by this document.

The root node could advertise the set of capabilities it supports in the DIO message. A node could take advantage of the knowledge that the root supports a particular capability. Similarly a node could advertise its capabilities in the DAO message using the capability control message option defined in this document. Capabilities advertised by non-root nodes are strictly a subset of the capabilities advertised by the root. In storing MOP, the DAO message from the 6LR could contain multiple target options. The targets of the capabilities option are indicated by one or more Target options that precede the Capabilties Option. This handling is similar to the Transit Information Option as supported in Section 6.7.8. of .

The MOP-extension could cause 3-byte increase in memory in the RPL-Instance. The MOP field in the RPL-Instance needs to be upgraded to a 32 bit integer. , it was possible to discard an unsupported DIO-MOP just by inspecting the base message. With this document, the MOPex is a different control message option and thus the discarding of the DIO message could happen after inspecting the message options. A node in storing MOP could independently construct a DAO message with target options containing its child/sub-childs. Thus with capabilities it needs to reconstruct the capabilities field as well. This may result in increase in the memory requirement on per routing-entry basis.

Thanks

IANA is requested to allocate MOP field value 0x7 in the DIO base object defined in RPL section 6.3.1 for MOP extension. TODO

The options defined in this document are carried in the base message objects as defined in . The RPL control message options are protected by the same security mechanisms that protect the base messages. Capabilities flag can reveal that the node has been upgraded or is running a old feature set. This document assumes that the base messages that carry these options are protected by RPL security mechanisms and thus are not visible to a malicious node.

&RFC2119; &RFC6550;

| DIO(CS1) | | |----------->| | | | | | DAO(CS2) | | |<-----------| | DAO(CS2) | | |<------------| | | | | CS: Capabilities Set CS1: Capabilities set advertised by root CS2: Capabilities set advertised by node. CS2 is a subset of CS1. ]]>