Protocol Action: 'Registry Fee Extension for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-epp-fees-20.txt)

The IESG <> Mon, 04 November 2019 14:52 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id D690F1208CC; Mon, 4 Nov 2019 06:52:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Protocol Action: 'Registry Fee Extension for the Extensible Provisioning Protocol (EPP)' to Proposed Standard (draft-ietf-regext-epp-fees-20.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <>,,,, James Gould <>,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Mon, 04 Nov 2019 06:52:36 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Nov 2019 14:52:40 -0000

The IESG has approved the following document:
- 'Registry Fee Extension for the Extensible Provisioning Protocol (EPP)'
  (draft-ietf-regext-epp-fees-20.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working

The IESG contact persons are Adam Roach, Alexey Melnikov and Barry Leiba.

A URL of this Internet Draft is:

Technical Summary

This document describes an Extensible Provisioning Protocol (EPP) 
extension mapping for registry fees.

Working Group Summary

draft-ietf-regext-epp-fees is on standards track.  This extension adds 
additional elements to the EPP domain name mapping defined in RFC 5731, 
which is an internet standard.

Document Quality

This document has been widely discussed on the mailing lists of the regext 
and former eppext working groups.  The authors have addressed all comments
and many changes have been incorporated in the document.  

CentralNic has a working implementation of this specification and other 
domain name registries have implemented earlier versions of the specification.

James Gould is the document shepherd.  Barry Leiba is the responsible AD.

RFC Editor Note
There are two citations to RFC5646, but no reference.  RFC5646 should be added as a Normative Reference.
In Section 6.1, [W3C.REC-xmlschema-1-20041028] should be added as a citation after the text "a complete schema representation".