Re: [lp-wan] Doub about sending missing tiles

Rodrigo Muñoz Lara <rmunozlara@ing.uchile.cl> Thu, 06 February 2020 01:07 UTC

Return-Path: <rmunozlara@ing.uchile.cl>
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 1F7DF120132 for <lp-wan@ietfa.amsl.com>; Wed, 5 Feb 2020 17:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ing.uchile.cl header.b=j2sod3EL; dkim=pass (1024-bit key) header.d=ing.uchile.cl header.b=j2sod3EL
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 zsiX0HOrvahJ for <lp-wan@ietfa.amsl.com>; Wed, 5 Feb 2020 17:07:35 -0800 (PST)
Received: from mail.cec.uchile.cl (mail2.cec.uchile.cl [200.9.100.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FE2312001B for <lp-wan@ietf.org>; Wed, 5 Feb 2020 17:07:33 -0800 (PST)
Received: from mail.cec.uchile.cl (localhost [127.0.0.1]) by mail.cec.uchile.cl (Postfix) with ESMTP id 4035CA0147 for <lp-wan@ietf.org>; Wed, 5 Feb 2020 22:07:31 -0300 (-03)
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.cec.uchile.cl 4035CA0147
Authentication-Results: mail2.cec.uchile.cl; dmarc=pass (p=none dis=none) header.from=ing.uchile.cl
Authentication-Results: mail2.cec.uchile.cl; spf=pass smtp.mailfrom=rmunozlara@ing.uchile.cl
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.cec.uchile.cl 4035CA0147
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ing.uchile.cl; s=default; t=1580951251; bh=PjeMEWfy9we/7YQ604Jde7MoNTRtPMfYGXeO6oZHDCM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=j2sod3EL7x1vpPb6bm1z/y6tz3ttwjqV+9tDTkZs6ShTRe1XJ+0ENCVtC7oGuoiOv MTc+/6NpgrDaL+E/v1frdsAhgbOq0rvoAyGPCob4xiJBxi68YC1FaHfaqXedaluXO7 O+ng1XcMn6Hf+Vj1kH7RnvJZM4cwCyJxKQflmcUY=
Received: from mail-ua1-f47.google.com (mail-ua1-f47.google.com [209.85.222.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (not verified)) by mail.cec.uchile.cl (Postfix) with ESMTPSA id 893CEA053F for <lp-wan@ietf.org>; Wed, 5 Feb 2020 22:07:30 -0300 (-03)
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.cec.uchile.cl 893CEA053F
Authentication-Results: mail2.cec.uchile.cl; dmarc=pass (p=none dis=none) header.from=ing.uchile.cl
Authentication-Results: mail2.cec.uchile.cl; spf=pass smtp.mailfrom=rmunozlara@ing.uchile.cl
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.cec.uchile.cl 893CEA053F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ing.uchile.cl; s=default; t=1580951251; bh=PjeMEWfy9we/7YQ604Jde7MoNTRtPMfYGXeO6oZHDCM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=j2sod3EL7x1vpPb6bm1z/y6tz3ttwjqV+9tDTkZs6ShTRe1XJ+0ENCVtC7oGuoiOv MTc+/6NpgrDaL+E/v1frdsAhgbOq0rvoAyGPCob4xiJBxi68YC1FaHfaqXedaluXO7 O+ng1XcMn6Hf+Vj1kH7RnvJZM4cwCyJxKQflmcUY=
Received: by mail-ua1-f47.google.com with SMTP id y3so1651710uae.3 for <lp-wan@ietf.org>; Wed, 05 Feb 2020 17:07:30 -0800 (PST)
X-Gm-Message-State: APjAAAXOfOo+N88e/rTUj6UdGfCkkm9ohSYUqJCZ+/f412cfc1X+hJnF 9dC2FeEX7sEyHeSbfOnBUEh/XNkNyUIV3yhL3iw=
X-Google-Smtp-Source: APXvYqwIFL4HGXXfqUPb+7sVqGm7k43jhk1ZlJh7DveG3+aWcRxEl8UPgyZLuFPLfhHLnKVrjVbOWk33hn1cBHU2fCU=
X-Received: by 2002:ab0:133:: with SMTP id 48mr298532uak.38.1580951249047; Wed, 05 Feb 2020 17:07:29 -0800 (PST)
MIME-Version: 1.0
References: <CALJ+G3UODKCPD=JDC0x-0rE663FcJj0P5N3eHCz9m--=jZby-g@mail.gmail.com> <30188_1577726994_5E0A3412_30188_419_1_DA2FF070.6E08D%dominique.barthel@orange.com> <CALJ+G3Xpu+bUVWpLrGu1834Enqy5O2ZKrmNAjzmdEt_W0TRXmg@mail.gmail.com> <32692_1580458505_5E33E209_32692_330_1_DA599B4C.6F996%dominique.barthel@orange.com>
In-Reply-To: <32692_1580458505_5E33E209_32692_330_1_DA599B4C.6F996%dominique.barthel@orange.com>
From: Rodrigo Muñoz Lara <rmunozlara@ing.uchile.cl>
Date: Wed, 05 Feb 2020 22:07:18 -0300
X-Gmail-Original-Message-ID: <CALJ+G3WKGZCpjn+X2AmS_cxEQopyQWofFgeCDvhHWmQC1iK+dw@mail.gmail.com>
Message-ID: <CALJ+G3WKGZCpjn+X2AmS_cxEQopyQWofFgeCDvhHWmQC1iK+dw@mail.gmail.com>
To: dominique.barthel@orange.com
Cc: "lp-wan@ietf.org" <lp-wan@ietf.org>, "ogimenez@semtech.com" <ogimenez@semtech.com>, Sandra Cespedes <scespedes@ing.uchile.cl>
Content-Type: multipart/alternative; boundary="0000000000009b5937059ddde5eb"
X-Virus-Scanned: ClamAV using ClamSMTP
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/1bHnIHnY6Nim0qMZXqm9tLfwo0s>
Subject: Re: [lp-wan] Doub about sending missing tiles
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: Thu, 06 Feb 2020 01:07:39 -0000

Hi Dominique

My answer below:

El vie., 31 ene. 2020 a las 5:15, <dominique.barthel@orange.com> escribió:

> Hello Rodrigo,
>
> Thanks for your questions, they are all good!
>
> > How do I tell the recipient which tiles I am sending in the SCHC
> fragment if the lost tiles are not contiguous?
> A SCHC Fragment can only send contiguous tiles.
>
*[Rodrigo] OK, I understand *

>
> > what happens if the lost tiles are not contiguous? Should the sender
> send them in the same way in a single SCHC fragment?
> If the lost tiles are not all contiguous, you can mix and match between
> the two options below
>
>    - Send one SCHC Fragment per missing tile (or better, per set of
>    contiguous missing tiles) *[Rodrigo] This is the option that I have
>    chosen to implement. Thank you*
>    - Send a SCHC Fragment with contiguous tiles that include the missing
>    ones. Indeed, the specification does not forbid to resend tiles that have
>    already been correctly received (we only say that the missing tiles have to
>    be resent).
>
>
> It's your implementor's freedom to choose a strategy:
>
>    - The simplest algorithm is to send a SCHC Fragment for each missing
>    tile.
>    - An easy improvement to this algorithm is to try to group contiguous
>    missing tiles into one SCHC Fragment, as much as the current MTU allows for.*
>    [Rodrigo] This is the option that I have chosen to implement. Thank you *
>    -  A more complex  algorithm is to evaluate the trade-off between
>    sending SCHC Fragments with only missing tiles, and sending SCHC Fragments
>    that combine missing tiles and correctly received tiles, with the goal of
>    minimising the total overhead (I.e. tradeoff between sending SCHC headers
>    versus resending correctly received tiles).
>
> Your choice!
>
> Best regards
>
> Dominique
>
> De : Rodrigo Muñoz Lara <rmunozlara@ing.uchile.cl>
> Date : Friday 31 January 2020 02:27
> À : Dominique Barthel <dominique.barthel@orange.com>
> Cc : "lp-wan@ietf.org" <lp-wan@ietf.org>, "ogimenez@semtech.com" <
> ogimenez@semtech.com>, Sandra Cespedes <scespedes@ing.uchile.cl>
> Objet : Re: [lp-wan] Doub about sending missing tiles
>
> Hi
>
> Thanks for your answer. Yes, that is the answer to my question.
>
> Related to the same,  I have a new question
>
> The draft indicates that when the sender receives a SCHC ACK with a bitmap
> that indicates lost tiles, the sender must send the lost tiles in a new
> SCHC fragment.
>
> My question is, what happens if the lost tiles are not contiguous? Should
> the sender send them in the same way in a single SCHC fragment? How do I
> tell the recipient which tiles I am sending in the SCHC fragment if the
> lost tiles are not contiguous?
>
> Thanks
>
> El lun., 30 dic. 2019 a las 14:29, <dominique.barthel@orange.com>
> escribió:
>
>> Hello Rodrigo,
>>
>> Thanks for you mail.
>> I'm unsure about what part of the text you actually refer to.
>> Section 8.3.1.2 is about the All-1 Fragment SCHC format
>>
>> https://tools.ietf.org/html/draft-ietf-lpwan-ipv6-static-context-hc-24#section-8.3.1.2
>>
>>
>> From the text you quote, I think you are talking about the Sender
>> Behavior of Ack-on-Error mode (section (8.4.3.1).
>> In this section, we are simply saying that the Sender must resend the
>> missing tiles. It may use several Fragments for this.
>> It does not matter that the tiles are re-send packed the same way in SCHC
>> Fragments as they were packed in the initial transmission.
>> Typically, if the MTU has changed to a lower value since the initial
>> transmission, the retransmitted tiles will have to be packed in a different
>> way (less tiles per SCHC Fragment).
>> Does this answer your question?
>> Best regards, and happy end of year
>>
>> Dominique
>>
>> De : lp-wan <lp-wan-bounces@ietf.org> on behalf of Rodrigo Muñoz Lara <
>> rmunozlara@ing.uchile.cl>
>> Date : Friday 27 December 2019 14:33
>> À : "lp-wan@ietf.org" <lp-wan@ietf.org>
>> Cc : "ogimenez@semtech.com" <ogimenez@semtech.com>, Sandra Cespedes <
>> scespedes@ing.uchile.cl>
>> Objet : [lp-wan] Doub about sending missing tiles
>>
>> Dear Author,
>>
>> I have a question about draft
>> "draft-ietf-lpwan-ipv6-static-context-hc-24". In section 8.3.1.2 say:
>>
>> "*On receiving a SCHC ACK, if the W field in the SCHC ACK not
>> corresponds to the last window of the SCHC Packet:*
>>
>>    -
>>
>>    *MUST send SCHC Fragment messages containing the tiles that reported missing in the SCHC ACK*"
>>
>>
>>
>> What happened if the missing tiles do not fit in a SCHC fragment?
>>
>> Regards
>>
>> _________________________________________________________________________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>>
>> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>