AD review draft-ietf-emu-eap-edhoc-06
The draft looks generally fine and clear. I have one question and
one comment
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Identifier | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | R |S|M| L | EDHOC Message Length ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EDHOC Data ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: EAP-EDHOC Request and Response Packet Format
4.1. EAP-EDHOC Request Packet
The EDHOC Message Length field can have a size of one to four octets
and is present only if the L flag bits represent a value greater than
0. This field provides the total length of the EDHOC message that is
being fragmented. When there is no fragmentation, it is not present.
EDHOC Data:
The EDHOC data consists of the whole or a fragment of the transported
EDHOC message.
How does one determine the length of the EDHOC Message Length field?
I think RFC4137, RFC5216, RFC6677 should probably be normative references ?
Paul
_______________________________________________
Emu mailing list -- [email protected]
To unsubscribe send an email to [email protected]
