Using E.164 numbers with the Session Initiation Protocol
RFC 3824, “Using E.164 numbers with the Session Initiation Protocol”, is an Informational document published in June 2004 by J. Peterson, H. Liu, J. Yu, B. Campbell. The canonical text is published by the RFC Editor.
Abstract
There are a number of contexts in which telephone numbers are employed by Session Initiation Protocol (SIP) applications, many of which can be addressed by ENUM. Although SIP was one of the primary applications for which ENUM was created, there is nevertheless a need to define procedures for integrating ENUM with SIP implementations. This document illustrates how the two protocols might work in concert, and clarifies the authoring and processing of ENUM records for SIP applications. It also provides guidelines for instances in which ENUM, for whatever reason, cannot be used to resolve a telephone number. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3824 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3823 MIME Media Type for the Systems Biology Markup Language
- RFC 3825 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information
- RFC 3822 Finding Fibre Channel over TCP/IP Entities Using Service Location Protocol version 2
- RFC 3826 The Advanced Encryption Standard Cipher Algorithm in the SNMP User-based Security Model
- RFC 3821 Fibre Channel Over TCP/IP
- RFC 3827 Additional Snoop Datalink Types
- RFC 3820 Internet X.509 Public Key Infrastructure Proxy Certificate Profile
- RFC 3828 The Lightweight User Datagram Protocol