On Fri, Jan 18, 2019 at 05:04:20PM +0100, Antoin Verschuren wrote: > Hi all, > > As discussed on the mailinglist, we have selected 5 documents that people > most want to be added to our milestone list. > To be able to to that the documents should first be adopted as working group > documents. > This is a formal adoption request for > draft-loffredo-regext-rdap-reverse-search > > The draft is available here: > https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-reverse-search/ > > Please review this draft to see if you think it is suitable for adoption by > REGEXT, and comment to the list, clearly stating your view. > Please also indicate if you are willing to contribute text, review, be a > document shepherd, etc.
First, I wish to thank Mario and his co-authors for opening this line of work. I have a few comments on this draft (and I'll let the chairs determine if I'm agreeing with adoption or not). 1. From an operational point of few, I think there maybe a need differentiate the support of the different searches. In my (limited opinion), the requirement to support reverse searches by handle and email address are different than the requirement to support reverse search of name and physical address. Therefore, I think operators and policy people need a way to differentiate the various searches in their documentation. Perhaps this can be done by breaking the searches into multiple drafts and therefore registry A can say the support RFC XXXX while registry B can say they support RFC YYYY. Just a thought. 2. I don't know if we want to tackle the issue of distributing reverse searches. But that is an issue here. 3. The complexity of the query parameters makes me wonder if we should consider another mechanism for these more complex extensions... One such mechanism would be a general extension of using POST with GraphQL, and then doing profiles of reverse search (and other things) on top of that. -andy _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
