References to bcp98

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

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