Major network operating system vendors and operators aligned on a agile incremental driven development roadmap for YANG-Push publisher implementations. We suggest follow same implementation pattern.
For reference and implementation: open-source library implementation in C for YANG-Push draft-ietf-netconf-udp-notif receiver.
End of 2025 · Minimum Viable Product 1:
draft-ietf-netconf-udp-notif transport (with segmentation option) and notifications encoded in RFC 7951 IETF-JSON.
RFC 8639 periodic subscription with anchor-time configurable in ietf-subscribed-notifications.
YANG notifications as defined in draft-netana-netconf-notif-envelope, YANG module name, version and yang-library-content-id as in draft-ietf-netconf-yang-notifications-versioning and notification capabilities (RFC 9196) discoverable as defined in their documents.
YANG-Library as defined in RFC 8525 and draft-ietf-netconf-yang-library-augmentation.
2026 · Minimum Viable Product 2:
Distributed notifications as defined in draft-ietf-netconf-distributed-notif.
YANG notifications encoded in CBOR (named identifiers) as defined in RFC 9254.
YANG notifications DTLS (1.2 MUST RFC RFC 6347, 1.3 SHOULD RFC 9147) encrypted as defined in draft-ietf-netconf-udp-notif.
2027 · Minimum Viable Product 3:
RFC 8641 on-change subscription configurable in ietf-subscribed-notifications.
RFC 8641 on-change and periodical subscription in RFC 9196 defined capabilities discoverable.
draft-ietf-netconf-udp-notif transport, encoding and encryption capabilities (RFC 9196) discoverable with draft-netana-netconf-yp-transport-capabilities.