lpwan Working Group                                          A. Minaburo
Internet-Draft                                                    Acklio
Intended status: Informational                                L. Toutain
Expires: June 8, September 11, 2017      Institut MINES TELECOM ; TELECOM Bretagne
                                                        December 5, 2016

        6LPWA IMT Atlantique
                                                          March 10, 2017

        LPWAN Static Context Header Compression (SCHC) for CoAP
               draft-ietf-lpwan-coap-static-context-hc-00
               draft-ietf-lpwan-coap-static-context-hc-01

Abstract

   This draft discusses the way SCHC header compression can be applied
   to CoAP headers in an LPWAN flow regarding the generated traffic.
   CoAP protocol differs from IPv6 and
   extend UDP protocols because the number of functions (CDF) CoAP
   Header has a flexible header due to optimize compression. variable options.  Another
   important difference is the asymmetric format in the header
   information used in the request and the response packets.  This draft
   shows that the Client and the Server do not uses the same fields and
   how the SCHC header compression can be used.

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 http://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 June 8, September 11, 2017.

Copyright Notice

   Copyright (c) 2016 2017 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
   (http://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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   [I-D.toutain-lpwan-ipv6-static-context-hc] defines a header
   compression
   technique mechanism for LPWA LPWAN network based on a static context.  This
   Where the context is said static since the element values composing
   the context are not learned during the packet exchanges but are
   previously installed. defined.  The
   context is context(s) is(are) known by both ends. ends before
   transmission.

   A context is composed of a set of rules (referenced (contexts) that are
   referenced by rule ids). Rule IDs (identifiers).  A rule describes the header
   fields with some associated Target Values (TV).  A Matching Operator
   (MO) is associated to each field. header field description.  The rule is
   selected if all the MO matches
   . A MOs fit the TVs.  In that case, a Compression
   Decompression Function is (CDF) associated to each field to
   define defines the
   link between the compressed and decompressed value for a
   specific field. each of the
   header fields.

   This draft discusses the way SCHC can be applied to CoAP headers and headers, how
   to extend MOs to match a specific element when several fields of the number
   same type are presented in the header.  It also introduces the notion
   of functions (CDF) to optimize compression. bidirectional or unidirectional (upstream and downstream) fields.

2.  Compressing  CoAP Compressing

   CoAP [RFC7252] is an implementation of a the REST architecture for
   contrained
   constrained devices.  Gateway between CoAP and HTTP can be easily
   build
   built since both protocol protocols uses the same address space (URL), caching
   mechanisms and methods.

   Nevertheless, if limited, the size of a CoAP header may be
   incompatible with too large
   for LPWAN constraints and some compression may be needed to reduce
   the header size.  CoAP compression is not straightforward.  Some
   differences between IPv6/UDP and CoAP can be
   enlighten. highlighted.  CoAP
   differs from IPv6 and UDP protocols: protocols in the following
   aspects:

   o  IPv6 and UDP are symmetrical protocols.  The same fields are found
      in the request and in the answer, response, only location position in the header
      may change (e.g. source and destination fields).  A CoAP request
      is different from an answer. response.  For instance, example, the URI-path option
      is mandatory in the request and may is not be found in the response.

   o  CoAP also obeys to the client/server paradigm and the compression
      rate can be different if the request is issued from a LPWAN node
      or from an external non LPWAN device.  For instance in the former case the a Thing (ES) aware of
      LPWAN constraints can generate a 1 byte token, but a regular CoAP
      cleint will certainly send a larger token size may be set to one byte.  In the latter case, the token
      size cannot be constraint and be up to 15 byte long. Thing.

   o  In IPv6, main header IPv6 and UDP header fields have a fixed size.  In CoAP, Token
      size may vary from 0 to 15 8 bytes, length is given by a field in the
      header.  More systematically, the CoAP options are described using
      the Type-Length-Value principle.  Evenmore regarding Type-Length-Value.  When applying SCHC header compression, the
      option
      token size value, is not known at the coding will be different. rule creation, the sender and the
      receiver must agree on its compressed size.

   o  The options type in CoAP are is not defined with the same value.  The
      Delta TLV coding makes that the type is not independant independent of
      previous option and may vary regarding the options contained in
      the header.

2.1.  CoAP usages behavior

   A LPWAN node can either be a client or a server and sometimes both.
   In the client mode, the LPWAN node sends request to a server and
   expected
   expects an answer or acknowledgements.  Acknowledgements can be at 2
   different levels:

   o  In the transport level, a CON message is acknowledged by an ACK
      message.  A NON confirmable messages are message is not acknowledged. acknowledged at all.

   o  In REST level, a REST request is acknowledged by an "error" code.
      The [RFC7967] defines an option to limit the number of
      acknowledgements.

   Note that acknowledgement can be optimized and a REST level
   acknowledgement can be used as a transport level acknowledgement.

2.2.  CoAP protocol analysis

   CoAP header format defines the following fields:

   o  version (2 bits): this field can be elided during a the SCHC
      compresssion

   o  type (2 bits): bits).  It defines the type of the transport messages, 4
      values are defined.  Regarding defined, regarding the type of exchange, if exchange.  If only NON
      messages are sent or CON/ACK messages, this field can be reduced
      to 0 or 1 bit.

   o  token length (4 bytes). bits).  The standard allows up to 15 8 bytes for a
      token length.
      token.  If a fix fixed token size is chosen, then this field can be
      elided.  If some variation in length are needed then 1 or 2 bits
      could be enough for most of LPWAN applications.

   o  code (8 bits).  This field codes the request and the response
      values.  In CoAP represents these values are represented in a more compact way,
      way then the coding used in HTTP, but the coding is not optimal.

   o  message id (16 bits).  This value of this header field is used to
      acknowledge CON frames.  The size of this field is computed to
      allow the anticipation (how many frames can be sent without
      acknowledgement).  When a value is used, the [RFC7252] defines the
      time before it can be reused without ambiguities.  This size
      defined may be too large for a LPWAN node sending or receiving few
      messages a day.

   o  Token (0 to 15 8 bytes).  Token identifies header field is used to identify
      active flows.  Regarding the usage for LPWAN (stability of in time
      and limited number), a short token (1 Byte) Byte or less) can be enough.

   o  options are coded through using delta-TLV.  The delta-T depends of on
      previous values, length is encoded inside the option.  The
      [RFC7252] distinguishes repeatable options that can appear several time
      times in the header.  Among them we can distinguish:

      *  list options which appear several time in the header but are
         exclusive such as the Accept option.

      *  cumulative options which appear several time times in the header but
         are part of a more generic value such as Uri-Path and Uri-
         Query.  In that case, some elements may not change during the
         Thing lifetime and other may change at each request.  For
         instance CoMi [I-D.ietf-core-comi] defines the following path
         /c/X6?k="eth0", where the first path element "c" does not
         change, the second element can vary over time with a different
         length (it represents the base64 enconding of a SID) and the
         query string can also vary over time.

      For a given flow some value options are stable through time.
      Observe, ETag, If-Match, If-None-Match and Size varies in each
      message.  Options can be stored in a SCHC context and cumulative
      options can be stored globally.

   The CoAP protocol must not be altered by the compression/
   decompression phase, but if no semantic is attributed to a value, it
   may be changed during this phase.  For instance instance, the compression
   phase may reduce the size of a token but must maintain its unicity.
   The decompressor will not be able to restore the original value but
   the behavior will remain the same.  If no special semantic is
   assigned to the token, this will be transparent.  If a special
   semantic is assigned to the token, its compression may not be
   possible.

