draft-ietf-regext-rdap-partial-response-02.txt   draft-ietf-regext-rdap-partial-response-03.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: November 28, 2019 May 27, 2019 Expires: January 31, 2020 July 30, 2019
Registration Data Access Protocol (RDAP) Partial Response Registration Data Access Protocol (RDAP) Partial Response
draft-ietf-regext-rdap-partial-response-02 draft-ietf-regext-rdap-partial-response-03
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. user authorization, the server can only return full responses.
Partial responses capability, especially in the case of search Partial responses 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 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 28, 2019. This Internet-Draft will expire on January 31, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 22 skipping to change at page 7, line 22
objects which are in turn provided according to a field set. objects which are in turn provided according to a field set.
5. Basic Field Sets 5. Basic Field Sets
In order to improve interoperability between clients and servers, the In order to improve interoperability between clients and servers, the
name, as well as the list of fields for each field set, should be name, as well as the list of fields for each field set, should be
shared by most of RDAP providers. This section defines three basic shared by most of RDAP providers. This section defines three basic
field sets which servers MAY implement to facilitate their field sets which servers MAY implement to facilitate their
interaction with clients: interaction with clients:
o "id": the server provides only the key field ("handle" for o "id": the server provides only the key field, respectively:
entities, "ldhName" for domains and nameservers). This field set "handle" for entities, "ldhName" for domains and nameservers. If
could be used when the client wants to simply obtain a collection a returned domain or nameserver is an IDN ([RFC5890]), then the
of object identifiers (Figure 4); "unicodeName" field MUST be included in the response. This field
set could be used when the client wants to simply obtain a
collection of object identifiers (Figure 4);
o "brief": it contains the fields that can be included in a "short" o "brief": it contains the fields that can be included in a "short"
response. This field set could be used when the client is asking response. This field set could be used when the client is asking
for a subset of the full response which gives a basic knowledge of for a subset of the full response which gives a basic knowledge of
each object; each object;
o "full": it contains all the information the server can provide for o "full": it contains all the information the server can provide for
a particular object. a particular object.
The "objectClassName" field is implicitly included in each of the The "objectClassName" field is implicitly included in each of the
skipping to change at page 10, line 35 skipping to change at page 10, line 35
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
RFC 5890, DOI 10.17487/RFC5890, August 2010,
<https://www.rfc-editor.org/info/rfc5890>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", Protocol (HTTP/1.1): Message Syntax and Routing",
RFC 7230, DOI 10.17487/RFC7230, June 2014, RFC 7230, DOI 10.17487/RFC7230, June 2014,
<https://www.rfc-editor.org/info/rfc7230>. <https://www.rfc-editor.org/info/rfc7230>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the [RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
Registration Data Access Protocol (RDAP)", RFC 7480, Registration Data Access Protocol (RDAP)", RFC 7480,
DOI 10.17487/RFC7480, March 2015, DOI 10.17487/RFC7480, March 2015,
<https://www.rfc-editor.org/info/rfc7480>. <https://www.rfc-editor.org/info/rfc7480>.
skipping to change at page 12, line 28 skipping to change at page 12, line 33
00: Initial working group version ported from draft-loffredo-regext- 00: Initial working group version ported from draft-loffredo-regext-
rdap-partial-response-03 rdap-partial-response-03
01: Removed "FOR DISCUSSION" items. Changed the basic field sets 01: Removed "FOR DISCUSSION" items. Changed the basic field sets
from REQUIRED to OPTIONAL. Removed the definition of fields from REQUIRED to OPTIONAL. Removed the definition of fields
included in "brief" field set. Provided a more detailed included in "brief" field set. Provided a more detailed
description of "subsetting_metadata" structure. Removed some description of "subsetting_metadata" structure. Removed some
references. references.
02: Added the "Negative Answers" section. Changed "IANA 02: Added the "Negative Answers" section. Changed "IANA
Considerations" section. Considerations" section.
03: Added the "unicodeName" field in the id fieldSet when a returned
domain or nameserver is an IDN. Added RFC5890 to "Normative
References" 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. 6 change blocks. 
7 lines changed or deleted 17 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/