Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

EDITORIAL. Align caption format #430

Merged
merged 2 commits into from
Aug 24, 2023
Merged

EDITORIAL. Align caption format #430

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a185b9
EDITORIAL. Align caption format
emanjon Aug 24, 2023
1860000
Merge branch 'master' into EDITORIAL.-Align-caption-format
gselander Aug 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 9 additions & 9 deletions draft-ietf-lake-edhoc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -422,7 +422,7 @@ The Initiator and the Responder need to have agreed on a single method to be use
| 3 | Static DH Key | Static DH Key |
+-------------+--------------------+--------------------+
~~~~~~~~~~~
{: #fig-method-types title="Authentication Keys for Method Types"}
{: #fig-method-types title="Authentication keys for method types."}
{: artwork-align="center"}

EDHOC does not have a dedicated message field to indicate the protocol version. Breaking changes to EDHOC can be introduced by specifying and registering new methods.
Expand Down Expand Up @@ -452,7 +452,7 @@ The integers with one-byte CBOR encoding are -24, ..., 23, see {{fig-int-one-byt
Integer: -24 -23 ... -2 -1 0 1 ... 23
CBOR encoding (1 byte): 37 36 ... 21 20 00 01 ... 17
~~~~~~~~~~~
{: #fig-int-one-byte title="One-Byte CBOR Encoded Integers"}
{: #fig-int-one-byte title="One-byte CBOR encoded integers."}
{: artwork-align="center"}

The byte strings which coincide with a one-byte CBOR encoding of an integer MUST be represented by the CBOR encoding of that integer. Other byte strings are simply encoded as CBOR byte strings.
Expand Down Expand Up @@ -1285,7 +1285,7 @@ Initiator Responder
+------------------------------------------------------------------>|
| message_1 |
~~~~~~~~~~~
{: #fig-error1 title="Cipher Suite Negotiation Example 1."}
{: #fig-error1 title="Cipher suite negotiation example 1."}
{: artwork-align="center"}

In Example 2 ({{fig-error2}}), the Responder supports cipher suites 8 and 9 but not the more preferred (by the Initiator) cipher suites 5, 6 or 7. To illustrate the negotiation mechanics we let the Initiator first make a guess that the Responder supports suite 6 but not suite 5. Since the Responder supports neither 5 nor 6, it rejects the first message_1 with an error indicating support for suites 8 and 9 in SUITES_R (in any order). The Initiator also supports suites 8 and 9, and prefers suite 8, so therefore selects suite 8 in the second message_1. The Initiator prepends in SUITES_I the selected suite 8 with the more preferred suites in order of preference, in this case suites 5, 6 and 7, to mitigate a potential attack on the cipher suite negotiation.
Expand All @@ -1308,7 +1308,7 @@ Initiator Responder
+------------------------------------------------------------------>|
| message_1 |
~~~~~~~~~~~
{: #fig-error2 title="Cipher Suite Negotiation Example 2."}
{: #fig-error2 title="Cipher suite negotiation example 2."}
{: artwork-align="center"}

## Unknown Credential Referenced
Expand Down Expand Up @@ -1508,7 +1508,7 @@ Reference: [[this document]]
+-------------+------------------------------+-------------------+

~~~~~~~~~~~
{: #fig-exporter-label title="EDHOC Exporter Label"}
{: #fig-exporter-label title="EDHOC exporter label."}


~~~~~~~~~~~ aasvg
Expand Down Expand Up @@ -1725,7 +1725,7 @@ The columns of the registry are Name, Label, Description, and Reference, where L
| | | CBOR byte string | Section 3.8.1 |
+-----------+-------+------------------------+-------------------+
~~~~~~~~~~~
{: #fig-ead-labels title="EAD Labels"}
{: #fig-ead-labels title="EAD labels."}

~~~~~~~~~~~ aasvg

Expand Down Expand Up @@ -1756,7 +1756,7 @@ IANA is requested to register the following entries in the "COSE Header Paramete
| | | | a 'cnf' claim |
+-----------+-------+----------------+---------------------------+
~~~~~~~~~~~
{: #fig-header-params title="COSE Header Parameter Labels"}
{: #fig-header-params title="COSE header parameter labels."}

## The Well-Known URI Registry {#well-known}

Expand Down Expand Up @@ -1928,7 +1928,7 @@ longer than the default oscore_salt_length.
| Responder | C_I | C_R |
+----------------+-----------+--------------+
~~~~~~~~~~~
{: #fig-edhoc-oscore-id-mapping title="Usage of connection identifiers in OSCORE" artwork-align="center"}
{: #fig-edhoc-oscore-id-mapping title="Usage of connection identifiers in OSCORE." artwork-align="center"}

Client and Server SHALL use the parameters above to establish an OSCORE Security Context, as per Section 3.2.1 of {{RFC8613}}.

Expand Down Expand Up @@ -2122,7 +2122,7 @@ For a complete specification and more examples, see {{RFC8949}} and {{RFC8610}}.
1, 2, true 0x0102f5 sequence
-----------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~
{: #fig-cbor-examples title="Examples of use of CBOR and CDDL" artwork-align="center"}
{: #fig-cbor-examples title="Examples of use of CBOR and CDDL." artwork-align="center"}

## CDDL Definitions {#CDDL}

Expand Down