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

Rodrigo Muñoz <rodrigo.munoz.lara@gmail.com> Mon, 16 September 2019 19:58 UTC

Return-Path: <rodrigo.munoz.lara@gmail.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 DF3D112010C for <lp-wan@ietfa.amsl.com>; Mon, 16 Sep 2019 12:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 S8TvfaaVo-Jn for <lp-wan@ietfa.amsl.com>; Mon, 16 Sep 2019 12:58:57 -0700 (PDT)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AD511200B1 for <lp-wan@ietf.org>; Mon, 16 Sep 2019 12:58:57 -0700 (PDT)
Received: by mail-ua1-x929.google.com with SMTP id i17so303661ual.7 for <lp-wan@ietf.org>; Mon, 16 Sep 2019 12:58:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZY5a9RxjpTz0xSdc+wkqzgZWMw+Y4JiLeih9aTBjrSw=; b=TqJXFsmjtOLDKC8rikSnWo2pYqEGgYlpfM0wpNaCgYsDinLFrWnzTzi75jmH/OuwfI UPE5ADAyjxBP5bNpeYUgWXqrsR3ZzRPbkrBC8yAH8DtWyThQZn/EqgEh3iSHTUFeffhc 3lwKKemEbN78d2/JUthjiImYnkdQwnyxqhtSeaBWGvS+FWtOi57yDw6ABqGSnOJEHtrM BeWEBK4BsSDdC8XVeo2fVREFtcooxrhel1cU3tzkpEAP94G8Q1kB1mwa9FZ/oabMAz19 DeYfb57EIYkCNuDrRYmp9NgAHGmmSTnT/5fi5cXF4eBZo32reR/XJstBIi4YrETbuZ7O EuwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZY5a9RxjpTz0xSdc+wkqzgZWMw+Y4JiLeih9aTBjrSw=; b=ZVwLo2F1C8Tlsm6lZcmfNBIXzgtWYwcBvInq8mY6nN2SLUGDt5Kt3bQTZfOA6/yO6e IC4e8Qt+J4CdVI2+rIWpDowFnz3rnMr8gLczyu1cvBW1+tGrqGcy00vnk5IhCA5TikeB QaG2kHBGwwwWehw8MSt9FVGyfwumPdyVPvd+okEKqxjkKIFTZ7VItmiIs36MwCPprMID Ua7qF/m6yRsGUts82djOXhOA+r0QTGmPYFfqVj06lWAQHCiQXA2DZ7O2grhWcSAttKz8 wnP01kCUkLjGIILxpcIkKk3W25UJKP+nWv4t1rcRB2y7esa9tCcJImw4490Iqj25gekK FaLg==
X-Gm-Message-State: APjAAAVHIEmHWP/bRXW//x4o2iMVWLiWNQ3dTmCF+tN0et8pN9/Wko4E OYJzFNzXepVycWyTKS9vQ8BwJ4ob5sMUjtRzWpw=
X-Google-Smtp-Source: APXvYqwDKGHQRyzIuGIzacLiWKO4jAocpi6A9txN1aHpuioxiw2NcIvdT0mTcUZfV1Lh5obSeJ3vs/0dWA43XkXSodc=
X-Received: by 2002:ab0:748c:: with SMTP id n12mr343986uap.119.1568663935689; Mon, 16 Sep 2019 12:58:55 -0700 (PDT)
MIME-Version: 1.0
References: <CALJ+G3WJxOmNjOz1jOV-G50G5L_bqV3BgHqvwM2VcPEnk4bQ6w@mail.gmail.com> <DBBPR08MB47575AE3E01C023A75C6621C898C0@DBBPR08MB4757.eurprd08.prod.outlook.com>
In-Reply-To: <DBBPR08MB47575AE3E01C023A75C6621C898C0@DBBPR08MB4757.eurprd08.prod.outlook.com>
From: Rodrigo Muñoz <rodrigo.munoz.lara@gmail.com>
Date: Mon, 16 Sep 2019 16:58:44 -0300
Message-ID: <CALJ+G3XgZaV1vHHMZsSRLiZdqd0mYvG0GRP7GCc7yMFSjN4npw@mail.gmail.com>
To: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>
Cc: "lp-wan@ietf.org" <lp-wan@ietf.org>, Sandra Cespedes <scespedes@ing.uchile.cl>
Content-Type: multipart/mixed; boundary="000000000000a91d6b0592b108c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/ucoaQHysFs-6ORoAWD3Ehbzmn1o>
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 19:59:00 -0000

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).

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

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

El lun., 16 sept. 2019 a las 13:06, Juan Carlos Zuniga (<
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> *On Behalf Of *Rodrigo Muñoz
> *Sent:* September 16, 2019 10:42 AM
> *To:* lp-wan@ietf.org
> *Cc:* Sandra Cespedes <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*