3.  SCHC rules for CoAP header compression

   This implies that draft refines the compressor/decompressor must be aware rules definition by adding the direction of
   the
   protocol state machine and do message, from the Thing point of view (uplink, downlink or
   bidirectional).  It does not processes request and response introduce new Machting Operator or new
   Compression Decompression Function, but add some possibility to check
   one particular element when several of them are present at the same way.
   time.

   A conservative compression leaves rule can contain CoAP and IPv6/UDP entries.  In that case, IPv6/UDP
   entries are tagged bidirectional.

3.1.  Directional Rules

   By default, an entry in a rule is bidirectional which means that it
   can be applied either on the uplink or downlink headers.  By
   specifying the direction, the LC will take into account the specific
   field only if the direction match.

   If the Thing is a client, the URI-Path option is only present on
   request and not on the response.  Therefore, the exact matching
   principle to select a rule cannot apply.

   Some options are marked unidirectional, the value unchanged.  Non
   conservative compression can (uplink or
   downlink) depends of the scenario.  A Uri-Path option will be used when marked
   uplink if the Thing acts as a CoAP implementation client and downlink if the Thing acts
   as a server.  If the Thing acts both as client and server, two
   different rules will be defined.

3.2.  Matching Operator

   The Matching Operator behavior has not been defined to work specifically changed, but the value must
   take a position value, if the entry is repeated :

         FID          TV      MO             CDF

         URI-Path     foo     equal 1      not-sent
         URI-Path     bar     equal 2      not-sent

                         Figure 1: Position entry.

   For instance, the rule Figure 1 matches with LPWAN network and uses
   large values /foo/bar, but not /bar/
   foo.

   The position is added after the natural argument of the MO, for fields.

2.2.1.  CoAP Compression Decompression Function

   To compress more efficiently CoAP message, several Compression/
   Decompression Function (CDF)
   example MSB (4,3) indicates a most significant bit matching of 4 bits
   in a field located in position 3.

3.3.  Compressed field length

   When the length is not clearly indicated in the rule, the value
   length must be defined.

2.2.1.1.  Static-mapping

   The goal of static-mapping sent with the field data, which means for CoAP to send
   directly the CoAP option where the delta-T is set to reduce 0.

   For the size CoMi path /c/X6?k="eth0" the rule can be set to:

         FID          TV      MO             CDF

         URI-Path     c       equal 1      not-sent
         URI-Path             ignore 2     value-sent
         URI-Query    k=      MSB (16, 1)  value-sent

                      Figure 2: CoMi URI compression

   Figure 2 shows the parsing and the compression of a field by
   allocating shorter value. the URI. where c is
   not sent.  The mapping second element is known sent with the length (i.e. 0x02 X 6)
   followed by both ends and
   stored in the query option (i.e. 0x08 k="eth0").

   [[NOTE we don't process URI with a table in both end context.  The Static-mapping multiple number of path element
   ??]].

