Draft: draft-ietf-lake-edhoc

Commentary: There was quite a lot of overlap between 3.3.2 and 3.4 . Tried to integrate 3.3.2 in 3.4 to avoid that .
Paragraph (version A):
EDHOC includes the selection of connection identifiers (C_I, C_R)
identifying a connection for which keys are agreed.  Connection
identifiers may be used in the ongoing EDHOC protocol (see ci-edhoc)
or in a subsequent application protocol, e.g., OSCORE (see ci-
oscore).  The connection identifiers do not have any cryptographic
purpose in EDHOC.
Paragraph (version B):
EDHOC includes the selection of connection identifiers (C_I, C_R)
identifying a connection for which keys are agreed.
Paragraph (version B):
Connection identifiers may be used to correlate EDHOC messages and
facilitate the retrieval of protocol state during EDHOC protocol
execution (see transport) or in a subsequent application protocol,
e.g., OSCORE (see ci-oscore).  The connection identifiers do not have
any cryptographic purpose in EDHOC.
Paragraph (version A):
Connection identifiers may be used to correlate EDHOC messages and
facilitate the retrieval of protocol state during EDHOC protocol
execution.  EDHOC transports that do not inherently provide
correlation across all messages of an exchange can send connection
identifiers along with EDHOC messages to gain that required
capability, see transport.  For an example of using connection
identifiers when CoAP is used as transport, see coap.
Paragraph (version A):
denial-of-service protection.
Paragraph (version A):
Besides these common transport-oriented properties, EDHOC transport
additionally needs to support the correlation between EDHOC messages,
including an indication of a message being message_1.  The
correlation may reuse existing mechanisms in the transport protocol.
For example, the CoAP Token may be used to correlate EDHOC messages
in a CoAP response and an associated CoAP request.  In the absence of
correlation between a message received and a message previously sent
inherent to the transport, the EDHOC connection identifiers may be
added, e.g., by prepending the appropriate connection identifier
(when available from the EDHOC protocol) to the EDHOC message.
Transport of EDHOC in CoAP payloads is described in coap, which also
shows how to use connection identifiers and message_1 indication with
CoAP.
Paragraph (version B):
demultiplex EDHOC messages from other types of messages,
Paragraph (version B):
denial-of-service protection,
Paragraph (version B):
message correlation.
Paragraph (version B):
The transport needs to support the correlation between EDHOC messages
and facilitate the retrieval of protocol state during EDHOC protocol
execution, including an indication of a message being message_1.  The
correlation may reuse existing mechanisms in the transport protocol.
For example, the CoAP Token may be used to correlate EDHOC messages
in a CoAP response and an associated CoAP request.
Paragraph (version B):
Connection identifiers may be used to correlate EDHOC messages and
facilitate the retrieval of protocol state during EDHOC protocol
execution.  EDHOC transports that do not inherently provide
correlation across all messages of an exchange can send connection
identifiers along with EDHOC messages to gain that required
capability, e.g., by prepending the appropriate connection identifier
(when available from the EDHOC protocol) to the EDHOC message.
Transport of EDHOC in CoAP payloads is described in coap, which also
shows how to use connection identifiers and message_1 indication with
CoAP.