References from rfc6140

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.

Reference type help

Document Title Status Type Downref
BCP 106 Randomness Requirements for Security
Refs Ref'd by
Best Current Practice informatively references
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 informatively references
BCP 98 The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
Refs Ref'd by
Best Current Practice normatively references
BCP 99 The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
Refs Ref'd by
Best Current Practice normatively references
RFC 2104 HMAC: Keyed-Hashing for Message Authentication
Refs Ref'd by
Informational normatively references Downref
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice Possible Reference
RFC 3261 SIP: Session Initiation Protocol
Refs Ref'd by
Proposed Standard informatively references
RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
Refs Ref'd by
Proposed Standard informatively references
RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification
Refs Ref'd by
Proposed Standard normatively references
RFC 3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
Refs Ref'd by
Proposed Standard informatively references
RFC 3608 Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
Refs Ref'd by
Proposed Standard informatively references
RFC 3680 A Session Initiation Protocol (SIP) Event Package for Registrations
Refs Ref'd by
Proposed Standard informatively references
RFC 3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard informatively references
RFC 3841 Caller Preferences for the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard informatively references
RFC 3966 The tel URI for Telephone Numbers
Refs Ref'd by
Proposed Standard informatively references
RFC 3968 The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
Refs Ref'd by
Best Current Practice Possible Reference
RFC 3969 The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
Refs Ref'd by
Best Current Practice Possible Reference
RFC 4086 Randomness Requirements for Security
Refs Ref'd by
Best Current Practice Possible Reference
RFC 4475 Session Initiation Protocol (SIP) Torture Test Messages
Refs Ref'd by
Informational informatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
Refs Ref'd by
Proposed Standard normatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
Refs Ref'd by
Proposed Standard informatively references
RFC 5626 Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard informatively references
RFC 5627 Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
Refs Ref'd by
Proposed Standard informatively references
RFC 5628 Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs)
Refs Ref'd by
Proposed Standard normatively 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 Possible Reference
RFC 5741 RFC Streams, Headers, and Boilerplates
Refs Ref'd by
Informational Possible Reference Possible Downref
RFC 5947 Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
Refs Ref'd by
Informational informatively references