Notification Message Headers and Bundles
draft-ietf-netconf-notification-messages-08

Document Type Expired Internet-Draft (netconf WG)
Last updated 2020-05-20 (latest revision 2019-11-17)
Replaces draft-voit-netconf-notification-messages
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Yang Validation 0 errors, 2 warnings.
Additional URLs
- 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 No shepherd assigned
IESG IESG state Expired
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-netconf-notification-messages-08.txt

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 (evoit@cisco.com)
Tim Jenkins (timjenki@cisco.com)
Henk Birkholz (henk.birkholz@sit.fraunhofer.de)
Andy Bierman (andy@yumaworks.com)
Alexander Clemm (ludwig@clemm.org)

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