Re: [lp-wan] Flow validation in ACK-on-error Mode

Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com> Mon, 16 September 2019 23:13 UTC

Return-Path: <juancarlos.zuniga@sigfox.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 503061200DF for <lp-wan@ietfa.amsl.com>; Mon, 16 Sep 2019 16:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sigfoxgroup.onmicrosoft.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 ebmZMFmzII6k for <lp-wan@ietfa.amsl.com>; Mon, 16 Sep 2019 16:13:14 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130113.outbound.protection.outlook.com [40.107.13.113]) (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 A432612006D for <lp-wan@ietf.org>; Mon, 16 Sep 2019 16:13:13 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Vs9gZQbkf68OYyQ2Hc+IKDx0kjFREWMiS04IQIawQwmk3FBU0LfsHPeRVgPgkPrvV6uDvvkcqm8uVtcyNlkpwiYeQNXKdkGShtJhAL4xFnMF4HRpawdqu8s6XqCWssHXq/oT/qsOT72nD2Dqi8+kzNHnuVQ+zt0FfhjAssPXkTbJFACX1QYIwNj2Ya5GWNAgsLhv2SF85SWj7zPnoRMiIv1dh8tUNJOBrDYLn75WSFeQOuFVurkHJfjWT2Kgg0KKtnFyYlbvz5uZvuAXmuPPZi8hvAu2RfiPp5dEq+SM/bUZqKnMK8BdOLVszowGle9e3SnFt+syhnggNOPzUfn6eA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RSsTAGyQ0/wO6xqjP5/yrnEiAm6BZJLNZSZWY+iX/8M=; b=RI6gWJ234PHqsjOnCLDbGQxkxyhAjTRCKS2i9cKphT9nc0V4NdcOulliSMCl5UnJOpiIPYgo6hRQuCVhYskB3d9aGJa8z+dMfhxvMPwtfCJA6rKWA5qmW5CDk1+znaQ1DlSX9N8+VMiN28fq2zIsflXZ4vjf6tDnkp5Eke5YcN+9ilD8rMnK+YBP8C3AtYPpzcOgoyF/65eaU22VJ9dVOqGgC0croZu1t+BWU2Z9cMGdemp1QjOPmfx0podbqS4tAiHDGvV6p9UQdBi8n+XSOLxY9Bsxm3Z39iDRGWJOtiTvzZo3VR+ueTX69aD9tO2s1LtvkDh7XlBFhntOk2ZPKg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sigfox.com; dmarc=pass action=none header.from=sigfox.com; dkim=pass header.d=sigfox.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigfoxgroup.onmicrosoft.com; s=selector2-sigfoxgroup-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RSsTAGyQ0/wO6xqjP5/yrnEiAm6BZJLNZSZWY+iX/8M=; b=UyDx9GPYnkm/WjgagrZe4zphTxVJGptzJhodxos+6a4wWyWElmMJI0ihJd9mw26Z0jDxT66pzPqxs2x9hccTlG2SaEmLyN/YonFtl1qFKETQvHBVflj/WiZae+eaK96ZcU4YG7kEzVtho3fOt1vshe5TN9IsiiM08PNscThuCYM=
Received: from DBBPR08MB4757.eurprd08.prod.outlook.com (10.255.78.84) by DBBPR08MB4918.eurprd08.prod.outlook.com (20.179.47.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.15; Mon, 16 Sep 2019 23:13:10 +0000
Received: from DBBPR08MB4757.eurprd08.prod.outlook.com ([fe80::385c:657:199c:5c6c]) by DBBPR08MB4757.eurprd08.prod.outlook.com ([fe80::385c:657:199c:5c6c%5]) with mapi id 15.20.2263.023; Mon, 16 Sep 2019 23:13:10 +0000
From: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>
To: Rodrigo Muñoz <rodrigo.munoz.lara@gmail.com>
CC: "lp-wan@ietf.org" <lp-wan@ietf.org>, Sandra Cespedes <scespedes@ing.uchile.cl>
Thread-Topic: [lp-wan] Flow validation in ACK-on-error Mode
Thread-Index: AQHVbJ0ITncwJ9Mfvk+uOsMiU4n7MqcuczkAgABF1gCAADCB0A==
Date: Mon, 16 Sep 2019 23:13:10 +0000
Message-ID: <DBBPR08MB47577AE9F13E27540B081351898C0@DBBPR08MB4757.eurprd08.prod.outlook.com>
References: <CALJ+G3WJxOmNjOz1jOV-G50G5L_bqV3BgHqvwM2VcPEnk4bQ6w@mail.gmail.com> <DBBPR08MB47575AE3E01C023A75C6621C898C0@DBBPR08MB4757.eurprd08.prod.outlook.com> <CALJ+G3XgZaV1vHHMZsSRLiZdqd0mYvG0GRP7GCc7yMFSjN4npw@mail.gmail.com>
In-Reply-To: <CALJ+G3XgZaV1vHHMZsSRLiZdqd0mYvG0GRP7GCc7yMFSjN4npw@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=juancarlos.zuniga@sigfox.com;
x-originating-ip: [104.163.146.28]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 899079b7-6a9a-4a88-01e3-08d73afb713f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DBBPR08MB4918;
x-ms-traffictypediagnostic: DBBPR08MB4918:
x-microsoft-antispam-prvs: <DBBPR08MB4918BF35E741C0962E31B673898C0@DBBPR08MB4918.eurprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0162ACCC24
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(39850400004)(136003)(346002)(376002)(366004)(53484002)(189003)(199004)(469094003)(5660300002)(66574012)(7696005)(2906002)(486006)(74316002)(9686003)(66946007)(52536014)(236005)(64756008)(66476007)(66556008)(5024004)(76176011)(81156014)(8676002)(6436002)(76116006)(66446008)(33656002)(14454004)(478600001)(86362001)(229853002)(446003)(11346002)(81166006)(9326002)(476003)(6916009)(71200400001)(25786009)(3846002)(790700001)(8936002)(14444005)(6246003)(6116002)(256004)(55016002)(6306002)(54906003)(54896002)(102836004)(66066001)(7736002)(26005)(6506007)(53546011)(186003)(316002)(99286004)(4326008)(71190400001); DIR:OUT; SFP:1102; SCL:1; SRVR:DBBPR08MB4918; H:DBBPR08MB4757.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: sigfox.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: eTwf9u9Zxa+vTzs9W/Ef4uW2Mv4uHC5KY3zheLx5QtfECSsEPwxNSZsnHJ3hfXCp8x+ULEad4WgMWn4iweMStsDM33Ues1VPMGRBSkVPFTCJmAotYyCuK550BR7SoqMJXO+0MDEE2FIlrKDQOL/G1Sy0qjZgP2cccfoACSekSUnNzAqq5EFTqgsws1IoYF7gpEvra82hURakrwiTx+4xW5b/R9IySWWmUf03+z4+P34OYsn2xLQWDuCgV3gHcs26GZRE8H1ednprM+EDIOpVu+n4/luu+xAg4rEOhyBU+BGodhEoxejC6LbWqFJUsDToHhFuF2nL4zbJc3cbxb+BTa7sd27i0buIWQv3JyTAjmRomGKZ2hQevmXC4YkS7amDr+Q+BR/5nBjNDBhQzpleqHQD4V5KNGtYN7rQTKy5vV4=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DBBPR08MB47577AE9F13E27540B081351898C0DBBPR08MB4757eurp_"
MIME-Version: 1.0
X-OriginatorOrg: sigfox.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 899079b7-6a9a-4a88-01e3-08d73afb713f
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Sep 2019 23:13:10.6112 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fcbc8bb1-061e-4b94-9f70-3ad917b0c8d3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 382ckQsryyVvNVtDug0coGmmDsl50OCD3q4SdudXeEXa3Zi5LizHpPYL/wJFTY6CWT1heZSa6mixeBV2c9+8AKGe3BHaDzQ4b5O1hvocjd8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBBPR08MB4918
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/l0M5Oz5enFECEOcDG1L3njwhAo0>
Subject: Re: [lp-wan] Flow validation in ACK-on-error Mode
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: Mon, 16 Sep 2019 23:13:17 -0000

Hi Rodrigo,

From: Rodrigo Muñoz <rodrigo.munoz.lara@gmail.com>
Sent: September 16, 2019 3:59 PM
To: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>
Cc: lp-wan@ietf.org; Sandra Cespedes <scespedes@ing.uchile.cl>
Subject: Re: [lp-wan] Flow validation in ACK-on-error Mode

Thanks Juan Carlos for your response.

My comments below:

In your flow, you are showing a “Retransmission Timer” time between the retransmitted Reg Frag 1 and the All-1.
[Rodrigo]: Yes. This timer is definided in draft-petrov-lpwan-ipv6-schc-over-lorawan document. In the 5.5.1 said: "If this ACK is not received the end-device sends an all-0 (or an all-1) fragment with no payload to request an SCHC ACK retransmission. The periodicity between retransmission of the all-0/all-1 fragments is device/application specific and may be different for each device (not specified).

[JCZ] Ok, I thought you were referring your question to the authors of the baseline LPWAN SCHC specification (draft-ietf-lpwan-ipv6-static-context-hc), which allows several implementations for different radio technologies. The answer I gave you was with different implementation in mind (e.g. Sigfox), in which you don’t have to wait for a retransmission timer to continue transmitting your other fragments after retransmitting the missing one. If draft-petrov defines it differently I would let the authors of that draft comment (BTW, the draft has been replaced by draft-ietf-lpwan-schc-over-lorawan).


If the All-1 is the fragment that would have normally followed Reg Frag 4, there is no need for the sender to wait between retransmitting Reg Frag 4 and the All-1.
[Rodrigo]: I don't understand this. Could you explain it in more detail please? Remember that in my diagram, fragment 1 is lost, but fragments 2, 3 and 4 correctly reach the receiver. In addition, I assume that these fragments are not in the last window, therefore an All-1 SCHC message should not be sent

[JCZ] Do you mean that there are other fragments after 4 that are not depicted, or that the All-1 is transmitted alone in the last window? Perhaps explaining this would help the discussion.

This All-1 would trigger again the receiver to send a SCHC ACK, which would notify the sender of the correct (or not) reception of all the previous fragments.
[rodrigo]: Yes, I also agree with you

The problem is: what happens when the sender relays the Frag 1 message and this message is lost. Neither the sender nor the receiver have timers to start retransmissions again, or do they have them?

I corrected the diagram to give more clarity

[JCZ] Again, in the implementation that I have in mind the transmitter would send the missing fragment followed by the next not-yet-transmitted fragments in the same window. I would let Ivo et al. comment about the implementation they propose in their draft.

Best, Juan Carlos


El lun., 16 sept. 2019 a las 13:06, Juan Carlos Zuniga (<juancarlos.zuniga@sigfox.com<mailto:juancarlos.zuniga@sigfox.com>>) escribió:
Hello Rodrigo,

Thanks for your enquiry.

In your flow, you are showing a “Retransmission Timer” time between the retransmitted Reg Frag 1 and the All-1.

If the All-1 is the fragment that would have normally followed Reg Frag 4, there is no need for the sender to wait between retransmitting Reg Frag 4 and the All-1.

This All-1 would trigger again the receiver to send a SCHC ACK, which would notify the sender of the correct (or not) reception of all the previous fragments.

I hope this helps.

Best,

Juan Carlos

From: lp-wan <lp-wan-bounces@ietf.org<mailto:lp-wan-bounces@ietf.org>> On Behalf Of Rodrigo Muñoz
Sent: September 16, 2019 10:42 AM
To: lp-wan@ietf.org<mailto:lp-wan@ietf.org>
Cc: Sandra Cespedes <scespedes@ing.uchile.cl<mailto:scespedes@ing.uchile.cl>>
Subject: [lp-wan] Flow validation in ACK-on-error Mode

Dear Author,

I am working on the implementation of the SCHC standard for Sigfox and LoRaWAN. I have the following doubt regarding the data flow when there is a failure in the transmission of a SCHC fragment in the ACK-on-error Mode.

In this email, I attach my draft compression. Is this flow ok?

I have assumed the following:

  *   The SCHC Ack is sent immediately by the receiver at the end of the window.
Regards
--
-------------------------------------------
Rodrigo Muñoz Lara


--
-------------------------------------------
Rodrigo Muñoz Lara