From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: regext@ietf.org
Subject: WG Review: Registration Protocols Extensions (regext)
The Registration Protocols Extensions (regext) WG in the Applications and
Real-Time Area of the IETF is undergoing rechartering. The IESG has not made
any determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to the
IESG mailing list (iesg@ietf.org) by 2018-07-31.
Registration Protocols Extensions (regext)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
James Galvin <galvin@elistx.com>
Antoin Verschuren <ietf@antoin.nl>
Assigned Area Director:
Adam Roach <adam@nostrum.com>
Applications and Real-Time Area Directors:
Adam Roach <adam@nostrum.com>
Ben Campbell <ben@nostrum.com>
Alexey Melnikov <aamelnikov@fastmail.fm>
Mailing list:
Address: regext@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/regext
Archive: https://mailarchive.ietf.org/arch/browse/regext/
Group page: https://datatracker.ietf.org/group/regext/
Charter: https://datatracker.ietf.org/doc/charter-ietf-regext/
The Extensible Provisioning Protocol (EPP, Standard 69) is the
standard domain name provisioning protocol for top-level domain name
registries. 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.
The Registration Data Access Protocol (RDAP, RFCs 7480-7484) is the
proposed standard for retrieving registration metadata from both
domain name and Regional Internet Registries. To ensure interoperable
implementations it's important to coordinate and standardize
extensions and profiles to be used by registries.
Extensions in both cases that are targeted for the Standards Track are
subject to more thorough review and open discussion within the IETF.
In addition, commonality may be discovered in related extensions,
especially EPP extensions listed on the EPP extension registry, for
which it would makes sense to merge them into a single standard
extension everybody agrees on.
The REGEXT 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 EPP 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 REGEXT
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. When there are no more proposals for Standards-Track extensions,
the working group will either close or become dormant, with the
decision made in consultation with the responsible AD. The charter
will be reviewed by the end of 2019 and will be refreshed by
rechartering if there is still a reason to keep the working group
going. In any case, the mailing list will remain open and available
for the use of the expert review process as described in RFC7451.
The working group may also, in consultation with its responsible area
director, take on work related to the operation of Internet identifier
registries, beyond the EPP and RDAP protocols.
Milestones:
Aug 2018 - Submit for publication "Registry Fee Extension for EPP"
Aug 2018 - Submit for publication "Change Poll Extension for EPP"
Sep 2018 - Submit for publication an informational RFC with requirements
for a registration protocol for third-party DNS providers
Dec 2018 - Submit for publication "Validate Mapping for the Extensible
Provisioning Protocol"
Mar 2019 - Submit for publication "EPP Domain Name Mapping Extension for
Bundling Registration"
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: regext-chairs@ietf.org,
The IESG <iesg@ietf.org>,
regext@ietf.org
Subject: WG Action: Rechartered Registration Protocols Extensions (regext)
The Registration Protocols Extensions (regext) WG in the Applications and
Real-Time Area of the IETF has been rechartered. For additional information,
please contact the Area Directors or the WG Chairs.
Registration Protocols Extensions (regext)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
James Galvin <galvin@elistx.com>
Antoin Verschuren <ietf@antoin.nl>
Assigned Area Director:
Adam Roach <adam@nostrum.com>
Applications and Real-Time Area Directors:
Adam Roach <adam@nostrum.com>
Ben Campbell <ben@nostrum.com>
Alexey Melnikov <aamelnikov@fastmail.fm>
Mailing list:
Address: regext@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/regext
Archive: https://mailarchive.ietf.org/arch/browse/regext/
Group page: https://datatracker.ietf.org/group/regext/
Charter: https://datatracker.ietf.org/doc/charter-ietf-regext/
Charter for Working Group
The Extensible Provisioning Protocol (EPP, Standard 69) is the
standard domain name provisioning protocol for top-level domain name
registries. 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 RFC 7451. Extensions may be registered
for informational purposes as long as there is a published
specification that has been reviewed by a designated expert. The
Registration Data Access Protocol (RDAP, RFCs 7480-7484) is the
proposed standard for retrieving registration metadata from both
domain name and Regional Internet Registries. To ensure interoperable
implementations it's important to coordinate and standardize
extensions and profiles to be used by registries.
Extensions in both cases that are targeted for the Standards Track are
subject to more thorough review and open discussion within the IETF.
In addition, commonality may be discovered in related extensions,
especially EPP extensions listed on the EPP extension registry, for
which it would makes sense to merge them into a single standard
extension everybody agrees on.
The REGEXT 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 EPP extensions will follow the expert
review process as described in RFC 7451 for inclusion in the EPP
extensions registry. These documents will not be part of the REGEXT
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. When there are no more proposals for Standards-Track extensions,
the working group will either close or become dormant, with the
decision made in consultation with the responsible AD. In any case,
the mailing list will remain open and available for the use of the
expert review process as described in RFC 7451.
The working group may also take on work to develop specifications that
describe the following types of information exchanged between entities
involved in Internet identifier registration that are using the RDAP or
EPP protocols:
* Uniform representation formats for publishing local policy or
configuration options regarding EPP and RDAP use.
* Data formats for files exchanged between registration entities that
need insertion in or extraction from EPP or RDAP.
* Technical guidance for registration processes that are supported by
EPP or RDAP.
Milestones:
Aug 2018 - Submit for publication "Registry Fee Extension for EPP"
Aug 2018 - Submit for publication "Change Poll Extension for EPP"
Sep 2018 - Submit for publication an informational RFC with requirements
for a registration protocol for third-party DNS providers
Dec 2018 - Submit for publication "Validate Mapping for the Extensible
Provisioning Protocol"
Mar 2019 - Submit for publication "EPP Domain Name Mapping Extension for
Bundling Registration"