Re: [lp-wan] Martin Duke's No Objection on draft-ietf-lpwan-schc-over-lorawan-12: (with COMMENT)

Olivier Gimenez <ogimenez@semtech.com> Wed, 28 October 2020 14:32 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 3CC463A09C5; Wed, 28 Oct 2020 07:32:40 -0700 (PDT)
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_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 3Q_xo9Tfs5NB; Wed, 28 Oct 2020 07:32:38 -0700 (PDT)
Received: from mail1.bemta23.messagelabs.com (mail1.bemta23.messagelabs.com [67.219.246.114]) (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 57A893A09C3; Wed, 28 Oct 2020 07:32:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semtech.com; s=k1; t=1603895551; i=@semtech.com; bh=vDSTN9WEvmsxpmvC/8zh67dHoXriZiKH7lRrikXmd8I=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=ZkKuZLNLWoCXqXIApuzcCfiyhXuBzGOc49eTN6N8hejyXr0Cgg9jeoVZgOZVXqPyu PnE2aZJlFU5BCUdg00KFRq3t2jLT7JA4tQsn6TplKhZaheUVgr6Kf/aScDJ73jk0s0 guUEB3zhs3P86yf6t7KTBqU+eVPwSE8RnBAN4LqUBM09G9AkGjmPdPqAZHzjBmQ0KO k949vvg1nUxPNVlpXTO+GDKJFp/lX+2drSIDwfRYlreFhiKAq2KOoaH46oBlmJYr8P 1Z7nuz6DW/7kbwhwAgfGwMA8OhS/L5bdoJ3GIavQXVV8vmCkggDMAmGJo5xPof+wya HPHJac1+tdvPA==
Received: from [100.112.7.19] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-3.bemta.az-c.us-east-1.aws.symcld.net id 23/9E-08584-FF0899F5; Wed, 28 Oct 2020 14:32:31 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHJsWRWlGSWpSXmKPExsXiofbjse6/hpn xBh2vNCymdP9ktHi98hijxYw/E5kt3syyt3hzdB6LxfTHL9gc2Dx2zrrL7rFkyU8mj5ZnJ9kC mKNYM/OS8isSWDO+zD7KUjChlbGi9ewJlgbGpc2MXYxcHEICDxglljR/Z4NwXjBKLLu2mBnC2 ckoMffCA6YuRk4ONgEdif/PZ7GC2CICzhIbVl4CK2IWeMMocentKRaQhLBAosSepU+ZIYqSJJ 5MOQq0gwPINpI480YRJMwioCpx8OQFdhCbV8BKYue/R4wgthDQzHVX74KVcwq4SDQs8AAJMwq ISXw/tQbsBGYBcYlbT+aD2RICAhJL9pxnhrBFJV4+/scKco6EwDRmicuHXkEl+CXmHb7OCmEr SLStOM4OMShRovHIXRaIGwQlTs58wgJxg6JE67SFzBMYxWch2TcLScssJC2zgE5lFtCUWL9LH 6JEUWJK90N2CFtDonXOXHZk8QWM7KsYzZKKMtMzSnITM3N0DQ0MdA0NjXRNdQ3NTPQSq3ST9U qLdVMTi0t0DfUSy4v1iitzk3NS9PJSSzYxApNBSgHrkh2M31990DvEKMnBpCTKe45pZrwQX1J +SmVGYnFGfFFpTmrxIUYZDg4lCV4mYHoREixKTU+tSMvMASYmmLQEB4+SCG9OHVCat7ggMbc4 Mx0idYoxkGPCy7mLmDkOHp0HJN/9XAwkP65aAiS/g8nNc5cCySMgUoglLz8vVUqc93E90CABk EEZpXlwa2DJ9hKjrJQwLyMDA4MQT0FqUW5mCar8K0ZxDkYlYd5zIFN4MvNK4K55BXQoE8ihuT NADi1JREhJNTAtPzxpbipzyrIOT8OApyE6ztfabr/1Waujb/TSe2bn2xcVsjzd2/dk7D4yO3S azcngXftbPuy/ntbzYPMEx7VNi97cTyg/pqttu6xsa9/xSKP4jqvGVwpKN3tOdKyTj6icxreX 44P8E5kDNUrFL+qDj//6HvmtrsFISTDFf+MJDcmpxyvqHlg8enA49eHaaQV1XxISMte+/z778 56o9wuqji9fv+9SXbDxoTt7F3fddJr0bJq1wuIHP3++fH8zeO1Jlj1i/xYZX5FWFX45nSnKef eHTc8bbmud9I6SFbp3atfFU+cuBt84sZpzz5MtKbMK/V8w3W3hc9N4pTjj9JzHq20fMgVdUnx 0oIpLUnjK9zAlluKMREMt5qLiRAC9kDGwMQQAAA==
X-Env-Sender: ogimenez@semtech.com
X-Msg-Ref: server-2.tower-414.messagelabs.com!1603895550!780065!1
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 3371 invoked from network); 28 Oct 2020 14:32:30 -0000
Received: from s72-38-248-227.static.datacom.cgocable.net (HELO ca01exedge1.semnet.dom) (72.38.248.227) by server-2.tower-414.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 28 Oct 2020 14:32:30 -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; Wed, 28 Oct 2020 10:31:51 -0400
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; Wed, 28 Oct 2020 10:32:28 -0400
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; Wed, 28 Oct 2020 10:32:28 -0400
From: Olivier Gimenez <ogimenez@semtech.com>
To: Martin Duke <martin.h.duke@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-lpwan-schc-over-lorawan@ietf.org" <draft-ietf-lpwan-schc-over-lorawan@ietf.org>, "lpwan-chairs@ietf.org" <lpwan-chairs@ietf.org>, "lp-wan@ietf.org" <lp-wan@ietf.org>, Dominique Barthel <dominique.barthel@orange.com>
Thread-Topic: Martin Duke's No Objection on draft-ietf-lpwan-schc-over-lorawan-12: (with COMMENT)
Thread-Index: AQHWq//6vp/mBkYzX06X6JpjPgzle6mtCozQ
Date: Wed, 28 Oct 2020 14:32:28 +0000
Message-ID: <e6d4f7d7d2a04b01bd96bc25f477f94b@semtech.com>
References: <160376189066.29116.7355217653650345123@ietfa.amsl.com>
In-Reply-To: <160376189066.29116.7355217653650345123@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXG9naW1lbmV6XGFwcGRhdGFccm9hbWluZ1wwOWQ4NDliNi0zMmQzLTRhNDAtODVlZS02Yjg0YmEyOWUzNWJcbXNnc1xtc2ctNjYxZmVkN2EtMTkyYS0xMWViLWI3NGQtYzg1Yjc2MWM1MDU3XGFtZS10ZXN0XDY2MWZlZDdiLTE5MmEtMTFlYi1iNzRkLWM4NWI3NjFjNTA1N2JvZHkuaHRtbCIgc3o9Ijg1NTciIHQ9IjEzMjQ4MzY5MTQ2ODQ0OTE4NSIgaD0iOGxsUVE3YVNDWjNLQ3ZoSFhNZTFFVzg1d0t3PSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
x-dg-rorf: true
x-originating-ip: [10.136.89.34]
Content-Type: multipart/alternative; boundary="_000_e6d4f7d7d2a04b01bd96bc25f477f94bsemtechcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/ofsAeOZvXXUiD8dwa2NQFm9trOM>
Subject: Re: [lp-wan] Martin Duke's No Objection on draft-ietf-lpwan-schc-over-lorawan-12: (with COMMENT)
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: Wed, 28 Oct 2020 14:32:41 -0000

