References to RFC 2806
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 |
---|---|---|---|---|
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 3398 |
Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
References Referenced by |
Proposed Standard | normatively references | |
RFC 3666 |
Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows
References Referenced by |
Best Current Practice | normatively references | |
RFC 3824 |
Using E.164 numbers with the Session Initiation Protocol (SIP)
References Referenced by |
Informational | normatively references | |
RFC 3485 |
The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3601 |
Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses
References Referenced by |
Proposed Standard | informatively references | |
RFC 3939 |
Calling Line Identification for Voice Mail Messages
References Referenced by |
Proposed Standard | informatively references | |
RFC 3966 |
The tel URI for Telephone Numbers
References Referenced by |
Proposed Standard | informatively references | |
RFC 3795 |
Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
References Referenced by |
Informational | Possible Reference | |
RFC 2916 |
E.164 number and DNS
References Referenced by |
Proposed Standard | Reference |