Notification Message Headers and Bundles
draft-ietf-netconf-notification-messages-08
Document | Type |
Expired Internet-Draft
(netconf WG)
Expired & archived
|
|
---|---|---|---|
Authors | Eric Voit , Tim Jenkins , Henk Birkholz , Andy Bierman , Alexander Clemm | ||
Last updated | 2020-05-20 (Latest revision 2019-11-17) | ||
Replaces | draft-voit-netconf-notification-messages | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Yang Validation | ☯ 0 errors, 2 warnings | ||
Additional resources |
Yang catalog entry for ietf-notification-messages@2019-10-10.yang
Yang impact analysis for draft-ietf-netconf-notification-messages Mailing list discussion |
||
Stream | WG state | Parked WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
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
This document defines a new notification message format. Included are: o a new notification mechanism and encoding to replace the one way operation of RFC-5277 o a set of common, transport agnostic message header objects. o how to bundle multiple event records into a single notification message. o how to ensure these new capabilities are only used with capable receivers.
Authors
Eric Voit
Tim Jenkins
Henk Birkholz
Andy Bierman
Alexander Clemm
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)