Skip to main content

Extensible Provisioning Protocol Extensions
charter-ietf-eppext-01-00

The information below is for an older proposed charter
Document Proposed charter Extensible Provisioning Protocol Extensions WG (eppext) Snapshot
Title Extensible Provisioning Protocol Extensions
Last updated 2015-10-14
State Draft Charter
WG State Active
IESG Responsible AD Barry Leiba
Charter edit AD Barry Leiba
Send notices to (None)

charter-ietf-eppext-01-00

The Extensible Provisioning Protocol (EPP, Standard 69) is the
standard domain name provisioning protocol for top-level domain name
registries, and the Internet Corporation for Assigned Names and
Numbers (ICANN) requires all new generic top-level domain registries
to implement EPP. To avoid many separate EPP extensions that provide
the same functions, it's important to coordinate and standardize EPP
extensions.

The EPP Extensions (EPPEXT) working group completed its first goal of
creating an IANA registry of EPP extensions. The registration process
of the registry is documented in RFC7451. Extensions may be
registered for informational purposes as long as there is a published
specification that has been reviewed by a designated expert.

Extensions that seek the status of Internet standard are subject to
more thorough review and open discussion within the IETF.

In addition, commonality may be discovered in extensions listed for
which it would makes sense to merge them into a single standard
extension everybody agrees on.

The EPPEXT working group is the home of the coordination effort for
standards track extensions. The selection of extensions for standards
track shall incorporate the following guidelines.

  1. Proprietary documented extensions and individual submissions of
    informational or experimental extensions will follow the expert review
    process as described in RFC7451 for inclusion in the EPP extensions
    registry. These documents will not be part of the EPPEXT working group
    work or milestones. The working group may discuss or advise on these
    documents.

  2. Extensions that seek standards track status can be suggested for WG
    adoption. If accepted by the working group then the development of
    the standard may proceed.

  3. The working group will exist as long as there is an extension
    seeking standards track status. When there are no more proposals
    for a standards track extension the working group will either close or
    go dormant according to IETF rules. The mailing list will remain open
    and available for the use of the expert review process as described in
    RFC7451.