References from draft-yusef-splices-invoke
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 |
Reference | ||
| BCP 26 |
References Referenced by |
Reference | ||
| BCP 66 |
References Referenced by |
Reference | ||
| draft-worley-sip-many-refers |
The Five Meanings of the REFER Method
References Referenced by |
Possible Reference | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Reference | |
| RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | Reference | |
| RFC 3265 |
Session Initiation Protocol (SIP)-Specific Event Notification
References Referenced by |
Proposed Standard | Reference | |
| RFC 3406 |
Uniform Resource Names (URN) Namespace Definition Mechanisms
References Referenced by |
Best Current Practice | Reference | |
| RFC 3515 |
The Session Initiation Protocol (SIP) Refer Method
References Referenced by |
Proposed Standard | Reference | |
| RFC 3880 |
Call Processing Language (CPL): A Language for User Control of Internet Telephony Services
References Referenced by |
Proposed Standard | Reference | |
| RFC 4538 |
Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | Reference | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Reference |