References from draft-zhou-netconf-multi-stream-originators

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document	Title	Status	Type
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
draft-ietf-core-coap-pubsub	Publish-Subscribe Broker for the Constrained Application Protocol (CoAP) Refs Ref'd by		informatively references
draft-ietf-netconf-notification-messages	Notification Message Headers and Bundles Refs Ref'd by		informatively references
draft-ietf-netconf-subscribed-notifications	Subscription to YANG Event Notifications Refs Ref'd by	Proposed Standard	informatively references
draft-ietf-netconf-yang-push	Subscription to YANG Datastores Refs Ref'd by	Proposed Standard	informatively references
draft-mahesh-netconf-https-notif	An HTTPS-based Transport for Configured Subscriptions Refs Ref'd by		informatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 3688	The IETF XML Registry Refs Ref'd by	Best Current Practice	normatively references
RFC 5246	The Transport Layer Security (TLS) Protocol Version 1.2 Refs Ref'd by	Proposed Standard	normatively references
RFC 6241	Network Configuration Protocol (NETCONF) Refs Ref'd by	Proposed Standard	normatively references
RFC 6242	Using the NETCONF Protocol over Secure Shell (SSH) Refs Ref'd by	Proposed Standard	normatively references
RFC 6536	Network Configuration Protocol (NETCONF) Access Control Model Refs Ref'd by	Proposed Standard	normatively references
RFC 7950	The YANG 1.1 Data Modeling Language Refs Ref'd by	Proposed Standard	normatively references
RFC 8040	RESTCONF Protocol Refs Ref'd by	Proposed Standard	normatively references