rfc9196v6.txt		rfc9196.txt
	skipping to change at line 824 ¶		skipping to change at line 824 ¶
	and what protocols might be used for such notifications. Knowledge		and what protocols might be used for such notifications. Knowledge
	of this type of value might, for example, allow an attacker to gain		of this type of value might, for example, allow an attacker to gain
	insight into how long unauthorized configuration changes might be		insight into how long unauthorized configuration changes might be
	active prior to detection and what communications channels might be		active prior to detection and what communications channels might be
	disrupted to extend the period of non-detection. Documents adding		disrupted to extend the period of non-detection. Documents adding
	additional capabilities via augmenting this module are encouraged to		additional capabilities via augmenting this module are encouraged to
	document the security considerations of the new YANG nodes, according		document the security considerations of the new YANG nodes, according
	to the guidance in BCP 216 [RFC8407].		to the guidance in BCP 216 [RFC8407].
	All protocol-accessible data nodes in augmented modules are read-only		All protocol-accessible data nodes in augmented modules are read-only
	and cannot be modified. The data in these modules is not security		and cannot be modified. Access control may be configured to avoid
	sensitive. Access control may be configured to avoid exposing the		exposing any read-only data that is defined by the augmenting module
	read-only data.		documentation as being security sensitive.
	When that data is in file format, the data should be protected		When that data is in file format, the data should be protected
	against modification or unauthorized access using normal file-		against modification or unauthorized access using normal file-
	handling mechanisms. The data in file format also inherits all the		handling mechanisms. The data in file format also inherits all the
	security considerations of [RFC9195], which includes additional		security considerations of [RFC9195], which includes additional
	considerations about read protections and distinguishes between data		considerations about read protections and distinguishes between data
	at rest and in motion.		at rest and in motion.
	7. IANA Considerations		7. IANA Considerations
	skipping to change at line 930 ¶		skipping to change at line 930 ¶
	[RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,		[RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
	E., and A. Tripathy, "Subscription to YANG Notifications",		E., and A. Tripathy, "Subscription to YANG Notifications",
	RFC 8639, DOI 10.17487/RFC8639, September 2019,		RFC 8639, DOI 10.17487/RFC8639, September 2019,
	<https://www.rfc-editor.org/info/rfc8639>.		<https://www.rfc-editor.org/info/rfc8639>.
	[RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications		[RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
	for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,		for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
	September 2019, <https://www.rfc-editor.org/info/rfc8641>.		September 2019, <https://www.rfc-editor.org/info/rfc8641>.
	[RFC9195] Lengyel, B. and B. Claise, "A File Format for YANG		[RFC9195] Lengyel, B. and B. Claise, "A File Format for YANG
	Instance Data", RFC 9195, DOI 10.17487/RFC9195, January		Instance Data", RFC 9195, DOI 10.17487/RFC9195, February
	2022, <https://www.rfc-editor.org/info/rfc9195>.		2022, <https://www.rfc-editor.org/info/rfc9195>.
	8.2. Informative References		8.2. Informative References
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
	[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of		[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of
	Documents Containing YANG Data Models", BCP 216, RFC 8407,		Documents Containing YANG Data Models", BCP 216, RFC 8407,
End of changes. 2 change blocks.
	4 lines changed or deleted		4 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/