Skip to content

Commit

Permalink
Updated references; consistency fixes in the YANG data model
Browse files Browse the repository at this point in the history
  • Loading branch information
marco-tiloca-sics committed Jan 27, 2025
1 parent e618641 commit c433fae
Show file tree
Hide file tree
Showing 2 changed files with 199 additions and 5 deletions.
12 changes: 7 additions & 5 deletions draft-ietf-schc-8824-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ normative:
RFC9175:
RFC9177:
RFC9363:
I-D.ietf-core-oscore-edhoc:
RFC9668:
I-D.ietf-core-oscore-groupcomm:
I-D.ietf-core-oscore-key-update:
I-D.ietf-core-href:
Expand Down Expand Up @@ -428,7 +428,7 @@ When a CoAP message uses the Request-Tag Option, SCHC compression MAY send its c

## CoAP Option EDHOC Field ## {#coap-options-edhoc}

The EDHOC field is an option defined in {{I-D.ietf-core-oscore-edhoc}} that a client can include in a CoAP request, in order to perform an optimized, shortened execution of the authenticated key exchange protocol EDHOC {{RFC9528}}. Such a request conveys both the final EDHOC message and actual application data, where the latter is protected with OSCORE {{RFC8613}} using a Security Context derived from the result of the current EDHOC execution.
The EDHOC field is an option defined in {{RFC9668}} that a client can include in a CoAP request, in order to perform an optimized, shortened execution of the authenticated key exchange protocol EDHOC {{RFC9528}}. Such a request conveys both the final EDHOC message and actual application data, where the latter is protected with OSCORE {{RFC8613}} using a Security Context derived from the result of the current EDHOC execution.

The EDHOC Option occurs at most once and is always empty. The SCHC Rule MUST describe an empty TV, with the MO set to "equal" and the CDA set to "not-sent".

Expand Down Expand Up @@ -2012,7 +2012,7 @@ The Device decrypts and verifies such a response, which results in the same Comp
| CoAP Request-Tag | CoAP option Request-Tag {{RFC9175}} |
| CoAP Q-Block1 | CoAP option Q-Block1 {{RFC9177}} |
| CoAP Q-Block2 | CoAP option Q-Block2 {{RFC9177}} |
| CoAP EDHOC | CoAP option EDHOC {{I-D.ietf-core-oscore-edhoc}} |
| CoAP EDHOC | CoAP option EDHOC {{RFC9668}} |
{: #table-coap-fields title="CoAP Fields" align="center"}

# Security Considerations
Expand Down Expand Up @@ -2156,7 +2156,7 @@ module ietf-schc-coap {
This module extends the ietf-schc module defined in RFC 9363 to
include the new CoAP options as defined in RFC YYYY.";

revision 2024-10-21 {
revision 2025-03-03 {
description
"New CoAP extensions and extended OSCORE fields.";
reference
Expand Down Expand Up @@ -2235,7 +2235,7 @@ module ietf-schc-coap {
description
"EDHOC option.";
reference
"RFC XXXX Using Ephemeral Diffie-Hellman Over COSE (EDHOC)
"RFC 9668 Using Ephemeral Diffie-Hellman Over COSE (EDHOC)
with the Constrained Application Protocol (CoAP)
and Object Security for Constrained RESTful
Environments (OSCORE)";
Expand Down Expand Up @@ -2323,6 +2323,8 @@ module ietf-schc-coap {

* Use "bit" instead of "b" as symbol for bit (per ISO/IEC 80000-13).

* Updated references.

* Fixes and editorial improvements.

## Version -02 to -03 ## {#sec-02-03}
Expand Down
192 changes: 192 additions & 0 deletions [email protected]
Original file line number Diff line number Diff line change
@@ -0,0 +1,192 @@
module ietf-schc-coap {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-schc-coap";
prefix schc-coap;

import ietf-schc {
prefix schc;
}

organization
"IETF Static Context Header Compression (schc) Working Group";
contact
"WG Web: <https://datatracker.ietf.org/wg/schc/about/>
WG List: <mailto:[email protected]>
Editor: Marco Tiloca
<mailto:[email protected]>";
description
"Copyright (c) 2021 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.
****************************************************************
This module extends the ietf-schc module defined in RFC 9363 to
include the new CoAP options as defined in RFC YYYY.";

revision 2025-03-03 {
description
"New CoAP extensions and extended OSCORE fields.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Sections 5 and 6)";
}

// Field ID

identity fid-coap-option-proxy-cri {
base "schc:fid-coap-option";
description
"Proxy-Cri option.";
reference
"RFC XXXX Constrained Resource Identifiers";
}

identity fid-coap-option-proxy-scheme-number {
base "schc:fid-coap-option";
description
"Proxy-Scheme-Number option.";
reference
"RFC XXXX Constrained Resource Identifiers";
}

identity fid-coap-option-hop-limit {
base "schc:fid-coap-option";
description
"Hop Limit option to avoid infinite forwarding loops.";
reference
"RFC 8768 Constrained Application Protocol (CoAP)
Hop-Limit Option";
}

identity fid-coap-option-echo {
base "schc:fid-coap-option";
description
"Echo option.";
reference
"RFC 9175 Constrained Application Protocol (CoAP):
Echo, Request-Tag, and Token Processing";
}

identity fid-coap-option-request-tag {
base "schc:fid-coap-option";
description
"Request-Tag option.";
reference
"RFC 9175 Constrained Application Protocol (CoAP):
Echo, Request-Tag, and Token Processing";
}

identity fid-coap-option-q-block1 {
base "schc:fid-coap-option";
description
"Q-Block1 option.";
reference
"RFC 9177 Constrained Application Protocol (CoAP)
Block-Wise Transfer Options Supporting
Robust Transmission";
}

identity fid-coap-option-q-block2 {
base "schc:fid-coap-option";
description
"Q-Block2 option.";
reference
"RFC 9177 Constrained Application Protocol (CoAP)
Block-Wise Transfer Options Supporting
Robust Transmission";
}

identity fid-coap-option-edhoc {
base "schc:fid-coap-option";
description
"EDHOC option.";
reference
"RFC 9668 Using Ephemeral Diffie-Hellman Over COSE (EDHOC)
with the Constrained Application Protocol (CoAP)
and Object Security for Constrained RESTful
Environments (OSCORE)";
}

identity fid-coap-option-oscore-x {
base "schc:fid-coap-option";
description
"CoAP option OSCORE x field.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}

identity fid-coap-option-oscore-nonce {
base "schc:fid-coap-option";
description
"CoAP option OSCORE nonce field.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}

identity fid-coap-option-oscore-y {
base "schc:fid-coap-option";
description
"CoAP option OSCORE y field.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}

identity fid-coap-option-oscore-oldnonce {
base "schc:fid-coap-option";
description
"CoAP option OSCORE old_nonce field.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}

// Function Length

identity fl-oscore-oscore-nonce-length {
base "schc:fl-base-type";
description
"Size in bytes of the OSCORE nonce corresponding to m+1.";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}

identity fl-oscore-oscore-oldnonce-length {
base "schc:fl-base-type";
description
"Size in bytes of the OSCORE old_nonce corresponding to w+1.
";
reference
"RFC YYYY Static Context Header Compression (SCHC) for the
Constrained Application Protocol (CoAP) (see
Section 6.4)
RFC XXXX Key Update for OSCORE (KUDOS)";
}
}

0 comments on commit c433fae

Please sign in to comment.