FW: [Enum] Document Action: 'Infrastructure ENUM Requirements' to Informational RFC
"Richard Shockey" <richard@shockey.us> Tue, 18 September 2007 16:08 UTC
Return-path: <enum-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXfcu-0003JP-Cu; Tue, 18 Sep 2007 12:08:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXfcs-0003Iw-6u for enum@ietf.org; Tue, 18 Sep 2007 12:08:38 -0400
Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IXfcl-00035x-Pj for enum@ietf.org; Tue, 18 Sep 2007 12:08:38 -0400
Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l8IG80k1026771 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <enum@ietf.org>; Tue, 18 Sep 2007 09:08:02 -0700
From: Richard Shockey <richard@shockey.us>
To: enum@ietf.org
Subject: FW: [Enum] Document Action: 'Infrastructure ENUM Requirements' to Informational RFC
Date: Tue, 18 Sep 2007 12:07:49 -0400
Message-ID: <00d901c7fa0e$107074c0$31515e40$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acf6BUFCuoOcMj8pSHWvZAguUdgE9gACKvhw
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Errors-To: enum-bounces@ietf.org
For those of you who do not subscribe to the IETF Announce List. We can presume that the other documents in the series will receive prompt attention. -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: Friday, September 14, 2007 4:38 PM To: IETF-Announce Cc: enum mailing list; enum chair; Internet Architecture Board; RFC Editor Subject: [Enum] Document Action: 'Infrastructure ENUM Requirements' to Informational RFC The IESG has approved the following document: - 'Infrastructure ENUM Requirements ' <draft-ietf-enum-infrastructure-enum-reqs-04.txt> as an Informational RFC This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Jon Peterson and Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs -04.txt Technical Summary This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP. Because end user ENUM as defined in RFC 3761 requires end user opt-in and control of the location of the NAPTRs, it is not suitable for interconnection needs bu service providers. The requirements in the document are needed for the WG to develop a technical solution. Working Group Summary The working group reviewed this document in 2005-6 and was document NIT review preformed by Alexander Mayrhofer <axelm@nic.at> Protocol Quality This document was reviewed for the IESG by Jon Peterson. Gen-ART review was performed by Gonzalo Camarillo. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] Document Action: 'Infrastructure ENUM Requ… The IESG
- FW: [Enum] Document Action: 'Infrastructure ENUM … Richard Shockey