References from rfc8599
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.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | informatively 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 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 3261 |
SIP: Session Initiation Protocol Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 3264 |
An Offer/Answer Model with Session Description Protocol (SDP) 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 | normatively references | |
| RFC 3891 |
The Session Initiation Protocol (SIP) "Replaces" Header Refs Ref'd by |
Proposed Standard | normatively references | |
| 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 | normatively references | |
| RFC 4320 |
Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 4321 |
Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction Refs Ref'd by |
Informational | informatively references | |
| RFC 5079 |
Rejecting Anonymous Requests 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 | informatively references | |
| RFC 6665 |
SIP-Specific Event Notification 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 | normatively references | |
| RFC 8030 |
Generic Event Delivery Using HTTP Push Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8291 |
Message Encryption for Web Push Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8292 |
Voluntary Application Server Identification (VAPID) for Web Push Refs Ref'd by |
Proposed Standard | normatively references |