Mode of Operation extension and Capabilities
draft-ietf-roll-mopex-cap-01

Document Type Replaced Internet-Draft (roll WG)
Last updated 2019-11-02
Replaces draft-rahul-roll-mop-ext
Replaced by draft-ietf-roll-capabilities
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Dec 2020 - Initial submission o... )
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-roll-capabilities
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-roll-mopex-cap-01.txt

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

JADHAV Rahul (rahul.ietf@gmail.com)
Pascal Thubert (pthubert@cisco.com)
Michael Richardson (mcr+ietf@sandelman.ca)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)