draft-ietf-regext-rdap-partial-response-14.txt   draft-ietf-regext-rdap-partial-response-15.txt 
Registration Protocols Extensions M. Loffredo Registration Protocols Extensions M. Loffredo
Internet-Draft M. Martinelli Internet-Draft M. Martinelli
Intended status: Standards Track IIT-CNR/Registro.it Intended status: Standards Track IIT-CNR/Registro.it
Expires: March 17, 2021 September 13, 2020 Expires: March 17, 2021 September 13, 2020
Registration Data Access Protocol (RDAP) Partial Response Registration Data Access Protocol (RDAP) Partial Response
draft-ietf-regext-rdap-partial-response-14 draft-ietf-regext-rdap-partial-response-15
Abstract Abstract
The Registration Data Access Protocol (RDAP) does not include The Registration Data Access Protocol (RDAP) does not include
capabilities to request partial responses. Servers will only return capabilities to request partial responses. Servers will only return
full responses that include all of the information that a client is full responses that include all of the information that a client is
authorized to receive. A partial response capability that limits the authorized to receive. A partial response capability that limits the
amount of information returned, especially in the case of search amount of information returned, especially in the case of search
queries, could bring benefits to both clients and servers. This queries, could bring benefits to both clients and servers. This
document describes an RDAP query extension that allows clients to document describes an RDAP query extension that allows clients to
skipping to change at page 12, line 50 skipping to change at page 12, line 50
https://example.com/rdap/domains?name=example*.com https://example.com/rdap/domains?name=example*.com
&fields=domainSearchResults(objectClassName,ldhName, &fields=domainSearchResults(objectClassName,ldhName,
unicodeName, unicodeName,
status, status,
events(eventAction,eventDate), events(eventAction,eventDate),
entities(objectClassName,handle,roles), entities(objectClassName,handle,roles),
nameservers(objectClassName,ldhName)) nameservers(objectClassName,ldhName))
Figure 5: Examples of CQL expressions for a domain search query Figure 5: Examples of CQL expressions for a domain search query
The latter approach seems to facilitate RDAP interoperability. The field set approach seems to facilitate RDAP interoperability.
Servers can define basic field sets which, if known to clients, can Servers can define basic field sets which, if known to clients, can
increase the probability of obtaining a valid response. The usage of increase the probability of obtaining a valid response. The usage of
field sets makes the query string be less complex. Moreover, the field sets makes the query string be less complex. Moreover, the
definition of pre-defined sets of fields makes it easier to establish definition of pre-defined sets of fields makes it easier to establish
result limits. result limits.
Finally, considering that there is no real need for RDAP users to Finally, considering that there is no real need for RDAP users to
have the maximum flexibility in defining all the possible sets of have the maximum flexibility in defining all the possible sets of
logically connected fields (e.g. users interested in domains usually logically connected fields (e.g. users interested in domains usually
need to know the status, the creation date, and the expiry date of need to know the status, the creation date, and the expiry date of
each domain), the latter approach is preferred. each domain), the field set approach is preferred.
Acknowledgements Acknowledgements
The authors would like to acknowledge Scott Hollenbeck, Tom Harrison, The authors would like to acknowledge Scott Hollenbeck, Tom Harrison,
Karl Heinz Wolf, Jasdip Singh, Patrick Mevzek, Benjamin Kaduk, Roman Karl Heinz Wolf, Jasdip Singh, Patrick Mevzek, Benjamin Kaduk, Roman
Danyliw, Murray Kucherawy, Erik Kline and Robert Wilton for their Danyliw, Murray Kucherawy, Erik Kline and Robert Wilton for their
contribution to this document. contribution to this document.
Change Log Change Log
skipping to change at page 14, line 49 skipping to change at page 14, line 49
+ replaced the phrase "the response MAY include additional + replaced the phrase "the response MAY include additional
information regarding the negative answer" with the phrase information regarding the negative answer" with the phrase
"the response MAY include additional information regarding "the response MAY include additional information regarding
the supported field sets"; the supported field sets";
+ added a new example; + added a new example;
* replaced the phrase "and subsequent denial of service due to * replaced the phrase "and subsequent denial of service due to
abuse" with the phrase "and subsequent denial of service" in abuse" with the phrase "and subsequent denial of service" in
"Security Considerations" section; "Security Considerations" section;
* corrected the [REST] reference in the "Informative References" * corrected the [REST] reference in the "Informative References"
section; section;
* in "Appendix A":; * in "Appendix A":
+ added the phrase " offered by data providers on the web" + added the phrase " offered by data providers on the web"
after the phrase "Looking at the implementation experiences after the phrase "Looking at the implementation experiences
of partial response"; of partial response";
+ replaced the phrase "servers should define a strategy" with + replaced the phrase "servers should define a strategy" with
the phrase "servers have to define a strategy"; the phrase "servers have to define a strategy";
+ replaced the term "latter approach" with the term "field set + replaced the term "latter approach" with the term "field set
approach" in the "Appendix A.1" section; approach" in the "Appendix A.1" section;
* updated the "Acknowledgements" section. * updated the "Acknowledgements" section.
15: Minor edit in the "Appendix A.1" section.
Authors' Addresses Authors' Addresses
Mario Loffredo Mario Loffredo
IIT-CNR/Registro.it IIT-CNR/Registro.it
Via Moruzzi,1 Via Moruzzi,1
Pisa 56124 Pisa 56124
IT IT
Email: mario.loffredo@iit.cnr.it Email: mario.loffredo@iit.cnr.it
 End of changes. 5 change blocks. 
4 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/