rfc8993v5.txt		rfc8993.txt
	skipping to change at line 560 ¶		skipping to change at line 560 ¶
	negotiate and/or synchronize technical objectives (i.e., network		negotiate and/or synchronize technical objectives (i.e., network
	parameters) of any kind and complexity. This requires some form of		parameters) of any kind and complexity. This requires some form of
	signaling between autonomic nodes. Autonomic nodes implementing a		signaling between autonomic nodes. Autonomic nodes implementing a
	specific use case might choose their own signaling protocol, as long		specific use case might choose their own signaling protocol, as long
	as it fits the overall security model. However, in the general case,		as it fits the overall security model. However, in the general case,
	any pair of autonomic nodes might need to communicate, so there needs		any pair of autonomic nodes might need to communicate, so there needs
	to be a generic protocol for this. A prerequisite for this is that		to be a generic protocol for this. A prerequisite for this is that
	autonomic nodes can discover each other without any preconfiguration,		autonomic nodes can discover each other without any preconfiguration,
	as mentioned above. To be generic, discovery and signaling must be		as mentioned above. To be generic, discovery and signaling must be
	able to handle any sort of technical objective, including ones that		able to handle any sort of technical objective, including ones that
	require complex data structures. The document "A GeneRic Autonomic		require complex data structures. The document "GeneRic Autonomic
	Signaling Protocol (GRASP)" [RFC8990] describes more detailed		Signaling Protocol (GRASP)" [RFC8990] describes more detailed
	requirements for discovery, negotiation, and synchronization in an		requirements for discovery, negotiation, and synchronization in an
	Autonomic Network. It also defines a protocol, called GRASP, for		Autonomic Network. It also defines a protocol, called GRASP, for
	this purpose; GRASP includes an integrated but optional discovery		this purpose; GRASP includes an integrated but optional discovery
	process.		process.
	GRASP is normally expected to run inside the ACP (see Section 4.6)		GRASP is normally expected to run inside the ACP (see Section 4.6)
	and to depend on the ACP for security. It may run insecurely for a		and to depend on the ACP for security. It may run insecurely for a
	short time during bootstrapping.		short time during bootstrapping.
	skipping to change at line 818 ¶		skipping to change at line 818 ¶
	The first three (pledge, join proxy, join registrar) support together		The first three (pledge, join proxy, join registrar) support together
	the trust enrollment process described in Section 5. For details see		the trust enrollment process described in Section 5. For details see
	[RFC8995].		[RFC8995].
	6.3.1. Enrollment ASAs		6.3.1. Enrollment ASAs
	6.3.1.1. The Pledge ASA		6.3.1.1. The Pledge ASA
	This ASA includes the function of an autonomic node that bootstraps		This ASA includes the function of an autonomic node that bootstraps
	into the domain with the help of an join proxy ASA (see below). Such		into the domain with the help of a join proxy ASA (see below). Such
	a node is known as a pledge during the enrollment process. This ASA		a node is known as a pledge during the enrollment process. This ASA
	must be installed by default on all nodes that require an autonomic		must be installed by default on all nodes that require an autonomic
	zero-touch bootstrap.		zero-touch bootstrap.
	6.3.1.2. The Join Proxy ASA		6.3.1.2. The Join Proxy ASA
	This ASA includes the function of an autonomic node that helps non-		This ASA includes the function of an autonomic node that helps non-
	enrolled, adjacent devices to enroll into the domain. This ASA must		enrolled, adjacent devices to enroll into the domain. This ASA must
	be installed on all nodes, although only one join proxy needs to be		be installed on all nodes, although only one join proxy needs to be
	active on a given LAN. See also [RFC8995].		active on a given LAN. See also [RFC8995].
	skipping to change at line 1269 ¶		skipping to change at line 1269 ¶
	This document has no IANA actions.		This document has no IANA actions.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[IDevID] IEEE, "IEEE Standard for Local and metropolitan area		[IDevID] IEEE, "IEEE Standard for Local and metropolitan area
	networks - Secure Device Identity", IEEE 802.1AR,		networks - Secure Device Identity", IEEE 802.1AR,
	<https://1.ieee802.org/security/802-1ar>.		<https://1.ieee802.org/security/802-1ar>.
	[RFC8990] Bormann, C., Carpenter, B., Ed., and B. Liu, Ed., "A		[RFC8990] Bormann, C., Carpenter, B., Ed., and B. Liu, Ed., "GeneRic
	GeneRic Autonomic Signaling Protocol (GRASP)", RFC 8990,		Autonomic Signaling Protocol (GRASP)", RFC 8990,
	DOI 10.17487/RFC8990, May 2021,		DOI 10.17487/RFC8990, May 2021,
	<https://www.rfc-editor.org/info/rfc8990>.		<https://www.rfc-editor.org/info/rfc8990>.
	[RFC8994] Eckert, T., Ed., Behringer, M., Ed., and S. Bjarnason, "An		[RFC8994] Eckert, T., Ed., Behringer, M., Ed., and S. Bjarnason, "An
	Autonomic Control Plane (ACP)", RFC 8994,		Autonomic Control Plane (ACP)", RFC 8994,
	DOI 10.17487/RFC8994, May 2021,		DOI 10.17487/RFC8994, May 2021,
	<https://www.rfc-editor.org/info/rfc8994>.		<https://www.rfc-editor.org/info/rfc8994>.
	[RFC8995] Pritikin, M., Richardson, M., Eckert, T., Behringer, M.,		[RFC8995] Pritikin, M., Richardson, M., Eckert, T., Behringer, M.,
	and K. Watsen, "Bootstrapping Remote Secure Key		and K. Watsen, "Bootstrapping Remote Secure Key
End of changes. 3 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/