rfc9877v1.txt		rfc9877.txt
	skipping to change at line 97 ¶		skipping to change at line 97 ¶
	purposes of this document. See [RFC8805] and [RFC9632] for further		purposes of this document. See [RFC8805] and [RFC9632] for further
	details.		details.
	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		"OPTIONAL" in this document are to be interpreted as described in
	BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	Indentation and whitespace in examples are provided only to		Indentation and whitespace in examples are provided only to
	illustrate element relationships, and they are not a required feature		illustrate element relationships and are not required features of
	of this specification.		this specification.
	"..." in examples is used as shorthand for elements defined outside		"..." in examples is used as shorthand for elements defined outside
	of this document.		of this document.
	2. Specification		2. Specification
	2.1. Media Type for a Geofeed Link		2.1. Media Type for a Geofeed Link
	[RFC9632] requires a geofeed file to be a UTF-8 [RFC3629] comma-		[RFC9632] requires a geofeed file to be a UTF-8 [RFC3629] comma-
	separated values (CSV) file, with a series of "#" comments at the end		separated values (CSV) file, with a series of "#" comments at the end
	skipping to change at line 197 ¶		skipping to change at line 197 ¶
	including the extension identifier in the "rdapConformance" array is		including the extension identifier in the "rdapConformance" array is
	that it signals to the client that the server hosts geofeed URLs for		that it signals to the client that the server hosts geofeed URLs for
	its IP network objects. This is useful where a client receives an IP		its IP network objects. This is useful where a client receives an IP
	network object without a geofeed link object, because in that case		network object without a geofeed link object, because in that case
	the client can infer that no geofeed data is available for that		the client can infer that no geofeed data is available for that
	object, since the server would have provided it if it were available.		object, since the server would have provided it if it were available.
	Although a server may use registered media types in its link objects		Although a server may use registered media types in its link objects
	without any restrictions, it is useful to define new RDAP extensions		without any restrictions, it is useful to define new RDAP extensions
	for those media types in order for the server to communicate to		for those media types in order for the server to communicate to
	clients that it will make data for that type accessible. This is the		clients that it will make data for that type accessible. This is
	same as what the server does with the "geofeed1" extension		what the server does with the "geofeed1" extension identifier.
	identifier.
	The "1" in "geofeed1" denotes that this is version 1 of the geofeed		The "1" in "geofeed1" denotes that this is version 1 of the geofeed
	extension. New versions of the geofeed extension will use different		extension. New versions of the geofeed extension will use different
	extension identifiers.		extension identifiers.
	2.4. Example		2.4. Example
	The following is an elided example of an IP network object with a		The following is an elided example of an IP network object with a
	geofeed link object:		geofeed link object:
	skipping to change at line 259 ¶		skipping to change at line 258 ¶
	the parent object for the initial response (and so on, recursively)		the parent object for the initial response (and so on, recursively)
	in the event that the initial response does not contain geofeed data.		in the event that the initial response does not contain geofeed data.
	Conversely, server operators should consider interface options for		Conversely, server operators should consider interface options for
	resource holders in order to support the provisioning of geofeed		resource holders in order to support the provisioning of geofeed
	links for all networks covered by the associated data.		links for all networks covered by the associated data.
	It is common for a resource holder to maintain a single geofeed file		It is common for a resource holder to maintain a single geofeed file
	containing the geofeed data for all of their resources. The resource		containing the geofeed data for all of their resources. The resource
	holder then updates each of their network object registrations to		holder then updates each of their network object registrations to
	refer to that single geofeed file. As with geofeed references in		refer to that single geofeed file. As with geofeed references in
	inetnum objects (per [RFC9632]), clients who find a geofeed link		inetnum: objects (per [RFC9632]), clients who find a geofeed link
	object within an IP network object and opt to retrieve the data from		object within an IP network object and opt to retrieve the data from
	the associated link MUST ignore any entry where the entry's IP		the associated link MUST ignore any entry where the entry's IP
	address range is outside the IP network object's address range.		address range is outside the IP network object's address range.
	Section 3.2 of [RFC8805] recommends that consumers of geofeed data		Section 3.2 of [RFC8805] recommends that consumers of geofeed data
	verify that the publisher of the data is authoritative for the		verify that the publisher of the data is authoritative for the
	relevant resources. The RDAP bootstrap process [RFC9224] helps		relevant resources. The RDAP bootstrap process [RFC9224] helps
	clients with this recommendation, since a client following that		clients with this recommendation, since a client following that
	process will be directed to the RDAP server that is able to make		process will be directed to the RDAP server that is able to make
	authoritative statements about the disposition of the relevant		authoritative statements about the disposition of the relevant
	skipping to change at line 291 ¶		skipping to change at line 290 ¶
	individual.		individual.
	Many jurisdictions have laws or regulations that restrict the use of		Many jurisdictions have laws or regulations that restrict the use of
	"personal data", per the definition in [RFC6973]. Given that,		"personal data", per the definition in [RFC6973]. Given that,
	registry operators should ascertain whether the regulatory		registry operators should ascertain whether the regulatory
	environment in which they operate permits implementation of the		environment in which they operate permits implementation of the
	functionality defined in this document.		functionality defined in this document.
	5. Security Considerations		5. Security Considerations
	Section 6 of [RFC9632] documents several security considerations that		Sections 6 and 9 of [RFC9632] document several security
	are equally relevant in the RDAP context.		considerations that are equally relevant in the RDAP context.
	A geofeed file MUST be referenced with an HTTPS URL, per Section 6 of		A geofeed file MUST be referenced with an HTTPS URL, per Section 6 of
	[RFC9632]. The geofeed file may also contain an RPKI signature, per		[RFC9632]. The geofeed file may also contain an RPKI signature, per
	Section 5 of [RFC9632].		Section 5 of [RFC9632].
	Besides that, this document does not introduce any new security		Besides that, this document does not introduce any new security
	considerations past those already discussed in the RDAP protocol		considerations past those already discussed in the RDAP protocol
	specifications ([RFC7481], [RFC9560]).		specifications ([RFC7481], [RFC9560]).
	6. IANA Considerations		6. IANA Considerations
	skipping to change at line 520 ¶		skipping to change at line 519 ¶
	<https://www.rfc-editor.org/info/rfc9560>.		<https://www.rfc-editor.org/info/rfc9560>.
	[STRUCTURED-SYNTAX-SUFFIXES]		[STRUCTURED-SYNTAX-SUFFIXES]
	IANA, "Structured Syntax Suffixes",		IANA, "Structured Syntax Suffixes",
	<https://www.iana.org/assignments/media-type-structured-		<https://www.iana.org/assignments/media-type-structured-
	suffix/>.		suffix/>.
	Acknowledgements		Acknowledgements
	Mark Kosters provided initial support and encouragement for this		Mark Kosters provided initial support and encouragement for this
	work, along with the [RFC9632] authors. Gavin Brown suggested using		work, along with the authors of [RFC9632]. Gavin Brown suggested
	a web link instead of a simple URL string to specify a geofeed file		using a web link instead of a simple URL string to specify a geofeed
	URL. Andy Newton, James Gould, Scott Hollenbeck, Mario Loffredo,		file URL. Andy Newton, James Gould, Scott Hollenbeck, Mario
	Orie Steele, Alexey Melnikov, Mark Nottingham, Rifaat Shekh-Yusef,		Loffredo, Orie Steele, Alexey Melnikov, Mark Nottingham, Rifaat
	Dale R. Worley, Dhruv Dhody, Mohamed Boucadair, Mahesh Jethanandani,		Shekh-Yusef, Dale R. Worley, Dhruv Dhody, Mohamed Boucadair, Mahesh
	Ketan Talaulikar, and Éric Vyncke provided valuable feedback for this		Jethanandani, Ketan Talaulikar, and Éric Vyncke provided valuable
	document.		feedback for this document.
	Authors' Addresses		Authors' Addresses
	Jasdip Singh		Jasdip Singh
	ARIN		ARIN
	Email: jasdips@arin.net		Email: jasdips@arin.net
	Tom Harrison		Tom Harrison
	APNIC		APNIC
	Email: tomh@apnic.net		Email: tomh@apnic.net
End of changes. 5 change blocks.
	15 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.48.