References from draft-shacham-http-corr-uris
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 |
Possible Reference | ||
BCP 78 |
References Referenced by |
Reference | ||
RFC 1123 |
Requirements for Internet Hosts - Application and Support
References Referenced by |
Internet Standard | Reference | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | Reference | |
RFC 2818 |
HTTP Over TLS
References Referenced by |
Informational | Reference | |
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | Reference | |
RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | Reference | |
RFC 3966 |
The tel URI for Telephone Numbers
References Referenced by |
Proposed Standard | Reference | |
RFC 4406 |
Sender ID: Authenticating E-Mail
References Referenced by |
Historic | Reference | |
RFC 4408 |
Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
References Referenced by |
Experimental | Reference | |
RFC 4474 |
Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | Reference |