References to rfc2392

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