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

The information below is for an old version of the document
Document Type Active Internet-Draft (eppext WG)
Last updated 2014-03-11
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      S. Hollenbeck
Internet-Draft                                             Verisign Labs
Intended status: Standards Track                          March 11, 2014
Expires: September 12, 2014

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

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 September 12, 2014.

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 September 12, 2014               [Page 1]
Internet-Draft           EPP Extension Registry               March 2014

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

Table of Contents

   1.  Conventions Used in This Document . . . . . . . . . . . . . .   2
     1.1.  Acronyms and Abbreviations  . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Extension Specification and Registration Procedure  . . . . .   3
     3.1.  Extension Specification . . . . . . . . . . . . . . . . .   3
       3.1.1.  Designated Expert Evaluation Criteria . . . . . . . .   3
     3.2.  Registration Procedure  . . . . . . . . . . . . . . . . .   4
       3.2.1.  Required Information  . . . . . . . . . . . . . . . .   4
       3.2.2.  Registration Form . . . . . . . . . . . . . . . . . .   5
       3.2.3.  Registration Processing . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

1.1.  Acronyms and Abbreviations

      EPP: Extensible Provisioning Protocol
      IANA: Internet Assigned Numbers Authority
      IPR: Intellectual Property Rights

2.  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].

Hollenbeck             Expires September 12, 2014               [Page 2]
Internet-Draft           EPP Extension Registry               March 2014

   RFCs 5730 and 5735 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.
Show full document text