References from RFC 4480
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
BCP 18 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
BCP 81 |
References Referenced by |
normatively references | ||
RFC 2141 |
URN Syntax
References Referenced by |
Proposed Standard | normatively references | |
RFC 2445 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar)
References Referenced by |
Proposed Standard | informatively references | |
RFC 2648 |
A URN Namespace for IETF Documents
References Referenced by |
Informational | normatively references | Downref |
RFC 2778 |
A Model for Presence and Instant Messaging
References Referenced by |
Informational | normatively references | Downref |
RFC 3856 |
A Presence Event Package for the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3860 |
Common Profile for Instant Messaging (CPIM)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3863 |
Presence Information Data Format (PIDF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3880 |
Call Processing Language (CPL): A Language for User Control of Internet Telephony Services
References Referenced by |
Proposed Standard | informatively references | |
RFC 4479 |
A Data Model for Presence
References Referenced by |
Proposed Standard | informatively references | |
RFC 4589 |
Location Types Registry
References Referenced by |
Proposed Standard | normatively references | |
STD 1 |
References Referenced by |
Possible Reference |