RFC 8639: Subscription to YANG Notifications
In plain English — editorial summary, not part of the RFC
This document defines a YANG data model and associated mechanisms enabling subscriber-specific subscriptions to a publisher's event streams. Applying these elements allows a subscriber to request and receive a continuous, customized feed of publisher-generated information.
Document record
- Document ID
- RFC8639
- Published
- September 2019
- Authors
- E. Voit; A. Clemm; A. Gonzalez Prieto; E. Nilsen-Nygaard; A. Tripathy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 77
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8641Subscription to YANG Notifications for Datastore UpdatesCurrent
September 2019
- RFC 8640Dynamic Subscription to YANG Events and Datastores over NETCONFCurrent
September 2019
- RFC 8650Dynamic Subscription to YANG Events and Datastores over RESTCONFCurrent
November 2019
- RFC 9197Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)Current
May 2022
- RFC 9232Network Telemetry FrameworkCurrent
May 2022
- RFC 9322In Situ Operations, Administration, and Maintenance (IOAM) Loopback and Active FlagsCurrent
November 2022
- RFC 9326In Situ Operations, Administration, and Maintenance (IOAM) Direct ExportingCurrent
November 2022
- RFC 9378In Situ Operations, Administration, and Maintenance (IOAM) DeploymentCurrent
April 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?