References from rfc7118
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
BCP 32 |
Reserved Top Level DNS Names References Referenced by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 2606 |
Reserved Top Level DNS Names References Referenced by |
Best Current Practice | informatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | informatively references | |
RFC 2617 |
HTTP Authentication: Basic and Digest Access Authentication References Referenced by |
Draft Standard | normatively references | |
RFC 3261 |
SIP: Session Initiation Protocol References Referenced by |
Proposed Standard | informatively references | |
RFC 3263 |
Session Initiation Protocol (SIP): Locating SIP Servers References Referenced by |
Proposed Standard | normatively references | |
RFC 3327 |
Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts References Referenced by |
Proposed Standard | informatively references | |
RFC 3403 |
Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database References Referenced by |
Proposed Standard | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | informatively references | |
RFC 4168 |
The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references | |
RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2 References Referenced by |
Proposed Standard | normatively references | |
RFC 5626 |
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
RFC 5627 |
Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates References Referenced by |
Informational | Possible Reference | Possible Downref |
RFC 5922 |
Domain Certificates in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
RFC 6223 |
Indication of Support for Keep-Alive References Referenced by |
Proposed Standard | informatively references | |
RFC 6265 |
HTTP State Management Mechanism References Referenced by |
Proposed Standard | informatively references | |
RFC 6455 |
The WebSocket Protocol References Referenced by |
Proposed Standard | informatively references | |
STD 66 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | informatively references | |
STD 68 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references |