CoAP Management Interface (CORECONF)
draft-ietf-core-comi-10
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Michel Veillette , Peter Van der Stok , Alexander Pelov , Andy Bierman , Ivaylo Petrov | ||
| Last updated | 2021-01-05 (Latest revision 2020-07-04) | ||
| Replaces | draft-vanderstok-core-comi | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Document shepherd | Carsten Bormann | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Carsten Bormann <cabo@tzi.org> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a network management interface for constrained devices and networks, called CoAP Management Interface (CORECONF). The Constrained Application Protocol (CoAP) is used to access datastore and data node resources specified in YANG, or SMIv2 converted to YANG. CORECONF uses the YANG to CBOR mapping and converts YANG identifier strings to numeric identifiers for payload size reduction. CORECONF extends the set of YANG based protocols, NETCONF and RESTCONF, with the capability to manage constrained devices and networks.
Authors
Michel Veillette
Peter Van der Stok
Alexander Pelov
Andy Bierman
Ivaylo Petrov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)