Richard Shockey | 3 Jun 2002 19:32

Re: EPP for E.164 - Start Last Call ???

At 09:14 AM 5/23/2002 -0700, you wrote:
>We want to bring to everyone's attention to the draft for provisioning 
>E.164 numbers using EPP in a registry 
>environment.

><http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt>http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt. 
>This draft was accepted as an ENUM working group item at the 53rd 
>IETF.  We would like to solicit comments for this draft so we can make 
>changes, if necessary, to the draft before the June 24th cut off date for 
>the 54th IETF in Japan.  We would like to move forward, as expediently as 
>possible, because the ENUM forum is very interested in having this draft 
>move to RFC before they adopt it into their provisioning process.

I'd like to re-note this message sent to the list earlier and poll the list 
for any objections to taking this to Last Call as a Informational document 
ASAP.

>

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
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 +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto: rshockey <at> ix.netcom.com> or
<mailto: rich.shockey <at> neustar.biz>
<http://www.neustar.biz>
<http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
(Continue reading)

Internet-Drafts | 4 Jun 2002 13:44
Picon
Favicon

I-D ACTION:draft-stastny-enum-scenarios-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: Scenarios for ENUM and ENUM-like Systems
	Author(s)	: R. Stastny
	Filename	: draft-stastny-enum-scenarios-00.txt
	Pages		: 18
	Date		: 03-Jun-02
	
This document analyzes scenarios for ENUM and ENUM-like Systems, both 
for ENUM used by End Users and also for ENUM-like Systems used by 
operators for network-specific or infrastructure purposes. It also 
gives some examples of ENUM Usage and proposes a new URI scheme to be 
used with ENUM. This may allow a way forward for the definition of 
ENUM Services and also for the definition of the required URIs and 
their parameters. 
This document therefore deals with information stored in the ENUM and 
the look-up process and the usage of the information retived in this 
look up process. 
It does not deal with the administrative process related to the 
population of the relevant zones.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-stastny-enum-scenarios-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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
(Continue reading)

Richard Shockey | 4 Jun 2002 16:12

Fwd: I-D ACTION:draft-stastny-enum-scenarios-00.txt


>To: IETF-Announce: ;
>CC: enum <at> ietf.org
>From: Internet-Drafts <at> ietf.org
>Reply-to: Internet-Drafts <at> ietf.org
>Date: Tue, 04 Jun 2002 07:44:13 -0400
>Subject: [Enum] I-D ACTION:draft-stastny-enum-scenarios-00.txt
>Sender: enum-admin <at> ietf.org
>X-Mailman-Version: 1.0
>List-Id: Enum Discussion List <enum.ietf.org>
>X-BeenThere: enum <at> ietf.org
>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : Scenarios for ENUM and ENUM-like Systems
>         Author(s)       : R. Stastny
>         Filename        : draft-stastny-enum-scenarios-00.txt
>         Pages           : 18
>         Date            : 03-Jun-02
>
>This document analyzes scenarios for ENUM and ENUM-like Systems, both
>for ENUM used by End Users and also for ENUM-like Systems used by
>operators for network-specific or infrastructure purposes. It also
>gives some examples of ENUM Usage and proposes a new URI scheme to be
>used with ENUM. This may allow a way forward for the definition of
>ENUM Services and also for the definition of the required URIs and
>their parameters.
>This document therefore deals with information stored in the ENUM and
(Continue reading)

Dave Crocker | 5 Jun 2002 17:49

Re: EPP for E.164 - Start Last Call ???

At 11:32 AM 6/3/2002 -0400, Richard Shockey wrote:
>I'd like to re-note this message sent to the list earlier and poll the 
>list for any objections to taking this to Last Call as a Informational 
>document ASAP.

EPP is IETF standards track.

ENUM is IETF standards track.

Why should not the use of ENUM for EPP also be standards track?

I believe it has sufficient utility and that it was developed and reviewed 
in the appropriate IETF manner.

d/

