Capturing/elaborating on my comments at the mic the WG meeting in Montreal…
Related to these three drafts:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/
I offer that the number of RDAP server implementations is about to go (perhaps
‘undergoing’) a significant increase due to the Aug 26 deadline for ICANN gTLD
registries and registrars to launch their own RDAP servers (see
https://www.icann.org/rdap ). Consequently, the RDAP community is in the
process of both rapidly expanding and gaining valuable implementation
experience with ‘basic’ RDAP implementation capabilities.
As it relates to the partial-response and sorting-and-paging drafts, I think
that the emerging implementation work will be providing an opportunity for both
the drafts to be exposed to experience gained on both the client and server.
As it relates to the reverse-search draft, the privacy considerations related
to this are subtle/complex within the context of recent/current IETF
discussions and are also related to legal/policy considerations outside the
IETF sphere. The outcome of forthcoming IETF discussions and incorporation of
relevant legal/policy discussions will (presumably) need to be taken into
consideration by this I-D.
I recognize and agree that ICANN gTLD policy work need not be a key dependency
for REGEXT work. But in this case, ICANN gTLD policy work is not the only
policy question that is being considered. There are also national
legislation/regulations that are emerging in this area and the EU GDPR is in
effect for just over a year (i.e GDPR is still relatively new). Consequently,
these EU/national policy considerations could have relevant impact.
Thus, for all three of these I-Ds, I would suggest that the milestone dates be
extended in order to allow for more experience (partial-response and
sorting-and-paging), more discussion (reverse-search), and for the relevant
policy work to be completed/incorporated (reverse-search). I think that the
extensions will allow for the documents to evolve/mature based on these items,
thus leading to more stable and long-lived documents.
Thanks,
Rick
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
