WG ACTION: Provisioning Registry Protocol (provreg)

[Edward Lewis <lewis@tislabs.com>]

Apparently, we're now legal...

>From: The IESG <iesg-secretary@ietf.org>
>To: IETF-Announce:;;@tislabs.com
>Subject: WG ACTION: Provisioning Registry Protocol (provreg)
>Date: Sat, 10 Feb 2001 16:22:12 -0500
>Sender: scoya@cnri.reston.va.us
>
>
>A new working group has been formed in the Applications Area of the IETF.
>For additional information, contact the Area Directors
>or the WG Chair.
>
>
>Provisioning Registry Protocol (provreg)
>----------------------------------------
>
> Charter
> Last Modified: 05-Feb-01
>
> Current Status: Active Working Group
>
> Chair(s):
>     Jaap Akkerhuis <jaap@mtxinu.com>
>     Ed Lewis <lewis@tis.com>
>
> Applications Area Director(s):
>     Ned Freed  <ned.freed@innosoft.com>
>     Patrik Faltstrom  <paf@cisco.com>
>
> Applications Area Advisor:
>     Patrik Faltstrom  <paf@cisco.com>
>
> Mailing Lists:
>     General Discussion:ietf-provreg@cafax.se
>     To Subscribe:      ietf-provreg-request@cafax.se
>         In Body:       subscribe ietf-provreg
>     Archive:           http://www.cafax.se/ietf-provreg/maillist/
>
>Description of Working Group:
>
>Administration of Domain Name Service (DNS) registration increasingly
>distinguishes between the operation of a "back-end" registry data base
>service for registrations, versus "front-end" support services by
>registrars who interact with registrants and with the registry.
>Especially for various Top-Level Domains, the desire is to permit
>multiple registrars to share access to the database.  Conversely, there
>is a desire to allow a registrar to access multiple registries via the
>same protocol, even if the registries differ in operational models.
>
>This working group will develop a specification of the requirements and
>limitations for a protocol that enables a registrar to access multiple
>registries and will develop a  protocol that satisfies those
>requirements. The protocol will permit interaction between a
>registrar's own application and registry applications.
>
>The initial specification will allow multiple registrars to register
>and maintain domain names within multiple Top Level Domains (TLDs). The
>specification should be flexible enough to support the different
>operational models of registries.  The specification should allow
>extension to support other registration data, such as address
>allocation and contact information. The working group will use as input
>the "Generic Registry-Registrar Protocol Requirements"
>(draft-hollenbeck-grrp-reqs-nn) and the Extensible Provisioning
>Protocol presentation, documented in (draft-hollenbeck-epp-nn).
>
>The group will consider support for multiple operational choices, such
>as for transport and security; it will create no new transport or
>security protocols.  The group may consider use of the new 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:
>
>* Specify the objects exchanged between the registry repository
>and registrars, the relationships among the objects, and the protocol
>for exchanging objects between a registrar and the registry; at a
>minimum the objects will include:  domain name, IP address, and contact
>details for registrants
>
>* Describe appropriate mechanisms for security during registrar access
>
>* List useful examples of registrar access transactions
>
> Goals and Milestones:
>
>   Feb 01       Working group agreement on functional requirements for
>protocol
>
>   Apr 01       Initial specification of provreg protocol
>
>
>   Jun 01       Second draft specification
>
>
>   Sep 01       Submit draft for standards track
>
>

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

Dilbert is an optimist.

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