Re: [lp-wan] I-D Action: draft-ietf-lpwan-schc-over-lorawan-05.txt

Olivier Gimenez <ogimenez@semtech.com> Fri, 20 December 2019 15:03 UTC

From: Olivier Gimenez <ogimenez@semtech.com>
To: "lp-wan@ietf.org" <lp-wan@ietf.org>
Thread-Topic: [lp-wan] I-D Action: draft-ietf-lpwan-schc-over-lorawan-05.txt
Thread-Index: AQHVt0SrWMKZBLqpZ0Wzt1Ey5eTT/qfDGvJA
Date: Fri, 20 Dec 2019 15:03:45 +0000
Message-ID: <18f03903e7714d4da38f564b9917e566@semtech.com>
References: <157685332952.4863.6087162830048048288@ietfa.amsl.com>
In-Reply-To: <157685332952.4863.6087162830048048288@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/Cc3VRLEOHe5bFdFgmu18IW9NTlE>
Subject: Re: [lp-wan] I-D Action: draft-ietf-lpwan-schc-over-lorawan-05.txt
Precedence: list

Hi,

I just pushed a new draft revision including the following changelog:

  *  Fix typos and formatting
  *  Add IID proposition
  *  Clarify lot of paragraphs following Dominique review
  *  Update acknowledgements
  *  Change ACK behaviour between each windows to optional for uplink fragmentation


We proposed an algorithm for IID which is close to the discussion we had with Dave Thaler during IETF-106, the idea is to create a hash derived from DevEUI and AppSKey. AppSkey is the only candidate we can find shared by the SCHC gateway and the device, which changes over time (RFC8065), in our case after each join/rejoin. This should also be validated by LoRaWAN security group to know if we can reuse AppSKey for such purpose

There is another proposition based on RFC7217 which the IID is "stable for each subnet": RID = F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key), where Net_Iface can be DevEUI and Network_ID the LoRaWAN netid. 

I prefer the first proposition as it will mitigate correlation over time, the drawback is that we reuse AppSKey for something else than payload LoRaWAN protection.
The second proposition need a way to share the secret_key before communication and using LoRaWAN Netid might be an issue in passive roaming.

Any thoughts or comments ?

Thank you, and merry Christmas !
Olivier

> -----Original Message-----
> From: lp-wan <lp-wan-bounces@ietf.org> On Behalf Of internet-
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 over Low Power Wide-Area Networks WG
> of the IETF.
> 
>         Title           : Static Context Header Compression (SCHC) over LoRaWAN
>         Authors         : Olivier Gimenez
>                           Ivaylo Petrov
>         Filename        : draft-ietf-lpwan-schc-over-lorawan-05.txt
>         Pages           : 24
>         Date            : 2019-12-20
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lpwan-schc-over-lorawan/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-lpwan-schc-over-lorawan-05
> https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-schc-over-lorawan-05
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-schc-over-lorawan-05
> 

To view our privacy policy, including the types of personal information we collect, process and share, and the rights and options you have in this respect, see www.semtech.com/legal.

[lp-wan] I-D Action: draft-ietf-lpwan-schc-over-l… internet-drafts
Re: [lp-wan] I-D Action: draft-ietf-lpwan-schc-ov… Olivier Gimenez