]> IIT-CNR/Registro.it

Via Moruzzi,1 Pisa IT 56124 mario.loffredo@iit.cnr.it http://www.iit.cnr.it

IIT-CNR/Registro.it

Via Moruzzi,1 Pisa IT 56124 maurizio.martinelli@iit.cnr.it http://www.iit.cnr.it

Applications and Real-Time Registration Protocols Extensions RDAP Partial response The Registration Data Access Protocol (RDAP) does not include capabilities to request partial responses. Servers will only return full responses that include all of the information that a client is authorized to receive. A partial response capability that limits the amount of information returned, especially in the case of search queries, could bring benefits to both clients and servers. This document describes an RDAP query extension that allows clients to specify their preference for obtaining a partial response.

The use of partial responses in RESTful API design is very common. The rationale is quite simple: instead of returning objects in API responses with all data fields, only a subset of the fields in each result object is returned. The benefit is obvious: less data transferred over the network means less bandwidth usage, faster server responses, less CPU time spent both on the server and the client, and less memory usage on the client. Currently, RDAP does not provide a client with any way to request a partial response. Servers can only provide the client with a full response . Servers cannot limit the amount of information returned in a response based on a client's preferences, and this creates inefficiencies. The protocol described in this specification extends RDAP search capabilities to enable partial responses through the provisioning of pre-defined sets of fields that clients can submit to an RDAP service by adding a new query parameter. The service is implemented using the Hypertext Transfer Protocol (HTTP) and the conventions described in .

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The path segment defined in this section is an OPTIONAL extension of search path segments defined in . This document defines an RDAP query parameter, "fieldSet", whose value is a non-empty string identifying a server-defined set of fields returned in place of the full response (). The field sets supported by a server are usually described in out-of-band documents (e.g., RDAP profile) together with other features. Moreover, this document defines in an in-band mechanism by means of which servers can provide clients with a basic information about the supported field sets.

This solution can be implemented by RDAP providers with less effort than field selection and is easily requested by clients. The considerations that have led to this solution are described in more detail in .

According to most advanced principles in REST design, collectively known as HATEOAS (Hypermedia as the Engine of Application State) , a client entering a REST application through an initial URI should use server-provided links to dynamically discover available actions and access the resources it needs. In this way, the client is not required to have prior knowledge of the service and, consequently, to hard code the URIs of different resources. This allows the server to make URI changes as the API evolves without breaking clients. Definitively, a REST service should be as self-descriptive as possible. Therefore, servers implementing the query parameter described in this specification SHOULD provide additional information in their responses about the available field sets. Such information is collected in a new JSON data structure named "subsetting_metadata" containing the following properties: "currentFieldSet": "String" (REQUIRED) either the value of the "fieldSet" parameter as specified in the query string, or the field set applied by default; "availableFieldSets": "AvailableFieldSet[]" (OPTIONAL) an array of objects, with each element describing an available field set. The AvailableFieldSet object includes the following members: "name": "String" (REQUIRED) the field set name; "default": "Boolean" (REQUIRED) whether the field set is applied by default. An RDAP server MUST define only one default field set; "description": "String" (OPTIONAL) a human-readable description of the field set; "links": "Link[]" (OPTIONAL) an array of links as described in containing the query string that applies the field set (see ).

Servers returning the "subsetting_metadata" section in their responses MUST include "subsetting" in the rdapConformance array.

An RDAP server MAY use the "links" array of the "subsetting_metadata" element to provide ready-made references to the available field sets (). The target URI in each link is the reference to an alternative to the current view of results identified by the context URI. The "value", "rel" and "href" JSON values MUST be specified. All other JSON values are OPTIONAL.

Representation of second level objects within a field set produces additional considerations. Since the representation of the topmost returned objects will vary according to the field set in use, the response may contain no relationships (e.g., for an abbreviated field set) or may contain associated objects as in a normal RDAP query response. Each field set can indicate the format of the additional objects to be returned, in the same manner that the format of the topmost objects is controlled by the field set.

