This repository is for the development of a IETF draft for the yang-push
- Subscription to YANG Event Notifications: https://tools.ietf.org/html/draft-ietf-netconf-subscribed-notifications-18
- NetConf YANG-PUSH: https://tools.ietf.org/html/draft-ietf-netconf-yang-push-20
- Dynamic subscription over RESTCONF: https://tools.ietf.org/html/draft-ietf-netconf-restconf-notif-10
- Dynamic subscription over Netconf: https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notifications-14
- i2rs-pub-sub-requirements: https://tools.ietf.org/html/rfc7923
- Issue Tracking: https://github.com/netconf-wg/yang-push/issues
Next revision of IETF Netconf YANG-PUSH (WORK IN PROGRESS, NOT AN I-D) https://github.com/netconf-wg/yang-push/blob/master/draft-ietf-netconf-yang-push-03.txt Latest update posted 6/14/2016
Next revision of IETF RFC5277bis (WORK IN PROGRESS, NOT AN I-D): https://github.com/netconf-wg/yang-push/blob/master/draft-gonzalez-netconf-5277bis-02.txt (note: IETF RFC5277bis will be moved to a separate git repository) Latest update posted 6/14/2016
Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:
The IETF plenary session The IESG, or any member thereof on behalf of the IESG Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices Any IETF working group or portion thereof Any Birds of a Feather (BOF) session The IAB or any member thereof on behalf of the IAB The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.
Please consult RFC 5378 and RFC 3979 for details.
A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.