4.  Application to CoAP header fields

   This section lists the different CoAP header fields and how they can
   be compressed.

4.1.  CoAP version field

   This field is
   conservative.

   Static-mapping bidirectional.

   This field contains always the same value, therefore the TV may be applied 1,
   the MO is set to several fields.  For instance "equal" and the CDF is set to "not-sent"

4.2.  CoAP type field may

   This field is bidirectional or undirectional.

   Several strategies can be reduced from 2 bits applied to 1 bit this field regarding the values
   used:

   o  if only CON/ACK one type is sent, for example NON message, its
      transmission can be avoided.  TV is set to the value, MO is set to
      "equal" and CDF is set to "not-sent".

   o  if two values are sent, for example CON and ACK and RST is not
      used, but this field can be reduced to one bit.  TV is set to a
      matching value {CON: 0, ACK: 1}, MO is set to match-mapping and
      CDF is set to mapping-sent.

   o  It is also possible avoid transmission of this field by marking it
      unidirectional.  In one direction, the TV is set to CON, MO is set
      to "equal" and CDF is set to "not-sent".  On the other direction,
      the TV is set to ACK, the MO is set to "equal" and the CDF is set
      to "not-sent".

   o  Otherwise TV is not set, MO is set to "ignore" and CDF is set to
      "value-sent".

4.3.  CoAP token length field

   This field is bi-directional.

   Several strategies can be applied to this field regarding the main benefit values:

   o  no token or a wellknown length, the transmission can be avoided.
      TV is compressing set to the length, the MO is set to "equal" and CDF is set
      to "not-sent"

   o  The length is variable from one message to another.  TV is not
      set, MO is set to "ignore" and CDF is set to "value-sent".  The
      size of the sent value must be known by ends.  The size may be 4
      bits.  The receiver must take into account this value to retrieve
      the token.  A CoAP proxy may be used before the compression to
      reduce the field size.

4.4.  CoAP code field. field

   This field is unidirectional.  The client and the server do not use
   the same values.

   The CoAP code field defines a tricky way to ensure compatibility with
   HTTP values.  Nevertheless only 21 values are defined by [RFC7252]
   compared to the 255 possible values.  So  So, it could efficiently be
   coded on 5 bits.  To allow flexibility and evolution if new codes are
   introduced, a static mapping table is associated to each instance  The number of
   this function.

   Figure 1 gives a possible mapping, it can be changed to add code may vary over time, some new
   codes may be introduced or reduced if some values are never used by both ends. applications use a limited number of
   values.

                  +------+------------------------------+-----------+
                  | Code | Description                  | Mapping   |
                  +------+------------------------------+-----------+
                  | 0.00 |                              |  0x00     |
                  | 0.01 | GET                          |  0x01     |
                  | 0.02 | POST                         |  0x02     |
                  | 0.03 | PUT                          |  0x03     |
                  | 0.04 | DELETE                       |  0x04     |
                  | 0.05 | FETCH                        |  0x05     |
                  | 0.06 | PATCH                        |  0x06     |
                  | 0.07 | iPATCH                       |  0x07     |
                  | 2.01 | Created                      |  0x08     |
                  | 2.02 | Deleted                      |  0x09     |
                  | 2.03 | Valid                        |  0x0A     |
                  | 2.04 | Changed                      |  0x0B     |
                  | 2.05 | Content                      |  0x0C     |
                  | 4.00 | Bad Request                  |  0x0D     |
                  | 4.01 | Unauthorized                 |  0x0E     |
                  | 4.02 | Bad Option                   |  0x0F     |
                  | 4.03 | Forbidden                    |  0x10     |
                  | 4.04 | Not Found                    |  0x11     |
                  | 4.05 | Method Not Allowed           |  0x12     |
                  | 4.06 | Not Acceptable               |  0x13     |
                  | 4.12 | Precondition Failed          |  0x14     |
                  | 4.13 | Request Entity Too Large     |  0x15     |
                  | 4.15 | Unsupported Content-Format   |  0x16     |
                  | 5.00 | Internal Server Error        |  0x17     |
                  | 5.01 | Not Implemented              |  0x18     |
                  | 5.02 | Bad Gateway                  |  0x19     |
                  | 5.03 | Service Unavailable          |  0x1A     |
                  | 5.04 | Gateway Timeout              |  0x1B     |
                  | 5.05 | Proxying Not Supported       |  0x1C     |
                  +------+------------------------------+-----------+

                  Figure 1: 3: Example of CoAP code mapping

   This CDF

   Figure 3 gives a possible mapping, it can also be applied to path changed to send a reference instead of
   the path value.

2.2.1.2.  Remapping

   With dynamic mapping, add new codes
   or reduced if some values are never used by both ends.

   The field can be treated differently in upstream than in downstream.
   If the mapping Thing is done dynamically, which means
   that a client an entry can be set on the other end has no way to uplink message
   with a code matching for 0.0X values and another for downlink values
   for Y.ZZ codes.  It is the learn opposite if the original value. thing is a server.

