RPL Mode of Operation extension
draft-rahul-mop-ext-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-02-07 | ||
| Replaced by | draft-rahul-roll-mop-ext | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-rahul-roll-mop-ext | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-rahul-mop-ext-00.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)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)