Re: [lp-wan] re-order header field request

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Wed, 21 June 2017 09:56 UTC

Return-Path: <carlesgo@entel.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 5BD50131CE3 for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 02:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 OuBpK-nAkoqW for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 02:56:00 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (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 AE326131C3A for <lp-wan@ietf.org>; Wed, 21 Jun 2017 02:55:59 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v5L9tt4S060104; Wed, 21 Jun 2017 11:55:55 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id A4BF51D53C1; Wed, 21 Jun 2017 11:55:54 +0200 (CEST)
Received: from 147.83.113.31 by webmail.entel.upc.edu with HTTP; Wed, 21 Jun 2017 11:55:25 +0200
Message-ID: <86fcc1550858ed0ceef59727db24cd24.squirrel@webmail.entel.upc.edu>
In-Reply-To: <CABONVQaZMv6NiUNB1FFToQgdbU4qXpyz1mX-J0+xk9mvB+tjqA@mail.gmail.com>
References: <386f3ac3-cc15-3fe7-8a7e-04d5be66c0ce@ackl.io> <ec067ef04c60b3fa38ea4887aa455314.squirrel@webmail.entel.upc.edu> <b1ae6a91-b3a3-6197-2648-d9001a9eff1e@ackl.io> <8dd1a778fe41fe8b6ce97cad2b43d62b.squirrel@webmail.entel.upc.edu> <CABONVQaZMv6NiUNB1FFToQgdbU4qXpyz1mX-J0+xk9mvB+tjqA@mail.gmail.com>
Date: Wed, 21 Jun 2017 11:55:25 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Cc: Arun <arun@ackl.io>, lp-wan <lp-wan@ietf.org>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.99.2 at dash
X-Virus-Status: Clean
X-Greylist: Delayed for 16:05:46 by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Wed, 21 Jun 2017 11:55:55 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/v8ZkQiWzEDRSoV1qrlEJK3BO64M>
Subject: Re: [lp-wan] re-order header field request
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Jun 2017 09:56:02 -0000

Hi Laurent,

> I don't think it is a problem to keep it, in a All 1 Frag, even if we
> don't
> use it (MIC is out of window numbering).  we have alignment on bytes when
> we send a message, so the benefit is not obvious if we don't keep it.

Thanks for your comment.

> But in  ACK message the W bit must be present.

Yes, this is covered by the new feature in -04 whereby all ACKs carry a   
 W bit, which indicates the window being acknowledged.

Cheers,

Carles


> Laurent
>
> On Wed, Jun 21, 2017 at 10:02 AM, Carles Gomez Montenegro <
> carlesgo@entel.upc.edu> wrote:
>
>> Hi Arun,
>>
>> The point here is that the Rule ID field in fragments except the last
>> one
>> will not use the W bit (or equivalently, have one bit less than the Rule
>> ID field in the last fragment as per current formats).
>>
>> So I'm wondering if this "additional bit" in the Rule ID of the last
>> fragment could have any useful purpose or not, or conversely would just
>> complicate the structure and uniformity of fragmentation headers.
>>
>> Thoughts?
>>
>> Cheers,
>>
>> Carles
>>
>>
>>
>> > Hi Carles,
>> >
>> >  Having the uniform header format seems to be an ideal solution but
>> > Tx'ing additional bit without any significance seems contentious.
>> > Will wait for more feedbacks or comments :)
>> >
>> > thanks,
>> > Arun