Liaison statement
Liaison statement from the IETF LPWAN WG to 3GPP
Additional information about IETF liaison relationships is available on the
IETF webpage
and the
Internet Architecture Board liaison webpage.
| State | Posted |
|---|---|
| Submitted Date | 2022-09-27 |
| From Group | lpwan |
| From Contact | Pascal Thubert |
| To Group | 3GPP |
| To Contacts | Lionel Morand <lionel.morand@orange.com> Susanna Kooistra <3GPPLiaison@etsi.org> |
| Cc | Éric Vyncke <evyncke@cisco.com> Erik Kline <ek.ietf@gmail.com> IPv6 over Low Power Wide-Area Networks Discussion List <lp-wan@ietf.org> Pascal Thubert <pthubert@cisco.com> Alexander Pelov <a@ackl.io> Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> |
| Response Contact | Alexander Pelov <a@ackl.io> Pascal Thubert <pthubert@cisco.com> |
| Purpose | For action |
| Deadline | 2022-10-20 Action Needed |
| Attachments | For action LPWAN to 3GPP |
| Body |
We write to 3GPP to expose new IETF work (https://datatracker.ietf.org/doc/draft-ietf-lpwan-schc-over-nbiot/) on the application of the SCHC protocol (RFC 8724/8824) on NB IOT. This document is currently under IETF Last Call till October 7th, 2022, and it should be submitted to the IESG evaluation for final approval on October 27th, 2022. All comments are welcome until the ballot of 20 October, to be sent to the last-call@ietf.org mailing list, or exceptionally to iesg@ietf.org instead . SCHC provides a deep compression of the IPv6 packets at Layer-3 and above, and enables new capabilities such as IPv6 and CoAP signaling in highly constrained network like LP-WANs where it was previously considered impossible. SCHC also provides a fragmentation mechanism that would not necessarily be used in the case of NB-IOT. The new work at the IETF LPWAN Working Group provides informational considerations on how SCHC could be used over the Radio link and the No-Access Stratum. It also provides a normative description of the usage of SCHC over the Non-IP Data Delivery service. We foresee a potential of collaboration and cross referencing between our IETF specifications and 3GPP standards and seek advice and feedback. |