Mode of Operation extension and Capabilities
draft-ietf-roll-mopex-cap-01
Document | Type |
Replaced Internet-Draft
(roll WG)
Expired & archived
|
|
---|---|---|---|
Authors | Rahul Jadhav , Pascal Thubert , Michael Richardson | ||
Last updated | 2019-11-02 | ||
Replaces | draft-rahul-roll-mop-ext | ||
Replaced by | draft-ietf-roll-capabilities, draft-ietf-roll-mopex | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-roll-mopex, draft-ietf-roll-capabilities | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Rahul Jadhav
Pascal Thubert
Michael Richardson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)