Re: [lp-wan] Fwd: I-D Action: draft-ietf-lpwan-schc-over-nbiot-08.txt

Sergio Aguilar Romero <sergio.aguilar.romero@upc.edu> Fri, 20 May 2022 11:05 UTC

Return-Path: <sergio.aguilar.romero@upc.edu>
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 B55F7C14F744 for <lp-wan@ietfa.amsl.com>; Fri, 20 May 2022 04:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=upc-edu.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eublpIwUWK5W for <lp-wan@ietfa.amsl.com>; Fri, 20 May 2022 04:05:27 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6573DC14F6EB for <lp-wan@ietf.org>; Fri, 20 May 2022 04:05:27 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id h205-20020a1c21d6000000b003972dda143eso722203wmh.3 for <lp-wan@ietf.org>; Fri, 20 May 2022 04:05:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=upc-edu.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:subject:from:in-reply-to:cc :date:message-id:references:to; bh=LJDgGqe1Np9b8l3nUTZe/Q0UJ4UJQt6VG7FoQ7DKCyA=; b=GdFasxX1Pj0jVnSCcM7L6G46J8RV3O5rV6pGnCqXhUg811mYUfhA3NBcgLUIOjjaxG Eek2LsFlx/q9+6aCfy2rWVPoJoRtKnHv4grv6WeAUu/vIt1N2Dnm29M9lbQ4WrTvi7cD jDbNx5qReGCVItzSGE+1Jl8UkwQekuiC2x4gnpAMRVsQjgPrRPNTFKGExg9k576PHFze tQpOMv7eZHLASFGQXhgKrGDvaQKR9HLXDOgqhFCpBTg/drfGKDI6nZO55OxOr4AHnOfl P1f98Te0rR+lCgsGxvlzSBOneTrmLHsZDRx129d8cKUPKcE8X/F6v9HHRE6kY6c0tApY NLSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:cc:date:message-id:references:to; bh=LJDgGqe1Np9b8l3nUTZe/Q0UJ4UJQt6VG7FoQ7DKCyA=; b=3yIefslYF/t3KE+wXapYWk7HjoDBPyOQofhXxlYghxLqgqtYaowtbLioCGIA7Wv0AY v3qIwdOOmS2ar/0mnZaFLpwzkET5RWmYWULUKyX6wwtS+HA1CuRVsrReZJ6lbFWnMYUc F0TjhIVliZq3u41AWuPDDcfKJ0x79ZVApwRY4n6B7XaIe/9roDBfn0mgrQex95Pbn+ko tJi36RtlReNiKVZWOuDIkRf/3JA9+OLhZjY9OcIeuvae97oRAqnXHPaVt9EBXRaR0B02 8VVv+7HH6cpVV9DqMTGUeZeXycPwo5qzirZbI76MkCx9uco/9hcMnjxOeNpnmVUH9/hV bwVg==
X-Gm-Message-State: AOAM531udyzhlCdc4KuhxOWwxo2urKABmejfaKxSW+ToQNXQYHcRWZko ZA4AV3uI4L8aQhLPTKnil/Z/AMG7PL5ofA==
X-Google-Smtp-Source: ABdhPJzajppyFOVivWIhKiQUxTuSArftkR6YNkRu6PdDZKB0MM5Bk5JI71YYhpeFkgd6ZG9njg/B9w==
X-Received: by 2002:a05:600c:3492:b0:397:eea:5a13 with SMTP id a18-20020a05600c349200b003970eea5a13mr7750192wmq.108.1653044725108; Fri, 20 May 2022 04:05:25 -0700 (PDT)
Received: from smtpclient.apple (199.red-79-154-1.dynamicip.rima-tde.net. [79.154.1.199]) by smtp.gmail.com with ESMTPSA id l16-20020a1c7910000000b003972dcfb614sm1792669wme.14.2022.05.20.04.05.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 May 2022 04:05:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Sergio Aguilar Romero <sergio.aguilar.romero@upc.edu>
In-Reply-To: <9d320edc27bb8d07749838c82d1962f7.squirrel@webmail.entel.upc.edu>
Cc: lp-wan <lp-wan@ietf.org>
Date: Fri, 20 May 2022 13:05:23 +0200
Message-Id: <44F2336B-291B-4A10-ADD5-9998D9184F00@upc.edu>
References: <9d320edc27bb8d07749838c82d1962f7.squirrel@webmail.entel.upc.edu>
To: Ana Minaburo <ana@ackl.io>
X-Mailer: iPhone Mail (19E258)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/Ugp5Yfj67s4hGBCcE_W4xlO_2HA>
Subject: Re: [lp-wan] Fwd: I-D Action: draft-ietf-lpwan-schc-over-nbiot-08.txt
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 20 May 2022 11:05:29 -0000

Hello Ana, Edgar, 

I have reviewed the draft and I have the following comments, mostly regarding SCHC Fragmentation.

In section 4.3.2: 

There are two fragmentation modes, No-Ack (for SCHC Packets larger than 1358 bytes) and ACK-on-Error for transfer blocks of up to, and larger than, 300 bits. However, there are no configuration values for No-ACK. 

