References from rfc4480

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 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 18	IETF Policy on Character Sets and Languages Refs Ref'd by	Best Current Practice	normatively references
BCP 78	Rights Contributors Provide to the IETF Trust Refs Ref'd by	Best Current Practice	informatively references
BCP 81	The IETF XML Registry Refs Ref'd by	Best Current Practice	normatively references
RFC 2141	URN Syntax Refs Ref'd by	Proposed Standard	normatively references
RFC 2445	Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by	Proposed Standard	informatively references
RFC 2648	A URN Namespace for IETF Documents Refs Ref'd by	Informational	normatively references	Downref
RFC 2778	A Model for Presence and Instant Messaging Refs Ref'd by	Informational	normatively references	Downref
RFC 3856	A Presence Event Package for the Session Initiation Protocol (SIP) Refs Ref'd by	Proposed Standard	normatively references
RFC 3860	Common Profile for Instant Messaging (CPIM) Refs Ref'd by	Proposed Standard	informatively references
RFC 3863	Presence Information Data Format (PIDF) Refs Ref'd by	Proposed Standard	normatively references
RFC 3880	Call Processing Language (CPL): A Language for User Control of Internet Telephony Services Refs Ref'd by	Proposed Standard	informatively references
RFC 4479	A Data Model for Presence Refs Ref'd by	Proposed Standard	informatively references
RFC 4589	Location Types Registry Refs Ref'd by	Proposed Standard	normatively references
STD 1	Internet Official Protocol Standards Refs Ref'd by	Historic	Possible Reference	Possible Downref