Mode of Operation extension
draft-ietf-roll-mopex-07
| Document | Type |
Expired Internet-Draft
(roll WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rahul Jadhav , Pascal Thubert , Michael Richardson | ||
| Last updated | 2023-12-06 (Latest revision 2023-06-04) | ||
| Replaces | draft-jadhav-roll-mopex, draft-ietf-roll-mopex-cap | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | Ines Robles | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | [email protected] |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Routing Protocol for Low-Power and Lossy Networks (RPL) can have different modes of operation (MOP) to allow nodes to agree on the basic primitives that must be supported to join a network. The MOP field defined in RFC6550 is fast depleting. This document specifies an extended MOP option for future use.
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.)