References from draft-goland-http-reliability
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 1123 |
Requirements for Internet Hosts - Application and Support
References Referenced by |
Internet Standard | Possible Reference | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | normatively references | |
RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax
References Referenced by |
Draft Standard | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
RFC 2774 |
An HTTP Extension Framework
References Referenced by |
Historic | informatively references | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
RFC 4122 |
A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by |
Proposed Standard | informatively references | |
RFC 822 |
STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
References Referenced by |
Internet Standard | informatively references | |
RFC 958 |
Network Time Protocol (NTP)
References Referenced by |
Unknown | informatively references |