References from draft-morais-iotops-inxu
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 |
---|---|---|---|---|
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2818 |
HTTP Over TLS
References Referenced by |
Informational | informatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | normatively references | |
RFC 7950 |
The YANG 1.1 Data Modeling Language
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8340 |
YANG Tree Diagrams
References Referenced by |
Best Current Practice | normatively references | |
RFC 8519 |
YANG Data Model for Network Access Control Lists (ACLs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8520 |
Manufacturer Usage Description Specification
References Referenced by |
Proposed Standard | normatively references |