Rubens,

Thanks, that minor issue will be addressed.

—

JG

[id:[email protected]]

James Gould
Distinguished Engineer
[email protected]

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>

From: Rubens Kuhl <[email protected]>
Date: Friday, January 12, 2018 at 6:52 PM
To: James Galvin <[email protected]>, James Gould <[email protected]>, 
<[email protected]>
Cc: Registration Protocols Extensions <[email protected]>
Subject: [EXTERNAL] Re: [regext] WGLC: 
https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token

I believe there is either a minor omission or punctuation error at Page 17:


6.3.  Neustar gTLD SRS



   Organisation: Neustar Inc.



Gould & Feher             Expires July 6, 2018                 [Page 17]

Internet-Draft               allocationToken                January 2018



   Name: Neustar generic Top Level Domain (gTLD) Shared Registry System

   (SRS).



   Description: The Neustar gTLD SRS implements the server side of

   draft-ietf-regext-allocation-token.  For several Top Level Domains



   Level of maturity: Production

The description probably meant to be a single phrase.

But it is not a show stopper for the document if the correction is to be done 
further down the road, since the meaning is unequivocal.


Rubens



On 12 Jan 2018, at 11:32, James Galvin 
<[email protected]<mailto:[email protected]>> wrote:

The document editors have indicated that the following document is ready for 
submission to the IESG to be considered for publication as a Proposed Standard:

Allocation Token Extension for the Extensible Provisioning Protocol (EPP)
https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token-05

If any working group member objects to the publication of this document please 
respond on the list by close of business everywhere, Friday, 26 January 2018.  
If there are no objections the document will be submitted to the IESG.

During the last call the chairs are looking for a document shepherd for this 
document.  If you are interesting in being the document shepherd please let the 
chairs know.  The document editors can not be the document shepherd.

Thanks,

Antoin and Jim
WG Co-Chairs

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to