Extension Registry for the Extensible Provisioning Protocol
draft-ietf-eppext-reg-09

The information below is for an old version of the document
Document Type Active Internet-Draft (eppext WG)
Last updated 2014-10-13 (latest revision 2014-10-03)
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd James Galvin
Shepherd write-up Show (last changed 2014-07-27)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Pete Resnick
Send notices to eppext-chairs@tools.ietf.org, draft-ietf-eppext-reg@tools.ietf.org, eppext@ietf.org
IANA IANA review state Version Changed - Review Needed
Network Working Group                                      S. Hollenbeck
Internet-Draft                                             Verisign Labs
Intended status: Informational                           October 3, 2014
Expires: April 6, 2015

      Extension Registry for the Extensible Provisioning Protocol
                        draft-ietf-eppext-reg-09

Abstract

   The Extensible Provisioning Protocol (EPP) includes features to add
   functionality by extending the protocol.  It does not, however,
   describe how those extensions are managed.  This document describes a
   procedure for the registration and management of extensions to EPP
   and it specifies a format for an IANA registry to record those
   extensions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 6, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Hollenbeck                Expires April 6, 2015                 [Page 1]
Internet-Draft           EPP Extension Registry             October 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Extension Specification and Registration Procedure  . . . . .   3
     2.1.  Extension Specification . . . . . . . . . . . . . . . . .   3
       2.1.1.  Designated Expert Evaluation Criteria . . . . . . . .   3
     2.2.  Registration Procedure  . . . . . . . . . . . . . . . . .   4
       2.2.1.  Required Information  . . . . . . . . . . . . . . . .   4
       2.2.2.  Registration Form . . . . . . . . . . . . . . . . . .   5
       2.2.3.  Registration Processing . . . . . . . . . . . . . . .   7
       2.2.4.  Updating Registry Entries . . . . . . . . . . . . . .   7
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Domain name registries implement a variety of operational and
   business models.  The differences in these models made it impossible
   to develop a "one size fits all" provisioning protocol, so the
   Extensible Provisioning Protocol (EPP, [RFC5730]) was designed to
   focus on a minimal set of common functionality with built-in
   extension capabilities that allow new features to be specified on an
   "as needed" basis.  Guidelines for extending EPP are documented in
   Informational RFC 3735 [RFC3735].

   RFCs 3735 and 5730 do not describe how extension development can be
   managed and coordinated.  This has led to a situation in which server
   operators can develop different extensions to address similar needs,
   such as the provisioning of Value Added Tax (VAT) information.
   Clients then need to support multiple extensions that serve similar
   purposes, and interoperability suffers.

   An IANA registry can be used to help manage and coordinate the
   development of protocol extensions.  This document describes an IANA
   registry that can be used to coordinate the development of EPP
   extensions.

Hollenbeck                Expires April 6, 2015                 [Page 2]
Internet-Draft           EPP Extension Registry             October 2014

2.  Extension Specification and Registration Procedure

   This section describes the format of an IANA registry and the
   procedures used to populate and manage registry entries.
Show full document text