Notification Message Headers and Bundles
draft-ietf-netconf-notification-messages-05
|
| Document |
Type |
|
Active Internet-Draft (netconf WG)
|
|
Last updated |
|
2019-02-15
|
|
Replaces |
|
draft-voit-netconf-notification-messages
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-netconf-notification-messages-05.txt:
xym 0.4:
Extracting 'ietf-notification-messages@2018-01-31.yang'
Removed 6 empty lines
ietf-notification-messages@2018-01-31.yang:
pyang 1.7.8: pyang --verbose --ietf -p {libs} {model}:
# read ietf-notification-messages@2018-01-31.yang (CL)
# read /a/www/ietf-datatracker/6.98.1/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-yang-types@2019-03-11.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-restconf.yang
# read /a/www/ietf-datatracker/6.98.1/env/share/yang/modules/ietf/ietf-restconf.yang
yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Additional URLs |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
NETCONF E. Voit
Internet-Draft Cisco Systems
Intended status: Standards Track H. Birkholz
Expires: August 19, 2019 Fraunhofer SIT
A. Bierman
YumaWorks
A. Clemm
Huawei
T. Jenkins
Cisco Systems
February 15, 2019
Notification Message Headers and Bundles
draft-ietf-netconf-notification-messages-05
Abstract
This document defines a new notification message format, using yang-
data. 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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 19, 2019.
Voit, et al. Expires August 19, 2019 [Page 1]
Internet-Draft Notifications February 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Header Objects . . . . . . . . . . . . . . . . . . . . . . . 3
4. Encapsulation of Header Objects in Messages . . . . . . . . . 4
4.1. One Notification per Message . . . . . . . . . . . . . . 5
4.2. Many Notifications per Message . . . . . . . . . . . . . 5
5. Configuration of Headers . . . . . . . . . . . . . . . . . . 8
6. Discovering Receiver Support . . . . . . . . . . . . . . . . 9
7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1. Normative References . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Changes between revisions . . . . . . . . . . . . . 20
Appendix B. Issues being worked . . . . . . . . . . . . . . . . 21
Appendix C. Subscription Specific Headers . . . . . . . . . . . 21
Appendix D. Implications to Existing RFCs . . . . . . . . . . . 22
D.1. Implications to RFC-7950 . . . . . . . . . . . . . . . . 22
D.2. Implications to RFC-8040 . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction
Mechanisms to support subscription to event notifications and yang
datastore push are being defined in
[I-D.draft-ietf-netconf-subscribed-notifications] and
[I-D.ietf-netconf-yang-push]. Work on those documents has shown that
notifications described in [RFC7950] section 7.16 could benefit from
transport independent headers. Communicating the following
Voit, et al. Expires August 19, 2019 [Page 2]
Show full document text