This section defines three basic field sets which servers MAY implement to facilitate their interaction with clients: "id": the server provides only the key field: "handle" for entities, "ldhName" for domains and nameservers. If a returned domain or nameserver is an Internationalized Domain Name (IDN) , then the "unicodeName" field MUST additionally be included in the response. This field set could be used when the client wants to obtain a collection of object identifiers (); "brief": the field set contains the fields that can be included in a "short" response. This field set could be used when the client is asking for a subset of the full response which provides only basic knowledge of each object; "full": the field set contains all of the information the server can provide for a particular object. The "objectClassName" field is implicitly included in each of the above field sets. RDAP providers SHOULD include a "links" field indicating the "self" link relationship. RDAP providers MAY also add any property providing service information. Fields included in the "brief" and "full" field set responses MUST take into account the user's access and authorization levels.

{ "rdapConformance": [ "rdap_level_0", "subsetting" ], ... "domainSearchResults": [ { "objectClassName": "domain", "ldhName": "example1.com", "links": [ { "value": "https://example.com/rdap/domain/example1.com", "rel": "self", "href": "https://example.com/rdap/domain/example1.com", "type": "application/rdap+json" } ] }, { "objectClassName": "domain", "ldhName": "example2.com", "links": [ { "value": "https://example.com/rdap/domain/example2.com", "rel": "self", "href": "https://example.com/rdap/domain/example2.com", "type": "application/rdap+json" } ] }, ... ] }

Each request including an empty or unsupported "fieldSet" value MUST produce an HTTP 400 (Bad Request) response code. Optionally, the response MAY include additional information regarding the supported field sets in the HTTP entity body ().

{ "errorCode": 400, "title": "Field set 'unknownfieldset' is not valid", "description": [ "Supported field sets are: 'afieldset', 'anotherfieldset'." ] }

IANA is requested to register the following value in the RDAP Extensions Registry: Extension identifier: subsetting Registry operator: Any Published specification: This document. Contact: IETF <iesg@ietf.org> Intended usage: This extension describes best practice for partial response provisioning.

NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Responsible Organization: Institute of Informatics and Telematics of the National Research Council (IIT-CNR)/Registro.it Location: https://rdap.pubtest.nic.it/ Description: This implementation includes support for RDAP queries using data from .it public test environment. Level of Maturity: This is an "alpha" test implementation. Coverage: This implementation includes all of the features described in this specification. Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it

Responsible Organization: Asia-Pacific Network Information Centre Location: https://github.com/APNIC-net/rdap-rmp-demo/tree/partial-response Description: A proof-of-concept for RDAP mirroring. Level of Maturity: This is a proof-of-concept implementation. Coverage: This implementation includes all of the features described in this specification. Contact Information: Tom Harrison, tomh@apnic.net

A search query typically requires more server resources (such as memory, CPU cycles, and network bandwidth) when compared to a lookup query. This increases the risk of server resource exhaustion and subsequent denial of service. This risk can be mitigated by supporting the return of partial responses combined with other strategies (e.g. restricting search functionality, limiting the rate of search requests, and truncating and paging results). Support for partial responses gives RDAP operators the ability to implement data access control policies based on the HTTP authentication mechanisms described in . RDAP operators can vary the information returned in RDAP responses based on a client's access and authorization levels. For example: the list of fields for each set can differ based on the client's access and authorization levels; the set of available field sets could be restricted based on the client's access and authorization levels. Servers can also define different result limits according to the available field sets, so a more flexible truncation strategy can be implemented. The new query parameter presented in this document provides RDAP operators with a way to implement a server that reduces inefficiency risks.

&RFC2119; &RFC5890; &RFC7230; &RFC7480; &RFC7481; &RFC7482; &RFC7483; &RFC7942; &RFC8174; &RFC8288; PH.D. DISSERTATION, UNIVERSITY OF CALIFORNIA, IRVINE

Looking at the implementation experiences of partial response offered by data providers on the web, two approaches are observed: The client explicitly describes the data fields to be returned; The client describes a name identifying a server-defined set of data fields. The former is more flexible than the latter because clients can specify all the data fields they need. However, it has some drawbacks: Fields have to be declared according to a given syntax. This is a simple task when the data structure of the object is flat, but it is much more difficult when the object has a tree structure like that of a JSON object. The presence of arrays and deep nested objects complicate both the syntax definition of the query and, consequently, the processing required on the server side; Clients need to recognize the returned data structure to avoid cases when the requested fields are invalid; The request of some fields might not match the client's access and authorization levels. Clients might request unauthorized fields and servers have to define a strategy for responding, such as always returning an error response or returning a response that ignores the unauthorized fields.