4.5.  CoAP Message ID field

   This
   function field is not conservative.  The mapping context must bidirectional.

   Message ID is used for two purposes:

   o  To acknowledge a CON message with an ACK.

   o  To avoid duplicate messages.

   In LPWAN, since a message can be stored in received by several radio gateway,
   some LPWAN technologies include a reliable way on the compressor, sequence number in L2 to avoid
   duplicate frames.  Therefore if lost the session with LPWAN node
   will message does not need to be lost, which
   acknowledged (NON or RST message), the Message ID field can be
   avoided.  In that case TV is not set, MO is set to ignore and CDF is
   set to "not-sent".  The decompressor can generate a traffic increase number.

   [[Note; check id this field is not used by OSCOAP .]]

   To optimize information sent on the LPWA
   network.

   This function converts a large number to a smaller one and maintain
   bi-directional mapping.  If LPWAN, shorter values may be used
   during the field has no semantic, such as exchange, but Message ID values generated a common CoAP
   token or a message ID, this
   implementation will not take into account this limitation.  Before
   the compression, a proxy may be needed to reduce the size.  In that
   case, the TV is set to 0x0000, MO is set to "MSB(l)" and CDF is set
   to "LSB(16-l)", where "l" is the size of the information
   sent on compressed header.

   Otherwise if no compression is needed the link. TV is not set, MO is set to
   ignore and CDF is set to "not-sent".

4.6.  CoAP Token field

   This mapping only applies for request compression,
   answers must keep field is bi-directional.

   Token is used to identify transactions and varies from one
   transaction to another.  Therefore, it is usually necessary to send
   the value original value.

   For instance a compression receives a of the token field on the LPWAN network.  The optimization
   will occur by using small values.

   Common CoAP request with a implementations may generate large
   token. tokens, even if
   shorter tokens could be used regarding the LPWAN characteristics.  A
   proxy may be needed to reduce the size of the token before
   compression.

   Otherwise the TV is not set, the MO is set to ignore and CDF is set
   to "value-sent".

   The compressor reduces decompression may know the length of the token size by allocating a unused
   value field from the
   token length field.

4.7.  CoAP option Content-format field.

   This field is unidirectional and must not be set to bidirectional in
   a smaller space.  When rule entry.  It is used only by the response come back, server to inform the
   compressor exchange client
   about of the smallest token with payload type and is never found in client requests.

   If the original one.

   This mean value is known by both sides, the TV contains that value and
   MO is set to "equal" and the compressor must CDF is set to "not-sent".

   Otherwise the TV is not set, MO is set to "ignore" and CDF is set to
   "value-sent"

   A mapping list can also be aware of used to reduce the size.

4.8.  CoAP state
   machine, option Accept field

   This field is unidirectional and must not be set to identify bidirectional in
   a request rule entry.  It is used only by the client to inform of the
   possible payload type and its associated response, but also
   determine when is never found in server response.

   The number of accept options is not limited and can vary regarding
   the usage.  To be selected a token rule must contain the exact number about
   accept options with their positions.

   if the accept value can must be reused.

2.2.1.3.  Reduce-entropy

   Reduce-entropy sent, the TV contains that value, MO is
   set to "ignore x" where "x" is the accept option's position and CDF
   is set to value-sent.  Since the value length is not known, it must
   be sent as a non-conservative function. CoAP TLV with delta-T set to 0.

   Otherwise the goal TV is not set, MO is set to
   minimize "equal x" where x is the increase
   accept option's position and CDF is set to "not-sent"

   [[note: it could be more liberal and do not provide the same order
   after decompression]]

4.9.  CoAP option Max-Age field

   This field is unidirectional and must not be set to bidirectional in
   a field value. rule entry.  It may be is used for the
   observe option, all increase in only by the original sequence number will
   lead server to an increase inform of 1 the caching
   duration and is never found in client requests.

   If the compressed value.

   For instance a LPWAN node duration is a CoAP server known by both ends, the TV is set with this
   duration, the MO is set to "equal" and receives Observe
   responses coming from an outside client.  The client uses a clock the CDF is set to
   generate Observe sequence number.  If that value has non particular
   meaning for "not-sent".

   Otherwise the CoAP server, increase of 1 will TV is not change set, the
   protocol behavior.  Reordering works MO is set to "ignore" and the same way CDF is
   set to "value-sent".  Since the value length is not known, it must be
   sent as for original
   Observe.

2.2.2. a CoAP mandatory header

   Figure 2 proposes some function assignments TLV with delta-T set to 0.

   [[note: we can reduce (or create a new option) the unit to minute,
   second is small for LPWAN ]]

4.10.  CoAP header
   fields.

/--------------------+---------------------+----------------------------------------\
| Field              |Function             | Behavior                               |
+--------------------+---------------------+----------------------------------------+
|version             |not-sent             |version option Uri-Host and Uri-Port fields

   This fields are unidirectional and must not be set to bidirectional
   in a rule entry.  They are used only by the client to access to a
   specific server and are never found in server response.

   For each option, if the value is always known by both ends, the same              |
