Diff: rfc9223v2.txt - rfc9223.txt

	rfc9223v2.txt	rfc9223.txt

	skipping to change at line 1716 ¶	skipping to change at line 1716 ¶
	building blocks apply directly to ROUTE as elaborated in the	building blocks apply directly to ROUTE as elaborated in the
	following along with some additional considerations.	following along with some additional considerations.

	Both encryption and integrity protection applied either on file or	Both encryption and integrity protection applied either on file or
	packet level, as recommended in the file corruption considerations of	packet level, as recommended in the file corruption considerations of
	RFC 6726 [RFC6726], SHOULD be used for ROUTE. Additionally, RFC 3740	RFC 6726 [RFC6726], SHOULD be used for ROUTE. Additionally, RFC 3740
	[RFC3740] documents multicast security architecture in great detail	[RFC3740] documents multicast security architecture in great detail
	with clear security recommendations that SHOULD be followed.	with clear security recommendations that SHOULD be followed.

	When ROUTE is carried over UDP and a reverse channel from receiver to	When ROUTE is carried over UDP and a reverse channel from receiver to

	sender is available, the security mechanisms provided in RFC 6347	sender is available, the security mechanisms provided in RFC 9147
	[RFC6347] SHALL apply. At the time, draft DTLS 1.3 based on TSL 1.3	[RFC9147] SHOULD be applied.
	[DTLS13] is pending publication and may be considered as the
	alternate means for security post publication.

	In regard to considerations for attacks against session description,	In regard to considerations for attacks against session description,
	this document does not specify the semantics or mechanism of delivery	this document does not specify the semantics or mechanism of delivery
	of session metadata, though the same threats apply for service using	of session metadata, though the same threats apply for service using
	ROUTE as well. Hence, a service using ROUTE SHOULD take these	ROUTE as well. Hence, a service using ROUTE SHOULD take these
	threats into consideration and address them appropriately following	threats into consideration and address them appropriately following
	the guidelines provided by RFC 6726 [RFC6726]. Additionally, to the	the guidelines provided by RFC 6726 [RFC6726]. Additionally, to the
	recommendations of RFC 6726 [RFC6726], for Internet connected	recommendations of RFC 6726 [RFC6726], for Internet connected
	devices, services SHOULD enable clients to access the session	devices, services SHOULD enable clients to access the session
	description information using HTTPS with customary authentication/	description information using HTTPS with customary authentication/

	skipping to change at line 1880 ¶	skipping to change at line 1878 ¶
	(CMAF) for segmented media", First edition, ISO/IEC	(CMAF) for segmented media", First edition, ISO/IEC
	FDIS 23000-19, January 2018,	FDIS 23000-19, January 2018,
	<https://www.iso.org/standard/71975.html>.	<https://www.iso.org/standard/71975.html>.

	[DASH] International Organization for Standardization,	[DASH] International Organization for Standardization,
	"Information technology - Dynamic adaptive streaming over	"Information technology - Dynamic adaptive streaming over
	HTTP (DASH) - Part 1: Media presentation description and	HTTP (DASH) - Part 1: Media presentation description and
	segment formats", Fourth edition, ISO/IEC 23009-1:2019,	segment formats", Fourth edition, ISO/IEC 23009-1:2019,
	December 2019, <https://www.iso.org/standard/79329.html>.	December 2019, <https://www.iso.org/standard/79329.html>.


	[DTLS13] Rescorla, E., Tschofenig, H., and N. Modadugu, "The
	Datagram Transport Layer Security (DTLS) Protocol Version
	1.3", Work in Progress, Internet-Draft, draft-ietf-tls-
	dtls13-43, 21 April 2022,
	<https://datatracker.ietf.org/doc/html/draft-ietf-tls-
	dtls13-43>.

	[DVBMABR] ETSI, "Digital Video Broadcasting (DVB); Adaptive media	[DVBMABR] ETSI, "Digital Video Broadcasting (DVB); Adaptive media
	streaming over IP multicast", version 1.1.1, ETSI TS 103	streaming over IP multicast", version 1.1.1, ETSI TS 103
	769, November 2020.	769, November 2020.

	[HTTP3] Bishop, M., Ed., "Hypertext Transfer Protocol Version 3	[HTTP3] Bishop, M., Ed., "Hypertext Transfer Protocol Version 3
	(HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-	(HTTP/3)", Work in Progress, Internet-Draft, draft-ietf-
	quic-http-34, 2 February 2021,	quic-http-34, 2 February 2021,
	<https://datatracker.ietf.org/doc/html/draft-ietf-quic-	<https://datatracker.ietf.org/doc/html/draft-ietf-quic-
	http-34>.	http-34>.

	[MBMS] ETSI, "Universal Mobile Telecommunications Systems (UMTS);	[MBMS] ETSI, "Universal Mobile Telecommunications Systems (UMTS);
	LTE; 5G; Multimedia Broadcast/Multicast Service (MBMS);	LTE; 5G; Multimedia Broadcast/Multicast Service (MBMS);
	Protocols and codecs", version 16.9.1, ETSI TS 126 346,	Protocols and codecs", version 16.9.1, ETSI TS 126 346,
	May 2021.	May 2021.

	[RFC3740] Hardjono, T. and B. Weis, "The Multicast Group Security	[RFC3740] Hardjono, T. and B. Weis, "The Multicast Group Security
	Architecture", RFC 3740, DOI 10.17487/RFC3740, March 2004,	Architecture", RFC 3740, DOI 10.17487/RFC3740, March 2004,
	<https://www.rfc-editor.org/info/rfc3740>.	<https://www.rfc-editor.org/info/rfc3740>.


	[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
	Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
	January 2012, <https://www.rfc-editor.org/info/rfc6347>.

	[RFC6968] Roca, V. and B. Adamson, "FCAST: Object Delivery for the	[RFC6968] Roca, V. and B. Adamson, "FCAST: Object Delivery for the
	Asynchronous Layered Coding (ALC) and NACK-Oriented	Asynchronous Layered Coding (ALC) and NACK-Oriented
	Reliable Multicast (NORM) Protocols", RFC 6968,	Reliable Multicast (NORM) Protocols", RFC 6968,
	DOI 10.17487/RFC6968, July 2013,	DOI 10.17487/RFC6968, July 2013,
	<https://www.rfc-editor.org/info/rfc6968>.	<https://www.rfc-editor.org/info/rfc6968>.

	[RFC8932] Dickinson, S., Overeinder, B., van Rijswijk-Deij, R., and	[RFC8932] Dickinson, S., Overeinder, B., van Rijswijk-Deij, R., and
	A. Mankin, "Recommendations for DNS Privacy Service	A. Mankin, "Recommendations for DNS Privacy Service
	Operators", BCP 232, RFC 8932, DOI 10.17487/RFC8932,	Operators", BCP 232, RFC 8932, DOI 10.17487/RFC8932,
	October 2020, <https://www.rfc-editor.org/info/rfc8932>.	October 2020, <https://www.rfc-editor.org/info/rfc8932>.

	[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based	[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
	Multiplexed and Secure Transport", RFC 9000,	Multiplexed and Secure Transport", RFC 9000,
	DOI 10.17487/RFC9000, May 2021,	DOI 10.17487/RFC9000, May 2021,
	<https://www.rfc-editor.org/info/rfc9000>.	<https://www.rfc-editor.org/info/rfc9000>.


		[RFC9147] Rescorla, E., Tschofenig, H., and N. Modadugu, "The
		Datagram Transport Layer Security (DTLS) Protocol Version
		1.3", RFC 9147, DOI 10.17487/RFC9147, April 2022,
		<https://www.rfc-editor.org/info/rfc9147>.

	Acknowledgments	Acknowledgments

	As outlined in the introduction and in ROUTE concepts in Section 9,	As outlined in the introduction and in ROUTE concepts in Section 9,
	the concepts specified in this document are the culmination of the	the concepts specified in this document are the culmination of the
	collaborative work of several experts and organizations over the	collaborative work of several experts and organizations over the
	years. The authors would especially like to acknowledge the work and	years. The authors would especially like to acknowledge the work and
	efforts of the following people and organizations to help realize the	efforts of the following people and organizations to help realize the
	technologies described in this document (in no specific order): Mike	technologies described in this document (in no specific order): Mike
	Luby, Kent Walker, Charles Lo, and other colleagues from Qualcomm	Luby, Kent Walker, Charles Lo, and other colleagues from Qualcomm
	Incorporated, LG Electronics, Nomor Research, Sony, and BBC R&D.	Incorporated, LG Electronics, Nomor Research, Sony, and BBC R&D.

End of changes. 4 change blocks.
	15 lines changed or deleted	7 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/