References from rfc3666
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 11 |
The Organizations Involved in the IETF Standards Process 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 63 |
Session Initiation Protocol for Telephones (SIP-T): Context and Architectures Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2617 |
HTTP Authentication: Basic and Digest Access Authentication Refs Ref'd by |
Draft Standard | normatively references | Downref |
| RFC 2806 |
URLs for Telephone Calls Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 2916 |
E.164 number and DNS Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 3204 |
MIME media types for ISUP and QSIG Objects Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 3261 |
SIP: Session Initiation Protocol Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 3264 |
An Offer/Answer Model with Session Description Protocol (SDP) Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 3398 |
Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping Refs Ref'd by |
Proposed Standard | normatively references | Downref |
| RFC 3665 |
Session Initiation Protocol (SIP) Basic Call Flow Examples Refs Ref'd by |
Best Current Practice | informatively references |