This document defines a protocol for sending notifications over
HTTPS. YANG modules for configuring publishers are also defined.
Examples are provided illustrating how to configure various
This document requires that the publisher is a "server" (e.g., a
NETCONF or RESTCONF server), but does not assume that the receiver is
Working Group Summary
The WG consensus represents the strong concurrence of a small amount of
individuals with the other folks giving comments on the changes of the
document. WGLC has received some detailed reviews and other additional
comments, there is no objection to publication.
As such, the document has reached broad agreement.
There was no controversy about particular points, and the shepherd doesn't
notice any decisions where the consensus was particularly rough.
This document has received enough review in both WG meeting and on the NETCONF
WG mailing list, both authors and the shepherd believe that all the comments
and questions from that review have been incorporated into the document.
The shepherd knows that there is an existing implementation from INSA Unyte
team, which is an open-sourced library for collecting HTTPS-notif protocol
message available at https://github.com/insa-unyte/https-notif-c-collector. No
other existing implementations have been publicly reported.
The shepherd is unaware of any potential implementers indicating plans to
I would like to thank Qiufang since I believe that this is the first time
she has acted in the Doc Shepherd role.
Qiufang Ma is the Doc Shepherd
Robert Wilton is the Area Director
IANA has flagged up a question regarding use of prefixes, but I think that
it is reasonable for RFCs defining YANG models to assume that if the YANG
models are XML encoded then they conform to RFC 7950. I.e., I think that
we should follow the existing practice used for other IETF RFCs containing
YANG module examples.