----------
Dave Crocker <mailto:dave <at> tribalwise.com>
TribalWise, Inc. <http://www.tribalwise.com>
tel +1.408.246.8253; fax +1.408.850.1850
Richard Shockey | 5 Jun 2002 19:15

Re: EPP for E.164 - Start Last Call ???

At 08:49 AM 6/5/2002 -0700, Dave Crocker wrote:
>At 11:32 AM 6/3/2002 -0400, Richard Shockey wrote:
>>I'd like to re-note this message sent to the list earlier and poll the 
>>list for any objections to taking this to Last Call as a Informational 
>>document ASAP.
>
>EPP is IETF standards track.
>
>ENUM is IETF standards track.
>
>Why should not the use of ENUM for EPP also be standards track?

Well my thinking was its just the data object without any real presentation 
of transport ..but your point is well taken ..

>I believe it has sufficient utility and that it was developed and reviewed 
>in the appropriate IETF manner.
>
>d/
>
>
>----------
>Dave Crocker <mailto:dave <at> tribalwise.com>
>TribalWise, Inc. <http://www.tribalwise.com>
>tel +1.408.246.8253; fax +1.408.850.1850

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
45980 Center Oak Plaza   Bldg 8     Sterling, VA  20166
(Continue reading)

Pfautz, Penn L, ALVAP | 5 Jun 2002 19:32
Picon
Favicon

RE: EPP for E.164 - Start Last Call ???

Richard:
While I'm generally supportive of the work to make use of EPP in ENUM provisioning, I have a couple of
potential concerns about the context in which it is used. These may prove insubstantial (I hope so) but I'd
like to offer them up anyway:

1. It's not entirely clear from the document what, if any, assumptions are being made about which
information flows in the ENUM provisioning process would make use of EPP. The Registry (Tier 1) -
Registrar interface seems the most likely candidate, but at least in the domestic USA ENUM Forum plan,
this would not require the NAPTR record objects, so I infer that Registrar - Tier 2 use is also
contemplated.  Can Scott or someone elese elaborate?

2. In the US ENUM Forum there has been some debate about what contact information the Tier 1 Registry would
actually have. EPP seems to assume a thick Registry  and I'm not sure there is agreement on this for ENUM. I'd
at least like to see some statements about contact objects being optional in the document.

Penn Pfautz
AT&T

-----Original Message-----
From: Richard Shockey [mailto:rich.shockey <at> neustar.com]
Sent: Monday, June 03, 2002 1:32 PM
To: enum <at> ietf.org
Subject: Re: [Enum] EPP for E.164 - Start Last Call ???

At 09:14 AM 5/23/2002 -0700, you wrote:
>We want to bring to everyone's attention to the draft for provisioning 
>E.164 numbers using EPP in a registry 
>environment.

><http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt>http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt. 
(Continue reading)

Hollenbeck, Scott | 5 Jun 2002 19:55
Picon
Favicon

RE: EPP for E.164 - Start Last Call ???

> -----Original Message-----
> From: Pfautz, Penn L, ALVAP [mailto:ppfautz <at> att.com]
> Sent: Wednesday, June 05, 2002 1:33 PM
> To: Richard Shockey; enum <at> ietf.org
> Subject: RE: [Enum] EPP for E.164 - Start Last Call ???
> 
> 
> Richard:
> While I'm generally supportive of the work to make use of EPP 
> in ENUM provisioning, I have a couple of potential concerns 
> about the context in which it is used. These may prove 
> insubstantial (I hope so) but I'd like to offer them up anyway:
> 
> 1. It's not entirely clear from the document what, if any, 
> assumptions are being made about which information flows in 
> the ENUM provisioning process would make use of EPP. The 
> Registry (Tier 1) - Registrar interface seems the most likely 
> candidate, but at least in the domestic USA ENUM Forum plan, 
> this would not require the NAPTR record objects, so I infer 
> that Registrar - Tier 2 use is also contemplated.  Can Scott 
> or someone elese elaborate?

I'd suggest that the scope is for any registry-registrar interface that
requires the provisioning of NAPTR information.  Maybe it's not needed for
the anticipated tier-1 situation in the US, but it's hardly safe to assume
that the same operating model holds world-wide.