+--------------------+---------------------+----------------------------------------+
|type                |value-sent           |if all TV is set
   with this value, the MO is set to "equal" and the CDF is set to "not-
   sent".

   Otherwise the types TV is not set, the MO is set to "ignore" and the CDF is
   set to "value-sent".  Since the value length is not known, it must be
   sent as a CoAP TLV with delta-T set to 0.

4.11.  CoAP option Uri-Path and Uri-Query fields

   This fields are used               |
|                    |static-mapping       |to reduce unidirectional and must not be set to one bit if 2 type bidirectional
   in a rule entry.  They are used |
|                    |not-sent             |if only one type by the client to access to a
   specific resource and are never found in server response.

   Path and Query option may have different formats.  Section 3.2 gives
   some examples.

   If the URI path as well as the query is used (e.g. NON)     |
+--------------------+---------------------+----------------------------------------+
|token length        |not-sent             |no tokens composed of 2 or fixed size                 |
|                    |compute-token-length |if token size more
   elements, then the position must be set in the MO parameters.

   If a Path or Query element is reduced                |
|                    |value-sent           |token stable over the time, then TV is sent integrally                |
+--------------------+---------------------+----------------------------------------+
|code                |value-sent           |no modification                         |
|                    |static-mapping       |code size reduction                     |
+--------------------+---------------------+----------------------------------------+
|message id          |value-sent           |no modification                         |
|token               |remapping            |reduces message id size                 |
+====================+=====================+========================================+
|Content-Format      |value-sent           |no modification                         |
|Accept              |not-sent             |defined set
   with its value, MO is set to "equal x" where x is the position in the rule                     |
|Max-Age             |static-mapping       |map
   Path or the Query and CDF is set to "not-sent".

   Otherwise if the possible value                  |
+--------------------+---------------------+----------------------------------------+
|Path:               |value-sent           |no modification                         |
|Uri-Host+Uri-Port+  |not-sent             |defined varies over time, TV is not set, MO is set to
   "ignore x" where x is the position in the rule                     |
|Uri-Path*+Uri-Query*|static-mapping       |a Path or in the Query and
   CDF is set to "value-sent".  Since the value length is not known, it
   must be sent as a CoAP TLV with deltaT set to 0.

   A Mapping list can be used to define reduce size of variable Paths or
   Queries.  In that case, to optimize the compression, several elements
   can be regrouped into a single entry.  Numbering of elements do not
   change, MO comparison is set with the first element of the matching.

   For instance, the following Path /foo/bar/variable/stable can leads
   to the rule defined Figure 4.

         FID        TV              MO                   CDF

         URI-Path   {"/foo/bar":1,  match-mapping 1      mapping-sent
                     "/bar/foo":2}
         URI-Path                   ignore 3             value-sent
         URI-Path     stable        equal 4              not-sent

                      Figure 4: complex path                |
|                    |                     |                                        |
|Proxy-Uri           |                     |Note: example

4.12.  CoAP option Proxy-URI and Proxy-Scheme fields

   These fields are unidirectional and must not be set to bidirectional
   in a rule entry.  They are used only by the full path client to access to a
   specific resource and are never found in server response.

   If the field value must be sent, TV is not set, MO is set to "ignore"
   and CDF is set to "value-sent.  A mapping can also be used.

   Otherwise the TV is set to the value, MO is set to "equal" and CDF is
   set to "not-sent"

4.13.  CoAP option ETag, If-Match, If-None-Match, Location-Path and
       Location-Query fields

   These fields are unidirectional.

   These fields values cannot be stored in   |
|Proxy-Scheme        |                     |context                                 |
+--------------------+---------------------+----------------------------------------+
|ETag                |value-sent           |Always a rule entry.  They must
   always be sent                             |
|Location-Path       |                     |                                        |
|Location-Query      |                     |                                        |
|If-Match            |                     |                                        |
|If-None-Match       |                     |                                        |
|Size1               |                     |                                        |
+--------------------+---------------------+----------------------------------------+

           Figure 2: with the request.

   [[Can include OSCOAP Object security in that category ]]

5.  Other RFCs

5.1.  Block

   Block option should be avoided in LPWAN.  The minimum size of 16
   bytes can be incompatible with some LPWAN technologies.

   [[Note: do we recommand LPWAN fragmentation since the smallest value
   of 16 is too big?]]

5.2.  Observe

   [RFC7641] defines the Observe option.  The TV is not set, MO is set
   to "ignore" and the CDF is set to "value-sent".  SCHC functions' example assignment does not limit
   the maximum size for CoAP

2.2.3. this option (3 bytes).  To reduce the
   transmission size either the Thing implementation should limit the
   value increase or a proxy can be used limit the increase.

   Since RST message may be sent to inform a server that the client do
   not require Observe response, a rule must allow the transmission of
   this message.

5.3.  No-Response

   [RFC7967]  defines an No-Response option limiting the responses made
   by a server to a request.  If the value is not by both ends, then TV
   is set to this value, MO is set to "equal" and CDF is set to "not-
   sent".

   Otherwise, if the value is changing over time, TV is not set, MO is
   set to "ignore" and CDF to "value-sent".  A matching list can also be
   used to reduce the size.

6.  Examples of CoAP header compression

2.2.3.1.

