Re: [lp-wan] SCHC over LoRaWAN - IID algorithm

Olivier Gimenez <ogimenez@semtech.com> Tue, 01 December 2020 16:39 UTC

Return-Path: <ogimenez@semtech.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036F73A13B1 for <lp-wan@ietfa.amsl.com>; Tue, 1 Dec 2020 08:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=semtech.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIYoS2LzdqQc for <lp-wan@ietfa.amsl.com>; Tue, 1 Dec 2020 08:39:45 -0800 (PST)
Received: from mail1.bemta24.messagelabs.com (mail1.bemta24.messagelabs.com [67.219.250.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88D503A13C3 for <lp-wan@ietf.org>; Tue, 1 Dec 2020 08:39:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semtech.com; s=k1; t=1606840784; i=@semtech.com; bh=LLp3nISl2T8rgUFGk8Sdim9JCESWBSCY7Wr8zkIsrhI=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=jbWyAaiRcTcsGjfcYAvaGiswO/L0ZAXMe5HEvealSWi6X+YMblXFea5wLvUWjbjPf OPFXSYNfR06w6UMV5FWGhmvrIquKC/mddZc3ta1Db5n6AaSW2QUkKMlaQmaCjKSQYL C95lNS8v4YBDOycSHbh0EOtoA21J43xsdmaDdTQDLXGPNO1PQhYDTVhdcJyPYu/7xd cskPpAaCuhSkkuLi9sgtMcmQhvcxiFThzKBHtxpUPPSU7UJspIJW+fa7NPoO2C8ajl 8R8SOH+Y/huqXORkB0pzY2zCqRi9hOP+MouisOflKJ1IyZgV//qad6h/5SK4o3aCBS 7QoBsJ4q1aLHg==
Received: from [100.112.128.111] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-a.us-west-2.aws.symcld.net id 83/91-03087-FC176CF5; Tue, 01 Dec 2020 16:39:43 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIKsWRWlGSWpSXmKPExsXiofbjse75wmP xBh9nili8mWVvcegSnwOTx4llV1g9liz5yRTAFMWamZeUX5HAmvHkzQeWgv8OFb/PPmJqYGx1 6GLk4hASuM8ocWDJCxYI5zmjxKlVV1khnB2MEjfun2fsYuTkYBPQkfj/fBYriC0ikC3xcOZ+M FtYQE9i1upmJoi4vsTdXx9YIGwriZOPb7CD2CwCKhIztkwGq+EFiq+4dR/MFhLoYZS4f8YJxO YUiJW4cXQDM4jNKCAm8f3UGrAaZgFxiVtP5oPZEgICEkv2nGeGsEUlXj7+B3aohMA0ZomFq+9 BJfgl5h2+zgphK0jMX3EAqJkDaFCiRPtVDogbBCVOznzCAnGDokTrtIXMExjFZiFZNwuhYxaS DoiwpsT6XfoQ1YoSU7ofskPYGhKtc+ayI4svYGRfxWiRVJSZnlGSm5iZo2toYKBraGika2hko WtobqmXWKWbqFdarFueWlyia6SXWF6sV1yZm5yTopeXWrKJERi/KQUNm3cwzn7zQe8QoyQHk5 Io75KIY/FCfEn5KZUZicUZ8UWlOanFhxhlODiUJHhjCoBygkWp6akVaZk5wFQCk5bg4FES4Q0 DphMh3uKCxNzizHSI1ClGb44JL+cuYuY4eHQekPzevBBIfly1BMQGk0fmLl3ELMSSl5+XKiXO uxFkgwDIiIzSPLgFsJR4iVFWSpiXkYGBQYinILUoN7MEVf4VozgHo5IwrxrIFJ7MvBK4O14Bn cgEdKLL58MgJ5YkIqSkGpgU3dpYt8fM+XTr99/iupm/ku/HGcypn1I92/Wa+qdZWw+1fNX6bB Fjt/Obw7oK1d1blEqm3LuyIShJ+GESw3O/xoOvtPWtr3swO+27xPhus4+7IDvzzllvNWUnuhx +FBrh9fr6Y/k79YcWlV7Q1hCat/HXSWfn2mPnf3lo3n5Ta8mmcNB5aciUOetkgzzX/3VJKj9a M0+Byf+u4+bX+a3BZ3591vDYmbrof7KWTNeeKVXf77Q02YgfbAly/Rd4ukPgcsP5BTvr9rgkT om8uyglYakG5+3Wlnvzfvxe91YuR7Txps+5Iymqk7hnfl/v2GF8+2xD61GtBmnfBXwaVSfFem c/dgvieVQbMCEztV5TiaU4I9FQi7moOBEAXQS3GAQEAAA=
X-Env-Sender: ogimenez@semtech.com
X-Msg-Ref: server-32.tower-334.messagelabs.com!1606840781!64418!2
X-Originating-IP: [72.38.248.227]
X-SYMC-ESS-Client-Auth: outbound-route-from=pass
X-StarScan-Received:
X-StarScan-Version: 9.60.3; banners=semtech.com,-,-
X-VirusChecked: Checked
Received: (qmail 26882 invoked from network); 1 Dec 2020 16:39:43 -0000
Received: from s72-38-248-227.static.datacom.cgocable.net (HELO ca01exedge1.semnet.dom) (72.38.248.227) by server-32.tower-334.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 1 Dec 2020 16:39:43 -0000
Received: from ca01mail2.semnet.dom (10.2.50.41) by ca01exedge1.semnet.dom (10.2.110.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1034.26; Tue, 1 Dec 2020 11:39:30 -0500
Received: from ca01mail2.semnet.dom (10.2.50.41) by ca01mail2.semnet.dom (10.2.50.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.26; Tue, 1 Dec 2020 11:39:40 -0500
Received: from ca01mail2.semnet.dom ([fe80::fdc8:c457:b09e:605d]) by ca01mail2.semnet.dom ([fe80::fdc8:c457:b09e:605d%22]) with mapi id 15.01.1034.026; Tue, 1 Dec 2020 11:39:40 -0500
From: Olivier Gimenez <ogimenez@semtech.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, "lp-wan@ietf.org" <lp-wan@ietf.org>
Thread-Topic: SCHC over LoRaWAN - IID algorithm
Thread-Index: AdbCbQjzz9SvL3/8RLugAyz6ft4oqAAAHb+QAWSg+fA=
Date: Tue, 01 Dec 2020 16:39:39 +0000
Message-ID: <906acd2692884ca6804d872f2b7d0495@semtech.com>
References: <a44b76924f8347bbb4e55c95a1ba7009@semtech.com> <CO1PR11MB48810E05F29AC3E7B0503BC2D8FB0@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB48810E05F29AC3E7B0503BC2D8FB0@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXG9naW1lbmV6XGFwcGRhdGFccm9hbWluZ1wwOWQ4NDliNi0zMmQzLTRhNDAtODVlZS02Yjg0YmEyOWUzNWJcbXNnc1xtc2ctY2MwNTQ3NWUtMzNmMy0xMWViLWI3NzQtYzg1Yjc2MWM1MDU3XGFtZS10ZXN0XGNjMDU0NzYwLTMzZjMtMTFlYi1iNzc0LWM4NWI3NjFjNTA1N2JvZHkuaHRtbCIgc3o9IjQ5MjUiIHQ9IjEzMjUxMzE0Mzc2ODE1OTYzMSIgaD0iVnJ2azRwVWFkMlh2NnduRTZNZWU1ZndrZm9ZPSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
x-dg-rorf: true
x-originating-ip: [10.136.88.44]
Content-Type: multipart/alternative; boundary="_000_906acd2692884ca6804d872f2b7d0495semtechcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/q3G0LD6JqfhQyx0H2PEw5bQbolE>
Subject: Re: [lp-wan] SCHC over LoRaWAN - IID algorithm
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 16:39:47 -0000

Thank you Pascal,

So I propose:
Note: Implementation also using another IID source MUST ensure that the same IID is shared between the device and the SCHC gateway.

Is it better ?

Olivier

From: lp-wan <lp-wan-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: 24 November 2020 15:28
To: Olivier Gimenez <ogimenez@semtech.com>; lp-wan@ietf.org
Subject: Re: [lp-wan] SCHC over LoRaWAN - IID algorithm

Hello Olivier




“

Note: Implementation also using another IID source MUST have same IID value on both device and SCHC gateway.
"

I agree with the intention. Now; this formulation could be read as “the GW and the device have the same IID” while you mean that “the GW and the device must obtain the same value as IID of the device”.

Keep safe;

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.