\
lpwan Working Group                                          I. Martinez
Internet-Draft                                                L. Toutain
Intended status: Standards Track  Institut MINES TELECOM; IMT Atlantique
Expires: 22 September 2022                                 21 March 2022


              Can Rules be adapted to a Meshed environment
                  draft-martinez-lpwan-meshed-rules-00

Abstract

   This document specifies how openSCHC handles the rule selection and
   how this process can be extended to a meshed environment.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 22 September 2022.

Copyright Notice

   Copyright (c) 2022 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.







Martinez & Toutain      Expires 22 September 2022               [Page 1]


Internet-Draft           LPWAN SCHC Meshed rules              March 2022


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Rule Manager  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Extending the model . . . . . . . . . . . . . . . . . . . . .   3
   4.  Management with simple identified rules . . . . . . . . . . .   3
   5.  Management with double identified rules . . . . . . . . . . .   3
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   This document specifies how openSCHC handles the rule selection and
   how this process can be extended to a meshed environment.

2.  Rule Manager

   OpenSCHC imports rule in JSON, such has:

   [{
       "DeviceID" : "udp:90.27.174.128:8888",
       "SoR" : [
            {
               "RuleID": 6,
               "RuleIDLength": 3,
               "Compression": [
               ....

                      Figure 1: Simple identified SoR.

   A specific device may have several rules, identified in the SoR (Set
   of Rules) key.  The device is identified by a DeviceID.  OpenSCHC
   allows to send SCHC packet over an udp tunnel.  In that case, the
   device ID starts with the udp keyword, followed by the IP address and
   the port number.

   In that architecture, the core SCHC may contains several devices'
   rules, idenfified by different ID.  The device side contains only the
   SoR associated to the device.

   When a packet arrive to the SCHC core, a machting rule is searched
   among all the rule.  The core SCHC uses the device ID to effectively
   send the SCHC packet to the device.

   The device answers back to the core SCHC, ignoring the device ID
   since this value identifies the device itself.





Martinez & Toutain      Expires 22 September 2022               [Page 2]


Internet-Draft           LPWAN SCHC Meshed rules              March 2022


   So, we can name core a SCHC instance containing rules that does not
   contains its own ID and a device a SCHC instance containing rules
   that contains only its own ID.  Communication from device to core is
   upstream and downstream in the reverse direction.

3.  Extending the model

   This example is defined for a star toplogy, and devices can send back
   their response in case of UDP tunnel or use the media in case of
   LPWAN.  In a meshed network, several instances may coexist and use
   the same ruleID for a device but the rule itself can be different.

   The previous rule can be updated to add a CoreID:

   [{
       "DeviceID" : "udp:90.27.174.128:8888",
       "CoreID": "udp:123.1.2.3:23628"
       "SoR" : [
            {
               "RuleID": 6,
               "RuleIDLength": 3,
               "Compression": [
               ....

                      Figure 2: Double identified SoR.

   The process for the core compression is the same.  When the device
   receives the SCHC packet, it identifies the coreID and select only
   rules coming from this instance.  When the devices sends a packet,
   instead of replying on the same port.

4.  Management with simple identified rules

   A device receives a SCHC packet on a single idendified SoR, keeps
   track of the sender to reply.  This could be either the technology or
   the address of the core.  Only one core is allowed in that case.

5.  Management with double identified rules

   A device receiving a SCHC packet on a double identifie SoR, does not
   have to keep track of the core address.  When a packet needs to be
   compressed, the selected rule indicates where to send the SCHC
   packet.  The device may have several SoR corresponding to each core.

6.  Normative References






Martinez & Toutain      Expires 22 September 2022               [Page 3]


Internet-Draft           LPWAN SCHC Meshed rules              March 2022


   [RFC8724]  Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and JC.
              Zuniga, "SCHC: Generic Framework for Static Context Header
              Compression and Fragmentation", RFC 8724,
              DOI 10.17487/RFC8724, April 2020,
              <https://www.rfc-editor.org/info/rfc8724>.

   [RFC8824]  Minaburo, A., Toutain, L., and R. Andreasen, "Static
              Context Header Compression (SCHC) for the Constrained
              Application Protocol (CoAP)", RFC 8824,
              DOI 10.17487/RFC8824, June 2021,
              <https://www.rfc-editor.org/info/rfc8824>.

Authors' Addresses

   Ivan Marino Martinez Bolivar
   Institut MINES TELECOM; IMT Atlantique
   2 rue de la Chataigneraie
   CS 17607
   35576 Cesson-Sevigne Cedex
   France
   Email: ivan-marino.martinez-bolivar@imt-atlantique.fr


   Laurent Toutain
   Institut MINES TELECOM; IMT Atlantique
   2 rue de la Chataigneraie
   CS 17607
   35576 Cesson-Sevigne Cedex
   France
   Email: Laurent.Toutain@imt-atlantique.fr





















Martinez & Toutain      Expires 22 September 2022               [Page 4]