On 18 Apr 2017, at 8:46, Hollenbeck, Scott wrote:

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-boun...@ietf.org] On Behalf Of
internet-dra...@ietf.org
Sent: Tuesday, April 18, 2017 8:34 AM
To: i-d-annou...@ietf.org
Subject: [EXTERNAL] I-D Action: draft-hollenbeck-regext-rdap-object-tag-
03.txt
…

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-object-tag/

This version includes a description of the Verisign Labs implementation of the proposed tagging scheme.

With this update I would like to ask the chairs to ask the WG to consider adoption of this document. I would also like to ask anyone else who might have implemented the scheme to let me know so that I can add more information to the Implementation Status section.

Scott,

Thanks for this. We will certainly add it to the list of documents to be considered for adoption.

Recall from our last meeting at the IETF, our AD does not want us to add any more documents to our milestone list until we moved some things along.

The actions we had agreed to at the meeting were as follows (summarized from the minutes of the last meeting):

1. With respect to the escrow documents (which were also being considered for adoption), the authors should revive the documents as individual contributions and add an implementation status section. We will consider these documents again after we complete the next two actions.

2. The WG needs to revisit its current list of extensions and clearly indicate those that are to be standards track and those that just need an entry in the extension registry.

3. For those documents intended for the standards track, poke the editors to see if there is going to be forward progress or consider withdrawing the documents.

Once we have cleaned up our current list of adopted documents, then we can consider adding new documents.

Jim

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to