Skip to content

Commit

Permalink
Added the YANG data model for the ietf-schc-coap-ext module
Browse files Browse the repository at this point in the history
  • Loading branch information
@marco-tiloca-sics
marco-tiloca-sics committed Feb 29, 2024
1 parent c97fd26 commit 7303380
Showing 1 changed file with 188 additions and 1 deletion.
189 changes: 188 additions & 1 deletion draft-ietf-schc-8824-update.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,7 @@ normative:
RFC8768:
RFC9175:
RFC9177:
RFC9363:
I-D.ietf-core-oscore-edhoc:
I-D.ietf-core-oscore-groupcomm:
I-D.ietf-core-oscore-key-update:
Expand Down Expand Up @@ -1899,7 +1900,193 @@ This document has no actions for IANA.

# YANG Data Model

TBD
This appendix defines the ietf-schc-coap-ext module, which extends the ietf-schc module defined in {{RFC9363}} to include the new CoAP options as defined in the present document.

~~~~~~~~~~~

<CODE BEGINS> file "ietf-schc@2024-03-04.yang"

module ietf-schc-coap-ext {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-schc-coap-ext";
prefix schc-coap-ext;

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:schc@ietf.org>
Editor: Marco Tiloca
<mailto:marco.tiloca@ri.se>";
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 2024-02-22 {
description
"Initial version for RFC YYYY ";
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-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-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)";
}

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

// Function Length

identity fl-oscore-oscore-nonce-length {
base fl-base-type;
description
"Size in bytes of the OSCORE nonce corresponding to m+1.";
reference
"RFC 8824 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 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)";
}
}

<CODE ENDS>

~~~~~~~~~~~
{: #fig-yang-data-model title="SCHC YANG Data Model" artwork-align="left"}

## Version -00 to -01 ## {#sec-00-01}

Expand Down

0 comments on commit 7303380

Please sign in to comment.