rfc9537v2.txt		rfc9537.txt
	skipping to change at line 110 ¶		skipping to change at line 110 ¶
	[RFC8259].		[RFC8259].
	2. Conventions Used in This Document		2. Conventions Used in This Document
	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.
	The JSON examples include extra line breaks and whitespace. For		The JSON examples include extra line breaks and empty space. For
	instance, the JSONPath expressions are broken out into multiple lines		instance, the JSONPath expressions are broken out into multiple lines
	when required for illustration.		when required for illustration.
	The JSONPath expressions in the examples are for illustration		The JSONPath expressions in the examples are for illustration
	purposes with single-role entities, and the exact expressions to be		purposes with single-role entities, and the exact expressions to be
	used by the server are out of scope.		used by the server are out of scope.
	3. Redaction Methods		3. Redaction Methods
	Redaction in RDAP can be handled in multiple ways. The resulting		Redaction in RDAP can be handled in multiple ways. The resulting
	skipping to change at line 1382 ¶		skipping to change at line 1382 ¶
	5. JSONPath Considerations		5. JSONPath Considerations
	JSONPath [RFC9535] is the default JSON path expression language.		JSONPath [RFC9535] is the default JSON path expression language.
	This section includes JSONPath considerations for clients and		This section includes JSONPath considerations for clients and
	servers.		servers.
	5.1. JSONPath Client Considerations		5.1. JSONPath Client Considerations
	This section covers considerations for clients that receive responses		This section covers considerations for clients that receive responses
	from servers using JSONPath [RFC9535] to identify redacted RDAP		from servers using JSONPath [RFC9535] to identify redacted RDAP
	fields with the "prePath", "postPath", or “replacementPath” member of		fields with the "prePath", "postPath", or "replacementPath" member of
	redacted objects in the "redacted" member. The list of JSONPath		redacted objects in the "redacted" member. The list of JSONPath
	client considerations include:		client considerations include:
	1. When the server is using the Redaction by Removal Method		1. When the server is using the Redaction by Removal Method
	(Section 3.1) or the Redaction by Replacement Value Method		(Section 3.1) or the Redaction by Replacement Value Method
	(Section 3.4) with an alternative field value, the JSONPath		(Section 3.4) with an alternative field value, the JSONPath
	expression of the "prePath" member will not resolve successfully		expression of the "prePath" member will not resolve successfully
	with the redacted response. The client can key off the "name"		with the redacted response. The client can key off the "name"
	member for display logic related to the redaction.		member for display logic related to the redaction.
	5.2. JSONPath Server Considerations		5.2. JSONPath Server Considerations
	This section covers considerations for servers using JSONPath		This section covers considerations for servers using JSONPath
	[RFC9535] to identify redacted RDAP fields with the "prePath",		[RFC9535] to identify redacted RDAP fields with the "prePath",
	"postPath", or “repacementPath” member of redacted objects in the		"postPath", or "replacementPath" member of redacted objects in the
	"redacted" member. The list of JSONPath considerations include:		"redacted" member. The list of JSONPath considerations include:
	1. Use absolute paths with the '$' JSONPath element. An example is		1. Use absolute paths with the '$' JSONPath element. An example is
	"$.handle" for the "Registry Domain ID" in a lookup response or		"$.handle" for the "Registry Domain ID" in a lookup response or
	"$.domainSearchResults[0].handle" in a search response.		"$.domainSearchResults[0].handle" in a search response.
	2. Validate a JSONPath expression with the non-redacted RDAP		2. Validate a JSONPath expression with the non-redacted RDAP
	response when using the "prePath" member, where evaluating the		response when using the "prePath" member, where evaluating the
	expression results in returning the redacted field.		expression results in returning the redacted field.
End of changes. 3 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48.