RE: Draft provreg charter

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

Dave,

I think we'd like to have the group chartered in January 2001, not 2005. ;-)

I see some extra words in the third paragraph, which I would suggest
rewording as follows:

"The group will consider support for multiple operational choices, such as
for transport and security, and may consider use of the protocol for diverse
registration and update scenarios in order to understand limitations and
possible extensions that are appropriate.  Specification for user interface 
access, such as by a web front end, is beyond the scope of this working
group.  Documentation from the working group will:"

I'd like to list some specific object identification targets in the first
documentation bullet if possible.   Leaving it open-ended makes it difficult
to determine when the group has finished it's work.  At a minimum, I think
we need to address domain name, host, and contact provisioning.  IP
addresses, ASNs, and telephone numbers have also been mentioned.  Do we want
to tackle those as formal working group deliverables?

Scott Hollenbeck
VeriSign Global Registry Services

-----Original Message-----
From: Dave Crocker [mailto:dcrocker@brandenburg.com]
Sent: Tuesday, December 26, 2000 12:29 PM
To: ietf-provreg@cafax.se
Subject: Draft provreg charter




Folks,

Here is a draft of the working group charter.  (Sorry for the delay.)  It 
reflects the changes I typed during the BOF, and string changes from 
'domreg' to 'provreg'.

d/



Provisioning Registry Protocol  (ProvReg)
------------------------------

  CHAIR(S):


  APPLICATIONS AREA DIRECTOR(S):
         Patrik Fältström
         Ned Freed

  AREA ADVISOR:


  MAILING LISTS:
General Discussion:
To Subscribe:
    In Body:             subscribe
    Alternate:
Archive:



DESCRIPTION OF WORKING GROUP:

Administration of Domain Name Service (DNS) registration increasingly 
distinguishes between the operation of a data base for registrations, 
called the registry, versus the  "front-end" sales and support services by 
registrars who interact with registrants and with the "back-end" 
registry.  Especially for various Top-Level Domains, the desire is to 
permit multiple registrars to share access to the database.  This working 
group will develop a protocol for registrar access to the registry. The 
protocol will permit interaction between a registrar's own application and 
the data base service running a domain name service registry repository.

The specification will allow multiple registrars to register domain names 
within a single Top Level Domain (TLD). The working group will use as input 
the Extensible Provisioning Protocol presentation, documented in 
<draft-hollenbeck-epp-00.txt>.

The group will consider support for multiple operational choices, such as 
for transport and security, and may consider use the protocol for other for 
other registration and update in order to understand limitations and 
possible extensions that are appropriate.  Specification for user interface 
access, such as by a web front end, is beyond the scope of this working
group.
Documentation from the working group will:

*       Specify the objects exchanged between the registry repository and 
registrars, their relationships to each other, and the protocol for 
exchanging objects between a registrar and the registry

*       Describe appropriate mechanisms for security and protection during 
registrar access

*       List useful examples of registrar access transactions


GOALS AND MILESTONES:
Jan, 2005       Working group chartered

Feb, 2001       Working group agreement on functional requirements for
protocol

Feb, 2001       Initial specification of provreg protocol

May, 2001       Second draft specification

Sep, 2001       Submit provreg draft for standards track






=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464