Re: [Enum] FW: I-D ACTION:draft-hollenbeck-epp-e164-00.txt

Richard Shockey <rich.shockey@neustar.com> Tue, 21 August 2001 15:22 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20055 for <enum-archive@odin.ietf.org>; Tue, 21 Aug 2001 11:22:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26951; Tue, 21 Aug 2001 11:08:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26920 for <enum@ns.ietf.org>; Tue, 21 Aug 2001 11:08:09 -0400 (EDT)
Received: from dnspri.npac.com (dnspri.npac.com [208.143.33.66]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19197 for <enum@ietf.org>; Tue, 21 Aug 2001 11:06:53 -0400 (EDT)
Received: by dnspri.npac.com; id KAA00964; Tue, 21 Aug 2001 10:08:10 -0500 (CDT)
Received: from unknown(192.168.20.227) by dnspri.npac.com via smap (V5.0) id xmad00940; Tue, 21 Aug 01 10:07:52 -0500
Message-Id: <5.1.0.14.2.20010821105049.02d12d90@127.0.0.1>
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 21 Aug 2001 11:08:01 -0400
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, enum@ietf.org
From: Richard Shockey <rich.shockey@neustar.com>
Subject: Re: [Enum] FW: I-D ACTION:draft-hollenbeck-epp-e164-00.txt
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60B84C2@vsvapostal3.prod.ne tsol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

At 02:22 PM 8/20/2001 -0400, Hollenbeck, Scott wrote:
>In the spirit of the note Patrik sent earlier today, I've written the
>individual submission I-D described below.  It's intended to be a "stake in
>the ground" for discussion using example data derived from RFC 2916.
>
><Scott/>


And on behalf of my co-chair ..I'd like to thank you for the submission. 
This is indeed a useful contribution to thoughtful technical discussion of 
ENUM related issues.  However I would want to point out that the problem 
statement that this document addresses is a potential tool for ENUM 
provisioning between various entities that is specifically under the 
authority of national administrations of E.164 resources as outlined in 
RFC2916 in RFC 3026.

Though, of course, it could be used in private implementations of ENUM 
technology where applicable.

A note to list readers: Concepts outlined in this draft have been developed 
in the IETF provreg working group that is developing protocols for Domain 
Name registration.

http://www.ietf.org/html.charters/provreg-charter.html

>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
>         Title           : Extensible Provisioning Protocol E.164 Number
>Mapping
>         Author(s)       : S. Hollenbeck
>         Filename        : draft-hollenbeck-epp-e164-00.txt
>         Pages           : 39
>         Date            : 17-Aug-01
>
>This document describes an Extensible Provisioning Protocol (EPP)
>mapping for the provisioning and management of E.164 numbers stored in
>a shared central repository.  Specified in XML, the mapping defines
>EPP command syntax and semantics as applied to E.164 numbers.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-e164-00.txt
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-hollenbeck-epp-e164-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-hollenbeck-epp-e164-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>
>_______________________________________________
>enum mailing list
>enum@ietf.org
>http://www1.ietf.org/mailman/listinfo/enum


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
45980 Center Oak Plaza   Bldg 8     Sterling, VA  20166
1120 Vermont Ave NW Suite 400 Washington DC 20005
Voice 571.434.5651 Cell : 314.503.0640,  Fax: 815.333.1237
<mailto: rshockey@ix.netcom.com> or
<mailto: rich.shockey@neustar.com>
<http://www.neustar.com>
<http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


_______________________________________________
enum mailing list
enum@ietf.org
http://www1.ietf.org/mailman/listinfo/enum