draft-ietf-regext-rdap-partial-response-08.txt   draft-ietf-regext-rdap-partial-response-09.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: October 16, 2020 April 14, 2020 Expires: October 16, 2020 April 14, 2020
Registration Data Access Protocol (RDAP) Partial Response Registration Data Access Protocol (RDAP) Partial Response
draft-ietf-regext-rdap-partial-response-08 draft-ietf-regext-rdap-partial-response-09
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. In fact, according to the capabilities to request partial responses. In fact, according to the
user authorization, the server can only return full responses. A user authorization, the server can only return full responses. A
partial response capability, especially in the case of search partial response capability, 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
specify their preference for obtaining a partial response. specify their preference for obtaining a partial response.
skipping to change at page 5, line 31 skipping to change at page 5, line 31
&fieldSet=afieldset", &fieldSet=afieldset",
"rel": "alternate", "rel": "alternate",
"href": "https://example.com/rdap/domains?name=*nr.com "href": "https://example.com/rdap/domains?name=*nr.com
&fieldSet=anotherfieldset", &fieldSet=anotherfieldset",
"title": "Result Subset Link", "title": "Result Subset Link",
"type": "application/rdap+json" "type": "application/rdap+json"
}, },
... ...
] ]
}, },
...
"domainSearchResults": [ "domainSearchResults": [
... ...
] ]
} }
Figure 2: Example of a "subsetting_metadata" instance Figure 2: Example of a "subsetting_metadata" instance
3. Dealing with Relationships 3. Dealing with Relationships
Some additional considerations can be made about how second level Some additional considerations can be made about how second level
skipping to change at page 7, line 8 skipping to change at page 7, line 8
above field sets. RDAP providers are RECOMMENDED to include a "self" above field sets. RDAP providers are RECOMMENDED to include a "self"
link in each field set. RDAP providers MAY also add any property link in each field set. RDAP providers MAY also add any property
providing service information. providing service information.
Fields included in "brief" and "full" field sets could be returned Fields included in "brief" and "full" field sets could be returned
according to the user access levels. according to the user access levels.
{ {
"rdapConformance": [ "rdapConformance": [
"rdap_level_0", "rdap_level_0",
"subsetting"
], ],
... ...
"domainSearchResults": [ "domainSearchResults": [
{ {
"objectClassName": "domain", "objectClassName": "domain",
"ldhName": "example1.com", "ldhName": "example1.com",
"links": [ "links": [
{ {
"value": "https://example.com/rdap/domain/example1.com", "value": "https://example.com/rdap/domain/example1.com",
"rel": "self", "rel": "self",
skipping to change at page 14, line 9 skipping to change at page 14, line 9
06: Clarified the use of self links in "Basic Field Sets" section. 06: Clarified the use of self links in "Basic Field Sets" section.
Added APNIC to the implementations of the "Implementation Status" Added APNIC to the implementations of the "Implementation Status"
section. section.
07: Changed "only a subset is returned" to "only a subset of fields 07: Changed "only a subset is returned" to "only a subset of fields
in each result object is returned" in the "Introduction" section. in each result object is returned" in the "Introduction" section.
Moved the "RDAP Conformance" section up in the document. Updated Moved the "RDAP Conformance" section up in the document. Updated
the "Acknowledgements" section. the "Acknowledgements" section.
08: Changed the rdapConformance tag "subsetting_level_0" to 08: Changed the rdapConformance tag "subsetting_level_0" to
"subsetting". Moved [RFC7942] to the "Normative References". "subsetting". Moved [RFC7942] to the "Normative References".
09: Corrected the "rdapConformance" content in Figure 3.
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. 4 change blocks. 
1 lines changed or deleted 4 lines changed or added

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