draft-ietf-regext-rdap-rir-search-09.txt		draft-ietf-regext-rdap-rir-search-10.txt
	Internet Engineering Task Force T. Harrison		Internet Engineering Task Force T. Harrison
	Internet-Draft APNIC		Internet-Draft APNIC
	Intended status: Standards Track J. Singh		Intended status: Standards Track J. Singh
	Expires: 21 September 2024 ARIN		Expires: 17 January 2025 ARIN
	20 March 2024		16 July 2024
	RDAP RIR Search		RDAP RIR Search
	draft-ietf-regext-rdap-rir-search-09		draft-ietf-regext-rdap-rir-search-10
	Abstract		Abstract
	The Registration Data Access Protocol (RDAP) is used by Regional		The Registration Data Access Protocol (RDAP) is used by Regional
	Internet Registries (RIRs) and Domain Name Registries (DNRs) to		Internet Registries (RIRs) and Domain Name Registries (DNRs) to
	provide access to their resource registration information. The core		provide access to their resource registration information. The core
	specifications for RDAP define basic search functionality, but there		specifications for RDAP define basic search functionality, but there
	are various IP and ASN-related search options provided by RIRs via		are various IP and ASN-related search options provided by RIRs via
	their Whois services for which there is no corresponding RDAP		their Whois services for which there is no corresponding RDAP
	functionality. This document extends RDAP to support those search		functionality. This document extends RDAP to support those search
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 21 September 2024.		This Internet-Draft will expire on 17 January 2025.
	Copyright Notice		Copyright Notice
	Copyright (c) 2024 IETF Trust and the persons identified as the		Copyright (c) 2024 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 17, line 16 ¶		skipping to change at page 17, line 16 ¶
	Responses for relation searches for reverse domain objects have the		Responses for relation searches for reverse domain objects have the
	same form as for a standard domain search response, per [RFC9083].		same form as for a standard domain search response, per [RFC9083].
	If the search can be processed by the server, but there are no		If the search can be processed by the server, but there are no
	results for the search, then the server returns an HTTP 200 (OK)		results for the search, then the server returns an HTTP 200 (OK)
	[RFC9110] response code, with the body of the response containing an		[RFC9110] response code, with the body of the response containing an
	empty results array.		empty results array.
	5. Reverse Search		5. Reverse Search
	RDAP reverse search is defined by		RDAP reverse search is defined by [RFC9536]. That document limits
	[I-D.ietf-regext-rdap-reverse-search]. That document limits reverse		reverse search to domains, nameservers, and entities. This document
	search to domains, nameservers, and entities. This document extends		extends reverse search to cover IP networks and autonomous system
	reverse search to cover IP networks and autonomous system numbers as		numbers as well.
	well.
	If a server receives a reverse search query with a searchable		If a server receives a reverse search query with a searchable
	resource type (per the definition of that term in		resource type (per the definition of that term in [RFC9536]) of
	[I-D.ietf-regext-rdap-reverse-search]) of "ips", then the reverse		"ips", then the reverse search will be performed on the IP network
	search will be performed on the IP network objects from its data		objects from its data store. Similarly, if a server receives a
	store. Similarly, if a server receives a reverse search query with a		reverse search query with a searchable resource type of "autnums",
	searchable resource type of "autnums", then the reverse search will		then the reverse search will be performed on the autonomous system
	be performed on the autonomous system number objects from its data		number objects from its data store.
	store.
	Additionally, Section 10 includes requests to register new entries		Additionally, Section 10 includes requests to register new entries
	for IP network and autonomous system number searches in the RDAP		for IP network and autonomous system number searches in the RDAP
	Reverse Search and RDAP Reverse Search Mapping IANA registries.		Reverse Search and RDAP Reverse Search Mapping IANA registries.
	6. RDAP Conformance		6. RDAP Conformance
	A server that supports the functionality specified in this document		A server that supports the functionality specified in this document
	MUST include additional string literals in the rdapConformance array		MUST include additional string literals in the rdapConformance array
	of its responses, in accordance with the following:		of its responses, in accordance with the following:
	skipping to change at page 19, line 29 ¶		skipping to change at page 19, line 29 ¶
	"Personal Data", per the definition in [RFC6973]. Given that, server		"Personal Data", per the definition in [RFC6973]. Given that, server
	operators should ascertain whether the regulatory environment in		operators should ascertain whether the regulatory environment in
	which they operate permits implementation of the functionality		which they operate permits implementation of the functionality
	defined in this document.		defined in this document.
	9. Security Considerations		9. Security Considerations
	[RFC7481] describes security requirements and considerations for RDAP		[RFC7481] describes security requirements and considerations for RDAP
	generally.		generally.
			[RFC9082] includes security considerations relating to object
			retrieval in RDAP. Those considerations are relevant here as well.
	10. IANA Considerations		10. IANA Considerations
	10.1. RDAP Extensions Registry		10.1. RDAP Extensions Registry
	IANA is requested to register the following values in the RDAP		IANA is requested to register the following values in the RDAP
	Extensions Registry:		Extensions Registry:
	* Extension identifier: rirSearch1		* Extension identifier: rirSearch1
	* Registry operator: Any		* Registry operator: Any
	skipping to change at page 25, line 31 ¶		skipping to change at page 25, line 31 ¶
	* Level of Maturity: This is a production implementation.		* Level of Maturity: This is a production implementation.
	* Coverage: This implementation includes the new basic searches		* Coverage: This implementation includes the new basic searches
	only.		only.
	* Contact Information: Ed Shryane, eshryane@ripe.net		* Contact Information: Ed Shryane, eshryane@ripe.net
	12. Acknowledgements		12. Acknowledgements
	The authors wish to thank Mario Loffredo, Andy Newton, Antoin		The authors wish to thank Mario Loffredo, Andy Newton, Antoin
	Verschuren, and James Gould for document review and associated		Verschuren, James Gould, and Scott Hollenbeck for document review and
	comments.		associated comments.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
	[I-D.ietf-regext-rdap-reverse-search]
	Loffredo, M. and M. Martinelli, "Registration Data Access
	Protocol (RDAP) Reverse Search", Work in Progress,
	Internet-Draft, draft-ietf-regext-rdap-reverse-search-26,
	13 November 2023, <https://datatracker.ietf.org/doc/html/
	draft-ietf-regext-rdap-reverse-search-26>.
	[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>.
	[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>.
	skipping to change at page 26, line 29 ¶		skipping to change at page 26, line 20 ¶
	[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the		[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
	Registration Data Access Protocol (RDAP)", STD 95,		Registration Data Access Protocol (RDAP)", STD 95,
	RFC 9083, DOI 10.17487/RFC9083, June 2021,		RFC 9083, DOI 10.17487/RFC9083, June 2021,
	<https://www.rfc-editor.org/info/rfc9083>.		<https://www.rfc-editor.org/info/rfc9083>.
	[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Semantics", STD 97, RFC 9110,		Ed., "HTTP Semantics", STD 97, RFC 9110,
	DOI 10.17487/RFC9110, June 2022,		DOI 10.17487/RFC9110, June 2022,
	<https://www.rfc-editor.org/info/rfc9110>.		<https://www.rfc-editor.org/info/rfc9110>.
			[RFC9536] Loffredo, M. and M. Martinelli, "Registration Data Access
			Protocol (RDAP) Reverse Search", RFC 9536,
			DOI 10.17487/RFC9536, April 2024,
			<https://www.rfc-editor.org/info/rfc9536>.
	13.2. Informative References		13.2. Informative References
	[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,		[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
	Morris, J., Hansen, M., and R. Smith, "Privacy		Morris, J., Hansen, M., and R. Smith, "Privacy
	Considerations for Internet Protocols", RFC 6973,		Considerations for Internet Protocols", RFC 6973,
	DOI 10.17487/RFC6973, July 2013,		DOI 10.17487/RFC6973, July 2013,
	<https://www.rfc-editor.org/info/rfc6973>.		<https://www.rfc-editor.org/info/rfc6973>.
	[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,
End of changes. 9 change blocks.
	25 lines changed or deleted		24 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/