I have read this draft. I work for an agency which has deployed RDAP in a globally connected context. I would welcome this draft progressing because we are already in a situation where public services designed to unite RDAP services could leverage this draft, and I want to see strong coherence between the names and numbers RDAP system behaviours.
I think this draft should be sent forward. -George On Fri, Apr 6, 2018 at 11:59 PM, James Galvin <gal...@elistx.com> wrote: > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Best Current > Practice: > > Registration Data Access Protocol (RDAP) Object Tagging > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-object-tag/ > > Please indicate your support for the publication of this document. > > If any working group member objects to the publication of this document > please respond on the list by close of business everywhere, Friday, 20 April > 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 interested in being the document shepherd please let > the chairs know. The document editors cannot be the document shepherd. > > If you’ve never been a document shepherd before don’t worry. It’s a great > way to understand the IETF process and your chairs would be delighted to > help you through it. > > Thanks, > > Antoin and Jim > WG Co-Chairs > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
