References from RFC 5263
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 78 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2778 |
A Model for Presence and Instant Messaging
References Referenced by |
Informational | informatively references | |
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 3265 |
Session Initiation Protocol (SIP)-Specific Event Notification
References Referenced by |
Proposed Standard | normatively references | |
RFC 3856 |
A Presence Event Package for the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3863 |
Presence Information Data Format (PIDF)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4346 |
The Transport Layer Security (TLS) Protocol Version 1.1
References Referenced by |
Historic | normatively references | |
RFC 5261 |
An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors
References Referenced by |
Proposed Standard | normatively references | |
RFC 5262 |
Presence Information Data Format (PIDF) Extension for Partial Presence
References Referenced by |
Proposed Standard | normatively references | |
STD 1 |
References Referenced by |
Possible Reference |