metasystema.org
CurrentINFORMATIONALIETF stream

RFC 3824: Using E.164 numbers with the Session Initiation Protocol (SIP)

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC3824
Published
June 2004
Authors
J. Peterson; H. Liu; J. Yu; B. Campbell
Status
INFORMATIONAL
Stream
IETF
Area
rai
Pages
16
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3824-using-e-164-numbers-with-the-session-initiation-protocol-sip