6.1.  Mandatory header with CON message

   In this first scenario, the LPWAN compressor receives from outside
   client a POST message, which is immediately acknowledged by the ES.
   Thing.  For this simple scenario, the rules are described Figure 3 5.

    rule id 1
   +-------------+-------+-----+---------------+----------------+
   +-------------+------+---------+-------------+-----+----------------+
   | Field       |TV    |MO       |CDF          |dir  | Sent           |
   +=============+=======+=====+===============+================+
   +=============+======+=========+=============+=====+================+
   |CoAP version | 01    |=   |equal    |not-sent     |bi   |                |
   |CoAP Type    |       |      |ignore   |value-sent   |bi   |TT              |
   |CoAP TKL     | 0000  |= 0    |equal    |not-sent     |bi   |                |
   |CoAP Code    |       |     |static-map ML1  |match-map|matching-sent|bi   |  CC CCC        |
   |CoAP MID     |       |     |dynamic-map 0000 |MSB(7 )  |LSB(9)       |bi   |         M-ID   |
   |CoAP Path    |/path  | Uri-Path| path |equal 1  |not-sent     |down |                |
   +-------------+-------+-----+---------------+----------------+
   +-------------+------+---------+-------------+-----+----------------+

          Figure 3: 5: CoAP Context to compress header without token

   Figure 3 gives a simple compression rule for CoAP headers without
   tokens.

   The version fields and Token Length fields are elided.  Code has shrunk to 5
   bits using the static-mapping function. matching list (as the one given Figure 3: 0.01 is
   value 0x01 and 2.05 is value 0x0c) Message-ID has shrunk to 9 bits to
   preserve alignment on byte boundary.  The most significant bit must
   be set to 0 through a CoAP proxy.  Uri-Path contains a single element
   indicated in the matching operator.

   Figure 4 6 shows the time diagram of the exchange.  A LPWAN Application
   Server sends a CON message.  Compression reduces the header sending
   only the Type, a mapped code and the Message ID is change to a value
   on least 9 bits. significant bits of
   Message ID.  The receiver decompress decompresses the header.  The message ID value
   is changed. .

   The CON message is a request, therefore the LC process to a dynamic
   mapping.  When the ES receives the ACK message, this will not
   initiate locally a the message ID mapping since it is a response.  The LC
   receives the ACK and uncompress uncompressed it to restore the original value.
   Dynamic Mapping context lifetime follows the same rules as message ID
   duration.

                   End System               LPWA LC
                        |                     |
                        |        rule id=1    |<----------------------
                        |<---------------------------|
                        |<--------------------| +-+-+--+----+--------+
  <-------------------- |  TTCC CCCM MMMM MMMM       | MMMM| |1|0| 4|0.01| 0x1234 0x0034 |
 +-+-+--+----+--------+ |  0000 0010 0000 0001       | 0011 0100| |  0xb4   p    a   t |
 |1|0| 1|0.01| 0x0001 0x0034 | |                     | |  h   |
 |  0xb4   p    a   t | |                     | +------+
 |  h   |               |                     |    dynamic mapping
 +------+               |                     |    +--------+--------+
                        |                     |    |0x1234  |  0x01  |
                        |                     |    +--------+--------+
----------------------->|       rule id=1     |
+-+-+--+----+--------+  |--------------------------->|  |-------------------->|
|1|2| 0|2.05| 0x0001 0x0034 |  |  TTCC CCCM MMMM MMMM     |------------------------> MMMM|------------------------>
+-+-+--+----+--------+  |  1001 1000 0000 0000 0001     | 0011 0100| +-+-+--+----+--------+
                        |                     | |1|2| 0|2.05| 0x1234 0x0034 |
                        v                     v +-+-+--+----+--------+

                Figure 4: 6: Compression with global addresses

   Note that the compressor and decompressor must understand the CoAP
   protocol:

   o

   The LC compressor detects a new transport request and allocate a
      new dynamic mapping value.

   o  When receiving a response the ES compressor ES detects that this
      is a response (type=2) therefore the message ID value can be further optimized by setting some fields
   unidirectional, as described in
      unchanged.

   o  The upstream compressor detects Figure 7.  Note that Type is an REST answer (code 2.05)
      therefore no more
   sent in the path option is compressed format, Compressed Code size in not inserted changed in the uncompress header

