References from rfc7852

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 181 Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by
Best Current Practice informatively references
BCP 195 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice informatively references
BCP 26 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
BCP 47 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
draft-ietf-slim-negotiating-human-language Negotiating Human Language in Real-Time Communications
References Referenced by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2392 Content-ID and Message-ID Uniform Resource Locators
References Referenced by
Proposed Standard normatively references
RFC 3204 MIME media types for ISUP and QSIG Objects
References Referenced by
Proposed Standard normatively references
RFC 3261 SIP: Session Initiation Protocol
References Referenced by
Proposed Standard normatively references
RFC 3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
References Referenced by
Informational informatively references
RFC 3459 Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
References Referenced by
Proposed Standard normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard informatively references
RFC 3966 The tel URI for Telephone Numbers
References Referenced by
Proposed Standard normatively references
RFC 4119 A Presence-based GEOPRIV Location Object Format
References Referenced by
Proposed Standard normatively references
RFC 5012 Requirements for Emergency Context Resolution with Internet Technologies
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 informatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 5322 Internet Message Format
References Referenced by
Draft Standard normatively references
RFC 5491 GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations
References Referenced by
Proposed Standard informatively references
RFC 5582 Location-to-URL Mapping Architecture and Framework
References Referenced by
Informational informatively references
RFC 5621 Message Body Handling in the Session Initiation Protocol (SIP)
References Referenced by
Proposed Standard normatively references
RFC 5646 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
RFC 5962 Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)
References Referenced by
Proposed Standard informatively references
RFC 5985 HTTP-Enabled Location Delivery (HELD)
References Referenced by
Proposed Standard informatively references
RFC 6350 vCard Format Specification
References Referenced by
Proposed Standard normatively references
RFC 6351 xCard: vCard XML Representation
References Referenced by
Proposed Standard informatively references
RFC 6443 Framework for Emergency Calling Using Internet Multimedia
References Referenced by
Informational informatively references
RFC 6698 The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
References Referenced by
Proposed Standard informatively references
RFC 6838 Media Type Specifications and Registration Procedures
References Referenced by
Best Current Practice normatively references
RFC 6848 Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
References Referenced by
Proposed Standard informatively references
RFC 6881 Best Current Practice for Communications Services in Support of Emergency Calling
References Referenced by
Best Current Practice informatively references
RFC 6973 Privacy Considerations for Internet Protocols
References Referenced by
Informational informatively references
RFC 7035 Relative Location Representation
References Referenced by
Proposed Standard informatively references
RFC 7090 Public Safety Answering Point (PSAP) Callback
References Referenced by
Proposed Standard informatively references
RFC 7303 XML Media Types
References Referenced by
Proposed Standard normatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice informatively references