References from draft-bierman-netconf-yang-api
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
draft-lhotka-netmod-yang-json |
Modeling JSON Text with YANG
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2392 |
Content-ID and Message-ID Uniform Resource Locators
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
RFC 3688 |
The IETF XML Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 5789 |
PATCH Method for HTTP
References Referenced by |
Proposed Standard | normatively references | |
RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 6020 |
YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6021 |
Common YANG Data Types
References Referenced by |
Proposed Standard | normatively references | |
RFC 6241 |
Network Configuration Protocol (NETCONF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6536 |
Network Configuration Protocol (NETCONF) Access Control Model
References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
References Referenced by |
normatively references |