RFC 7923: Requirements for Subscription to YANG Datastores
In plain English — editorial summary, not part of the RFC
This document provides requirements for a service that allows client applications to subscribe to updates of a YANG datastore. Based on criteria negotiated as part of a subscription, updates will be pushed to targeted recipients. Such a capability eliminates the need for periodic polling of YANG datastores by applications and fills a functional gap in existing YANG transports (i.e., Network Configuration Protocol (NETCONF) and RESTCONF). Such a service can be summarized as a "pub/sub" service for YANG datastore updates. Beyond a set of basic requirements for the service, various refinements are addressed. These refinements include: periodicity of object updates, filtering out of objects underneath a requested a subtree, and delivery QoS guarantees.
Document record
- Document ID
- RFC7923
- Published
- June 2016
- Authors
- E. Voit; A. Clemm; A. Gonzalez Prieto
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7922Interface to the Routing System (I2RS) Traceability: Framework and Information ModelCurrent
June 2016
- RFC 7921An Architecture for the Interface to the Routing SystemCurrent
June 2016
- RFC 7926Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered NetworksCurrent
July 2016
- RFC 7920Problem Statement for the Interface to the Routing SystemCurrent
June 2016
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 7935The Profile for Algorithms and Key Sizes for Use in the Resource Public Key InfrastructureUpdated
August 2016
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?