In addition to those listed above, RDAP responses raise some specific issues: Relevant entity object information is included in a jCard, but such information cannot be easily selected because it is split into the items of a jagged array; RDAP responses contain some properties providing service information (e.g. rdapConformance, links, notices, remarks, etc.) which are not normally selected but they are just as important. They could be returned anyway but, in this case, the server would provide unrequested data. It is possible to address these issues. For example, the Catnap Query Language is a comprehensive expression language that can be used to customize the JSON response of a RESTful web service. Application of CQL to RDAP responses would explicitly identify the output fields that would be acceptable when a few fields are requested but it would become very complicated when processing a larger number of fields. In the following, two CQL expressions for a domain search query are shown (). In the first, only objectClassName and ldhName are requested. In the second, the fields of a possible WHOIS-like response are listed.

The latter approach seems to facilitate RDAP interoperability. Servers can define basic field sets which, if known to clients, can increase the probability of obtaining a valid response. The usage of field sets makes the query string be less complex. Moreover, the definition of pre-defined sets of fields makes it easier to establish result limits. Finally, considering that there is no real need for RDAP users to have the maximum flexibility in defining all the possible sets of logically connected fields (e.g. users interested in domains usually need to know the status, the creation date, and the expiry date of each domain), the latter approach is preferred.

The authors would like to acknowledge Scott Hollenbeck, Tom Harrison, Karl Heinz Wolf, Jasdip Singh, Patrick Mevzek, Benjamin Kaduk, Roman Danyliw, Murray Kucherawy, Erik Kline and Robert Wilton for their contribution to this document.

Initial working group version ported from draft-loffredo-regext-rdap-partial-response-03 Removed "FOR DISCUSSION" items. Changed the basic field sets from REQUIRED to OPTIONAL. Removed the definition of fields included in "brief" field set. Provided a more detailed description of "subsetting_metadata" structure. Removed some references. Added the "Negative Answers" section. Changed "IANA Considerations" section. Added the "unicodeName" field in the id fieldSet when a returned domain or nameserver is an IDN. Added RFC5890 to "Normative References" section. Recommended the RDAP providers to include a "self" link in any field set other than "full". Updated "Acknowledgements" section. Moved "Approaches to Partial Response Implementation" section to the appendix. Clarified the use of self links in "Basic Field Sets" section. Added APNIC to the implementations of the "Implementation Status" section. Changed "only a subset is returned" to "only a subset of fields in each result object is returned" in the "Introduction" section. Moved the "RDAP Conformance" section up in the document. Updated the "Acknowledgements" section. Changed the rdapConformance tag "subsetting_level_0" to "subsetting". Moved to the "Normative References". Corrected the "rdapConformance" content in . Corrected the JSON content in . Clarified the meaning of both context and target URIs in a result subset link defined in . Updated the "Acknowledgements" section. Minor pre-AD review edits. Additional minor pre-AD review edits. Edits due to Gen-ART review: in the first paragraph of clarified how field sets are defined by a server, in the first sentence of replaced SHOULD with MUST. Other minor edits due to AD review. Edits due to IESG review: replaced "fewer data transferred" with "less data transferred" in the "Introduction" section; in the "Subsetting Metadata" section;: replaced the phrase "collected in a new data structure" with the phrase "collected in a new JSON data structure"; replaced "Members are:" with "The AvailableFieldSet object includes the following members:"; clarified that an RDAP server MUST define only one default field set; clarified the required members of a Link object in the "Subsetting Links" section; rewritten the "Dealing with Relationships" section; in the "Basic Field Sets" section: replaced the phrase "include a 'self' link in each field set" with the phrase "include a 'links' field indicating the 'self' link relationship"; replaced the phrase "'unicodeName' field MUST be included" with the phrase "'unicodeName' field MUST additionally be included"; in the "Negative Answers" section: replaced the phrase "the response MAY include additional information regarding the negative answer" with the phrase "the response MAY include additional information regarding the supported field sets"; added a new example; replaced the phrase "and subsequent denial of service due to abuse" with the phrase "and subsequent denial of service" in "Security Considerations" section; corrected the [REST] reference in the "Informative References" section; in "Appendix A":; added the phrase " offered by data providers on the web" after the phrase "Looking at the implementation experiences of partial response"; replaced the phrase "servers should define a strategy" with the phrase "servers have to define a strategy"; replaced the term "latter approach" with the term "field set approach" in the "Appendix A.1" section; updated the "Acknowledgements" section.