References to rfc3968
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.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-ietf-sipcore-callinfo-spam |
SIP Call-Info Parameters for Labeling Calls References Referenced by |
Proposed Standard | normatively references | |
|
draft-ietf-sipcore-callinfo-spam
As bcp98 |
SIP Call-Info Parameters for Labeling Calls References Referenced by |
Proposed Standard | normatively references | |
|
RFC 4485
As bcp98 |
Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP) References Referenced by |
Informational | normatively references | |
|
RFC 4538
As bcp98 |
Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
| RFC 5626 |
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
|
RFC 5626
As bcp98 |
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
|
RFC 5627
As bcp98 |
Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
|
RFC 6140
As bcp98 |
Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | normatively references | |
|
RFC 6665
As bcp98 |
SIP-Specific Event Notification References Referenced by |
Proposed Standard | normatively references | |
| RFC 6794 |
A Framework for Session Initiation Protocol (SIP) Session Policies References Referenced by |
Proposed Standard | normatively references | |
|
RFC 6794
As bcp98 |
A Framework for Session Initiation Protocol (SIP) Session Policies References Referenced by |
Proposed Standard | normatively references | |
| RFC 7329 |
A Session Identifier for the Session Initiation Protocol (SIP) References Referenced by |
Informational | normatively references | |
| RFC 7339 |
Session Initiation Protocol (SIP) Overload Control References Referenced by |
Proposed Standard | normatively references | |
|
RFC 7339
As bcp98 |
Session Initiation Protocol (SIP) Overload Control References Referenced by |
Proposed Standard | normatively references | |
| RFC 7463 |
Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR) References Referenced by |
Proposed Standard | normatively references | |
|
RFC 7463
As bcp98 |
Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR) References Referenced by |
Proposed Standard | normatively references | |
| RFC 8498 |
A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP) References Referenced by |
Informational | normatively references | |
|
RFC 8498
As bcp98 |
A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP) References Referenced by |
Informational | normatively references | |
| RFC 8606 |
ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field References Referenced by |
Proposed Standard | normatively references | |
|
RFC 8606
As bcp98 |
ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field References Referenced by |
Proposed Standard | normatively references | |
| RFC 8787 |
Location Source Parameter for the SIP Geolocation Header Field References Referenced by |
Proposed Standard | normatively references | |
|
RFC 8787
As bcp98 |
Location Source Parameter for the SIP Geolocation Header Field References Referenced by |
Proposed Standard | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
|
RFC 5226
As bcp98 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
| RFC 5727 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area References Referenced by |
Best Current Practice | informatively references | |
|
RFC 5727
As bcp98 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area References Referenced by |
Best Current Practice | informatively references | |
| RFC 5923 |
Connection Reuse in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
|
RFC 5923
As bcp98 |
Connection Reuse in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
|
RFC 5989
As bcp98 |
A SIP Event Package for Subscribing to Changes to an HTTP Resource References Referenced by |
Proposed Standard | informatively references | |
| RFC 6223 |
Indication of Support for Keep-Alive References Referenced by |
Proposed Standard | informatively references | |
|
RFC 6223
As bcp98 |
Indication of Support for Keep-Alive References Referenced by |
Proposed Standard | informatively references | |
| RFC 6665 |
SIP-Specific Event Notification References Referenced by |
Proposed Standard | informatively references | |
| RFC 6809 |
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
|
RFC 6809
As bcp98 |
Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | informatively references | |
| RFC 8055 |
Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm References Referenced by |
Proposed Standard | informatively references | |
|
RFC 8055
As bcp98 |
Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm References Referenced by |
Proposed Standard | informatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
|
RFC 8126
As bcp98 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
| RFC 8496 |
P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP) References Referenced by |
Informational | informatively references | |
| RFC 4485 |
Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP) References Referenced by |
Informational | Possible Reference | |
| RFC 4538 |
Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 5627 |
Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 6140 |
Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) References Referenced by |
Proposed Standard | Possible Reference |