Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)
draft-ietf-regext-epp-registry-maintenance-19

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: James Galvin <galvin@elistx.com>, The IESG <iesg@ietf.org>, draft-ietf-regext-epp-registry-maintenance@ietf.org, galvin@elistx.com, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-epp-registry-maintenance-19.txt)

The IESG has approved the following document:
- 'Registry Maintenance Notification for the Extensible Provisioning
   Protocol (EPP)'
  (draft-ietf-regext-epp-registry-maintenance-19.txt) as Proposed Standard

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

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-registry-maintenance/

Ballot Text

Technical Summary

   This document describes an Extensible Provision Protocol (EPP)
   extension called "Registry Maintenance Notification", used by EPP
   servers to notify EPP clients and allow EPP clients to query EPP
   servers on maintenance events.

Working Group Summary

This work originated in the Technical Operations subcommittee of registries and registrars in ICANN's Generic Names Supporting Organization (GNSO).  Since it is an EPP protocol extension it was submitted to the REGEXT working group for consideration as a Proposed Standard.

As the work was developed within its community of interest, the specification arrived mostly complete.  There was minor discussion of a few details and without objection the working group agreed to Proposed Standard status for the specification.

Document Quality

The document was reviewed by EPP experts among the working group members and found to be excellent quality.
The document represents strong consensus of a few individuals, with no objection from anyone else.

Personnel

   The document shepherd is James Galvin.
   The Responsible Area Director is Murray Kucherawy.

RFC Editor Note