2.2.3.2.  Exchange with token

   The following scenario introduces tokens.  The LC manages two
   remapping contexts.  One for Message ID and the other for token.  ES
   manages one context for Message ID.  Mapping is trigged by the
   reception of CON messages
   that example (8 values are needed to compress or CoAP code all the requests and 21 to compress.
   Note that
   code all the compressed message ID size has been reduced to 7 bits,
   compared to responses in the previous example, to maintain byte boundary
   alignment.

  +----------------+------------------------+----------------+-----------------+ matching list Figure 3)
    rule id 1
   +-------------+------+---------+-------------+---+----------------+
   | Field          |   Function             | Ctxt Value     |       |TV    |MO       |CDF          |dir| Sent compressed           |
  +----------------+------------------------+----------------+-----------------+
   +=============+======+=========+=============+===+================+
   |CoAP version | not-sent 01   |equal    |not-sent     |bi |                |
   |CoAP Type    | CON  |equal    |not-sent     |dw |                |
   |CoAP Type    | value-sent ACK  |equal    |not-sent     |up |                |TT                |
   |CoAP TKL     | compute-token-length   | 0    |equal    |not-sent     |bi |  LL                |
   |CoAP Code    | map-code ML2  |match-map|matching-sent|dw |CCCC C          | mapping table
   |CoAP Code    |      CCCC ML3  |match-map|matching-sent|up |CCCC C          |
   |CoAP MID     | remapping              | 7 bits 0000 |MSB(5)   |LSB(11)      |bi |       M-ID     |
   |CoAP Token      | remapping              | 8 bits         |            token|
  |CoAP Path Uri-Path| path |equal 1  |not-sent     |dw | not-sent               |/data/humidity                |
  +----------------+------------------------+----------------+-----------------+
   +-------------+------+---------+-------------+---+----------------+

   ML1 = {CON : 0, ACK:1} ML2 = {POST:0, 2.04:1, 0.00:3}

          Figure 5: 7: CoAP Context to compress header with without token
                   End System                      LPWA LC

6.2.  Complete exchange

   In that example, the Thing is using CoMi and sends queries for 2 SID.

     CON
     MID=0x0012     |                         |
     POST           |        SHIM=1              |<----------------------
                        |<---------------------------|   +-+-+--+----+--------+
  <--------------------                         |  TT LL CCCC  C  MMMMMMM
     Accept X       |   |1|0| 4|0.01| 0x1234                         |
 +-+-+--+----+--------+
     /c/k=AS        |------------------------>|
                    |  00 01 0000  1  0000001                         |
                    |      DEADBEEF                         |
 |1|0| 1|0.01| 0x0001
                    |<------------------------|  ACK MID=0x0012
                    |                         |  0000  0001  0.00
                    |                         |  0xb4   d    a   t
                    |                         |  01   0xb4   d   a
                    |<------------------------|   CON
                    |                         |  Token   MID=0X0034
                    |                         |   a     0x08 h   u   Content-Format X
   ACK MID=0x0034   |------------------------>|
   0.00

    rule id 3
   +-------------+------+---------+-------------+---+----------------+
   | Field       |TV    |MO       |CDF          |dir| Sent           |    t   a    0x08 h
   +=============+======+=========+=============+===+================+
   |CoAP version | 01   |equal    |not-sent     |bi |                |
   |CoAP Type    |   m     i    d   i CON  |equal    |not-sent     |up |                |    u   m     i   d
   |CoAP Type    | ACK  |equal    |not-sent     |dw |                |
   |CoAP TKL     |   t     y 1    |equal    |not-sent     |bi |                |    i   t     y
   |CoAP Code    | POST |equal    |not-sent     |up |                |
   |CoAP Code    | 0.00 |equal    |not-sent     |dw |                |
   |CoAP MID     | 0000 |MSB(8)   |LSB(8)       |bi |MMMMMMMM        |   +------------+
 +-----------------+
   |CoAP Token   |      |ignore   |send-value   |up |TTTTTTTT        | Mid mapping: 1234 ->
   |CoAP Uri-Path| /c   |equal 1  |not-sent     |dw |                | Tk  mapping: DEADBEEF ->
   |CoAP Uri-query ML4  |equal 1
----------------------->|       SHIM=1  |not-sent     |dw |P               |
+-+-+--+----+--------+  |--------------------------->|
|1|2| 0|0.00| 0x0001
   |CoAP Content | X    |equal    |not-sent     |up |    TT LL CCCC C MMMMMMMM   |------------------------>
+-+-+--+----+--------+                |    10
   +-------------+------+---------+-------------+---+----------------+

    rule id 4
   +-------------+------+---------+-------------+---+----------------+
   | Field       |TV    |MO       |CDF          |dir| Sent           |
   +=============+======+=========+=============+===+================+
   |CoAP version | 01 0000 0 00000001   |equal    |not-sent     |bi | +-+-+--+----+--------+                |
   |CoAP Type    | |1|2| 0|0.00| 0x1234 CON  |equal    |not-sent     |dw |                |
   |CoAP Type    | +-+-+--+----+--------+
----------------------->| ACK  |equal    |not-sent     |up |
+-+-+--+----+--------+  |--------------------------->|
|1|0| 0|2.05| 0xCAFE                |
   |CoAP TKL     |    TT LL CCCC C MMMMMMMM   |------------------------> 1    |equal    |not-sent     |bi | 0x01    2     5                |
   |CoAP Code    |    00 01 1100 0 00000002 2.05 |equal    |not-sent     |dw | +-+-+--+----+--------+
+--------------------+                |
   |CoAP Code    | 0.00 |equal    |not-sent     |up |                |
   |CoAP MID     | 0000  0001 |MSB(8)   |LSB(8)       |bi |MMMMMMMM        | |1|0| 4|2.05| 0x0001
   |CoAP Token   |      |ignore   |send-value   |dw |TTTTTTTT        |
   |COAP Accept  | X    |equal    |not-sent     |dw |    2 5                |
   +-------------+------+---------+-------------+---+----------------+

   alternative rule:

    rule id 4
   +-------------+------+---------+-------------+---+----------------+
   | Field       |TV    |MO       |CDF          |dir| Sent           |       DEADBEEF
   +=============+======+=========+=============+===+================+
   |CoAP version | 01   |equal    |not-sent     |bi |                |
   |CoAP Type    |    2    5 ML1  |equal    |match-sent(1)|bi |t               |
   |CoAP TKL     |
