rfc9569v7.txt		rfc9569.txt
	skipping to change at line 935 ¶		skipping to change at line 935 ¶
	concerns. The field MUST contain only ASCII characters. In case		concerns. The field MUST contain only ASCII characters. In case
	the original URL contains international characters (e.g., in the		the original URL contains international characters (e.g., in the
	domain name), the ALTO server implementation MUST properly encode		domain name), the ALTO server implementation MUST properly encode
	the URL into the ASCII format (e.g., using the "urlencode"		the URL into the ASCII format (e.g., using the "urlencode"
	function).		function).
	A server MUST NOT use the same URI for different TIPS views,		A server MUST NOT use the same URI for different TIPS views,
	either for different resources or for different request bodies to		either for different resources or for different request bodies to
	the same resource. URI generation is implementation specific; for		the same resource. URI generation is implementation specific; for
	example, one may compute a Universally Unique Identifier (UUID)		example, one may compute a Universally Unique Identifier (UUID)
	[RFC4122] or a hash value based on the request and append it to a		[RFC9562] or a hash value based on the request and append it to a
	base URL. For performance considerations, it is NOT RECOMMENDED		base URL. For performance considerations, it is NOT RECOMMENDED
	to use properties that are not included in the request body to		to use properties that are not included in the request body to
	determine the URI of a TIPS view, such as cookies or the client's		determine the URI of a TIPS view, such as cookies or the client's
	IP address, which may result in duplicated TIPS views in cases		IP address, which may result in duplicated TIPS views in cases
	such as mobile clients. However, this is not mandatory as a		such as mobile clients. However, this is not mandatory as a
	server might intentionally use client information to compute the		server might intentionally use client information to compute the
	TIPS view URI to provide service isolation between clients.		TIPS view URI to provide service isolation between clients.
	tips-view-summary: Contains an updates-graph-summary.		tips-view-summary: Contains an updates-graph-summary.
	skipping to change at line 1740 ¶		skipping to change at line 1740 ¶
	Security (TLS) and Datagram Transport Layer Security		Security (TLS) and Datagram Transport Layer Security
	(DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, November		(DTLS)", BCP 195, RFC 9325, DOI 10.17487/RFC9325, November
	2022, <https://www.rfc-editor.org/info/rfc9325>.		2022, <https://www.rfc-editor.org/info/rfc9325>.
	11.2. Informative References		11.2. Informative References
	[IANA-Media-Type]		[IANA-Media-Type]
	IANA, "Media Types",		IANA, "Media Types",
	<https://www.iana.org/assignments/media-types>.		<https://www.iana.org/assignments/media-types>.
	[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
	Unique IDentifier (UUID) URN Namespace", RFC 4122,
	DOI 10.17487/RFC4122, July 2005,
	<https://www.rfc-editor.org/info/rfc4122>.
	[RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme",		[RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme",
	RFC 7617, DOI 10.17487/RFC7617, September 2015,		RFC 7617, DOI 10.17487/RFC7617, September 2015,
	<https://www.rfc-editor.org/info/rfc7617>.		<https://www.rfc-editor.org/info/rfc7617>.
	[RFC9205] Nottingham, M., "Building Protocols with HTTP", BCP 56,		[RFC9205] Nottingham, M., "Building Protocols with HTTP", BCP 56,
	RFC 9205, DOI 10.17487/RFC9205, June 2022,		RFC 9205, DOI 10.17487/RFC9205, June 2022,
	<https://www.rfc-editor.org/info/rfc9205>.		<https://www.rfc-editor.org/info/rfc9205>.
			[RFC9562] Davis, K., Peabody, B., and P. Leach, "Universally Unique
			IDentifiers (UUIDs)", RFC 9562, DOI 10.17487/RFC9562, May
			2024, <https://www.rfc-editor.org/info/rfc9562>.
	Appendix A. A High-Level Deployment Model		Appendix A. A High-Level Deployment Model
	Conceptually, the TIPS system consists of three types of resources:		Conceptually, the TIPS system consists of three types of resources:
	(R1): The TIPS frontend to create TIPS views.		(R1): The TIPS frontend to create TIPS views.
	(R2): The TIPS view directory, which provides metadata (e.g.,		(R2): The TIPS view directory, which provides metadata (e.g.,
	references) about the network resource data.		references) about the network resource data.
	(R3): The actual network resource data, encoded as complete ALTO		(R3): The actual network resource data, encoded as complete ALTO
	skipping to change at line 1925 ¶		skipping to change at line 1924 ¶
	Kai Gao		Kai Gao
	Sichuan University		Sichuan University
	No.24 South Section 1, Yihuan Road		No.24 South Section 1, Yihuan Road
	Chengdu		Chengdu
	610000		610000
	China		China
	Email: kaigao@scu.edu.cn		Email: kaigao@scu.edu.cn
	Roland Schott		Roland Schott
	Deutsche Telekom		Deutsche Telekom
	Ida-Rhodes-Straße 2		Deutsche-Telekom-Allee 9
	64295 Darmstadt		64295 Darmstadt
	Germany		Germany
	Email: Roland.Schott@telekom.de		Email: Roland.Schott@telekom.de
	Yang Richard Yang		Yang Richard Yang
	Yale University		Yale University
	51 Prospect Street		51 Prospect Street
	New Haven, CT 06511		New Haven, CT 06511
	United States of America		United States of America
	Email: yry@cs.yale.edu		Email: yry@cs.yale.edu
End of changes. 4 change blocks.
	7 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48.