RFC 3762 on Telephone Number Mapping (ENUM) Service Registration for H.323
rfc-editor@rfc-editor.org Mon, 03 May 2004 12:21 UTC
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23611 for <ietf-announce-archive@odin.ietf.org>; Mon, 3 May 2004 08:21:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKcK0-0003jg-9o for ietf-announce-archive@odin.ietf.org; Mon, 03 May 2004 08:13:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43CDKGc014338 for ietf-announce-archive@odin.ietf.org; Mon, 3 May 2004 08:13:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKc2Q-0003Y4-1O; Mon, 03 May 2004 07:55:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJhyb-0004TK-8d for ietf-announce@optimus.ietf.org; Fri, 30 Apr 2004 20:03:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14371 for <ietf-announce@ietf.org>; Fri, 30 Apr 2004 20:03:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJhyZ-0004Oz-A1 for ietf-announce@ietf.org; Fri, 30 Apr 2004 20:03:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJhxs-0004Jn-00 for ietf-announce@ietf.org; Fri, 30 Apr 2004 20:02:45 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BJhx8-00048U-00; Fri, 30 Apr 2004 20:01:58 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4100fU08465; Fri, 30 Apr 2004 17:00:41 -0700 (PDT)
Message-Id: <200405010000.i4100fU08465@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3762 on Telephone Number Mapping (ENUM) Service Registration for H.323
Cc: rfc-editor@rfc-editor.org, enum@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 30 Apr 2004 17:00:41 -0700
X-ISI-4-28-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@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=-9.0 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3762 Title: Telephone Number Mapping (ENUM) Service Registration for H.323 Author(s): O. Levin Status: Standards Track Date: April 2004 Mailbox: oritl@microsoft.com Pages: 5 Characters: 8450 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-h323-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3762.txt The H.323 specification defines a means for building multimedia communication services over an arbitrary Packet Based Network, including the Internet. This document registers a Telephone Number Mapping (ENUM) service for H.323 according to specifications and guidelines in RFC 3761. This document is a product of the Telephone Number Mapping Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@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@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.