To: ietf-announce at ietf.org
From: rfc-editor at rfc-editor.org
Date: Tue, 29 Jun 2004 16:24:46 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed at isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.5 required=5.0 tests=AWL,BIZ_TLD,
MIME_BOUND_NEXTPART,NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no
version=2.60
Cc: sipping at ietf.org, rfc-editor at rfc-editor.org
Subject: [Sipping] RFC 3824 on Using E.164 numbers with the Session
Initiation Protocol (SIP)
X-BeenThere: sipping at ietf.org
X-Mailman-Version: 2.1.5
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
<mailto:sipping-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping at ietf.org>
List-Help: <mailto:sipping-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
<mailto:sipping-request at ietf.org?subject=subscribe>
Sender: sipping-bounces at ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 3824
Title: Using E.164 numbers with the Session Initiation
Protocol (SIP)
Author(s): J. Peterson, H. Liu, J. Yu, B. Campbell
Status: Informational
Date: June 2004
Mailbox: jon.peterson at neustar.biz, hong.liu at neustar.biz,
james.yu at neustar.biz, bcampbell at dynamicsoft.com
Pages: 16
Characters: 36535
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sipping-e164-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3824.txt
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 document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
Content-Type: text/plain
Content-ID: <040629161550.RFC at RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc3824
<ftp://ftp.isi.edu/in-notes/rfc3824.txt>
_______________________________________________
Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP