References to rfc2392

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
draft-ietf-calext-jscalendar JSCalendar: A JSON representation of calendar data
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-ecrit-data-only-ea Data-Only Emergency Calls
Refs Ref'd by
Proposed Standard normatively references
draft-rosen-rue Interoperability Profile for Relay User Equipment
Refs Ref'd by
normatively references
RFC 4119 A Presence-based GEOPRIV Location Object Format
Refs Ref'd by
Proposed Standard normatively references
RFC 5318 The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
Refs Ref'd by
Informational normatively references
RFC 5368 Referring to Multiple Resources in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 5547 A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
Refs Ref'd by
Proposed Standard normatively references
RFC 5621 Message Body Handling in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 5707 Media Server Markup Language (MSML)
Refs Ref'd by
Informational normatively references
RFC 6047 iCalendar Message-Based Interoperability Protocol (iMIP)
Refs Ref'd by
Proposed Standard normatively references
RFC 6442 Location Conveyance for the Session Initiation Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 6787 Media Resource Control Protocol Version 2 (MRCPv2)
Refs Ref'd by
Proposed Standard normatively references
RFC 7852 Additional Data Related to an Emergency Call
Refs Ref'd by
Proposed Standard normatively references
RFC 8226 Secure Telephone Identity Credentials: Certificates
Refs Ref'd by
Proposed Standard normatively references
RFC 8262 Content-ID Header Field in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-jmap-mail JMAP (JSON Meta Application Protocol) for Mail
Refs Ref'd by
Proposed Standard informatively references
RFC 4227 Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Refs Ref'd by
Proposed Standard informatively references
RFC 4463 A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks
Refs Ref'd by
Informational informatively references
RFC 5545 Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Refs Ref'd by
Proposed Standard informatively references
RFC 6772 Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
Refs Ref'd by
Proposed Standard informatively references
RFC 8040 RESTCONF Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 3795 Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
Refs Ref'd by
Informational Possible Reference
RFC 3288 Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Refs Ref'd by
Proposed Standard Reference
RFC 3340 The Application Exchange Core
Refs Ref'd by
Historic Reference
RFC 3391 The MIME Application/Vnd.pwg-multiplexed Content-Type
Refs Ref'd by
Informational Reference