References from rfc5222

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 13 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by
Best Current Practice normatively references
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 78 Rights Contributors Provide to the IETF Trust
References Referenced by
Best Current Practice informatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by
Draft Standard normatively references
RFC 2818 HTTP Over TLS
References Referenced by
Informational normatively references Downref
RFC 3023 XML Media Types
References Referenced by
Proposed Standard normatively references
RFC 3261 SIP: Session Initiation Protocol
References Referenced by
Proposed Standard informatively references
RFC 3833 Threat Analysis of the Domain Name System (DNS)
References Referenced by
Informational informatively references
RFC 3921 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
References Referenced by
Proposed Standard informatively references
RFC 3958 Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
References Referenced by
Proposed Standard informatively references
RFC 3966 The tel URI for Telephone Numbers
References Referenced by
Proposed Standard informatively references
RFC 4033 DNS Security Introduction and Requirements
References Referenced by
Proposed Standard informatively references
RFC 4119 A Presence-based GEOPRIV Location Object Format
References Referenced by
Proposed Standard normatively references
RFC 4288 Media Type Specifications and Registration Procedures
References Referenced by
Best Current Practice Possible Reference
RFC 4848 Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)
References Referenced by
Proposed Standard normatively references
RFC 5012 Requirements for Emergency Context Resolution with Internet Technologies
References Referenced by
Informational informatively references
RFC 5031 A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
References Referenced by
Proposed Standard normatively references
RFC 5069 Security Threats and Requirements for Emergency Call Marking and Mapping
References Referenced by
Informational informatively references
RFC 5139 Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
References Referenced by
Proposed Standard normatively references
RFC 5223 Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP)
References Referenced by
Proposed Standard informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice Possible Reference
STD 1 Internet Official Protocol Standards
References Referenced by
Historic Possible Reference Possible Downref