Re: [lp-wan] re-order header field request
Arun <arun@ackl.io> Wed, 21 June 2017 07:48 UTC
Return-Path: <arun@ackl.io>
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 0BBDA131787 for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 00:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 gvAr5SbzoGzp for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 00:48:25 -0700 (PDT)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CECF41317A5 for <lp-wan@ietf.org>; Wed, 21 Jun 2017 00:47:29 -0700 (PDT)
Received: from mfilter6-d.gandi.net (mfilter6-d.gandi.net [217.70.178.135]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 86E321720D1 for <lp-wan@ietf.org>; Wed, 21 Jun 2017 09:47:28 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter6-d.gandi.net
Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter6-d.gandi.net (mfilter6-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id IRLWcpM0KpOz for <lp-wan@ietf.org>; Wed, 21 Jun 2017 09:47:26 +0200 (CEST)
X-Originating-IP: 192.44.77.204
Received: from [192.168.1.157] (nat-asr-incub-b204.rennes.enst-bretagne.fr [192.44.77.204]) (Authenticated sender: arun@acklio.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C6F9C17210C for <lp-wan@ietf.org>; Wed, 21 Jun 2017 09:47:26 +0200 (CEST)
To: lp-wan@ietf.org
References: <386f3ac3-cc15-3fe7-8a7e-04d5be66c0ce@ackl.io> <ec067ef04c60b3fa38ea4887aa455314.squirrel@webmail.entel.upc.edu>
From: Arun <arun@ackl.io>
Message-ID: <b1ae6a91-b3a3-6197-2648-d9001a9eff1e@ackl.io>
Date: Wed, 21 Jun 2017 09:47:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <ec067ef04c60b3fa38ea4887aa455314.squirrel@webmail.entel.upc.edu>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="1GqOJGR13VxFSRBXOHbfW0eE35PNtTliC"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/fLWGPQBCb2qDMew5gPMay7ovlhY>
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 07:48:28 -0000
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 On 20/06/2017 18:01, Carles Gomez Montenegro wrote: > Hi Arun, > > Thanks for pointing this out. > > Your proposal seems fine to me, except for the (possibly minor) detail > that in your proposal "R" would comprise a number of header fields for the > last fragment that would be different from the number of fields in > previous fragments. > > Maybe we could also consider another solution: adding the W bit in the > header of the last fragment of the packet. > > I haven't found examples of scenarios where the W bit is actually needed > in the last fragment (i.e. fragment with "all ones" CFN). However, I'm > wondering if there is an actual benefit or a related use case that may > require *not* having a W bit in the last fragment header. (If anyone has > any in mind, please chime in!) > > On the other hand, if we have the W bit also in the last fragment header, > header format will be more uniform across all fragments. > > Thoughts? > > Cheers, > > Carles > > > > >> Hi all, >> Absence of window bit in the last fragment of the packet makes it tricky >> to unmarshall the header at the receiver. >> As I see it, the receiver up front shall know the length of the CFN >> field depending on the Window size configured but doesn't know to >> anticipate the last fragment unless indicated by CFN. >> So I think, we need to maintain same order on all fragment headers. >> >> existing; >> >> <------------ R ----------> >> <--T--> 1 <--N--> >> +-- ... --+- ... -+-+- ... -+ >> | Rule ID | DTag |W| CFN | >> +-- ... --+- ... -+-+- ... -+ >> >> shall be; >> <------------ R ----------> >> <--T--> <--N--> 1 >> +-- ... --+- ... -+- ... -+-+ >> | Rule ID | DTag | CFN |W| >> +-- ... --+- ... -+- ... -+-+ >> >> and for the last fragment >> <------------ R ----------> >> <--T--> <--N--> >> +-- ... --+- ... -+- ... -+-+ >> | Rule ID | DTag | CFN |MIC >> +-- ... --+- ... -+- ... -+-+ >> >> >> what do you think? >> >> >> thanks, >> Arun >> >> _______________________________________________ >> 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] re-order header field request Arun
- Re: [lp-wan] re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] re-order header field request weigengyu
- [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] re-order header field request Arun
- Re: [lp-wan] re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] re-order header field request Laurent Toutain
- Re: [lp-wan] re-order header field request Arun
- Re: [lp-wan] re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request Arun
- Re: [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request அருண்பிரபு (arunprabhu)
- Re: [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] Fw: re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request Pascal Thubert (pthubert)
- Re: [lp-wan] Fw: re-order header field request weigengyu
- Re: [lp-wan] Fw: re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] Fw: re-order header field request weigengyu
- [lp-wan] lpwan-overview comments Alper Yegin
- Re: [lp-wan] lpwan-overview comments Alexander Pelov
- Re: [lp-wan] lpwan-overview comments Alper Yegin
- Re: [lp-wan] Fw: re-order header field request Arun
- Re: [lp-wan] Fw: re-order header field request Carles Gomez Montenegro
- Re: [lp-wan] Fw: re-order header field request Laurent Toutain
- Re: [lp-wan] lpwan-overview comments Stephen Farrell
- Re: [lp-wan] lpwan-overview comments Stephen Farrell
- Re: [lp-wan] lpwan-overview comments Alper Yegin
- Re: [lp-wan] lpwan-overview comments Stephen Farrell
- Re: [lp-wan] Fw: re-order header field request Pascal Thubert (pthubert)
- Re: [lp-wan] lpwan-overview comments Alper Yegin
- Re: [lp-wan] lpwan-overview comments Stephen Farrell