Re: [lp-wan] [core] Fwd: New Version Notification for draft-tiloca-lpwan-8824-update-00.txt

Hello Marco, and co-authors,

Thanks for the RFC 8824 update effort.

In 6lo we have a document that enables the transmission of SCHC-compressed
IPv6(/UDP/CoAP) packets over IEEE 802.15.4 networks [1].

In RFC 8824, there is the following text, which applies to the above draft:
"If an LPWAN is the Layer 2 technology being used, the SCHC security
considerations discussed in [RFC8724
<https://www.rfc-editor.org/rfc/rfc8824.html#RFC8724>] continue to apply.
When using another Layer 2 protocol, the use of a cryptographic
integrity-protection mechanism to protect the SCHC headers is REQUIRED."

In the context of a possible RFC 8824 update, we (coauthors of [1]) were
wondering whether the "REQUIRED" requirement level in RFC 8824 could be
lowered to "SHOULD". The motivation for using SCHC to compress headers is
performance (in terms of energy, latency, bandwidth, etc.). Since IEEE
802.15.4 allows a "no security" mode, it might be interesting to support
SCHC-compressed CoAP headers over the "no security" mode as well, which
would involve lower overhead (of course, at the expense of reduced
security, for scenarios where the "no security" mode may be reasonable),
and where SCHC would allow a greater performance improvement versus the
default scenario.

Perhaps, could this topic be considered in the RFC 8824 update?

(Also, now that SCHC is expanding beyond LPWANs, the previous comment may
also apply for other L2 technologies...)

Cheers,

Carles (on behalf of the authors of [1])

[1] https://datatracker.ietf.org/doc/draft-ietf-6lo-schc-15dot4

On Mon, 13 Mar 2023 at 19:40, Marco Tiloca <marco.tiloca=
40ri.se@dmarc.ietf.org> wrote:

> Hello LPWAN,
>
> (also CCing CoRE for information)
>
> We have recently submitted the new document draft-tiloca-lpwan-8824-update
> [1].
>
> This draft considers the use of SCHC for header compression of CoAP
> messages and aims at updating RFC 8824, by especially:
>
> - Defining the compression of CoAP options introduced after RFC 8824.
>
> - Updating the compression of the CoAP option OSCORE, in the light of
> recent developments related to the security protocol OSCORE (RFC 8613).
>
> - Clarifying how the SCHC compression handles the CoAP payload marker.
>
> - Defining how the SCHC compression works in the presence of CoAP proxies.
>
>
> Comments and feedback are very welcome!
>
> Best,
> /Marco
>
>
> [1] https://datatracker.ietf.org/doc/draft-tiloca-lpwan-8824-update/
>
>
> -------- Forwarded Message --------
> Subject: New Version Notification for
> draft-tiloca-lpwan-8824-update-00.txt
> Date: Mon, 13 Mar 2023 08:10:00 -0700
> From: internet-drafts@ietf.org
> To: Ivan Martinez <ivanmarinomartinez@gmail.com>
> <ivanmarinomartinez@gmail.com>, Laurent Toutain
> <Laurent.Toutain@imt-atlantique.fr> <Laurent.Toutain@imt-atlantique.fr>,
> Laurent Toutain <laurent.toutain@imt-atlantique.fr>
> <laurent.toutain@imt-atlantique.fr>, Marco Tiloca <marco.tiloca@ri.se>
> <marco.tiloca@ri.se>
>
>
> A new version of I-D, draft-tiloca-lpwan-8824-update-00.txt
> has been successfully submitted by Marco Tiloca and posted to the
> IETF repository.
>
> Name: draft-tiloca-lpwan-8824-update
> Revision: 00
> Title: Clarifications and Updates on using Static Context Header
> Compression (SCHC) for the Constrained Application Protocol (CoAP)
> Document date: 2023-03-13
> Group: Individual Submission
> Pages: 16
> URL:
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-tiloca-lpwan-8824-update-00.txt&data=05%7C01%7Cmarco.tiloca%40ri.se%7Cc512bbd0c9f74b8d16a108db23d50a19%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638143170284458189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GmsWKwYDNrX7H2liDSpZSZmgLQ%2BxbHpGMoAVX523IjE%3D&reserved=0
> Status:
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-tiloca-lpwan-8824-update%2F&data=05%7C01%7Cmarco.tiloca%40ri.se%7Cc512bbd0c9f74b8d16a108db23d50a19%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638143170284458189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=yTymJuq4PRUwsenqTFSgFZcJHhV3kF%2FhWtqSU5FXymo%3D&reserved=0
> Html:
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-tiloca-lpwan-8824-update-00.html&data=05%7C01%7Cmarco.tiloca%40ri.se%7Cc512bbd0c9f74b8d16a108db23d50a19%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638143170284458189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=n0Hy%2FQQZmBv9OnBxqbPRnKczgEnf2FOjSNfMuUvXn3I%3D&reserved=0
> Htmlized:
> https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-tiloca-lpwan-8824-update&data=05%7C01%7Cmarco.tiloca%40ri.se%7Cc512bbd0c9f74b8d16a108db23d50a19%7C5a9809cf0bcb413a838a09ecc40cc9e8%7C0%7C0%7C638143170284458189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=KiyI3Fy%2FZrpi0OvEimOvq4aB%2BC4Pq1gCiMn2wyFXNek%3D&reserved=0
>
>
> Abstract:
> This document clarifies, updates and extends the method specified in
> RFC 8824 for compressing Constrained Application Protocol (CoAP)
> headers using the Static Context Header Compression and fragmentation
> (SCHC) framework. In particular, it considers recently defined CoAP
> options and specifies how CoAP headers are compressed in the presence
> of intermediaries. Therefore, this document updates RFC 8824.
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>