Hi all,
as you may note from the change log and diff tool, I have made a couple
of arrangements to the document:
- Have moved RFC6973 from Normative to Informative References because it
is an Informational RFC. I apologize if I missed this mistake before WGLC.
- Have removed the reference to rdap-openid . The reference was used in
the Appendix as a mere hint to a possible way to specify a purpose for a
reverse search query and, IMO, its removal don't change the meaning of
the sentence where It is cited. After the discussion at last aside
meeting at IETF, it seemed to me appropriate to remove that reference to
avoid a dependency from a document in deep progress. The only open
dependency left is on jsonpath-base which is expected to end the
evaluation process shortly.
Both the changes have been agreed with the shepherd.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: [regext] I-D Action:
draft-ietf-regext-rdap-reverse-search-15.txt
Data: Mon, 14 Nov 2022 06:13:16 -0800
Mittente: internet-dra...@ietf.org
Rispondi-a: regext@ietf.org
A: i-d-annou...@ietf.org
CC: regext@ietf.org
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Registration Protocols Extensions WG of
the IETF.
Title : Registration Data Access Protocol (RDAP) Reverse search capabilities
Authors : Mario Loffredo
Maurizio Martinelli
Filename : draft-ietf-regext-rdap-reverse-search-15.txt
Pages : 14
Date : 2022-11-14
Abstract:
The Registration Data Access Protocol (RDAP) does not include query
capabilities for finding the list of domains related to a set of
entities matching a given search pattern. In the RDAP context, an
entity can be associated with any defined object class. Moreover,
other relationships between object classes exist and might be used
for providing a reverse search capability. Therefore, a reverse
search can be applied to other use cases besides the classic domain-
entity scenario. This document describes an RDAP extension that
allows servers to provide a reverse search feature based on the
relationship defined in RDAP between an object class for search and
any related object class. The reverse search based on the domain-
entity relationship is treated as a particular case.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/
There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-reverse-search-15
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-reverse-search-15
Internet-Drafts are also available by rsync at
rsync.ietf.org::internet-drafts
_______________________________________________
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
