diff --git a/submission-updates/draft-ietf-ace-edhoc-oscore-profile.html b/submission-updates/draft-ietf-ace-edhoc-oscore-profile.html
index cb6d444..dfc4e37 100644
--- a/submission-updates/draft-ietf-ace-edhoc-oscore-profile.html
+++ b/submission-updates/draft-ietf-ace-edhoc-oscore-profile.html
@@ -1466,16 +1466,16 @@
Option 1 supports update of access rights protected with the existing OSCORE Security Context (see Section 4.5 ), whereas option 2 always generates a new OSCORE Security Context. If option 2 is implemented and there is a need to perform an update of access rights without changing OSCORE Security Context, then C needs to also implement option 1 or to rely on some other method, such as the alternative workflow of the ACE framework (see [I-D.ietf-ace-workflow-and-params ] ).¶
-
+
-
-
+
@@ -1531,47 +1522,46 @@
+
Access
Information
- POST
- /authz-info
- (access_token)
- 2.01
- Created
- EDHOC
- Mutual
- authentication
- and
- derivation
- of
- an
- OSCORE
- Security
- Context
- /Proof-of-possession
- and
- Security
- Context
- storage/
- OSCORE
- Request
- OSCORE
- Response
- /Proof-of-possession
- and
- Security
- Context
- storage
- (latest)/
- OSCORE
- Request
- OSCORE
- Response
- ...
+ POST
+ /edhoc
+ (EDHOC
+ message_1)
+ 2.04
+ Changed
+ (EDHOC
+ message_2)
+ /
+ Derivation
+ of
+ OSCORE
+ Security
+ Context
+ /
+ POST
+ /edhoc
+ (EDHOC
+ message_3
+ with
+ access_token
+ in
+ EAD_3)
+ /
+ Derivation
+ of
+ OSCORE
+ Security
+ Context
+ /
+ OSCORE
+ Request
+ OSCORE
+ Response
¶
Figure 1 :
-Protocol Overview Example. Names of messages coincide with those of RFC 9200 when applicable.
+Protocol Outline using EDHOC Forward Message Flow.
diff --git a/submission-updates/draft-ietf-ace-edhoc-oscore-profile.txt b/submission-updates/draft-ietf-ace-edhoc-oscore-profile.txt
index 863db06..708a37f 100644
--- a/submission-updates/draft-ietf-ace-edhoc-oscore-profile.txt
+++ b/submission-updates/draft-ietf-ace-edhoc-oscore-profile.txt
@@ -393,35 +393,28 @@ Table of Contents
|<--------------------------------- Access Token ------+
| + Access Information |
| | |
- +----- POST /authz-info ---->| |
- | (access_token) | |
+ +------- POST /edhoc ------>| |
+ | (EDHOC message_1) | |
| | |
- |<------ 2.01 Created -------+ |
+ |<------ 2.04 Changed -------+ |
+ | (EDHOC message_2) | |
| | |
- | <========= EDHOC ========> | |
- | Mutual authentication | |
- | and derivation of an | |
- | OSCORE Security Context | |
+ / Derivation of OSCORE | |
+ Security Context / | |
| | |
- | /Proof-of-possession and |
- | Security Context storage/ |
+ +------- POST /edhoc ------>| |
+ | (EDHOC message_3 with | |
+ | access_token in EAD_3) | |
| | |
- +----- OSCORE Request ------>| |
- | | |
- |<---- OSCORE Response ------| |
- | | |
- /Proof-of-possession | |
- and Security Context | |
- storage (latest)/ | |
+ | / Derivation of OSCORE |
+ | Security Context / |
| | |
+----- OSCORE Request ------>| |
| | |
|<---- OSCORE Response ------| |
| | |
- | ... | |
- Figure 1: Protocol Overview Example. Names of messages coincide
- with those of RFC 9200 when applicable.
+ Figure 1: Protocol Outline using EDHOC Forward Message Flow.
3. Client-AS Communication