Mid mapping: CAFE -> 1    |equal    |not-sent     |bi |                | +-----------+
   |CoAP Code    | ML2  |equal    |match-sent(1)|up | cc             |                            |<------------------------
                        |<---------------------------| +-+-+--+----+--------+
<-----------------------|     TT LL CCCC C  MMMMMMMM
   |CoAP Code    | |1|2| 0|0.00|0x0001 ML3  |equal    |match-sent(2)|dw |
+-+-+--+----+--------+ cc             |
   |CoAP MID     |     10 00 0000 0  00000002 |MSB(8)   |LSB(8)       |bi |MMMMMMMM        | +-+-+--+----+--------+
|1|2| 0|0.00| 0xCAFE
   |CoAP Token   |      |ignore   |send-value   |dw |TTTTTTTT        |
   |CoAP Uri-Path| /c   |equal 1  |not-sent     |dw |                |
   |CoAP Uri-query ML4  |equal 1  |not-sent     |dw |P               |
+-+-+--+----+--------+
   |CoAP Content | X    |equal    |not-sent     |up |
                        v                            v

                     Figure 6: Compression with token

3.                |
   |COAP Accept  | x    |equal    |not-sent     |dw |                |
   +-------------+------+---------+-------------+---+----------------+

   ML1 {CON:0, ACK:1} ML2 {POST:0, 0.00: 1} ML3 {2.05:0, 0.00:1}
   ML4 {NULL:0, k=AS:1, K=AZE:2}

7.  Normative References

   [I-D.ietf-core-comi]
              Stok, P., Bierman, A., Veillette, M., and A. Pelov, "CoAP
              Management Interface", draft-ietf-core-comi-00 (work in
              progress), January 2017.

   [I-D.toutain-lpwan-ipv6-static-context-hc]
              Minaburo, A. and L. Toutain, "LPWAN Static Context Header
              Compression (SCHC) for IPv6 and UDP", draft-toutain-lpwan-
              ipv6-static-context-hc-00 (work in progress), September
              2016.

   [RFC1332]  McGregor, G., "The PPP Internet Protocol Control Protocol
              (IPCP)", RFC 1332, DOI 10.17487/RFC1332, May 1992,
              <http://www.rfc-editor.org/info/rfc1332>.

   [RFC3095]  Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,
              Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le,
              K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K.,
              Wiebke, T., Yoshimura, T., and H. Zheng, "RObust Header
              Compression (ROHC): Framework and four profiles: RTP, UDP,
              ESP, and uncompressed", RFC 3095, DOI 10.17487/RFC3095,
              July 2001, <http://www.rfc-editor.org/info/rfc3095>.

   [RFC4944]  Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
              "Transmission of IPv6 Packets over IEEE 802.15.4
              Networks", RFC 4944, DOI 10.17487/RFC4944, September 2007,
              <http://www.rfc-editor.org/info/rfc4944>.

   [RFC4997]  Finking, R. and G. Pelletier, "Formal Notation for RObust
              Header Compression (ROHC-FN)", RFC 4997,
              DOI 10.17487/RFC4997, July 2007,
              <http://www.rfc-editor.org/info/rfc4997>.

   [RFC5225]  Pelletier, G. and K. Sandlund, "RObust Header Compression
              Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and
              UDP-Lite", RFC 5225, DOI 10.17487/RFC5225, April 2008,
              <http://www.rfc-editor.org/info/rfc5225>.

   [RFC6282]  Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
              Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
              DOI 10.17487/RFC6282, September 2011,
              <http://www.rfc-editor.org/info/rfc6282>.

   [RFC7252]  Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014,
              <http://www.rfc-editor.org/info/rfc7252>.

   [RFC7641]  Hartke, K., "Observing Resources in the Constrained
              Application Protocol (CoAP)", RFC 7641,
              DOI 10.17487/RFC7641, September 2015,
              <http://www.rfc-editor.org/info/rfc7641>.

   [RFC7967]  Bhattacharyya, A., Bandyopadhyay, S., Pal, A., and T.
              Bose, "Constrained Application Protocol (CoAP) Option for
              No Server Response", RFC 7967, DOI 10.17487/RFC7967,
              August 2016, <http://www.rfc-editor.org/info/rfc7967>.

Authors' Addresses

   Ana Minaburo
   Acklio
   2bis rue de la Chataigneraie
   35510 Cesson-Sevigne Cedex
   France

   Email: ana@ackl.io

   Laurent Toutain
   Institut MINES TELECOM ; TELECOM Bretagne IMT Atlantique
   2 rue de la Chataigneraie
   CS 17607
   35576 Cesson-Sevigne Cedex
   France

   Email: Laurent.Toutain@telecom-bretagne.eu Laurent.Toutain@imt-atlantique.fr