
Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2RGr4d1009048 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 27 Mar 2002 17:53:04 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2RGr4dU009047 for ietf-provreg-outgoing; Wed, 27 Mar 2002 17:53:04 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from neteka.com ([66.48.4.181]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with SMTP id g2RGr3d1009042 for <ietf-provreg@cafax.se>; Wed, 27 Mar 2002 17:53:03 +0100 (MET)
Message-ID: <020501c1d5b0$27497350$6501a8c0@EDMON15>
From: "Edmon Chung" <edmon@neteka.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, <ietf-provreg@cafax.se>
References: <3CD14E451751BD42BA48AAA50B07BAD60189B864@vsvapostal3.bkup6>
Subject: Re: Revised PROVREG WG minutes - 53rd IETF
Date: Wed, 27 Mar 2002 11:55:08 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hi,
O... I got momentarily mixed up with implementation of the API with the epp
protocol commands.  My bad. ;-p
Edmon


----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Edmon Chung'" <edmon@neteka.com>; <ietf-provreg@cafax.se>
Sent: Wednesday, March 27, 2002 11:12 AM
Subject: RE: Revised PROVREG WG minutes - 53rd IETF


> > -----Original Message-----
> > From: Edmon Chung [mailto:edmon@neteka.com]
> > Sent: Wednesday, March 27, 2002 10:52 AM
> > To: Scott Rose; ietf-provreg@cafax.se
> > Subject: Re: Revised PROVREG WG minutes - 53rd IETF
> >
> >
> > Hi Scott,
> > Sorry I didnt respond to the minutes earlier.
> > At the Minneapolis meeting, I did talk about the SG implmentation.
> > Neteka is finalizing the EPP implementation at .sg to be
> > launched in May
> > 2002.
> > One of the issues we faced during the implementation was the
> > need to have
> > multiple statuses for a domain name.  In fact now that I
> > think more about
> > it, I believe this is probably an interesting enough topic that might
> > benefit to be added into the core documents.  The flexibility
> > for multiple
> > statuses means that additional EPP commands is needed to
> > add/delete/edit
> > statuses instead of simply updating the domain info.
> > thoughts everyone?
> > Edmon
>
> Objects like domains can already have multiple status values (several are
> already defined) at the same time, though some values are mutually
> exclusive.  I don't understand the problem as you've described it so
please
> provide more detail.
>
> -Scott-
>



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2RGCad1008842 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 27 Mar 2002 17:12:36 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2RGCadj008841 for ietf-provreg-outgoing; Wed, 27 Mar 2002 17:12:36 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2RGCYd1008836 for <ietf-provreg@cafax.se>; Wed, 27 Mar 2002 17:12:35 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id LAA24833; Wed, 27 Mar 2002 11:12:33 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <G5S3M5YR>; Wed, 27 Mar 2002 11:12:33 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B864@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Edmon Chung'" <edmon@neteka.com>, ietf-provreg@cafax.se
Subject: RE: Revised PROVREG WG minutes - 53rd IETF
Date: Wed, 27 Mar 2002 11:12:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> -----Original Message-----
> From: Edmon Chung [mailto:edmon@neteka.com]
> Sent: Wednesday, March 27, 2002 10:52 AM
> To: Scott Rose; ietf-provreg@cafax.se
> Subject: Re: Revised PROVREG WG minutes - 53rd IETF
> 
> 
> Hi Scott,
> Sorry I didnt respond to the minutes earlier.
> At the Minneapolis meeting, I did talk about the SG implmentation.
> Neteka is finalizing the EPP implementation at .sg to be 
> launched in May
> 2002.
> One of the issues we faced during the implementation was the 
> need to have
> multiple statuses for a domain name.  In fact now that I 
> think more about
> it, I believe this is probably an interesting enough topic that might
> benefit to be added into the core documents.  The flexibility 
> for multiple
> statuses means that additional EPP commands is needed to 
> add/delete/edit
> statuses instead of simply updating the domain info.
> thoughts everyone?
> Edmon

Objects like domains can already have multiple status values (several are
already defined) at the same time, though some values are mutually
exclusive.  I don't understand the problem as you've described it so please
provide more detail.

-Scott-


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2RFncd1008695 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 27 Mar 2002 16:49:38 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2RFncBd008694 for ietf-provreg-outgoing; Wed, 27 Mar 2002 16:49:38 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from neteka.com ([66.48.4.181]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with SMTP id g2RFnad1008687 for <ietf-provreg@cafax.se>; Wed, 27 Mar 2002 16:49:37 +0100 (MET)
Message-ID: <01d101c1d5a7$4cbcf070$6501a8c0@EDMON15>
From: "Edmon Chung" <edmon@neteka.com>
To: "Scott Rose" <scottr@antd.nist.gov>, <ietf-provreg@cafax.se>
References: <3CA1D502.53E71FD@antd.nist.gov>
Subject: Re: Revised PROVREG WG minutes - 53rd IETF
Date: Wed, 27 Mar 2002 10:51:45 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hi Scott,
Sorry I didnt respond to the minutes earlier.
At the Minneapolis meeting, I did talk about the SG implmentation.
Neteka is finalizing the EPP implementation at .sg to be launched in May
2002.
One of the issues we faced during the implementation was the need to have
multiple statuses for a domain name.  In fact now that I think more about
it, I believe this is probably an interesting enough topic that might
benefit to be added into the core documents.  The flexibility for multiple
statuses means that additional EPP commands is needed to add/delete/edit
statuses instead of simply updating the domain info.
thoughts everyone?
Edmon

----- Original Message -----
From: "Scott Rose" <scottr@antd.nist.gov>
To: <ietf-provreg@cafax.se>
Sent: Wednesday, March 27, 2002 9:19 AM
Subject: Revised PROVREG WG minutes - 53rd IETF


> I got everyone's comments, and made the corrections.  Here is the
> (final?) version of the minutes.  I will submit them to minutes@ietf.org
> by the end of the week.
>
> Thanks for the comments everyone,
> Scott Rose
>
>
>
> PROVREG Meeting minutes
> Taken by Scott Rose (scottr@nist.gov)
>
> 1. WG status (Ed Lewis)
>  - Core Documents:  In IESG process in various stages
>  - Other documents - no discussion
>  - 1 Unsolicited individual submission
>  - Next target:  move core drafts to draft standard as per RFC 2026
>    1.  Patrik F:  We need 2 independent client and 2 servers to test
> interop.
>     (all must work together)
>
>
> 2. Last Call Comments on EPP drafts (Scott Hollenbeck)
>  - Requirements Draft:
>   1. WG last call completed
>   2. Comments by IESG in Feb, completed in Feb.
>   3. Waiting IESG
>  - EPP core drafts
>   1. Last call ends 29 March - few comments for additions or corrections
>  - Questions
> Patrik:  IESG or AD has not received any more comments than those
> mentioned in the meeting.
>
>
> 3. In-process documents
>  - BEEP - new revision available in the future.
>   1. Comment:  Is anyone planning any implementation on this draft?
>  - Container draft - will not be continued.
>  - SMTP draft - Still being worked on (rumor).  Some interest in seeing
> this as a draft.
>  - Push feature draft - missing description document.  No one has
>    responsibility for that draft.  If Push feature is desired, please
> submit an
>    individual submission draft.
>
> 4. Implementations (about 5 )
>  - RTK (Sourceforge project) release Java version of registry tool
>   1. Different releases for different levels of EPP(draft revisions) -
> plan on
>      restructuring releases into one package
>  - Melbourne IT (for AusRegistry work) (B. Tonkin):  .au registry
> release (also a Sourceforge project).
>   1. Does contain implementation specific extensions (differs from .us
> extensions)
>   2. first country code to use EPP
>  - Verisign (S. Hollenbeck).
>   1. Non-core effort (smaller domains)  using EPP for registry
>   2. When EPP reaches RFC status, .com/net/org will go to EPP
>   3. Registry (Verisign) will not hold customer information/contact.
> That will still
>      reside at the registrar level.
>   4. All RRP based registration systems will eventually migrate to EPP
> once contract expires
>  - .sg registry
>   1. assumed that one status for domain name
>  - NIC Mexico (F. Arias):
>   1. looking at rolling EPP out.  But using other means to authenticate
> the registrant.  Either using the registrar and EPP (with some further
> security functionality like PKI) or some other authentication protocol
> (not relying on EPP).
>
> 5. Registry-specific extensions (H. Liu)
>  - .us TLD implementation for public review
>  - Informational - may not be WG draft, but informational as an
> extension to EPP.  Test to
>    see if EPP really is extensible and still remain interpretational.
>  - Differences from draft specs:
>   1. Collect NEXUS info for usTLD registration
>   2. 2 new parameters:  AppPurpose and NexusCatagory
>  - Alternatives:  Name-value pairs or new XML schema definition
>  - Comments:
>   1. Where scheme modified?  ContactObject extension field
>
> 6. Scott H.  draft on EPP and DNSSEC/ENUM an individual submission, but
> belongs/will
>    remain independent submission (not DNSEXT) and hoped to be
>    included in DNSOP WG
>  -
> http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-secdns-00.txt
>
> 7. Next Steps
>  - Need for a BCP/Informational RFC on how these extensions should
> look?
>   1. moved to list
>  - Interoperability test:  of core protocol specs, not extensions.
>   1. When:  wait until we get RFC status  -  winner
>  - No BEEP/SMTP comments
>
> General comments/questions
> 1. if we start talking about extensions - rechartering necessary?
> 2. Question of "status of command" request message - what it means and
> the status of the draft.
>    - Original poser of the question not present, so no further progress
> on debate could be made - Scott Hollenbeck gave some explination of the
> status of the draft (on hold).
>



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2REJXd1007982 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 27 Mar 2002 15:19:33 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2REJXAW007981 for ietf-provreg-outgoing; Wed, 27 Mar 2002 15:19:33 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from is1-50.antd.nist.gov (is1-50.antd.nist.gov [129.6.50.251]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2REJWd1007976 for <ietf-provreg@cafax.se>; Wed, 27 Mar 2002 15:19:32 +0100 (MET)
Received: from antd.nist.gov (lapdancer.antd.nist.gov [129.6.51.14]) by is1-50.antd.nist.gov (8.9.3/8.9.3) with ESMTP id JAA26462 for <ietf-provreg@cafax.se>; Wed, 27 Mar 2002 09:19:24 -0500 (EST)
Message-ID: <3CA1D502.53E71FD@antd.nist.gov>
Date: Wed, 27 Mar 2002 09:19:46 -0500
From: Scott Rose <scottr@antd.nist.gov>
Organization: NIST
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: Revised PROVREG WG minutes - 53rd IETF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I got everyone's comments, and made the corrections.  Here is the
(final?) version of the minutes.  I will submit them to minutes@ietf.org
by the end of the week.

Thanks for the comments everyone,
Scott Rose



PROVREG Meeting minutes
Taken by Scott Rose (scottr@nist.gov)
 
1. WG status (Ed Lewis)
 - Core Documents:  In IESG process in various stages
 - Other documents - no discussion
 - 1 Unsolicited individual submission
 - Next target:  move core drafts to draft standard as per RFC 2026
   1.  Patrik F:  We need 2 independent client and 2 servers to test
interop.  
    (all must work together)
 

2. Last Call Comments on EPP drafts (Scott Hollenbeck)
 - Requirements Draft: 
  1. WG last call completed
  2. Comments by IESG in Feb, completed in Feb.
  3. Waiting IESG
 - EPP core drafts
  1. Last call ends 29 March - few comments for additions or corrections
 - Questions
Patrik:  IESG or AD has not received any more comments than those
mentioned in the meeting.
 

3. In-process documents
 - BEEP - new revision available in the future.
  1. Comment:  Is anyone planning any implementation on this draft?
 - Container draft - will not be continued.
 - SMTP draft - Still being worked on (rumor).  Some interest in seeing
this as a draft.
 - Push feature draft - missing description document.  No one has 
   responsibility for that draft.  If Push feature is desired, please
submit an
   individual submission draft.  
 
4. Implementations (about 5 )
 - RTK (Sourceforge project) release Java version of registry tool 
  1. Different releases for different levels of EPP(draft revisions) -
plan on 
     restructuring releases into one package
 - Melbourne IT (for AusRegistry work) (B. Tonkin):  .au registry
release (also a Sourceforge project).  
  1. Does contain implementation specific extensions (differs from .us
extensions)
  2. first country code to use EPP
 - Verisign (S. Hollenbeck).
  1. Non-core effort (smaller domains)  using EPP for registry
  2. When EPP reaches RFC status, .com/net/org will go to EPP
  3. Registry (Verisign) will not hold customer information/contact. 
That will still 
     reside at the registrar level.
  4. All RRP based registration systems will eventually migrate to EPP
once contract expires
 - .sg registry
  1. assumed that one status for domain name
 - NIC Mexico (F. Arias):  
  1. looking at rolling EPP out.  But using other means to authenticate
the registrant.  Either using the registrar and EPP (with some further
security functionality like PKI) or some other authentication protocol
(not relying on EPP).
 
5. Registry-specific extensions (H. Liu)
 - .us TLD implementation for public review
 - Informational - may not be WG draft, but informational as an
extension to EPP.  Test to 
   see if EPP really is extensible and still remain interpretational.
 - Differences from draft specs:
  1. Collect NEXUS info for usTLD registration
  2. 2 new parameters:  AppPurpose and NexusCatagory
 - Alternatives:  Name-value pairs or new XML schema definition
 - Comments:
  1. Where scheme modified?  ContactObject extension field  
 
6. Scott H.  draft on EPP and DNSSEC/ENUM an individual submission, but
belongs/will 
   remain independent submission (not DNSEXT) and hoped to be
   included in DNSOP WG
 -
http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-secdns-00.txt
 
7. Next Steps
 - Need for a BCP/Informational RFC on how these extensions should
look?  
  1. moved to list
 - Interoperability test:  of core protocol specs, not extensions.
  1. When:  wait until we get RFC status  -  winner
 - No BEEP/SMTP comments
 
General comments/questions
1. if we start talking about extensions - rechartering necessary?
2. Question of "status of command" request message - what it means and
the status of the draft.
   - Original poser of the question not present, so no further progress
on debate could be made - Scott Hollenbeck gave some explination of the
status of the draft (on hold).


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2NG8Kd1015955 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 23 Mar 2002 17:08:20 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2NG8JaT015954 for ietf-provreg-outgoing; Sat, 23 Mar 2002 17:08:19 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2NG8Id1015949 for <ietf-provreg@cafax.se>; Sat, 23 Mar 2002 17:08:19 +0100 (MET)
Received: from 208-58-208-87.s87.tnt2.annp.md.dialup.rcn.com ([208.58.208.87]) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.33 #10) id 16oo41-0007iF-00; Sat, 23 Mar 2002 11:08:17 -0500
X-Sender: lewis@pop.tislabs.com (Unverified)
Message-Id: <v03130300b8c14159b090@[166.63.190.161]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 22 Mar 2002 15:17:59 -0500
To: ietf-provreg@cafax.se
From: Edward Lewis <lewis@tislabs.com>
Subject: Containers
Cc: lewis@tislabs.com
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

During the meeting at Minneapolis it became apparent that no one in the
room, including the editors of the document, continues to support the
document.  The question before the list is, should work on the containers
draft continue AND are the interested parties willing to take on the
editorship responsibilities?

Unless someone speaks up positively, the draft will be removed as a WG item
sometime before the next IETF meeting.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

Opinions expressed are property of my evil twin, not my employer.




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2LCavd1004137 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 21 Mar 2002 13:36:57 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2LCavm2004136 for ietf-provreg-outgoing; Thu, 21 Mar 2002 13:36:57 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2LCatd1004131 for <ietf-provreg@cafax.se>; Thu, 21 Mar 2002 13:36:56 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id HAA22853; Thu, 21 Mar 2002 07:36:53 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <G5S3J0SJ>; Thu, 21 Mar 2002 07:36:53 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B82C@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Daniel Manley'" <dmanley@tucows.com>, ietf-provreg@cafax.se
Subject: RE: DCP
Date: Thu, 21 Mar 2002 07:36:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> -----Original Message-----
> From: Daniel Manley [mailto:dmanley@tucows.com]
> Sent: Wednesday, March 20, 2002 6:35 PM
> To: ietf-provreg@cafax.se
> Subject: DCP
> 
> 
> Hi everyone,
> 
> I was curious which registries plan on implementing DCP in 
> the EPP greeting?

It's still TBD in com/net/org.  We're still doing our product planning and
requirements analysis to support the development effort.

-Scott-


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KNa7d1000864 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 21 Mar 2002 00:36:07 +0100 (MET)
Received: by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2KNa632000863 for ietf-provreg-outgoing; Thu, 21 Mar 2002 00:36:06 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nyc02.smtp.stsn.com (p8.usnyc1.stsn.com [199.106.216.8]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KNa5d1000858 for <ietf-provreg@cafax.se>; Thu, 21 Mar 2002 00:36:06 +0100 (MET)
Received: from tucows.com ([10.0.227.247]) by nyc02.smtp.stsn.com with Microsoft SMTPSVC(5.0.2195.3779); Wed, 20 Mar 2002 18:42:19 -0700
Message-ID: <3C991CB4.7040903@tucows.com>
Date: Wed, 20 Mar 2002 17:35:16 -0600
From: Daniel Manley <dmanley@tucows.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9) Gecko/20020311
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: DCP
References: <3C99134D.9DD2E26F@antd.nist.gov>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Mar 2002 01:42:19.0125 (UTC) FILETIME=[A33AE250:01C1D079]
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hi everyone,

I was curious which registries plan on implementing DCP in the EPP greeting?

Dan





Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KNX4d1000840 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 21 Mar 2002 00:33:04 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2KNX34Y000839 for ietf-provreg-outgoing; Thu, 21 Mar 2002 00:33:03 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KNWsd1000834 for <ietf-provreg@cafax.se>; Thu, 21 Mar 2002 00:32:54 +0100 (MET)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g2KNSBI23003; Wed, 20 Mar 2002 18:28:11 -0500 (EST) (envelope-from brunner@nic-naa.net)
Message-Id: <200203202328.g2KNSBI23003@nic-naa.net>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: Scott Rose <scottr@antd.nist.gov>
cc: ietf-provreg@cafax.se, brunner@nic-naa.net
Subject: Re: Minn provreg meeting notes 
In-Reply-To: Message from Scott Rose <scottr@antd.nist.gov>  of "Wed, 20 Mar 2002 17:55:09 EST." <3C99134D.9DD2E26F@antd.nist.gov> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 20 Mar 2002 18:28:11 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

thanks scott. normally that's "gov't inaction".



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KMtXd1000638 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 20 Mar 2002 23:55:33 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2KMtXHb000637 for ietf-provreg-outgoing; Wed, 20 Mar 2002 23:55:33 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from noc-e.ietf53.cw.net (noc-e.ietf53.cw.net [166.63.177.40]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2KMtMd1000629 for <ietf-provreg@cafax.se>; Wed, 20 Mar 2002 23:55:32 +0100 (MET)
Received: from antd.nist.gov (wireless-dhcp-187-130.ietf53.cw.net [166.63.187.130]) by noc-e.ietf53.cw.net (Postfix) with ESMTP id C06EE6A90E for <ietf-provreg@cafax.se>; Wed, 20 Mar 2002 16:55:21 -0600 (CST)
Message-ID: <3C99134D.9DD2E26F@antd.nist.gov>
Date: Wed, 20 Mar 2002 17:55:09 -0500
From: Scott Rose <scottr@antd.nist.gov>
Organization: NIST
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: Minn provreg meeting notes
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Here's the first draft of the meeting minutes from the PROVREG WG. 
Please send any corrections/comments to me.  If none, the minutes will
be submitted to the meeting proceedings.

Gov't in action ;-)
Scott R.

************************************************************************
Provreg Meeting minutes
 
1. WG status (Ed Lewis)
 - Core Documents:  In IESG process in various stages
 - Other documents - no discussion
 - 1 Unsolicited individual submission
 - Next target:  move core drafts to draft standard as per RFC 2026
   1.  Patrik F:  We need 2 independent client and 2 servers to test
interop.  
    (all must work together)
 

2. Last Call Comments on EPP drafts (Scott Hollenbeck)
 - Requirements Draft: 
  1. WG last call completed
  2. Comments by IESG in Feb, completed in Feb.
  3. Waiting IESG
 - EPP core drafts
  1. Last call ends 29 March - few comments for additions or corrections
 - Questions
Patrik:  IESG or AD has not received any more comments than those
mentioned in the meeting.
 

3. In-process documents
 - BEEP - new revision available in the future.
  1. Comment:  Is anyone planning any implementation on this draft?
 - Container draft - will not be continued.
 - SMTP draft - Still being worked on (rumor).  Some interest in seeing
this as a draft.
 - Push feature draft - missing description document.  No one has 
   responsibility for that draft.  If Push feature is desired, please
submit an
   individual submission draft.  
 
4. Implementations (about 5 )
 - RTK (Sourceforge project) release Java version of registry tool 
  1. Different releases for different levels of EPP(draft revisions) -
plan on 
     restructuring releases into one package
 - Nominum:  .au registry release.  
  1. Adding different extensions than listed in draft
  2. first country code to use EPP
 - Verisign
  1. Non-core effort (smaller domains)  using EPP for registry
  2. When EPP reaches RFC status, .com/net/org will go to EPP
  3. Registry (Verisign) will not hold customer information/contact. 
That will still 
     reside at the registrar level.
  4. All RRP based registration systems will eventually migrate to EPP
once contract expires
 - .sg registry
  1. assumed that one status for domain name
 - NIC Mexico:  
  1. looking at rolling EPP out.  But using other means to authenticate
registrar-registrar 
     communication
 
5. Registry-specific extensions (H. Liu)
 - .us TLD implementation for public review
 - Informational - may not be WG draft, but informational as an
extension to EPP.  Test to 
   see if EPP really is extensible and still remain interpretational.
 - Differences from draft specs:
  1. Collect NEXUS info for usTLD registration
  2. 2 new parameters:  AppPurpose and NexusCatagory
 - Alternatives:  Name-value pairs or new XML schema definition
 - Comments:
  1. Where scheme modified?  ContactObject extension field  
 
6. Scott H.  draft on EPP and DNSSEC/ENUM an individual submission, but
belongs/will 
   remain independent submission (not DNSEXT) and hoped to be
   included in DNSOP WG
 -
http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-secdns-00.txt
 
7. Next Steps
 - Need for a BCP/Informational RFC on how these extensions should
look?  
  1. moved to list
 - Interoperability test:  of core protocol specs, not extensions.
  1. When:  wait until we get RFC status  -  winner
 - No BEEP/SMTP comments
 
General comments/questions
1. if we start talking about extensions - rechartering necessary?
2. Question of "status of command" request message - what it means and
the status of the draft.
   - Author not present, so no formal answer available.


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CLeq2N015282 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 12 Mar 2002 22:40:52 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2CLeqbk015281 for ietf-provreg-outgoing; Tue, 12 Mar 2002 22:40:52 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CLep2N015276 for <ietf-provreg@cafax.se>; Tue, 12 Mar 2002 22:40:51 +0100 (MET)
Received: by sentry.gw.tislabs.com; id QAA06612; Tue, 12 Mar 2002 16:46:24 -0500 (EST)
Received: from dhcp1.netsec.tislabs.com(199.171.39.21) by sentry.gw.tislabs.com via smap (V5.5) id xma006598; Tue, 12 Mar 02 16:46:03 -0500
X-Sender: lewis@pop.tislabs.com
Message-Id: <v03130305b8b425ee94d3@[199.171.39.21]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 12 Mar 2002 16:39:52 -0500
To: agenda@ietf.org, ietf-provreg@cafax.se
From: Edward Lewis <lewis@tislabs.com>
Subject: Provreg agenda for Minneapolis
Cc: lewis@tislabs.com
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

1 WG status (Ed Lewis)

2 Last Call Comments (Scott Hollenbeck)
http://www.ietf.org/internet-drafts/draft-ietf-provreg-grrp-reqs-06.txt
  and
http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00026.html
  referring to the following
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-domain-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-host-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-contact-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-tcp-04.txt

3 In Process Documents (Authors of those)
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-beep-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-container-01.txt

4 Implementations (Few minutes from those wanting to report)

5 Registry-Specific Extensions (Hong Liu)
http://www.ietf.org/internet-drafts/draft-liu-epp-ustld-00.txt

6 WG Next Steps
Discussion...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

Do you have the time to listen to me whine
About nothing and everything all at once?
-- Green Day ("Basket Case")

Opinions expressed are property of my evil twin, not my employer.




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CCm02N013084 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 12 Mar 2002 13:48:00 +0100 (MET)
Received: by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2CCm0Ie013083 for ietf-provreg-outgoing; Tue, 12 Mar 2002 13:48:00 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CClx2N013078 for <ietf-provreg@cafax.se>; Tue, 12 Mar 2002 13:47:59 +0100 (MET)
Received: by sentry.gw.tislabs.com; id HAA24039; Tue, 12 Mar 2002 07:53:33 -0500 (EST)
Received: from dhcp1.netsec.tislabs.com(199.171.39.21) by sentry.gw.tislabs.com via smap (V5.5) id xma024030; Tue, 12 Mar 02 07:53:28 -0500
X-Sender: lewis@pop.tislabs.com
Message-Id: <v03130300b8b3a8bd33d8@[208.58.209.74]>
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60189B7C6@vsvapostal3.bkup6>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 12 Mar 2002 07:45:45 -0500
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
From: Edward Lewis <lewis@tislabs.com>
Subject: RE: Agenda?
Cc: "'Edward Lewis'" <lewis@tislabs.com>, ietf-provreg@cafax.se
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Good Sugggestion...that should be #6 on the agenda.

At 9:28 PM -0500 3/11/02, Hollenbeck, Scott wrote:
>Ed,
>
>Maybe we ought to spend some time discussing "next steps"?  Should we
>declare victory and go home assuming the last call docs advance, or are
>there other things to do with interop testing, docs for the address
>registries etc?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

Do you have the time to listen to me whine
About nothing and everything all at once?
-- Green Day ("Basket Case")

Opinions expressed are property of my evil twin, not my employer.




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CCfM2N013039 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 12 Mar 2002 13:41:22 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2CCfMHP013038 for ietf-provreg-outgoing; Tue, 12 Mar 2002 13:41:22 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2CCfL2N013033 for <ietf-provreg@cafax.se>; Tue, 12 Mar 2002 13:41:21 +0100 (MET)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g2CHe8Z06495; Tue, 12 Mar 2002 12:40:08 -0500 (EST) (envelope-from brunner@nic-naa.net)
Message-Id: <200203121740.g2CHe8Z06495@nic-naa.net>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
cc: "'Edward Lewis'" <lewis@tislabs.com>, ietf-provreg@cafax.se, brunner@nic-naa.net
Subject: Re: Agenda? 
In-Reply-To: Your message of "Mon, 11 Mar 2002 21:28:15 EST." <3CD14E451751BD42BA48AAA50B07BAD60189B7C6@vsvapostal3.bkup6> 
Date: Tue, 12 Mar 2002 12:40:07 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> Maybe we ought to spend some time discussing "next steps"?  Should we
> declare victory and go home assuming the last call docs advance, or are

works for me. we know we're not going to get consensus on:

	o transport other than conection-oriented, synchronous,
	o event/state model other than client-server,
	o abstractions or groupings of operations,
	o national requirements,
	o other

> there other things to do with interop testing,

not strictly required, as a process issue. the existing installed base
appears to have exhausted this requirement, not to mention themselves.

>                                                docs for the address
> registries etc?

upon mature reflection, i think i erred in thinking that this wg could
meet the RIR and dependent needs. there's a lot of generic tld industry
explicit and implicit conditions in what we've managed to accomplish,
reflecting the material interests of the core contributors.

recently in another venue i've been confronted by the assumption that
this wg would be the natural place for key word provisioning to go. for
some values of "key word systems", the material conditions (r-star roles,
costs, etc.) are similar to (replicate or incorporate) the icann domain
name registration industry, but not the national domain name registries.

in theory, yeah, its just state with a aaa model ... this wg could make
a thing as generally useful as nfs or beep or ldap, but ...

in practice oil and water. gtlds and cctlds do not mix. tlds and slds do
not mix. domains and addresses do not mix. domains and keywords probably
should not mix (to their mutual benefit, not to mention the iesg).

i suggest we return all non-LC'd drafts to their authors as individual
submissions, wind down, and let the r-star players go their merry ways.

declare victory, go home, works for me.
eric


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2C2SQ2N011616 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 12 Mar 2002 03:28:26 +0100 (MET)
Received: by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2C2SQi4011615 for ietf-provreg-outgoing; Tue, 12 Mar 2002 03:28:26 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2C2SP2N011610 for <ietf-provreg@cafax.se>; Tue, 12 Mar 2002 03:28:25 +0100 (MET)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id VAA24458; Mon, 11 Mar 2002 21:28:23 -0500 (EST)
Received: by vsvapostalgw1.bkup1 with Internet Mail Service (5.5.2653.19) id <GGQ3LL75>; Mon, 11 Mar 2002 21:28:23 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B7C6@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Edward Lewis'" <lewis@tislabs.com>, ietf-provreg@cafax.se
Subject: RE: Agenda?
Date: Mon, 11 Mar 2002 21:28:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Ed,

Maybe we ought to spend some time discussing "next steps"?  Should we
declare victory and go home assuming the last call docs advance, or are
there other things to do with interop testing, docs for the address
registries etc?

-Scott-

> -----Original Message-----
> From: Edward Lewis [mailto:lewis@tislabs.com]
> Sent: Monday, March 11, 2002 3:21 PM
> To: ietf-provreg@cafax.se
> Cc: lewis@tislabs.com
> Subject: Agenda?
> 
> 
> In lieu of a more formal agenda, I propose this one.
> 
> 1 WG status (Ed Lewis)
> 2 Last Call Comments (Scott Hollenbeck)
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-grrp-re
> qs-06.txt
>   and
> http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00026.html
>   referring to the following
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-06.txt
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-dom
> ain-04.txt
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-host-04.txt
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-con
> tact-04.txt
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-tcp-04.txt
> 3 In Process Documents (Authors of those)
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-beep-01.txt
> http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-con
> tainer-01.txt
> 4 Implementations (Few minutes from those wanting to report)
> 5 Registry-Specific Extensions (Hong Liu)
> http://www.ietf.org/internet-drafts/draft-liu-epp-ustld-00.txt
> 
> If I don't hear from anyone, I'll send this to agenda@ tomorrow.
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis                                                NAI Labs
> Phone: +1 443-259-2352                      Email: lewis@tislabs.com
> 
> Do you have the time to listen to me whine
> About nothing and everything all at once?
> -- Green Day ("Basket Case")
> 
> Opinions expressed are property of my evil twin, not my employer.
> 


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2BKM22N009535 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 11 Mar 2002 21:22:02 +0100 (MET)
Received: by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g2BKM2Qu009534 for ietf-provreg-outgoing; Mon, 11 Mar 2002 21:22:02 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g2BKM12N009529 for <ietf-provreg@cafax.se>; Mon, 11 Mar 2002 21:22:01 +0100 (MET)
Received: by sentry.gw.tislabs.com; id PAA11500; Mon, 11 Mar 2002 15:27:35 -0500 (EST)
Received: from dhcp1.netsec.tislabs.com(199.171.39.21) by sentry.gw.tislabs.com via smap (V5.5) id xma011485; Mon, 11 Mar 02 15:26:36 -0500
X-Sender: lewis@pop.tislabs.com
Message-Id: <v03130306b8b2bff2b565@[199.171.39.21]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 11 Mar 2002 15:21:12 -0500
To: ietf-provreg@cafax.se
From: Edward Lewis <lewis@tislabs.com>
Subject: Agenda?
Cc: lewis@tislabs.com
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

In lieu of a more formal agenda, I propose this one.

1 WG status (Ed Lewis)
2 Last Call Comments (Scott Hollenbeck)
http://www.ietf.org/internet-drafts/draft-ietf-provreg-grrp-reqs-06.txt
  and
http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00026.html
  referring to the following
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-domain-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-host-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-contact-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-tcp-04.txt
3 In Process Documents (Authors of those)
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-beep-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-container-01.txt
4 Implementations (Few minutes from those wanting to report)
5 Registry-Specific Extensions (Hong Liu)
http://www.ietf.org/internet-drafts/draft-liu-epp-ustld-00.txt

If I don't hear from anyone, I'll send this to agenda@ tomorrow.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

Do you have the time to listen to me whine
About nothing and everything all at once?
-- Green Day ("Basket Case")

Opinions expressed are property of my evil twin, not my employer.




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g292k3ni027971 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 9 Mar 2002 03:46:03 +0100 (MET)
Received: by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g292k3Je027970 for ietf-provreg-outgoing; Sat, 9 Mar 2002 03:46:03 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g292k1ni027965 for <ietf-provreg@cafax.se>; Sat, 9 Mar 2002 03:46:01 +0100 (MET)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id VAA07269; Fri, 8 Mar 2002 21:45:30 -0500 (EST)
Received: by vsvapostalgw1.bkup1 with Internet Mail Service (5.5.2653.19) id <GGQ3JWF3>; Fri, 8 Mar 2002 21:45:29 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B7B5@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'iesg@ietf.org'" <iesg@ietf.org>
Cc: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: Some EPP Last Call Comments
Date: Fri, 8 Mar 2002 21:45:23 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

After the provreg WG's EPP documents finished WG last call, but before the
IESG's last call was issued, I received word of a few defects that should be
fixed and also a few requests for additions.  Here are links to the comments
made publicly, and text for those I received privately:

1. Category: Fix
http://www.cafax.se/ietf-provreg/maillist/2002-02/msg00032.html

In the epp-06 schema, this:

<element name="clTRID" type="epp:trIDStatusType"
 minOccurs="0"/>

should be changed to this:

<element name="clTRID" type="epp:trIDStatusType"
 minOccurs="0" maxOccurs="unbounded"/>

This will allow more than one element as described in the text.

2. Category: Fix
http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00004.html

In the domain-04 schema, this element in the <info> response:

<element name="registrant" type="domain:contactType"
 minOccurs="0"/>

should be changed to this:

<element name="registrant" type="eppcom:clIDType"
 minOccurs="0"/>

This will make the data type correct in the <info> response.

3. Category: Requested Additions
http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00006.html

A request to add an additional response code, additional statuses, and
explanatory text.

4. Category: Fix and Requested Addition
http://www.cafax.se/ietf-provreg/maillist/2002-03/msg00013.html

A fix to increase the length of the contact-04 postal code field from 10 to
16 characters, and a request to add an OPTIONAL field to better help explain
server error conditions.

5. Category: Documentation
I received a private suggestion to number document paragraphs that describe
elements in addition to indenting them to better help identify parent-child
relationships.

6. Category: Requested Addition
Patrik suggested a modification to the object <authInfo> structure such that
authentication mechanisms other than passwords could be defined in the
future without requiring change to an existing schema.  This can be done by
changing the <authInfo> data types slightly to accommodate namespace
extensions.

-Scott-


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28NPuni026556 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 9 Mar 2002 00:25:56 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g28NPuTJ026555 for ietf-provreg-outgoing; Sat, 9 Mar 2002 00:25:56 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from bean.ar.com (bean.ar.com [66.123.187.68]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28NPsni026550 for <ietf-provreg@cafax.se>; Sat, 9 Mar 2002 00:25:55 +0100 (MET)
Received: from flash.ar.com (wessorh@flash [66.123.187.80]) by bean.ar.com (8.12.2/8.12.0) with ESMTP id g28NPq1x025022; Fri, 8 Mar 2002 15:25:52 -0800 (PST)
Date: Fri, 8 Mar 2002 15:25:52 -0800 (PST)
From: Rick Wesson <wessorh@ar.com>
To: Patrick <patrick@stealthgeeks.net>
cc: Olafur Osvaldsson <oli@isnic.is>, James Woods <jwoods@netstormmedia.com>, <ietf-provreg@cafax.se>
Subject: Re: Open Source Server Implementation
In-Reply-To: <20020308151505.Y56842-100000@rockstar.stealthgeeks.net>
Message-ID: <Pine.LNX.4.33.0203081524590.29189-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

basic fusion puchaed by new.net ?!?

see
http://www.prnewswire.com/cgi-bin/micro_stories.pl?ACCT=156973&TICK=NEWN&STORY=/www/story/02-28-2002/0001677927&EDATE=Feb%2B28,%2B2002


-rick

On Fri, 8 Mar 2002, Patrick wrote:

> On Fri, 8 Mar 2002, Olafur Osvaldsson wrote:
>
> >
> >
> > On Mon, 07 Jan 2002, James Woods wrote:
> >
> > > Hi Scott,
> > >
> > > We have two EPP implementation services that we plan to launch soon,
> > > (the openess is under debate right now but I think I'll win this one ;)
> > > one is a modified client (ala GUI) called CuteEPP the other EPPserv.
> > > Regardless of whether these get "opened" or not our dev team would love
> > > to hook up with others wishing to do so.
> > >
> >
> > Any news on this, did you win?  :)
>
> They(Basic Fusion) got bought.
>
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>                                Patrick Greenwell
>          Asking the wrong questions is the leading cause of wrong answers
> \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
>



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28NFWni026502 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 9 Mar 2002 00:15:32 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g28NFWrZ026501 for ietf-provreg-outgoing; Sat, 9 Mar 2002 00:15:32 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from rockstar.stealthgeeks.net (h-66-134-120-173.LSANCA54.covad.net [66.134.120.173]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with SMTP id g28NFUni026496 for <ietf-provreg@cafax.se>; Sat, 9 Mar 2002 00:15:30 +0100 (MET)
Received: (qmail 56871 invoked by uid 1001); 8 Mar 2002 23:15:29 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Mar 2002 23:15:29 -0000
Date: Fri, 8 Mar 2002 15:15:29 -0800 (PST)
From: Patrick <patrick@stealthgeeks.net>
To: Olafur Osvaldsson <oli@isnic.is>
cc: James Woods <jwoods@netstormmedia.com>, <ietf-provreg@cafax.se>
Subject: Re: Open Source Server Implementation
In-Reply-To: <20020308215212.A50431@isnic.is>
Message-ID: <20020308151505.Y56842-100000@rockstar.stealthgeeks.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

On Fri, 8 Mar 2002, Olafur Osvaldsson wrote:

>
>
> On Mon, 07 Jan 2002, James Woods wrote:
>
> > Hi Scott,
> >
> > We have two EPP implementation services that we plan to launch soon,
> > (the openess is under debate right now but I think I'll win this one ;)
> > one is a modified client (ala GUI) called CuteEPP the other EPPserv.
> > Regardless of whether these get "opened" or not our dev team would love
> > to hook up with others wishing to do so.
> >
>
> Any news on this, did you win?  :)

They(Basic Fusion) got bought.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
                               Patrick Greenwell
         Asking the wrong questions is the leading cause of wrong answers
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28LqHni026185 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 8 Mar 2002 22:52:17 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g28LqHM7026184 for ietf-provreg-outgoing; Fri, 8 Mar 2002 22:52:17 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from amun.isnic.is (amun.isnic.is [193.4.58.10]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28LqGni026179 for <ietf-provreg@cafax.se>; Fri, 8 Mar 2002 22:52:16 +0100 (MET)
Received: from amun.isnic.is (oli@localhost.isnic.is [127.0.0.1]) by amun.isnic.is (8.12.2/8.12.1/isnic) with ESMTP id g28LqDvt055972; Fri, 8 Mar 2002 21:52:14 GMT (envelope-from oli@amun.isnic.is)
Received: (from oli@localhost) by amun.isnic.is (8.12.2/8.12.1/Submit) id g28LqDLf055969; Fri, 8 Mar 2002 21:52:13 GMT (envelope-from oli)
Date: Fri, 8 Mar 2002 21:52:13 +0000
From: Olafur Osvaldsson <oli@isnic.is>
To: James Woods <jwoods@netstormmedia.com>
Cc: ietf-provreg@cafax.se
Subject: Re: Open Source Server Implementation
Message-ID: <20020308215212.A50431@isnic.is>
References: <3CD14E451751BD42BA48AAA50B07BAD60189B509@vsvapostal3.bkup6> <003f01c197cc$279b3450$6501a8c0@deltaflyer>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <003f01c197cc$279b3450$6501a8c0@deltaflyer>; from jwoods@netstormmedia.com on Mon, Jan 07, 2002 at 05:39:23PM -0500
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

On Mon, 07 Jan 2002, James Woods wrote:

> Hi Scott,
> 
> We have two EPP implementation services that we plan to launch soon,
> (the openess is under debate right now but I think I'll win this one ;)
> one is a modified client (ala GUI) called CuteEPP the other EPPserv.
> Regardless of whether these get "opened" or not our dev team would love
> to hook up with others wishing to do so.
> 

Any news on this, did you win?  :)

	Oli

-- 
Olafur Osvaldsson
Systems Administrator
Internet a Islandi hf.
Tel:   +354 525-5291
Email: oli@isnic.is


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28KTJni025854 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 8 Mar 2002 21:29:19 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g28KTJA5025853 for ietf-provreg-outgoing; Fri, 8 Mar 2002 21:29:19 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28KTHni025848 for <ietf-provreg@cafax.se>; Fri, 8 Mar 2002 21:29:18 +0100 (MET)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01886; Fri, 8 Mar 2002 15:29:14 -0500 (EST)
Message-Id: <200203082029.PAA01886@ietf.org>
To: IETF-Announce: ;
Cc: ietf-provreg@cafax.se
From: The IESG <iesg-secretary@ietf.org>
SUBJECT: Last Call: Extensible Provisioning Protocol to Proposed Standard
Reply-to: iesg@ietf.org
Date: Fri, 08 Mar 2002 15:29:14 -0500
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

The IESG has received a request from the Provisioning Registry Protocol
Working Group to consider publication of the following Internet-Drafts
as Proposed Standards:

 o Extensible Provisioning Protocol
	<draft-ietf-provreg-epp-06.txt> 
 o Extensible Provisioning Protocol Domain Name Mapping
	<draft-ietf-provreg-epp-domain-04.txt>
 o Extensible Provisioning Protocol Host Mapping
	<draft-ietf-provreg-epp-host-04.txt> 
 o Extensible Provisioning Protocol Contact Mapping
	<draft-ietf-provreg-epp-contact-04.txt>
 o Extensible Provisioning Protocol Transport Over TCP
	<draft-ietf-provreg-epp-tcp-04.txt>

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by March 29, 2002.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-domain-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-host-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-contact-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-provreg-epp-tcp-04.txt




Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28D2Jni023704 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 8 Mar 2002 14:02:19 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g28D2JaY023703 for ietf-provreg-outgoing; Fri, 8 Mar 2002 14:02:19 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g28D2Ini023698 for <ietf-provreg@cafax.se>; Fri, 8 Mar 2002 14:02:18 +0100 (MET)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g28I0BW23128; Fri, 8 Mar 2002 13:00:11 -0500 (EST) (envelope-from brunner@nic-naa.net)
Message-Id: <200203081800.g28I0BW23128@nic-naa.net>
To: "Liu, Hong" <Hong.Liu@neustar.biz>
cc: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, brunner@nic-naa.net
Subject: Re: Additional Response Code and Status Code for EPP 
In-Reply-To: Your message of "Mon, 04 Mar 2002 15:03:55 CST." <23309E398D84D5119D0F00306E07513901181B18@dc02.npac.com> 
Date: Fri, 08 Mar 2002 13:00:11 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This seems appropos, from the Portland Pattern Repository (de facto home
of the extreme programming discipline), hosted by Cunningham & Cunningham.

	"Life's too short to write code that nobody wants."

I'm not going to put conditional in my implementation, either there exists
a right-to-publish (register) or there exists a right-to-retract (modify).

Conditional completions (keywords: speculation,lottery,lazy evaluation)
are for those who have the requirment. It isn't general, and shouldn't
be in EPP.

Eric


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g27LgXni020186 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 22:42:33 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g27LgXoc020185 for ietf-provreg-outgoing; Thu, 7 Mar 2002 22:42:33 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from mail.libertyrms.com ([66.46.52.34]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g27LgVni020180 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 22:42:32 +0100 (MET)
Received: from [10.1.1.80] (helo=dun49) by mail.libertyrms.com with esmtp (Exim 3.22 #3 (Debian)) id 16j5eX-0002Ye-00; Thu, 07 Mar 2002 16:42:21 -0500
Reply-To: <myoung@libertyrms.info>
From: "Michael Young" <myoung@libertyrms.info>
To: "'Daniel Manley'" <dmanley@tucows.com>, <ietf-provreg@cafax.se>
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 16:42:41 -0500
Organization: Liberty RMS
Message-ID: <012d01c1c621$020c8580$5001010a@dun49>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <3C87C9A3.6000001@tucows.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I agree with Dan in that registrars are always well-advised to improve
their level of quality control (as is everyone), but I believe firmly
that the availibility of an optional tag such as this is going to help
that process immensely.  In view of someone who operates a registry, I
believe we could do a much better job of helping the registrars be
successful with this option.  At the end of the day we are here to help
registrars regardless; it would only make it faster and easier for
everyone if we can feed them more meaningful information on their errors
in the first place.  

Michael Young
myoung@libertyrms.info



-----Original Message-----
From: owner-ietf-provreg@cafax.se [mailto:owner-ietf-provreg@cafax.se]
On Behalf Of Daniel Manley
Sent: Thursday, March 07, 2002 3:12 PM
To: ietf-provreg@cafax.se
Subject: Re: Some More Off-List Comments


Is all this extra information really needed?  Registrars should be 
validating as much information as possible before sending to the 
registry.  This would weed out 95% of problem data.  To now add reasons 
to values makes the registry hold the registrar's hand where the 
registrar should be smarter than your average registrant.  All of this 
user-friendliness also adds more development burden on the registry.

Dan


Hollenbeck, Scott wrote:

>>-----Original Message-----
>>From: Daniel Manley [mailto:dmanley@tucows.com]
>>Sent: Thursday, March 07, 2002 2:38 PM
>>To: Hollenbeck, Scott
>>Cc: 'lynettek@netnumber.com'; ietf-provreg@cafax.se
>>Subject: Re: Some More Off-List Comments
>>
>>
>>Shouldn't the "reason" tie in with the array of <values>?
>>Because each 
>>field could have a different reason.
>>
>
>Sure, I suppose it could.
>
>-Scott-
>






Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g27LEHni020059 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 22:14:17 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0/Submit) id g27LEHYU020058 for ietf-provreg-outgoing; Thu, 7 Mar 2002 22:14:17 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.3.Beta0/8.12.3.Beta0) with ESMTP id g27LEGni020053 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 22:14:16 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id QAA16832; Thu, 7 Mar 2002 16:14:15 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJXRQV>; Thu, 7 Mar 2002 16:14:15 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD601E2C06D@vsvapostal3.bkup6>
From: "Gould, James" <JGould@verisign.com>
To: ietf-provreg@cafax.se, "'Daniel Manley'" <dmanley@tucows.com>
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 16:14:10 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Yes, this extra information is needed.  Many errors generated by the server
business logic are mapped to the EPP result codes, but that is not enough
information for a Registrar or CSR to track down the exact reason for the
error.  If the server knows what caused the error (i.e. "Credit limit has
been exceeded", "foo.com is reserved", "Must have admin contact")
it would be helpful for it to be able to return the reason to the client.
This will save calls to CSR's with errors that are obvious 
from the reason.  The reason can be made optional, so there should be no
impact to existing implementations, and by adding it a substantial amount of
effort will be saved in handling Registrar issues.  

Jim

> ----------
> From: 	Daniel Manley
> Sent: 	Thursday, March 7, 2002 3:12 PM
> To: 	ietf-provreg@cafax.se
> Subject: 	Re: Some More Off-List Comments
> 
> Is all this extra information really needed?  Registrars should be 
> validating as much information as possible before sending to the 
> registry.  This would weed out 95% of problem data.  To now add reasons 
> to values makes the registry hold the registrar's hand where the 
> registrar should be smarter than your average registrant.  All of this 
> user-friendliness also adds more development burden on the registry.
> 
> Dan
> 
> 
> Hollenbeck, Scott wrote:
> 
> >>-----Original Message-----
> >>From: Daniel Manley [mailto:dmanley@tucows.com]
> >>Sent: Thursday, March 07, 2002 2:38 PM
> >>To: Hollenbeck, Scott
> >>Cc: 'lynettek@netnumber.com'; ietf-provreg@cafax.se
> >>Subject: Re: Some More Off-List Comments
> >>
> >>
> >>Shouldn't the "reason" tie in with the array of <values>?  
> >>Because each 
> >>field could have a different reason.
> >>
> >
> >Sure, I suppose it could.
> >
> >-Scott-
> >
> 
> 
> 


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K8lSQ015230 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 21:08:47 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27K8ldp015229 for ietf-provreg-outgoing; Thu, 7 Mar 2002 21:08:47 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K8kSQ015224 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 21:08:46 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id PAA12939; Thu, 7 Mar 2002 15:08:44 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJXQD9>; Thu, 7 Mar 2002 15:08:44 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD601E2C06C@vsvapostal3.bkup6>
From: "Gould, James" <JGould@verisign.com>
To: "'Daniel Manley'" <dmanley@tucows.com>, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc: ietf-provreg@cafax.se
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 15:08:39 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I would prefer a less complex alternative of having a freeform "reason" per
error result and not per error value.  Since an error response can contain
multiple error results, and each error result can reference multiple error
element tag/values, it would be simpler to have the "reason" an element of
the error result.  Multiple error results can be used to satisfy the error
reporting requirements.  

Jim

> ----------
> From: 	Hollenbeck, Scott
> Sent: 	Thursday, March 7, 2002 2:36 PM
> To: 	'Daniel Manley'
> Cc: 	ietf-provreg@cafax.se
> Subject: 	RE: Some More Off-List Comments
> 
> > -----Original Message-----
> > From: Daniel Manley [mailto:dmanley@tucows.com]
> > Sent: Thursday, March 07, 2002 2:38 PM
> > To: Hollenbeck, Scott
> > Cc: 'lynettek@netnumber.com'; ietf-provreg@cafax.se
> > Subject: Re: Some More Off-List Comments
> > 
> > 
> > Shouldn't the "reason" tie in with the array of <values>?  
> > Because each 
> > field could have a different reason.
> 
> Sure, I suppose it could.
> 
> -Scott-
> 
> 


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K5bSQ015209 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 21:05:37 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g27K5bQU015208 for ietf-provreg-outgoing; Thu, 7 Mar 2002 21:05:37 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from balsa.cetp.ipsl.fr (balsa.cetp.ipsl.fr [193.52.172.32]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K5aSQ015203 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 21:05:36 +0100 (MET)
Received: (from porteneu@localhost) by balsa.cetp.ipsl.fr (8.9.3+Sun/8.9.1) id VAA02889; Thu, 7 Mar 2002 21:03:45 +0100 (MET)
Date: Thu, 7 Mar 2002 21:03:45 +0100 (MET)
From: Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>
Message-Id: <200203072003.VAA02889@balsa.cetp.ipsl.fr>
To: ietf-provreg@cafax.se, lampson@iaregistry.com, shollenbeck@verisign.com
Subject: RE: Some More Off-List Comments
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

The French rules for writing postal address are normalized,
cf. AFNOR XP Z 10-011, May 1997 so called norme 38.
In short:
   6 lignes maximum  
  38 characters maximum per line (including spaces)

The exemple with instructions is given at:
http://preproduction.laposte.fr/sna/saisie/saisiepart.asp

Yes, indeed we have Cedex indications.
Usually Cedex follows city name, something like
        75982 PARIS CEDEX 20
and is NOT a ZIP code
More instructions at:
http://www.laposte.fr/produits/courrier/code.htm

And yes, indeed our ZIP code is on the left side
of the city name - like in almost all continental Europe.

You may note that some European countries add a country prefix
to their ZIP code, but unfortunately this prefix seems
car's plates based, therefore not universal.
It would be much better postal services use ISO 3166-1,
like bank do in their IBAN - International Bank Account Number,
but it is another debate.

I am in favor of 16 characters for ZIP area, rather than 10.
And for postal address respecting countrie's rules
- looking on IANA content for ccTLD is just making me nervous.

Elisabeth Porteneuve
--


-------Original Message---------------------------------------------
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Mike Lampson'" <lampson@iaregistry.com>,
        "'ietf-provregcafaxse'"
	 <ietf-provreg@cafax.se>
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 10:56:51 -0500 

> -----Original Message-----
> From: Mike Lampson [mailto:lampson@iaregistry.com]
> Sent: Thursday, March 07, 2002 10:46 AM
> To: Hollenbeck Scott; 'ietf-provregcafaxse'
> Subject: Re: Some More Off-List Comments
> 
> 
> Scott,
> 
> The Universal Postal Union only lists 5 digit postal codes 
> for both France
> and Mexico.

[snip]

FWIW here's the text of the comment I received from Asbjorn Stiera; I don't
think he'll mind me forwarding it to provide context:

"according to a postcode site (1), Mexico allows a 13 digit postal code 
for their "bulk mail code". In addition, in France it is not uncommon to 
append "CEDEX" to the postcode "for business adresses with special 
delivery arrangements" (1)(2), meaning a French post code can 
potentially have 11 digits (5+" "+5)."

I didn't see these possibilities mentioned on the UPU site, though.

> P.S. Without knowing the specific needs (and future changes) of postal
> identifiers used throughout the world, I would say that a 16 
> character limit
> sounds better than 10.

That was part of Asbjorn's argument as well.

-Scott-

(1)
http://www.magma.ca/~djcl/postcd.txt

(2)
http://www.faqs.org/faqs/culture-french-faq/miscellaneous/section-2.html



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K1QSQ015191 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 21:01:26 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27K1Pj8015190 for ietf-provreg-outgoing; Thu, 7 Mar 2002 21:01:25 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from toronto.mail.tucows.com (toronto.mail.tucows.com [207.136.98.42]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27K1OSQ015185 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 21:01:24 +0100 (MET)
Received: from dmanley.pc.internal.tucows.com ([10.0.10.19] helo=tucows.com) by toronto.mail.tucows.com with esmtp (Exim 3.20 #2) id 16j44q-00029m-00 for ietf-provreg@cafax.se; Thu, 07 Mar 2002 15:01:24 -0500
Message-ID: <3C87C9A3.6000001@tucows.com>
Date: Thu, 07 Mar 2002 15:12:19 -0500
From: Daniel Manley <dmanley@tucows.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020212
X-Accept-Language: en-us
MIME-Version: 1.0
To: ietf-provreg@cafax.se
Subject: Re: Some More Off-List Comments
References: <3CD14E451751BD42BA48AAA50B07BAD60189B7AC@vsvapostal3.bkup6>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Is all this extra information really needed?  Registrars should be 
validating as much information as possible before sending to the 
registry.  This would weed out 95% of problem data.  To now add reasons 
to values makes the registry hold the registrar's hand where the 
registrar should be smarter than your average registrant.  All of this 
user-friendliness also adds more development burden on the registry.

Dan


Hollenbeck, Scott wrote:

>>-----Original Message-----
>>From: Daniel Manley [mailto:dmanley@tucows.com]
>>Sent: Thursday, March 07, 2002 2:38 PM
>>To: Hollenbeck, Scott
>>Cc: 'lynettek@netnumber.com'; ietf-provreg@cafax.se
>>Subject: Re: Some More Off-List Comments
>>
>>
>>Shouldn't the "reason" tie in with the array of <values>?  
>>Because each 
>>field could have a different reason.
>>
>
>Sure, I suppose it could.
>
>-Scott-
>





Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27JaVSQ014956 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 20:36:31 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27JaVn9014955 for ietf-provreg-outgoing; Thu, 7 Mar 2002 20:36:31 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27JaUSQ014950 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 20:36:30 +0100 (MET)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id OAA11068; Thu, 7 Mar 2002 14:36:29 -0500 (EST)
Received: by vsvapostalgw1.bkup1 with Internet Mail Service (5.5.2653.19) id <GGQ323M7>; Thu, 7 Mar 2002 14:36:28 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B7AC@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Daniel Manley'" <dmanley@tucows.com>
Cc: ietf-provreg@cafax.se
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 14:36:18 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> -----Original Message-----
> From: Daniel Manley [mailto:dmanley@tucows.com]
> Sent: Thursday, March 07, 2002 2:38 PM
> To: Hollenbeck, Scott
> Cc: 'lynettek@netnumber.com'; ietf-provreg@cafax.se
> Subject: Re: Some More Off-List Comments
> 
> 
> Shouldn't the "reason" tie in with the array of <values>?  
> Because each 
> field could have a different reason.

Sure, I suppose it could.

-Scott-


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27JR9SQ014914 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 20:27:09 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27JR9Sl014913 for ietf-provreg-outgoing; Thu, 7 Mar 2002 20:27:09 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from toronto.mail.tucows.com (toronto.mail.tucows.com [207.136.98.42]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27JR3SQ014908 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 20:27:03 +0100 (MET)
Received: from dmanley.pc.internal.tucows.com ([10.0.10.19] helo=tucows.com) by toronto.mail.tucows.com with esmtp (Exim 3.20 #2) id 16j3XQ-0008OS-00; Thu, 07 Mar 2002 14:26:52 -0500
Message-ID: <3C87C18B.4070700@tucows.com>
Date: Thu, 07 Mar 2002 14:37:47 -0500
From: Daniel Manley <dmanley@tucows.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020212
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
CC: "'lynettek@netnumber.com'" <lynettek@netnumber.com>, ietf-provreg@cafax.se
Subject: Re: Some More Off-List Comments
References: <3CD14E451751BD42BA48AAA50B07BAD60189B7A7@vsvapostal3.bkup6>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Shouldn't the "reason" tie in with the array of <values>?  Because each 
field could have a different reason.

Dan


Hollenbeck, Scott wrote:

>The <msg> element is used to carry only a specified set of response messages
>used to describe the response codes.  As it was explained to me, the
><reason> element would be optional, and could be used to provide additional
>info that would help a client understand why an error occurred.
>
>For example, if an error response of 2306 (Parameter value policy error) is
>returned, the <msg> element would carry "Parameter value policy error" and
>the <reason> element could be used to explain exactly what the policy
>violation is.  This should be helpful both for clients who are trying to
>understand what went wrong and customer service folks on the server side who
>might have to help debug client problems.
>
>-Scott-
>
>>-----Original Message-----
>>From: Lynette Khirallah [mailto:lynettek@netnumber.com]
>>Sent: Thursday, March 07, 2002 1:58 PM
>>To: 'Hollenbeck, Scott'; ietf-provreg@cafax.se
>>Subject: RE: Some More Off-List Comments
>>
>>
>>is there already a <msg> element in the <result> that is 
>>being used for
>>human-readable error condition explanations? I just checked the latest
>>contact draft and there is a <msg> element in the <result>. 
>>How is this
>><reason> element any different from <msg>?
>>If you do add another text element, can it be optional?
>>
>>thanks,
>>Lynette
>>





Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27J5KSQ014798 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 20:05:20 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27J5KMF014797 for ietf-provreg-outgoing; Thu, 7 Mar 2002 20:05:20 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27J5DSQ014792 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 20:05:14 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id OAA09355; Thu, 7 Mar 2002 14:05:11 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJXPAF>; Thu, 7 Mar 2002 14:05:11 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B7A7@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'lynettek@netnumber.com'" <lynettek@netnumber.com>, ietf-provreg@cafax.se
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 14:05:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

The <msg> element is used to carry only a specified set of response messages
used to describe the response codes.  As it was explained to me, the
<reason> element would be optional, and could be used to provide additional
info that would help a client understand why an error occurred.

For example, if an error response of 2306 (Parameter value policy error) is
returned, the <msg> element would carry "Parameter value policy error" and
the <reason> element could be used to explain exactly what the policy
violation is.  This should be helpful both for clients who are trying to
understand what went wrong and customer service folks on the server side who
might have to help debug client problems.

-Scott-

> -----Original Message-----
> From: Lynette Khirallah [mailto:lynettek@netnumber.com]
> Sent: Thursday, March 07, 2002 1:58 PM
> To: 'Hollenbeck, Scott'; ietf-provreg@cafax.se
> Subject: RE: Some More Off-List Comments
> 
> 
> is there already a <msg> element in the <result> that is 
> being used for
> human-readable error condition explanations? I just checked the latest
> contact draft and there is a <msg> element in the <result>. 
> How is this
> <reason> element any different from <msg>?
> If you do add another text element, can it be optional?
> 
> thanks,
> Lynette


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27IvXSQ014758 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 19:57:33 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27IvWiH014757 for ietf-provreg-outgoing; Thu, 7 Mar 2002 19:57:33 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from hvmta02-stg.us.psimail.psi.net (hvmta02-ext.us.psimail.psi.net [38.202.36.30]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27IvQSQ014752 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 19:57:31 +0100 (MET)
Received: from lynettek ([65.203.166.34]) by hvmta02-stg.us.psimail.psi.net (InterMail vM.4.01.02.17 201-229-119) with SMTP id <20020307185724.BXHS1238.hvmta02-stg.us.psimail.psi.net@lynettek>; Thu, 7 Mar 2002 13:57:24 -0500
Reply-To: <lynettek@netnumber.com>
From: "Lynette Khirallah" <lynettek@netnumber.com>
To: "'Hollenbeck, Scott'" <shollenbeck@verisign.com>, <ietf-provreg@cafax.se>
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 13:58:01 -0500
Message-ID: <005e01c1c60a$01a5f2f0$22a6cb41@netnumber.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60189B79D@vsvapostal3.bkup6>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

is there already a <msg> element in the <result> that is being used for
human-readable error condition explanations? I just checked the latest
contact draft and there is a <msg> element in the <result>. How is this
<reason> element any different from <msg>?
If you do add another text element, can it be optional?

thanks,
Lynette

> -----Original Message-----
> From: owner-ietf-provreg@cafax.se
> [mailto:owner-ietf-provreg@cafax.se]On
> Behalf Of Hollenbeck, Scott
> Sent: Thursday, March 07, 2002 9:26 AM
> To: 'ietf-provreg@cafax.se'
> Subject: Some More Off-List Comments
>
>
> I've received a few more comments for protocol
> fixes/improvements off-list.
> I intend to send these to the IESG when they open the last call:
>
> - Increase the length of the contact postal code field to 16
> characters
> because postal codes longer than 10 characters (the current limit) are
> possible in some countries, such as Mexico and France.  Perhaps list
> participants living or working in those countries can confirm?
>
> - Add a child "reason" text element to the <result> element
> so that error
> conditions can be explained more fully in a server-defined,
> human-readable
> way.
>
> -Scott-



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27FuvSQ013925 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 16:56:57 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g27FuvkY013924 for ietf-provreg-outgoing; Thu, 7 Mar 2002 16:56:57 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27FuuSQ013919 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 16:56:56 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id KAA28619; Thu, 7 Mar 2002 10:56:54 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJXK4W>; Thu, 7 Mar 2002 10:56:54 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B79E@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Mike Lampson'" <lampson@iaregistry.com>, "'ietf-provregcafaxse'" <ietf-provreg@cafax.se>
Subject: RE: Some More Off-List Comments
Date: Thu, 7 Mar 2002 10:56:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> -----Original Message-----
> From: Mike Lampson [mailto:lampson@iaregistry.com]
> Sent: Thursday, March 07, 2002 10:46 AM
> To: Hollenbeck Scott; 'ietf-provregcafaxse'
> Subject: Re: Some More Off-List Comments
> 
> 
> Scott,
> 
> The Universal Postal Union only lists 5 digit postal codes 
> for both France
> and Mexico.

[snip]

FWIW here's the text of the comment I received from Asbjorn Stiera; I don't
think he'll mind me forwarding it to provide context:

"according to a postcode site (1), Mexico allows a 13 digit postal code 
for their "bulk mail code". In addition, in France it is not uncommon to 
append "CEDEX" to the postcode "for business adresses with special 
delivery arrangements" (1)(2), meaning a French post code can 
potentially have 11 digits (5+" "+5)."

I didn't see these possibilities mentioned on the UPU site, though.

> P.S. Without knowing the specific needs (and future changes) of postal
> identifiers used throughout the world, I would say that a 16 
> character limit
> sounds better than 10.

That was part of Asbjorn's argument as well.

-Scott-

(1)
http://www.magma.ca/~djcl/postcd.txt

(2)
http://www.faqs.org/faqs/culture-french-faq/miscellaneous/section-2.html


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27FjxSQ013835 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 16:45:59 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g27FjxoD013834 for ietf-provreg-outgoing; Thu, 7 Mar 2002 16:45:59 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from smtp02.infoave.net (smtp02.infoave.net [165.166.0.27]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27FjwSQ013829 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 16:45:58 +0100 (MET)
Received: from ML ([165.166.145.85]) by SMTP00.InfoAve.Net (PMDF V6.0-25 #38780) with SMTP id <01KF2REH6CTG9KNFPC@SMTP00.InfoAve.Net> for ietf-provreg@cafax.se; Thu, 07 Mar 2002 10:45:39 -0500 (EST)
Date: Thu, 07 Mar 2002 10:45:37 -0500
From: Mike Lampson <lampson@iaregistry.com>
Subject: Re: Some More Off-List Comments
To: Hollenbeck Scott <shollenbeck@verisign.com>, "'ietf-provregcafaxse'" <ietf-provreg@cafax.se>
Message-id: <005a01c1c5ef$2099f1e0$5591a6a5@IS.INFOAVE.NET>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <3CD14E451751BD42BA48AAA50B07BAD60189B79D@vsvapostal3.bkup6>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Scott,

The Universal Postal Union only lists 5 digit postal codes for both France
and Mexico.  Note that the UPU also indicates placement of postal codes when
sending mail.  These 2 countries both place their postal code to the left of
the locality.

Start here:
  http://www.upu.int/publications/en/post_code.shtml
and click on "Addressing formats" to look up information for a specific
country.

Regards,

Mike Lampson
The Registry at Info Avenue, LLC

P.S. Without knowing the specific needs (and future changes) of postal
identifiers used throughout the world, I would say that a 16 character limit
sounds better than 10.


----- Original Message -----
From: "Hollenbeck Scott" <shollenbeck@verisign.com>
To: "'ietf-provregcafaxse'" <ietf-provreg@cafax.se>
Sent: Thursday, March 07, 2002 9:26 AM
Subject: Some More Off-List Comments


I've received a few more comments for protocol fixes/improvements off-list.
I intend to send these to the IESG when they open the last call:

- Increase the length of the contact postal code field to 16 characters
because postal codes longer than 10 characters (the current limit) are
possible in some countries, such as Mexico and France.  Perhaps list
participants living or working in those countries can confirm?

- Add a child "reason" text element to the <result> element so that error
conditions can be explained more fully in a server-defined, human-readable
way.

-Scott-



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27EQESQ013450 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 7 Mar 2002 15:26:14 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g27EQEvR013449 for ietf-provreg-outgoing; Thu, 7 Mar 2002 15:26:14 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g27EQCSQ013444 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 15:26:13 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id JAA23099 for <ietf-provreg@cafax.se>; Thu, 7 Mar 2002 09:26:11 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJX2RW>; Thu, 7 Mar 2002 09:26:11 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B79D@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: Some More Off-List Comments
Date: Thu, 7 Mar 2002 09:26:06 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I've received a few more comments for protocol fixes/improvements off-list.
I intend to send these to the IESG when they open the last call:

- Increase the length of the contact postal code field to 16 characters
because postal codes longer than 10 characters (the current limit) are
possible in some countries, such as Mexico and France.  Perhaps list
participants living or working in those countries can confirm?

- Add a child "reason" text element to the <result> element so that error
conditions can be explained more fully in a server-defined, human-readable
way.

-Scott-


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25J3mSQ002986 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 5 Mar 2002 20:03:48 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g25J3mPC002985 for ietf-provreg-outgoing; Tue, 5 Mar 2002 20:03:48 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25J3lSQ002978 for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 20:03:47 +0100 (MET)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g2601hW08441; Tue, 5 Mar 2002 19:01:43 -0500 (EST) (envelope-from brunner@nic-naa.net)
Message-Id: <200203060001.g2601hW08441@nic-naa.net>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
cc: "'Roger Castillo Cortazar'" <castillo@nic.mx>, ietf-provreg@cafax.se, brunner@nic-naa.net
Subject: Re: EPP schemas and example XML instances. 
In-Reply-To: Message from "Hollenbeck, Scott" <shollenbeck@verisign.com>  of "Tue, 05 Mar 2002 13:35:38 EST." <3CD14E451751BD42BA48AAA50B07BAD60189B77A@vsvapostal3.bkup6> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 05 Mar 2002 19:01:43 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

> I think Eric Brunner-Williams also has them on an ftp site, but I'll let him
> speak to that if he so chooses.

yup.

ftp://nic-naa.net/pub/epp-ta
user=anonymous, password=<your email is a courtesy>
in pub/epp-ta:
-rw-r--r--  1 1000  0  10485 Jan 26 00:28 epp-06.tar.gz



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25IZhSQ002832 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 5 Mar 2002 19:35:43 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g25IZhVq002831 for ietf-provreg-outgoing; Tue, 5 Mar 2002 19:35:43 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25IZfSQ002826 for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 19:35:42 +0100 (MET)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id NAA14675; Tue, 5 Mar 2002 13:35:40 -0500 (EST)
Received: by vsvapostalgw1.bkup1 with Internet Mail Service (5.5.2653.19) id <GGQ3GK7J>; Tue, 5 Mar 2002 13:35:39 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B77A@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Roger Castillo Cortazar'" <castillo@nic.mx>, ietf-provreg@cafax.se
Subject: RE: EPP schemas and example XML instances.
Date: Tue, 5 Mar 2002 13:35:38 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I have two places available:

http://www.verisign-grs.com/files/

and

ftp://ftp.verisign.com/pub/epp/

I think Eric Brunner-Williams also has them on an ftp site, but I'll let him
speak to that if he so chooses.

-Scott-

> -----Original Message-----
> From: Roger Castillo Cortazar [mailto:castillo@nic.mx]
> Sent: Tuesday, March 05, 2002 1:03 PM
> To: ietf-provreg@cafax.se
> Subject: EPP schemas and example XML instances.
> 
> 
> Hi everybody.
> 
> Where can I get EPP schemas and example XML instances ?
> I've been trynig the ftp sites mentioned in a message from 
> last year, ;-)
> but my ftp client freezes.


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25I3xSQ002729 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 5 Mar 2002 19:03:59 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g25I3xZr002728 for ietf-provreg-outgoing; Tue, 5 Mar 2002 19:03:59 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from mail.nic.mx (mail.nic.mx [200.23.1.17]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g25I3vSQ002720 for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 19:03:58 +0100 (MET)
Received: from rcastillo.nic.mx (rcastillo.nic.com.mx [200.33.1.31]) (authenticated (0 bits)) by mail.nic.mx (8.11.6/8.11.6) with ESMTP id g25I3NX19226 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO) for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 12:03:24 -0600 (CST)
Message-Id: <5.1.0.14.0.20020305115734.03612e48@mail.nic.mx>
X-Sender: castillo@mail.nic.mx
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 05 Mar 2002 12:02:47 -0600
To: ietf-provreg@cafax.se
From: Roger Castillo Cortazar <castillo@nic.mx>
Subject: EPP schemas and example XML instances.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hi everybody.

Where can I get EPP schemas and example XML instances ?
I've been trynig the ftp sites mentioned in a message from last year, ;-)
but my ftp client freezes.

Do I need something special to get the examples ?

Greetings.


Roger Castillo Cortazar
NIC-Mexico http://www.nic.mx
Top Level Domain .MX



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g253A16W012662 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 5 Mar 2002 04:10:01 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g253A0dg012661 for ietf-provreg-outgoing; Tue, 5 Mar 2002 04:10:00 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from toronto.mail.tucows.com (toronto.mail.tucows.com [207.136.98.42]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g2539x6W012653 for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 04:09:59 +0100 (MET)
Received: from cpe0050ba56ff24.cpe.net.cable.rogers.com ([24.157.140.141] helo=tucows.com) by toronto.mail.tucows.com with asmtp (TLSv1:RC4-MD5:128) (Exim 3.20 #2) id 16i5Kw-00067g-00 for ietf-provreg@cafax.se; Mon, 04 Mar 2002 22:09:58 -0500
Message-ID: <3C843788.2080901@tucows.com>
Date: Mon, 04 Mar 2002 22:12:08 -0500
From: Daniel Manley <dmanley@tucows.com>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.8) Gecko/20020204
X-Accept-Language: en-us
MIME-Version: 1.0
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: Re: Additional Response Code and Status Code for EPP
References: <3CD14E451751BD42BA48AAA50B07BAD60189B76F@vsvapostal3.bkup6>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

That's cool with me.

Dan


Hollenbeck, Scott wrote:

>If no one objects I'll add these to the comments to be sent to the IESG to
>assist them in their review.
>
>-Scott-
>
>>-----Original Message-----
>>From: Liu, Hong [mailto:Hong.Liu@neustar.biz]
>>Sent: Monday, March 04, 2002 4:04 PM
>>To: 'ietf-provreg@cafax.se'
>>Subject: Additional Response Code and Status Code for EPP
>>
>>
>>Scott,
>>
>>To support the pending update/create feature, we would like to see the
>>following be added to the EPP spec:
>>
>>(1) A new response code for "Command completed successfully; action
>>pending";
>>
>>(2) A "pendingVerification" status for the host and contact 
>>object mappings;
>>
>>(3) A "pendingUpdate" status for the domain, host and contact object
>>mappings;
>>
>>(4) Clarification on pending update that: The requesting 
>>registrar MUST wait
>>for a pending update to be completed before issuing another 
>>update on the
>>same object;
>>
>>(5) Clarification on notification after pending update is completed.
>>
>>Thanks!
>>
>>--Hong
>>
>>Note: Both (1) and (2) for host object mapping have already 
>>been suggested
>>in 
>>http://www.cafax.se/ietf-provreg/maillist/2002-02/msg00038.html
>>
>>
>>
>>





Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g250lM6W011441 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 5 Mar 2002 01:47:22 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g250lMIV011440 for ietf-provreg-outgoing; Tue, 5 Mar 2002 01:47:22 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g250lL6W011435 for <ietf-provreg@cafax.se>; Tue, 5 Mar 2002 01:47:21 +0100 (MET)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id TAA19741; Mon, 4 Mar 2002 19:47:14 -0500 (EST)
Received: by vsvapostalgw1.bkup1 with Internet Mail Service (5.5.2653.19) id <GGQ3FXPT>; Mon, 4 Mar 2002 19:47:14 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B76F@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Liu, Hong'" <Hong.Liu@neustar.biz>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: RE: Additional Response Code and Status Code for EPP
Date: Mon, 4 Mar 2002 19:47:13 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

If no one objects I'll add these to the comments to be sent to the IESG to
assist them in their review.

-Scott-

> -----Original Message-----
> From: Liu, Hong [mailto:Hong.Liu@neustar.biz]
> Sent: Monday, March 04, 2002 4:04 PM
> To: 'ietf-provreg@cafax.se'
> Subject: Additional Response Code and Status Code for EPP
> 
> 
> Scott,
> 
> To support the pending update/create feature, we would like to see the
> following be added to the EPP spec:
> 
> (1) A new response code for "Command completed successfully; action
> pending";
> 
> (2) A "pendingVerification" status for the host and contact 
> object mappings;
> 
> (3) A "pendingUpdate" status for the domain, host and contact object
> mappings;
> 
> (4) Clarification on pending update that: The requesting 
> registrar MUST wait
> for a pending update to be completed before issuing another 
> update on the
> same object;
> 
> (5) Clarification on notification after pending update is completed.
> 
> Thanks!
> 
> --Hong
> 
> Note: Both (1) and (2) for host object mapping have already 
> been suggested
> in 
> http://www.cafax.se/ietf-provreg/maillist/2002-02/msg00038.html
> 
> 
> 
> 


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24MfC6W011167 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 4 Mar 2002 23:41:12 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g24MfCcH011166 for ietf-provreg-outgoing; Mon, 4 Mar 2002 23:41:12 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from host3.onnethosting.com (host3.onnethosting.com [209.239.43.8]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24MfB6W011161 for <ietf-provreg@cafax.se>; Mon, 4 Mar 2002 23:41:11 +0100 (MET)
Received: from 161.149.50.110 (localhost [127.0.0.1]) by host3.onnethosting.com (8.10.2/8.10.2) with ESMTP id g24Mf4a03514; Mon, 4 Mar 2002 17:41:04 -0500
To: "Liu, Hong" <Hong.Liu@neustar.biz>
From: "Asaad Y. Alnajjar   (Millennium Inc.)" <alnajjar@any-dns.com>
Subject: Re: Additional Response Code and Status Code for EPP
Reply-To: alnajjar@any-dns.com
CC: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Date: Mon, 4 Mar 2002 14:37:59 -0800
X-Sender: asaad@any-dns.com
X-Originating-Host: 161.149.50.110 [161.149.50.100]; Mon, 4 Mar 2002 22:41:04 GMT
X-Mailer: WebMail Check v2.3.21 (2000-7-19)
X-Browser: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT), JavaScript: On
Message-ID: <jUsT.aNoTheR.mEsSaGe.iD.10152816643511@any-dns.com>
MIME-Version: 1.0
X-Priority: 1 (Highest)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Dear All

I need a speaker from IETF to give a presentation on IDNs at our 
upcoming AINC meeting in Tunisia.

http://www.any-dns.com/ainc-tunis.htm

Kindly contact me to coordinate, regards,

Asaad Alnajjar
Exec. Director AINC
CEO Millennium Inc.








Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24L466W010859 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 4 Mar 2002 22:04:06 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g24L46Dx010858 for ietf-provreg-outgoing; Mon, 4 Mar 2002 22:04:06 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24L446W010853 for <ietf-provreg@cafax.se>; Mon, 4 Mar 2002 22:04:05 +0100 (MET)
Received: from chiimc01.il.neustar.com (dmz1.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g24L42f01693 for <ietf-provreg@cafax.se>; Mon, 4 Mar 2002 16:04:03 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19) id <GG2DTNAA>; Mon, 4 Mar 2002 15:03:57 -0600
Message-ID: <23309E398D84D5119D0F00306E07513901181B18@dc02.npac.com>
From: "Liu, Hong" <Hong.Liu@neustar.biz>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: Additional Response Code and Status Code for EPP
Date: Mon, 4 Mar 2002 15:03:55 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Scott,

To support the pending update/create feature, we would like to see the
following be added to the EPP spec:

(1) A new response code for "Command completed successfully; action
pending";

(2) A "pendingVerification" status for the host and contact object mappings;

(3) A "pendingUpdate" status for the domain, host and contact object
mappings;

(4) Clarification on pending update that: The requesting registrar MUST wait
for a pending update to be completed before issuing another update on the
same object;

(5) Clarification on notification after pending update is completed.

Thanks!

--Hong

Note: Both (1) and (2) for host object mapping have already been suggested
in 
http://www.cafax.se/ietf-provreg/maillist/2002-02/msg00038.html







Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24DdF6W008708 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 4 Mar 2002 14:39:15 +0100 (MET)
Received: by nic.cafax.se (8.12.2/8.12.2/Submit) id g24DdFka008707 for ietf-provreg-outgoing; Mon, 4 Mar 2002 14:39:15 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24DdD6W008702 for <ietf-provreg@cafax.se>; Mon, 4 Mar 2002 14:39:14 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id IAA15594; Mon, 4 Mar 2002 08:39:11 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <1SLJV3JB>; Mon, 4 Mar 2002 08:39:11 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B765@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'asbjorn.rrp@theglobalname.org'" <asbjorn.rrp@theglobalname.org>
Cc: ietf-provreg@cafax.se
Subject: RE: "registrant" in domain-1.0.xsd
Date: Mon, 4 Mar 2002 08:39:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

I wonder how that slipped through...

Yes, the type in the <info> response should be fixed such that the
registrant element is of type eppcom:clIDType.  Something else to deal with
at the next editing opportunity.

-Scott- 

> -----Original Message-----
> From: asbjorn.rrp@theglobalname.org
> [mailto:asbjorn.rrp@theglobalname.org]
> Sent: Monday, March 04, 2002 6:17 AM
> To: shollenbeck@verisign.com
> Cc: ietf-provreg@cafax.se
> Subject: "registrant" in domain-1.0.xsd
> 
> 
> Hi,
> 
> whereas "registrant" is defined as
> 
>       <element name="registrant" type="eppcom:clIDType"
>        minOccurs="0"/>
> 
> in both createType and chgType (for updates), it is defined as
> 
>       <element name="registrant" type="domain:contactType"
>        minOccurs="0"/>
> 
> in infDataType. Even though the "type" part of contactType is 
> not required, 
> wouldn't it for consistency be better to have it as 
> eppcom:clIDType in 
> infDataType as well? This will stop anyone from putting 
> anything in the 
> type-part of the field...
> 
> 
> Asbjorn


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g24BGY6W008099 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 4 Mar 2002 12:16:34 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g24BGY8r008098 for ietf-provreg-outgoing; Mon, 4 Mar 2002 12:16:34 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from mx12.nameplanet.com (mx12.nameplanet.com [62.70.3.42]) by nic.cafax.se (8.12.2/8.12.2) with SMTP id g24BGX6W008093 for <ietf-provreg@cafax.se>; Mon, 4 Mar 2002 12:16:33 +0100 (MET)
Received:  4 Mar 2002 11:16:32 -0000
Received: from unknown (HELO www3.nameplanet.com) (192.168.2.43) by mx12 with SMTP; 4 Mar 2002 11:16:32 -0000
Received: (qmail 18579 invoked by uid 400); 4 Mar 2002 11:16:32 -0000
Date: 4 Mar 2002 11:16:32 -0000
Message-ID: <20020304111632.18577.qmail@www3.nameplanet.com>
From: asbjorn.rrp@theglobalname.org
To: shollenbeck@verisign.com
Cc: ietf-provreg@cafax.se
MIME-Version: 1.0
Subject: "registrant" in domain-1.0.xsd
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Hi,

whereas "registrant" is defined as

      <element name="registrant" type="eppcom:clIDType"
       minOccurs="0"/>

in both createType and chgType (for updates), it is defined as

      <element name="registrant" type="domain:contactType"
       minOccurs="0"/>

in infDataType. Even though the "type" part of contactType is not required, 
wouldn't it for consistency be better to have it as eppcom:clIDType in 
infDataType as well? This will stop anyone from putting anything in the 
type-part of the field...


Asbjorn

-- 
 The information transmitted in this email is intended only for the person(s)
 or entity to which it is addressed and may contain proprietary, confidential
 and/or privileged material. If you have received this email in error, please
 contact the sender by replying and delete this email so that it is not
 recoverable. If you are not the intended recipient(s), any retention, review,
 disclosure, distribution, copying, printing, dissemination, or other use of,
 or taking of any action in reliance upon, this information is strictly
 prohibited and without liability on our part.


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g22AK66W029820 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 2 Mar 2002 11:20:06 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g22AK58P029819 for ietf-provreg-outgoing; Sat, 2 Mar 2002 11:20:05 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from host3.onnethosting.com (host3.onnethosting.com [209.239.43.8]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g22AK36W029814 for <ietf-provreg@cafax.se>; Sat, 2 Mar 2002 11:20:04 +0100 (MET)
Received: from Computer (lsanca1-ar23-4-61-023-244.lsanca1.vz.dsl.gtei.net [4.61.23.244]) by host3.onnethosting.com (8.10.2/8.10.2) with SMTP id g229Jdq12911; Sat, 2 Mar 2002 04:19:40 -0500
Message-ID: <001c01c1c1cb$75289400$f4173d04@vz.dsl.genuity.net>
From: "Asaad Y. Alnajjar - Millennium Inc." <alnajjar@any-dns.com>
To: <Undisclosed-Recipient:@host3.onnethosting.com;>
Subject: Seminar Invitation / Registration Form - AINC Tunisia April 2002  RESPONSE REQUESTED -
Date: Sat, 2 Mar 2002 01:19:03 -0800
Organization: Millennium Inc.
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0011_01C1C188.3DB3EF80"
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01C1C188.3DB3EF80
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0012_01C1C188.3DB3EF80"


------=_NextPart_001_0012_01C1C188.3DB3EF80
Content-Type: text/plain;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

New Page 1

------=_NextPart_001_0012_01C1C188.3DB3EF80
Content-Type: text/html;
	charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<BASE HREF=3D"file://C:\TEMP\">=0A=
=0D<html>

<head>
<meta name=3D"GENERATOR" content=3D"Microsoft FrontPage 5.0">
<meta name=3D"ProgId" content=3D"FrontPage.Editor.Document">
<title>New Page 1</title>
</head>

<frameset rows=3D"28,*">
  <frame name=3D"header" scrolling=3D"no" noresize target=3D"main">
  <frame name=3D"main" src=3D"http://www.any-dns.com/ainc-tunis.htm" =
target=3D"_blank">
  <noframes>
  <body>

  <p>This page uses frames, but your browser doesn't support them.</p>

  </body>
  </noframes>
</frameset>

</html>

------=_NextPart_001_0012_01C1C188.3DB3EF80--

------=_NextPart_000_0011_01C1C188.3DB3EF80
Content-Type: text/html;
	name="ainc-tunis.htm"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="ainc-tunis.htm"

<html>

<head>
<meta name=3D"GENERATOR" content=3D"Microsoft FrontPage 5.0">
<meta name=3D"ProgId" content=3D"FrontPage.Editor.Document">
<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dwindows-1252">
<meta http-equiv=3D"Content-Language" content=3D"en-us">
<title>The Arabic Internet Names Consortium AINC</title>
<base target=3D"_blank">
<meta name=3D"Microsoft Theme" content=3D"any-dns 001, default">
<meta name=3D"Microsoft Border" content=3D"none">
</head>

<body background=3D"_themes/any-dns/earth.gif" bgcolor=3D"#FFFFFF" =
text=3D"#000000" link=3D"#0000FF" vlink=3D"#CC0000" =
alink=3D"#00CC00"><!--mstheme--><font face=3D"Times New Roman">

<p align=3D"center"><a href=3D"http://www.arabicdomainname.org">
<img border=3D"0" src=3D"images/ainclogo.gif" width=3D"291" =
height=3D"147"></a></p>
<p align=3D"justify"><b><span style=3D"background-color: =
#FFFF00">&nbsp;&nbsp;&nbsp; The Arabic Internet Names Consortium AINC, =
under the=20
patronage of the Government of Tunisia Ministry of Communications and =
Information Technology, is organizing  AINC=20
fourth General Body Meeting, the Second Arab ccTLD meeting,&nbsp; and =
the Third Arabic=20
Domain Name Seminar titled ( <font face=3D"Arial">
<i>Arabic Domains, eCommerce and Internet - Past, Present and =
Future</i></font><font face=3D"Arial" size=3D"2">) </font>on the=20
15th - 17th of April 2002 at the=20
<a href=3D"http://www.lepalace.com.tn/htmla/sommairea.htm">Le Palace =
Hotel</a>, Tunis, Tunisia.&nbsp; The meetings=20
will discuss arabic domain name registration policies, arabic gTLDs, =
arabic ccTLDs, linguistic concerns,=20
technology=20
IETF direction and other multilingual domain name related =
issues.</span><br>
<br>
<span style=3D"background-color: #FFFF00">&nbsp;&nbsp;&nbsp;
You are cordially invited to attend the meetings which will be open to =
all AINC=20
members and the members of the global domain related agencies ( ICANN, =
IETF, WIPO,=20
ITU, CENTER, Arab League, Arab ICT Forum, ...etc). Final Agenda will be=20
circulated within couple weeks.<br>
</span>
<br>
<span style=3D"background-color: #FFFF00">&nbsp;&nbsp;&nbsp;
I take this opportunity to extend an invitation to you, on behalf of the =

Tunisian Government &amp; Ministry of Communications,&nbsp; to =
participate to this annual=20
regional event, considered one of the top Information Technology and=20
Telecommunications in the region .<br>
</span>
<br>
<span style=3D"background-color: #FFFF00">Please note that =
accommodations and local transportation will be=20
provided by our host, however, we do need your confirmation prior to=20
<font color=3D"#FF0000">March 15,=20
2002</font>.</span><br>
<br>
<span style=3D"background-color: #FFFF00">Best Regards<br>
Asaad Alnajjar&nbsp;
<a href=3D"mailto:alnajjar@any-DNS.com?subject=3DAINC Meeting - =
Tunisia">
(alnajjar@any-DNS.com)</a><br>
AINC Executive Director</span><br>
&nbsp;</b></p>
<!--msthemeseparator--><p align=3D"center"><img =
src=3D"_themes/any-dns/fieruled.gif" width=3D"600" height=3D"10"></p>
<form method=3D"POST" action=3D"_derived/nortbots.htm" =
onSubmit=3D"location.href=3D'_derived/nortbots.htm';return false;" =
webbot-onSubmit webbot-action=3D"--WEBBOT-SELF--">
  <!--webbot bot=3D"SaveResults" u-file=3D"_private/ainc-tunis.htm" =
s-format=3D"HTML/PRE" s-label-fields=3D"TRUE" =
b-reverse-chronology=3D"FALSE" s-email-format=3D"TEXT/PRE" =
s-email-address=3D"ainc-tunis@any-dns.com" b-email-label-fields=3D"TRUE" =
b-email-subject-from-field=3D"TRUE" s-email-subject=3D"Attendance =
Confirmation - Tunisia April 2002" s-date-format=3D"%d %b %Y" =
s-time-format=3D"%H:%M:%S" s-builtin-fields=3D"REMOTE_USER Date Time" =
u-confirmation-url=3D"http://www.arabicdomainname.org" startspan =
--><strong>[FrontPage Save Results Component]</strong><!--webbot =
bot=3D"SaveResults" endspan i-checksum=3D"6561" -->
  <p><strong>Registration form:</strong></p>
  <dl>
    <dd>
    <!--mstheme--></font><table>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Name</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b><input type=3D"text" size=3D"35" maxlength=3D"256" =
name=3D"Username"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Company</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b>
        <input type=3D"text" size=3D"35" maxlength=3D"256" =
name=3D"Company"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Arrival</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b>
        <input type=3D"text" size=3D"50" maxlength=3D"256" =
name=3D"Arrival"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Departure</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b>
        <input type=3D"text" size=3D"50" maxlength=3D"256" =
name=3D"Departure"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Other Info</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b>
        <input type=3D"text" size=3D"50" maxlength=3D"256" =
name=3D"Information"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">E-mail</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b><input type=3D"text" size=3D"35" maxlength=3D"256" =
name=3D"UserEmail"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">Tel</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b><input type=3D"text" size=3D"35" maxlength=3D"256" =
name=3D"UserTel"></b></font><!--mstheme--></font></td>
      </tr>
      <tr>
        <td><!--mstheme--><font face=3D"Times New Roman"><b><font =
color=3D"#0000FF">FAX</font></b><!--mstheme--></font></td>
        <td><!--mstheme--><font face=3D"Times New Roman"><font =
color=3D"#0000FF"><b><input type=3D"text" size=3D"35" maxlength=3D"256" =
name=3D"UserFAX"></b></font><!--mstheme--></font></td>
      </tr>
    </table><!--mstheme--><font face=3D"Times New Roman">
    </dd>
  </dl>
  <dl>
    <dd>
    <input type=3D"checkbox" name=3D"ContactRequested" =
value=3D"VisaLetterRequested">
    <b>
    <font color=3D"#0000FF">I need an invitation letter for VISA =
application.</font></dd>
    </b>
  <p><strong>Prospective Speakers include your speech Title &amp; brief =
description=20
  below:</strong></p>
  <dl>
    <dd><textarea name=3D"SeminarSpeakers" rows=3D"5" =
cols=3D"50"></textarea></dd>
  </dl>
    <dt>&nbsp;</dt>
  </dl>
  <p><input type=3D"submit" value=3D"Submit Confirmation">
  <input type=3D"reset" value=3D"Clear Form"></p>
</form>
<h5><!--mstheme--><font face=3D"Verdana, Arial, Helvetica" =
color=3D"#0033CC"><font size=3D"1">Asaad Alnajjar&nbsp;
Copyright =A9 2000-2002 [AINC]. All rights reserved.&nbsp;&nbsp;
Revised: <!--webbot bot=3D"TimeStamp" s-type=3D"EDITED" =
s-format=3D"%m/%d/%y" startspan -->03/01/02<!--webbot bot=3D"TimeStamp" =
i-checksum=3D"12482" endspan -->.</font><!--mstheme--></font></h5>

<!--mstheme--></font></body>

</html>
------=_NextPart_000_0011_01C1C188.3DB3EF80--



Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g21Ehc6W025395 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 1 Mar 2002 15:43:38 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g21EhcKf025394 for ietf-provreg-outgoing; Fri, 1 Mar 2002 15:43:38 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g21EhZ6W025389 for <ietf-provreg@cafax.se>; Fri, 1 Mar 2002 15:43:36 +0100 (MET)
Received: from chiimc01.il.neustar.com (dmz1.il.neustar.com [209.173.57.65]) by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g21EhKS06541; Fri, 1 Mar 2002 08:43:21 -0600
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19) id <FXFAJ8DA>; Fri, 1 Mar 2002 08:43:15 -0600
Message-ID: <23309E398D84D5119D0F00306E07513901181B06@dc02.npac.com>
From: "Liu, Hong" <Hong.Liu@neustar.biz>
To: "'Eric Brunner-Williams in Portland Maine'" <brunner@nic-naa.net>
Cc: "'Hollenbeck, Scott'" <shollenbeck@verisign.com>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: RE: Pending Update 
Date: Fri, 1 Mar 2002 08:43:10 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Eric,

You raised some good points about the semantics of pending update. We are
well aware of these issues you raised. My approach, at least from what I
learned on this list, is that I'd better state the problem clearly first
before dwelling into solutions, -:)

I take it that you are not objecting to pending update, but want to get the
semantics right regarding whether multiple pending updates should be
serialized on the registrar side. Am I correct?

For those who want to get a quick understanding of this thread, there are
three issues Eric raised in his email. [Eric, please correct me if I
misunderstood your views.]:

(1) Is the registrar allowed to cancel a pending update before it is
confirmed of the execution of the operation?

(2) Is the registrar allowed to issue multiple updates to the same object
before it is confirmed of the execution of the first operation?

(3) What is the mechanism to correlate messages in pending update situation?

To some extent, some of these questions have touched upon the overlapping
areas between registry policy and protocol mechanism. I would like to hear
more discussions from the list.

Please see my comments in line.

--Hong

-----Original Message-----
From: Eric Brunner-Williams in Portland Maine
[mailto:brunner@nic-naa.net]
Sent: Friday, March 01, 2002 4:02 AM
To: Liu, Hong
Cc: 'Eric Brunner-Williams in Portland Maine'; 'Hollenbeck, Scott';
'ietf-provreg@cafax.se'; brunner@nic-naa.net
Subject: Re: Pending Update 



>                                                           ... The
registrar
> may not serilize the update operations on an object, i.e., wait for the
> first update to be completed before requesting another. At least we are
not
> making such an assumption.

[snip...]

How does a registrar revoke a hung job (an asychronous write)?  

<HL> 
Whether revocation of a pending update is allowed or not in EPP is an issue
independent of the serialization of update requests from the registrar side.
So we have a decision to make. Then we can talk about possible solutions.
<HL/>


Wouldn't it be simpler to simply do a transport mapping for an existing
filesystem (over tcp) with the semantics you require?

As you observe, data bases do do this (serialize operations against object).

Putting a data base, or at least this bit of semantics, "into" the protocol
is an option. It seems simpler to observe, as Scott did, that asynchronous
exchanges might result in higher error rates if a client issues commands
without waiting to receive the responses for prior commands, rather than to
attempt to guarantee that they won't.

<HL>
Good point. Forcing the serialization of multiple updates on the same object
on the registrar side does simplify the problem, especially on the registry
side. I would like to hear from the registrars what they think of this
issue.
<HL/>

> Do we need more information from EPP, such as time-stamp ...

Scott and Klaus discussed roll-back last September, on-list, and I privately
discussed temporal identifier requirements with Scott on 8 Feb '01.

<HL>
Actually, I was talking about a different problem. Since pending update is
an "extended" transaction, meaning beyond the simple request-response
two-way handshake, we need to have a way to correlate the messages in the
same transaction. The transaction ID can be used for that purpose IF we make
it mandatory in pending update requests. This is another issue we need to
address.
<HL/>

Eric


Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g2143F6W023463 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 1 Mar 2002 05:03:15 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.2/8.12.2/Submit) id g2143FVF023462 for ietf-provreg-outgoing; Fri, 1 Mar 2002 05:03:15 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from nic-naa.net (dt0b4n7d.maine.rr.com [24.95.12.125]) by nic.cafax.se (8.12.2/8.12.2) with ESMTP id g2143D6W023457 for <ietf-provreg@cafax.se>; Fri, 1 Mar 2002 05:03:14 +0100 (MET)
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.11.6/8.11.1) with ESMTP id g21926G01624; Fri, 1 Mar 2002 04:02:06 -0500 (EST) (envelope-from brunner@nic-naa.net)
Message-Id: <200203010902.g21926G01624@nic-naa.net>
To: "Liu, Hong" <Hong.Liu@neustar.biz>
cc: "'Eric Brunner-Williams in Portland Maine'" <brunner@nic-naa.net>, "'Hollenbeck, Scott'" <shollenbeck@verisign.com>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, brunner@nic-naa.net
Subject: Re: Pending Update 
In-Reply-To: Your message of "Thu, 28 Feb 2002 13:39:39 CST." <23309E398D84D5119D0F00306E07513901181AFE@dc02.npac.com> 
Date: Fri, 01 Mar 2002 04:02:06 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

>                                                           ... The registrar
> may not serilize the update operations on an object, i.e., wait for the
> first update to be completed before requesting another. At least we are not
> making such an assumption.

Wow. That's novel.

So you want an in-protocol mechanism to ensure the temporally well-ordered
commit of asychronous writes. Because registrars don't view "hung jobs" as
edge-case bugs, subject to registrar-revocation or registry-cancellation,
but as a deferred write, and the effective state of an object the subject
of lazy evaluation semantics.

How does a registrar revoke a hung job (an asychronous write)?  

Wouldn't it be simpler to simply do a transport mapping for an existing
filesystem (over tcp) with the semantics you require?

As you observe, data bases do do this (serialize operations against object).

Putting a data base, or at least this bit of semantics, "into" the protocol
is an option. It seems simpler to observe, as Scott did, that asynchronous
exchanges might result in higher error rates if a client issues commands
without waiting to receive the responses for prior commands, rather than to
attempt to guarantee that they won't.

> Do we need more information from EPP, such as time-stamp ...

Scott and Klaus discussed roll-back last September, on-list, and I privately
discussed temporal identifier requirements with Scott on 8 Feb '01.

Eric

