Protocol Action: 'Allocation Token Extension for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-allocation-token-12.txt)

The IESG <iesg-secretary@ietf.org> Wed, 03 October 2018 19:22 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Allocation Token Extension for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-allocation-token-12.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, adam@nostrum.com, regext-chairs@ietf.org, pm@dotandco.com, draft-ietf-regext-allocation-token@ietf.org, Patrick Mevzek <patrick+ietf@deepcore.org>, regext@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <153859452949.9200.17270223647964991867.idtracker@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 12:22:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Y9VVsWidBW1cyUn3C2pB8QDZUyA>

The IESG has approved the following document:
- 'Allocation Token Extension for the Extensible Provisioning Protocol
   (EPP)'
  (draft-ietf-regext-allocation-token-12.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working
Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token/




Technical Summary

This document describes an Extensible Provisioning Protocol (EPP)
extension for including an Allocation Token in "query" and "transform"
commands.  The Allocation Token is used as a credential that
authorizes a client to request the allocation of a specific object
from the server, using one of the EPP transform commands including
create and transfer.

Working Group Summary

The document has received substantial review, both at face-to-face meetings
and on the regext mailing list. The shepherd's writeup contains significant
detail of these reviews. Consensus was smooth, with no major disagreements
arising in the working group.

Document Quality

Four implementations by three companies are documented. All
four are currently in production use. All EPP XML examples
have been validated against the XML schema provided in the
draft by the Document Shepherd.

Personnel

The document shepherd is Patrick Mevzek, pm@dotandco.com
The responsible Area Director is Adam Roach, adam@nostrum.com

Protocol Action: 'Allocation Token Extension for … The IESG