References from rfc4354
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.
| 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 67 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area 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 | |
| RFC 2141 |
URN Syntax Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3023 |
XML Media Types Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3261 |
SIP: Session Initiation Protocol Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3265 |
Session Initiation Protocol (SIP)-Specific Event Notification Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3427 |
Change Process for the Session Initiation Protocol (SIP) Refs Ref'd by |
Best Current Practice | Possible Reference | |
| RFC 3851 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3903 |
Session Initiation Protocol (SIP) Extension for Event State Publication Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 4353 |
A Framework for Conferencing with the Session Initiation Protocol (SIP) Refs Ref'd by |
Informational | informatively references | |
| STD 63 |
UTF-8, a transformation format of ISO 10646 Refs Ref'd by |
Internet Standard | normatively references |