References from draft-hardie-p2poverlay-pointers
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 78 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
RFC 3023 |
XML Media Types
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
RFC 4234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Draft Standard | normatively references | |
RFC 4288 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 4395 |
Guidelines and Registration Procedures for New URI Schemes
References Referenced by |
Best Current Practice | normatively references |