rfc9820v3.txt		rfc9820.txt
	skipping to change at line 302 ¶		skipping to change at line 302 ¶
	* "path" is some local path on the device to make the path unique.		* "path" is some local path on the device to make the path unique.
	This could be omitted if desired.		This could be omitted if desired.
	* "eap" is the name that indicates that the URI is for the EAP peer.		* "eap" is the name that indicates that the URI is for the EAP peer.
	This has no meaning for the protocol but helps with debugging.		This has no meaning for the protocol but helps with debugging.
	* "counter" is an incrementing unique number for every new EAP		* "counter" is an incrementing unique number for every new EAP
	Request.		Request.
	So, per Figure 3, the URI for the first resource would be "a/eap/1".		So, per Figure 3, the URI for the first resource would be "/a/eap/1".
	* Step 1. The EAP authenticator sends a POST message to the		* Step 1. The EAP authenticator sends a POST message to the
	resource indicated in Step 0 (e.g., "/a/eap/1"). The payload in		resource indicated in Step 0 (e.g., "/a/eap/1"). The payload in
	this message contains the first EAP message (EAP-Request/Identity,		this message contains the first EAP message (EAP-Request/Identity,
	or EAP-Req/Id) and the Recipient ID of the EAP authenticator (RID-		or EAP-Req/Id) and the Recipient ID of the EAP authenticator (RID-
	C) for OSCORE, and MAY contain a CBOR array with a list of		C) for OSCORE, and MAY contain a CBOR array with a list of
	proposed cipher suites (CS-C) for OSCORE. If the cipher suite		proposed cipher suites (CS-C) for OSCORE. If the cipher suite
	list is not included, the default cipher suite for OSCORE is used.		list is not included, the default cipher suite for OSCORE is used.
	The details of the cipher suite negotiation are discussed in		The details of the cipher suite negotiation are discussed in
	Section 6.1.		Section 6.1.
End of changes. 1 change blocks.
	1 lines changed or deleted		1 lines changed or added
This html diff was produced by rfcdiff 1.48.