The tile size is in the order of bits, from 2 bits to 16 bits, to avoid padding in transfer blocks. The recommend values for 300 bit transfer block are M = 1, and N = 3, therefore, 2 windows of 7 tiles, for a total of 14 tiles. Considering a tile of 8 bits, the MAX_SCHC_PACKET is 114 bits, and 224 bits for an 16 bits tile, below the 300 bits. 

For more than 300 bits, and M of 3 bits, i.e., 7 windows, and 7 tiles per windows (N = 3), the MAX_SCHC_PACKET is 392 bits for a tile of 8 bits, and 784 bits for a tile if 16 bits. I wonder if these values are meant to be bytes. Also, if the 7 windows are to have more downlink opportunities i.e., more All-0? 

There no fragment figures, as there is in the LoRaWAN and Sigfox documents. 

From RFC8734 Appendix D, is missing:
- RulesIDs for the different Fragmentation modes.
- WINDOW_SIZE, M and N for No-ACK mode. 
 - How the to differentiate the All-0 from the SCHC ACK REQ, and the All-1 from the Sender-Abort, for ACK-on-Error and No-ACK.
- if the last tile must be in the All-1, or be a L2 word less.
- when to listen to ACKs (not sure if you have to send an uplink message to receive a downlink, if so, appendix F must be taken into account).
- size and method of the RCS.
- recommendation on padding bits value.

Another detail is that the L2 word is defined as 8 bits. In ACK-on-Error, the tile size MUST be at least the size of the L2 word. Therefore, 2 bits and 4 bits are not possibles tile size values. Moreover, tiles sizes are missing for No-ACK mode. 

Note that if the MTU is 1358 bytes, the optimal tile size in terms of ACK size is the largest one, 1357 or 1356 bytes depending on the header size. If fragmentation is required, for example, for a SCHC Packet of 1500 bytes, with a tile of 8 bits, 1500 tiles are required, for a tile of 4 bits, 3000 tiles, and 6000 tiles for 2 bits, without considering the number of windows and M size. The bitmap, in a 1358 bytes MTU, and using compound ACK, can be up to 10000 bits, but the device energy consumption and processing time increases with the number of tiles, at least in my experience, as every tile must be processed before building the SCHC Fragment. Moreover, with a tile of 1356 bytes you need 2 tiles and 1 window. In both cases only two SCHC Fragments are needed.

Let me know if I missed any detail in the document. I can collaborate with fragment figures if needed.

Best regards,

Sergio

> On May 20, 2022, at 7:37 AM, Carles Gomez Montenegro <carlesgo@entel.upc.edu> wrote:
> Hello Ana, Edgar,
> 
> Many thanks for taking my comments into consideration!
> 
> I just have the following remaining comments:
> 
> - Section 4.3 is entitled "End-to-End Compression". However, it also
> defines how to use fragmentation (in 4.3.2), so probably the title should
> be updated.
> 
> - Regarding the fragmentation parameters in 4.3.2, I understand that
> default values for the following parameters would need to be specified as
> well:
> 
>    - MAX_ACK_REQUESTS
> 
>    - WINDOW_SIZE
> 
>    - RCS size
> 
> 
> Thanks,
> 
> Carles
> 
> 
> 
> 
>> Hello,
>> 
>> Here you will find the last version of the draft-SCHC over NBIoT, this
>> version includes the inputs from Carles.
>> Please review the file and send comments.
>> 
>> Thank you for your inputs
>> Ana & Edgar
>> 
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org>
>> Date: Thu, May 19, 2022 at 6:55 PM
>> Subject: [lp-wan] I-D Action: draft-ietf-lpwan-schc-over-nbiot-08.txt
>> To: <i-d-announce@ietf.org>
>> Cc: <lp-wan@ietf.org>
>> 
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the IPv6 over Low Power Wide-Area Networks WG
>> of the IETF.
>> 
>>        Title           : SCHC over NBIoT
>>        Authors         : Edgar Ramos
>>                          Ana Minaburo
>>        Filename        : draft-ietf-lpwan-schc-over-nbiot-08.txt
>>        Pages           : 20
>>        Date            : 2022-05-19
>> 
>> Abstract:
>>   The Static Context Header Compression and Fragmentation (SCHC)
>>   specification describes header compression and fragmentation
>>   functionalities for LPWAN (Low Power Wide Area Networks)
>>   technologies.  The Narrowband Internet of Things (NB-IoT)
>>   architecture may adapt SCHC to improve its capacities.
>> 
>>   This document describes the use of SCHC over the NB-IoT wireless
>>   access and provides use-cases for efficient parameterization.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-lpwan-schc-over-nbiot/
>> 
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-schc-over-nbiot-08
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-schc-over-nbiot-08
>> 
>> 
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>> 
>> 
>> _______________________________________________
>> lp-wan mailing list
>> lp-wan@ietf.org
>> https://www.ietf.org/mailman/listinfo/lp-wan
>> _______________________________________________
>> lp-wan mailing list
>> lp-wan@ietf.org
>> https://www.ietf.org/mailman/listinfo/lp-wan
> 
> 
> _______________________________________________
> lp-wan mailing list
> lp-wan@ietf.org
> https://www.ietf.org/mailman/listinfo/lp-wan