> -----Original Message----- > From: I-D-Announce [mailto:i-d-announce-boun...@ietf.org] On Behalf Of > internet-dra...@ietf.org > Sent: Tuesday, October 25, 2016 5:39 PM > To: i-d-annou...@ietf.org > Subject: I-D Action: draft-lozano-ietf-regext-registrar-expiration- > date-00.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Registrar Registration Expiration Date > Extension Mapping for the Extensible Provisioning Protocol (EPP) > Author : Gustavo Lozano > Filename : draft-lozano-ietf-regext-registrar-expiration- > date-00.txt > Pages : 13 > Date : 2016-10-25 > > Abstract: > This document describes an Extensible Provisioning Protocol (EPP) > extension mapping for the provisioning and management of the > registrar registration expiration date for domain names stored in a > shared central repository. Specified in XML, this mapping extends > the EPP domain name mapping.
Quick comment that is a repeat of something I said in some other context at some other time (sorry, it's all a bit of a blur): This document needs to add a paragraph or two that explains *exactly* what a "registrar registration expiration date" is and how it relates to the <domain:exDate> element defined in RFC 5731. The draft defines the mechanics for the extension, but it doesn't provide enough information to explain what this value is, what purpose it serves, and why it might differ from the exDate. The informative reference to the "GNSO Council Policy Recommendations for a new Consensus Policy on Thick Whois" mentions a registrar expiration date, but it doesn't explain what it is, either. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
