draft-ietf-regext-rdap-reverse-search-06.txt   draft-ietf-regext-rdap-reverse-search-07.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 11, 2021 April 9, 2021 Expires: 8 April 2022 5 October 2021
Registration Data Access Protocol (RDAP) Reverse search capabilities Registration Data Access Protocol (RDAP) Reverse search capabilities
draft-ietf-regext-rdap-reverse-search-06 draft-ietf-regext-rdap-reverse-search-07
Abstract Abstract
The Registration Data Access Protocol (RDAP) does not include query The Registration Data Access Protocol (RDAP) does not include query
capabilities to find the list of domains related to a set of entities capabilities to find the list of domains related to a set of entities
matching a given search pattern. In the RDAP context, an entity can matching a given search pattern. In the RDAP context, an entity can
be associated to any defined object class. Therefore, a reverse be associated to any defined object class. Therefore, a reverse
search can be applied to other use cases than the classic domain- search can be applied to other use cases than the classic domain-
entity scenario. This document describes RDAP query extensions that entity scenario. This document describes RDAP query extensions that
allow servers to provide a reverse search feature based on the allow servers to provide a reverse search feature based on the
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 October 11, 2021. This Internet-Draft will expire on 8 April 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Simplified BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 4
2. RDAP Path Segment Specification . . . . . . . . . . . . . . . 4 2. RDAP Path Segment Specification . . . . . . . . . . . . . . . 4
3. RDAP Conformance . . . . . . . . . . . . . . . . . . . . . . 5 3. RDAP Conformance . . . . . . . . . . . . . . . . . . . . . . 5
4. Implementation Considerations . . . . . . . . . . . . . . . . 5 4. Implementation Considerations . . . . . . . . . . . . . . . . 6
5. Implementation Status . . . . . . . . . . . . . . . . . . . . 5 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 6
5.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 6 5.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6 7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Paradigms to Enforce Access Control on Reverse Appendix A. Paradigms to Enforce Access Control on Reverse Search
Search in RDAP . . . . . . . . . . . . . . . . . . . 9 in RDAP . . . . . . . . . . . . . . . . . . . . . . . . . 10
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 10 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Reverse Whois is a service provided by many web applications that Reverse Whois is a service provided by many web applications that
allow users to find domain names owned by an individual or a company allow users to find domain names owned by an individual or a company
starting from the owner's details, such as name and email. Even if starting from the owner's details, such as name and email. Even if
it has been considered useful for some legal purposes (e.g. it has been considered useful for some legal purposes (e.g.
uncovering trademark infringements, detecting cybercrime cases), its uncovering trademark infringements, detecting cybercrime cases), its
availability as a standardized Whois capability has been objected for availability as a standardized Whois capability has been objected for
two main reasons, which now don't seem to conflict with an RDAP two main reasons, which now don't seem to conflict with an RDAP
skipping to change at page 3, line 20 skipping to change at page 3, line 23
almost always performed by specifying an entity role (e.g. almost always performed by specifying an entity role (e.g.
registrant, technical contact) and this can contribute to restricting registrant, technical contact) and this can contribute to restricting
the result set. the result set.
Reverse searches, such as finding the list of domain names associated Reverse searches, such as finding the list of domain names associated
with contacts or nameservers may be useful to registrars as well. with contacts or nameservers may be useful to registrars as well.
Usually, registries adopt out-of-band solutions to provide results to Usually, registries adopt out-of-band solutions to provide results to
registrars asking for reverse searches on their domains. Possible registrars asking for reverse searches on their domains. Possible
reasons for such requests are: reasons for such requests are:
o the loss of synchronization between the registrar database and the * the loss of synchronization between the registrar database and the
registry database; registry database;
* the need for such data to perform massive EPP [RFC5730] updates
o the need for such data to perform massive EPP [RFC5730] updates
(e.g. changing the contacts of a set of domains, etc.). (e.g. changing the contacts of a set of domains, etc.).
Currently, RDAP does not provide any way for a client to search for Currently, RDAP does not provide any way for a client to search for
the collection of domains associated with an entity [RFC7482]. A the collection of domains associated with an entity [RFC9082]. A
query (lookup or search) on domains can return the array of entities query (lookup or search) on domains can return the array of entities
related to a domain with different roles (registrant, registrar, related to a domain with different roles (registrant, registrar,
administrative, technical, reseller, etc.), but the reverse operation administrative, technical, reseller, etc.), but the reverse operation
is not allowed. Only reverse searches to find the collection of is not allowed. Only reverse searches to find the collection of
domains related to a nameserver (ldhName or ip) can be requested. domains related to a nameserver (ldhName or ip) can be requested.
Since an entity can be in relationship with any RDAP object Since an entity can be in relationship with any RDAP object
[RFC7483], the availability of a reverse search can be common to all [RFC9083], the availability of a reverse search can be common to all
resource type path segments defined for search. resource type path segments defined for search.
The protocol described in this specification aims to extend the RDAP The protocol described in this specification aims to extend the RDAP
query capabilities to enable the reverse search based on the query capabilities to enable the reverse search based on the
relationship between any object and the associated entities. The relationship between any object and the associated entities. The
extension is implemented by adding new path segments (i.e. search extension is implemented by adding new path segments (i.e. search
paths) and using a RESTful web service [REST]. The service is paths) and using a RESTful web service [REST]. The service is
implemented using the Hypertext Transfer Protocol (HTTP) [RFC7230] implemented using the Hypertext Transfer Protocol (HTTP) [RFC7230]
and the conventions described in [RFC7480]. and the conventions described in [RFC7480].
skipping to change at page 4, line 8 skipping to change at page 4, line 16
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. RDAP Path Segment Specification 2. RDAP Path Segment Specification
The new search paths are OPTIONAL extensions of those defined in The new search paths are OPTIONAL extensions of those defined in
[RFC7482]. A generic reverse search path is described by the syntax: [RFC9082]. A generic reverse search path is described by the syntax:
{resource-type}/reverse/{role}?{property}=<search pattern> {resource-type}/reverse/{role}?{property}=<search pattern>
The path segments are defined as in the following: The path segments are defined as in the following:
o resource-type: it MUST be one of resource type path segments * resource-type: it MUST be one of resource type path segments
defined in Section 3.2 of [RFC7482]: "domains", "nameservers" or defined in Section 3.2 of [RFC9082]: "domains", "nameservers" or
"entities"; "entities";
* role: it MUST be one of the roles described in Section 10.2.4 of
o role: it MUST be one of the roles described in Section 10.2.4 of [RFC9083]. For role independent reverse searches, the value
[RFC7483]. For role independent reverse searches, the value
"entity" MUST be used; "entity" MUST be used;
* property: it identifies the entity property to be used in matching
o property: it identifies the entity property to be used in matching
the search pattern. A pre-defined list of properties includes: the search pattern. A pre-defined list of properties includes:
fn, handle, email, city, country, cc. The mapping between such fn, handle, email, city, country, cc. The mapping between such
properties and the RDAP properties is shown in Table 1. Some of properties and the RDAP properties is shown in Table 1. Some of
the properties are related to jCard elements [RFC7095] but, being the properties are related to jCard elements [RFC7095] but, being
jCard the JSON format for vCard [RFC6350], the corresponding jCard the JSON format for vCard [RFC6350], the corresponding
definitions are included in vCard specification. Servers MAY definitions are included in vCard specification. Servers MAY
implement additional properties to those defined in this document. implement additional properties to those defined in this document.
Partial string matching is allowed as defined in section 4.1 of Partial string matching is allowed as defined in section 4.1 of
[RFC7482]. [RFC9082].
+-------------------+--------------------+--------+--------+--------+ +=========================+===============+==========+=======+======+
| Reverse search | RDAP property | RFC | RFC | RFC | | Reverse search property | RDAP property | RFC | RFC | RFC |
| property | | 7483 | 6350 | 8605 | | | | 9083 | 6350 | 8605 |
+-------------------+--------------------+--------+--------+--------+ +=========================+===============+==========+=======+======+
| handle | handle | 5.1. | | | | handle | handle | 5.1. | | |
| fn | jCard fn | | 6.2.1 | | +-------------------------+---------------+----------+-------+------+
| email | jCard email | | 6.4.2 | | | fn | jCard fn | | 6.2.1 | |
| city | locality in jCard | | 6.3.1 | | +-------------------------+---------------+----------+-------+------+
| | adr | | | | | email | jCard email | | 6.4.2 | |
| country | country name in | | 6.3.1 | | +-------------------------+---------------+----------+-------+------+
| | jCard adr | | | | | city | locality in | | 6.3.1 | |
| cc | country code in | | | 3.1 | | | jCard adr | | | |
| | jCard adr | | | | +-------------------------+---------------+----------+-------+------+
+-------------------+--------------------+--------+--------+--------+ | country | country name | | 6.3.1 | |
| | in jCard adr | | | |
+-------------------------+---------------+----------+-------+------+
| cc | country code | | | 3.1 |
| | in jCard adr | | | |
+-------------------------+---------------+----------+-------+------+
Table 1: Mapping between the reverse search properties and the RDAP Table 1: Mapping between the reverse search properties and the
properties RDAP properties
https://example.com/rdap/domains/reverse/technical?handle=CID-40* https://example.com/rdap/domains/reverse/technical?handle=CID-40*
https://example.com/rdap/domains/reverse/registrant?fn=Bobby* https://example.com/rdap/domains/reverse/registrant?fn=Bobby*
https://example.com/rdap/domains/reverse/registrant?cc=US https://example.com/rdap/domains/reverse/registrant?cc=US
https://example.com/rdap/entites/reverse/registrar?handle=RegistrarX https://example.com/rdap/entites/reverse/registrar?handle=RegistrarX
Figure 1: Examples of reverse search queries Figure 1: Examples of reverse search queries
The "country" property can be used as an alternative to "cc" when The "country" property can be used as an alternative to "cc" when
RDAP servers don't include the jCard "cc" parameter [RFC8605] in RDAP servers don't include the jCard "cc" parameter [RFC8605] in
their response. their response.
3. RDAP Conformance 3. RDAP Conformance
Servers complying with this specification MUST include the value Servers complying with this specification MUST include the value
"reverse_search" in the rdapConformance property of the help response "reverse_search" in the rdapConformance property of the help response
[RFC7483]. The information needed to register this value in the [RFC9083]. The information needed to register this value in the
"RDAP Extensions" registry is described in Section 6. "RDAP Extensions" registry is described in Section 6.
4. Implementation Considerations 4. Implementation Considerations
The implementation of the proposed extension is technically feasible. The implementation of the proposed extension is technically feasible.
Both handle and fn are used as standard path segments to search for Both handle and fn are used as standard path segments to search for
entities [RFC7482]. With regards to the other reverse search entities [RFC9082]. With regards to the other reverse search
properties, namely email, city and country code, the impact of their properties, namely email, city and country code, the impact of their
usage on server processing is evaluated to be the same as other usage on server processing is evaluated to be the same as other
existing query capabilities (e.g. wildcard prefixed search pattern) existing query capabilities (e.g. wildcard prefixed search pattern)
so the risks to degrade the performance or to generate huge result so the risks to degrade the performance or to generate huge result
sets can be mitigated by adopting the same policies (e.g. restricting sets can be mitigated by adopting the same policies (e.g. restricting
the search functionality, limiting the rate of search requests the search functionality, limiting the rate of search requests
according to the user profile, truncating and paging the results, according to the user profile, truncating and paging the results,
returning partial responses). returning partial responses).
5. Implementation Status 5. Implementation Status
skipping to change at page 6, line 18 skipping to change at page 6, line 46
According to RFC 7942, "this will allow reviewers and working groups According to RFC 7942, "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable experimentation running code, which may serve as evidence of valuable experimentation
and feedback that have made the implemented protocols more mature. and feedback that have made the implemented protocols more mature.
It is up to the individual working groups to use this information as It is up to the individual working groups to use this information as
they see fit". they see fit".
5.1. IIT-CNR/Registro.it 5.1. IIT-CNR/Registro.it
Responsible Organization: Institute of Informatics and Telematics * Responsible Organization: Institute of Informatics and Telematics
of National Research Council (IIT-CNR)/Registro.it of National Research Council (IIT-CNR)/Registro.it
Location: https://rdap.pubtest.nic.it/ * Location: https://rdap.pubtest.nic.it/
Description: This implementation includes support for RDAP queries * Description: This implementation includes support for RDAP queries
using data from the public test environment of .it ccTLD. using data from the public test environment of .it ccTLD.
Level of Maturity: This is an "alpha" test implementation. * Level of Maturity: This is an "alpha" test implementation.
Coverage: This implementation includes all of the features
* Coverage: This implementation includes all of the features
described in this specification. described in this specification.
Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it * Contact Information: Mario Loffredo, mario.loffredo@iit.cnr.it
6. IANA Considerations 6. IANA Considerations
IANA is requested to register the following value in the RDAP IANA is requested to register the following value in the RDAP
Extensions Registry: Extensions Registry:
Extension identifier: reverse_search * Extension identifier: reverse_search
Registry operator: Any * Registry operator: Any
Published specification: This document. * Published specification: This document.
Contact: IETF <iesg@ietf.org> * Contact: IETF <iesg@ietf.org>
Intended usage: This extension describes reverse search query * Intended usage: This extension describes reverse search query
patterns for RDAP. patterns for RDAP.
7. Privacy Considerations 7. Privacy Considerations
The use of the capability described in this document MUST be The use of the capability described in this document MUST be
compliant with the rules about privacy protection each RDAP provider compliant with the rules about privacy protection each RDAP provider
is subject to. Sensitive registration data MUST be protected and is subject to. Sensitive registration data MUST be protected and
accessible for permissible purposes only. This functionality SHOULD accessible for permissible purposes only. This functionality SHOULD
be only accessible to authorized users and only for a specified use be only accessible to authorized users and only for a specified use
case. case.
Already the request for this functionality could contain Personal Already the request for this functionality could contain Personal
Identifiable Information and SHOULD therefore only be available over Identifiable Information and SHOULD therefore only be available over
HTTPS. HTTPS.
Providing reverse search in RDAP carries the following threats as Providing reverse search in RDAP carries the following threats as
described in [RFC6973]: described in [RFC6973]:
o Correlation * Correlation
o Disclosure * Disclosure
o Misuse of information * Misuse of information
Therefore, RDAP providers are REQUIRED to mitigate the risk of those Therefore, RDAP providers are REQUIRED to mitigate the risk of those
threats by implementing appropriate measures supported by security threats by implementing appropriate measures supported by security
services (see Section 8). services (see Section 8).
8. Security Considerations 8. Security Considerations
Security services required to provide controlled access to the Security services required to provide controlled access to the
operations specified in this document are described in [RFC7481]. A operations specified in this document are described in [RFC7481]. A
non exhaustive list of access control paradigms an RDAP provider can non exhaustive list of access control paradigms an RDAP provider can
skipping to change at page 8, line 34 skipping to change at page 9, line 20
[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)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
RFC 7480, DOI 10.17487/RFC7480, March 2015, RFC 7480, DOI 10.17487/RFC7480, March 2015,
<https://www.rfc-editor.org/info/rfc7480>. <https://www.rfc-editor.org/info/rfc7480>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the [RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
RFC 7481, DOI 10.17487/RFC7481, March 2015, RFC 7481, DOI 10.17487/RFC7481, March 2015,
<https://www.rfc-editor.org/info/rfc7481>. <https://www.rfc-editor.org/info/rfc7481>.
[RFC7482] Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol (RDAP) Query Format", RFC 7482,
DOI 10.17487/RFC7482, March 2015,
<https://www.rfc-editor.org/info/rfc7482>.
[RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", RFC 7483,
DOI 10.17487/RFC7483, March 2015,
<https://www.rfc-editor.org/info/rfc7483>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions: [RFC8605] Hollenbeck, S. and R. Carney, "vCard Format Extensions:
ICANN Extensions for the Registration Data Access Protocol ICANN Extensions for the Registration Data Access Protocol
(RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019, (RDAP)", RFC 8605, DOI 10.17487/RFC8605, May 2019,
<https://www.rfc-editor.org/info/rfc8605>. <https://www.rfc-editor.org/info/rfc8605>.
[RFC9082] Hollenbeck, S. and A. Newton, "Registration Data Access
Protocol (RDAP) Query Format", STD 95, RFC 9082,
DOI 10.17487/RFC9082, June 2021,
<https://www.rfc-editor.org/info/rfc9082>.
[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 9083, DOI 10.17487/RFC9083, June 2021,
<https://www.rfc-editor.org/info/rfc9083>.
10.2. Informative References 10.2. Informative References
[draft-ietf-regext-rdap-openid] [draft-ietf-regext-rdap-openid]
Hollenbeck, S., "Federated Authentication for the Hollenbeck, S., "Federated Authentication for the
Registration Data Access Protocol (RDAP) using OpenID Registration Data Access Protocol (RDAP) using OpenID
Connect", <https://datatracker.ietf.org/doc/draft-ietf- Connect", <https://datatracker.ietf.org/doc/draft-ietf-
regext-rdap-openid/>. regext-rdap-openid/>.
[ICANN-RA] [ICANN-RA] Internet Corporation For Assigned Names and Numbers,
Internet Corporation For Assigned Names and Numbers,
"Registry Agreement", July 2017, "Registry Agreement", July 2017,
<https://newgtlds.icann.org/sites/default/files/ <https://newgtlds.icann.org/sites/default/files/
agreements/agreement-approved-31jul17-en.pdf>. agreements/agreement-approved-31jul17-en.pdf>.
[ICANN-RDS1] [ICANN-RDS1]
Internet Corporation For Assigned Names and Numbers, Internet Corporation For Assigned Names and Numbers,
"Final Report from the Expert Working Group on gTLD "Final Report from the Expert Working Group on gTLD
Directory Services: A Next-Generation Registration Directory Services: A Next-Generation Registration
Directory Service (RDS)", June 2014, Directory Service (RDS)", June 2014,
<https://www.icann.org/en/system/files/files/final-report- <https://www.icann.org/en/system/files/files/final-report-
skipping to change at page 10, line 5 skipping to change at page 10, line 38
fielding_dissertation.pdf>. fielding_dissertation.pdf>.
Appendix A. Paradigms to Enforce Access Control on Reverse Search in Appendix A. Paradigms to Enforce Access Control on Reverse Search in
RDAP RDAP
Access control can be implemented according to different paradigms Access control can be implemented according to different paradigms
introducing increasingly stringent rules. The paradigms reported introducing increasingly stringent rules. The paradigms reported
here in the following leverage the capabilities either supported here in the following leverage the capabilities either supported
natively or provided as extensions by the OpenID Connect [OIDCC]: natively or provided as extensions by the OpenID Connect [OIDCC]:
o Role-Based Access Control: access rights are granted depending on * Role-Based Access Control: access rights are granted depending on
roles. Generally, this is done by grouping users into fixed roles. Generally, this is done by grouping users into fixed
categories and assigning each category with static grants. A more categories and assigning each category with static grants. A more
dynamic approach can be implemented by using the OpenID Connect dynamic approach can be implemented by using the OpenID Connect
"scope" claim; "scope" claim;
* Purpose-Based Access Control: access rules are based on the notion
o Purpose-Based Access Control: access rules are based on the notion
of purpose which means the intended usage of some data by a user. of purpose which means the intended usage of some data by a user.
It can be implemented by tagging a request with the usage purpose It can be implemented by tagging a request with the usage purpose
and making the RDAP server check the compliance between the given and making the RDAP server check the compliance between the given
purpose and the control rules applied to data to be returned. The purpose and the control rules applied to data to be returned. The
purpose can be stated within an out-of-band process by setting the purpose can be stated within an out-of-band process by setting the
OpenID Connect RDAP specific "purpose" claim as defined in OpenID Connect RDAP specific "purpose" claim as defined in
[draft-ietf-regext-rdap-openid]; [draft-ietf-regext-rdap-openid];
o Attribute-Based Access Control: rules to manage access rights are * Attribute-Based Access Control: rules to manage access rights are
evaluated and applied according to specific attributes describing evaluated and applied according to specific attributes describing
the context within which data are requested. It can be the context within which data are requested. It can be
implemented by setting within an out-of-band process additional implemented by setting within an out-of-band process additional
OpenID Connect claims describing the request context and making OpenID Connect claims describing the request context and making
the RDAP server check the compliance between the given context and the RDAP server check the compliance between the given context and
the control rules applied to data to be returned; the control rules applied to data to be returned;
* Time-Based Access Control: data access is allowed for limited time
o Time-Based Access Control: data access is allowed for limited time
only. It can be implemented by assigning the users with temporary only. It can be implemented by assigning the users with temporary
credentials linked to access grants whose scope is limited. credentials linked to access grants whose scope is limited.
Appendix B. Change Log Appendix B. Change Log
00: Initial working group version ported from draft-loffredo-regext- 00: Initial working group version ported from draft-loffredo-regext-
rdap-reverse-search-04 rdap-reverse-search-04
01: Updated "Privacy Considerations" section. 01: Updated "Privacy Considerations" section.
02: Revised the text. 02: Revised the text.
03: Refactored the query model. 03: Refactored the query model.
04: Keepalive refresh. 04: Keepalive refresh.
05: Reorganized "Abstract". Corrected "Conventions Used in This 05: Reorganized "Abstract". Corrected "Conventions Used in This
Document" section. Added "RDAP Conformance" section. Changed Document" section. Added "RDAP Conformance" section. Changed
"IANA Considerations" section. Added references to RFC7095 and "IANA Considerations" section. Added references to RFC7095 and
RFC8174. Other minor edits. RFC8174. Other minor edits.
06: Updated "Privacy Considerations", "Security Considerations" and 06: Updated "Privacy Considerations", "Security Considerations" and
"Acknowledgements" sections. Added some normative and informative "Acknowledgements" sections. Added some normative and informative
references. Added Appendix A. references. Added Appendix A.
07: Updated normative refernces.
Authors' Addresses Authors' Addresses
Mario Loffredo Mario Loffredo
IIT-CNR/Registro.it IIT-CNR/Registro.it
Via Moruzzi,1 Via Moruzzi,1
Pisa 56124 56124 Pisa
IT Italy
Email: mario.loffredo@iit.cnr.it Email: mario.loffredo@iit.cnr.it
URI: http://www.iit.cnr.it URI: http://www.iit.cnr.it
Maurizio Martinelli Maurizio Martinelli
IIT-CNR/Registro.it IIT-CNR/Registro.it
Via Moruzzi,1 Via Moruzzi,1
Pisa 56124 56124 Pisa
IT Italy
Email: maurizio.martinelli@iit.cnr.it Email: maurizio.martinelli@iit.cnr.it
URI: http://www.iit.cnr.it URI: http://www.iit.cnr.it
 End of changes. 40 change blocks. 
92 lines changed or deleted 93 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/