References from rfc4354
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 67 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area References Referenced by |
Best Current Practice | normatively references | |
BCP 78 |
Rights Contributors Provide to the IETF Trust References Referenced by |
Best Current Practice | informatively references | |
RFC 2141 |
URN Syntax References Referenced by |
Proposed Standard | normatively references | |
RFC 3023 |
XML Media Types References Referenced by |
Proposed Standard | normatively 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 3427 |
Change Process for the Session Initiation Protocol (SIP) References Referenced by |
Best Current Practice | Possible Reference | |
RFC 3851 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification References Referenced by |
Proposed Standard | normatively references | |
RFC 3903 |
Session Initiation Protocol (SIP) Extension for Event State Publication References Referenced by |
Proposed Standard | normatively references | |
RFC 4353 |
A Framework for Conferencing with the Session Initiation Protocol (SIP) References Referenced by |
Informational | informatively references | |
STD 63 |
UTF-8, a transformation format of ISO 10646 References Referenced by |
Internet Standard | normatively references |