References from draft-sparks-sipcore-refer-clarifications
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 149 |
Session Initiation Protocol (SIP) Call Control - Transfer References Referenced by |
Best Current Practice | informatively references | |
draft-sparks-sipcore-refer-explicit-subscription |
Explicit Subscriptions for the REFER Method References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 3261 |
SIP: Session Initiation Protocol References Referenced by |
Proposed Standard | normatively references | |
RFC 3515 |
The Session Initiation Protocol (SIP) Refer Method References Referenced by |
Proposed Standard | normatively references | |
RFC 4488 |
Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription References Referenced by |
Proposed Standard | informatively references | |
RFC 4538 |
Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
RFC 5589 |
Session Initiation Protocol (SIP) Call Control - Transfer References Referenced by |
Best Current Practice | informatively references | |
RFC 5627 |
Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
RFC 6665 |
SIP-Specific Event Notification References Referenced by |
Proposed Standard | normatively references |