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

<dominique.barthel@orange.com> Mon, 30 December 2019 17:29 UTC

Return-Path: <dominique.barthel@orange.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 2203A120B43 for <lp-wan@ietfa.amsl.com>; Mon, 30 Dec 2019 09:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 R8LBe5HDzJ_p for <lp-wan@ietfa.amsl.com>; Mon, 30 Dec 2019 09:29:56 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B394120B42 for <lp-wan@ietf.org>; Mon, 30 Dec 2019 09:29:56 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 47mkvk2qWHz109H; Mon, 30 Dec 2019 18:29:54 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.98]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 47mkvk255mzyPk; Mon, 30 Dec 2019 18:29:54 +0100 (CET)
Received: from OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905]) by OPEXCAUBM7F.corporate.adroot.infra.ftgroup ([fe80::d9:d3cd:85bd:d331%21]) with mapi id 14.03.0468.000; Mon, 30 Dec 2019 18:29:54 +0100
From: dominique.barthel@orange.com
To: Rodrigo Muñoz Lara <rmunozlara@ing.uchile.cl>, "lp-wan@ietf.org" <lp-wan@ietf.org>
CC: "ogimenez@semtech.com" <ogimenez@semtech.com>, Sandra Cespedes <scespedes@ing.uchile.cl>
Thread-Topic: [lp-wan] Doub about sending missing tiles
Thread-Index: AQHVvLpcCfBOkyHPakOawno2+LUsqafS9AaA
Date: Mon, 30 Dec 2019 17:29:53 +0000
Message-ID: <30188_1577726994_5E0A3412_30188_419_1_DA2FF070.6E08D%dominique.barthel@orange.com>
References: <CALJ+G3UODKCPD=JDC0x-0rE663FcJj0P5N3eHCz9m--=jZby-g@mail.gmail.com>
In-Reply-To: <CALJ+G3UODKCPD=JDC0x-0rE663FcJj0P5N3eHCz9m--=jZby-g@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.3.170325
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_DA2FF0706E08Ddominiquebarthelorangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/rvapu9Thk2LMwmsQkZGMsIySOzM>
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: Mon, 30 Dec 2019 17:29:58 -0000

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<mailto:lp-wan-bounces@ietf.org>> on behalf of Rodrigo Muñoz Lara <rmunozlara@ing.uchile.cl<mailto:rmunozlara@ing.uchile.cl>>
Date : Friday 27 December 2019 14:33
À : "lp-wan@ietf.org<mailto:lp-wan@ietf.org>" <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>
Cc : "ogimenez@semtech.com<mailto:ogimenez@semtech.com>" <ogimenez@semtech.com<mailto:ogimenez@semtech.com>>, Sandra Cespedes <scespedes@ing.uchile.cl<mailto: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.