> 2. In the US ENUM Forum there has been some debate about what 
> contact information the Tier 1 Registry would actually have. 
> EPP seems to assume a thick Registry  and I'm not sure there 
(Continue reading)

Richard Shockey | 5 Jun 2002 21:00

RE: EPP for E.164 - Start Last Call ???

At 01:32 PM 6/5/2002 -0400, Pfautz, Penn L, ALVAP wrote:
>Richard:
>While I'm generally supportive of the work to make use of EPP in ENUM 
>provisioning, I have a couple of potential concerns about the context in 
>which it is used. These may prove insubstantial (I hope so) but I'd like 
>to offer them up anyway:

I'm wondering if we should even be hinting at a transport here ...EPP is a 
transport mechanism I wondering how we can abstract this whole mechanism to 
things like SOAP etc.

Just a thought not a monkey wrench... its just that I see opportunities for 
provisioning using variety of mechanisms.

>1. It's not entirely clear from the document what, if any, assumptions are 
>being made about which information flows in the ENUM provisioning process 
>would make use of EPP. The Registry (Tier 1) - Registrar interface seems 
>the most likely candidate, but at least in the domestic USA ENUM Forum 
>plan, this would not require the NAPTR record objects, so I infer that 
>Registrar - Tier 2 use is also contemplated.  Can Scott or someone elese 
>elaborate?

Well my thought is that this document outlines a possible mechanism for T1 
- T2 data interchange using this data object ..but by no means the only one 
or the eventual dominant one we have markets for that ..which was one other 
reason I thought this might be better as Informational ..Penn ..what are 
your thoughts?

>2. In the US ENUM Forum there has been some debate about what contact 
>information the Tier 1 Registry would actually have. EPP seems to assume a 
(Continue reading)

Patrik Fältström | 5 Jun 2002 23:15
Picon
Favicon

RE: EPP for E.164 - Start Last Call ???

--On 2002-06-05 15.00 -0400 Richard Shockey <rich.shockey <at> NeuStar.com>
wrote:

> I'm wondering if we should even be hinting at a transport here ...EPP is
> a transport mechanism I wondering how we can abstract this whole
> mechanism to things like SOAP etc.

SOAP, I hate when getting it into my eyes ;-)

Joke aside, as wg co-chair I have heard from several parties they want to
be able to create registry/registrar systems passing "whatever" information
needed when creating thick or thin registries holding ENUM information.

No, I don't know if they mean with registry the party holding the NAPTR
record or the one delegating NS records for E.164 numbers.

What the goal is should be clear enough when reading the document, and if
it is not, that is not a general question, but issue which should be
addressed by the document editor(s).

    paf
Pfautz, Penn L, ALVAP | 7 Jun 2002 15:16
Picon
Favicon

RE: EPP for E.164 - Start Last Call ???

Looking over the draft-ietf-enum-epp-e164-00.txt and the other EPP I-Ds I've come to the following
conclusions which I'd like test others' agreement to since I'm not protocol wizard:

1. draft-ietf-enum-epp-e164-00.txt is just about provisioning of NAPTR records.
So from the  perspective of the US ENUM Forum, UKENUM, (and probably the ITU supplement )it has nothing to do
with the Registrar-Tier 1 Registry interface, but speaks more to a Registrar - Tier 2, Registrant - Tier 2,
or ASP - Tier 2 interface.

2. The functions defined in <draft-ietf-provreg-epp-domain-04.txt> are sufficient to handle
Registrar-Tier 1 Registry for ENUM as have been generally discussed e.g. in the some earlier I-Ds and in
the US ENUM Forum.

3. The hosts provisioned in Tier 1 will be external hosts (with a TLD different from that used for ENUM domain
names) and thus managed on a per-client (per Registrar) basis so there will be no issues with two different
Registrars registering differernt ENUM domain names that point to the same Tier 2 name server.

4. EPP allows a domain name to be registered without any name servers specified (although in this case it
can't get DNS service)

Penn Pfautz

Gmane