Dear Martin,



Thank you for your feedback, I answered inline to your comments



Best regards

Olivier



> -----Original Message-----

> From: Martin Duke via Datatracker <noreply@ietf.org>

>

>

> ----------------------------------------------------------------------

> COMMENT:

> ----------------------------------------------------------------------

>

> I found this document to be very tough going without reading through RFC8724.

>

> - I am not sure what Fig. 5 depicts. Does this mean that an "SCHC Packet" is a

> subset of an "SCHC Message", prepended by the Fport and LoRaWan payload?

> Because Fig. 4 of RFC 8724 says an "SCHC Packet" consists of a "Payload"

> prepended by the Rule ID (which corresponds to the FPort) and "Compression

> Residue". Please align the terminology!



[OG] Thank you for this cath. Figure 5 title and its introduction should be SCHC Packet instead of SCHC Message.

I also described what is composing the "LoRaWAN payload". Commit 78ee6f8<https://github.com/Acklio/schc-over-lorawan/commit/78ee6f83dd646bc19d4224494d92e500254ae21e>



> - There are numerous terms from 8724 that could use a brief definition here on

> first use: for example RuleID, MSB, RX1, RX2, and IID.



[OG] RuleID and IID: I have been asked to remove terminology present in RFC8724 from the SCHC over LoRaWAN draft.

Nevertheless I added, MSB, RX, RX1/RX2 in commit  eadd014<https://github.com/Acklio/schc-over-lorawan/commit/eadd014d96c476d1842954e3d75243c797bd8258>





> - Sec 5.6.2:

>    For battery powered devices, it is RECOMMENDED to use the ACK

>    mechanism at the end of each window instead of waiting until the end

>    of all windows...

>

>    For non-battery powered devices, the SCHC receiver MAY also choose to

>    send a SCHC ACK only at the end of all windows.  This will reduce

>    downlink load on the LoRaWAN network, by reducing the number of

>    downlinks.

>

> This text is ambiguous. For example, the first paragraph can be interpreted as

> "battery-powered devices SHOULD send an ACK at the end of each window,

> instead of waiting till the end of all windows", or "endpoints sending to battery-

> powered devices SHOULD send an ACK at the end of each window...."



[OG] We are in the section " Uplink fragmentation: From device to SCHC gateway"  where introduction define:

"the device is the fragment transmitter, and the SCHC gateway the fragment receiver"

so it cannot be "endpoints sending to battery-powered devices"



> To the

> layman, it is a little odd that the non-battery-powered devices are more

> encouraged to send fewer messages! Some explanatory text would be useful.



[OG] Ok, I explained it in commit bfe0c82<https://github.com/Acklio/schc-over-lorawan/commit/bfe0c82ea2be008076bb1ed126412784714bdbe7>: "This will avoid useless uplinks if the device has lost network coverage."





> - Sec 5.6.5.3.1

> "All fragments but the last have an FCN=0

>    (because window size is 1).  Following it, the device MUST transmit

>    the SCHC ACK message."

>

> What is "it"? All fragments, or the FCN=1 fragment?



[OG] The All-0 SCHC Fragment (ie FCN=0). Changed in commit 81a9b24<https://github.com/Acklio/schc-over-lorawan/commit/81a9b24888b7d94c848aef88d030ea9e6d0b4fb6>





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.