IETF Logo Mail Archive

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

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Wed, 21 June 2017 06:13 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 136DB127843 for <lp-wan@ietfa.amsl.com>; Tue, 20 Jun 2017 23:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 sb7D3w8PW8hW for <lp-wan@ietfa.amsl.com>; Tue, 20 Jun 2017 23:13:48 -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 82A5E1315DE for <lp-wan@ietf.org>; Tue, 20 Jun 2017 23:13:46 -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 v5L6DfCo044427; Wed, 21 Jun 2017 08:13:41 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id D735E1D53C1; Wed, 21 Jun 2017 08:13:40 +0200 (CEST)
Received: from 83.55.156.17 by webmail.entel.upc.edu with HTTP; Wed, 21 Jun 2017 08:13:11 +0200
Message-ID: <bb800cdb12109667145b6d6f0adda50a.squirrel@webmail.entel.upc.edu>
In-Reply-To: <331F64BD15B741A986014F6C1AA51C75@WeiGengyuPC>
References: <386f3ac3-cc15-3fe7-8a7e-04d5be66c0ce@ackl.io> <ec067ef04c60b3fa38ea4887aa455314.squirrel@webmail.entel.upc.edu> <331F64BD15B741A986014F6C1AA51C75@WeiGengyuPC>
Date: Wed, 21 Jun 2017 08:13:11 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: weigengyu <weigengyu@vip.sina.com>
Cc: Arun <arun@ackl.io>, lp-wan <lp-wan@ietf.org>, Laurent Toutain <laurent@ackl.io>, Ana Minaburo <ana@ackl.io>
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 14:11:43 by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Wed, 21 Jun 2017 08:13:42 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/ZnhZj_boib7v9v8GwWsST-fT93g>
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 06:13:51 -0000

Hi Gengyu,

> Why each successive fragment must contain a Rule ID?
> It is known that the DTag is used as an indication of fragments belonged
> to
> the same IPv6 packet.
> A Rule ID in the first fragement can be passed to the receiver how to do
> HC
> compression,
> but the successive fragments containing a Rule ID just send a redundent
> information to the receiver.
> Right?

The Rule ID is needed to provide a receiver with information on what type
of content is being carried (and how it has to be handled). Note that not
all IPv6 packets will require fragmentation, and then losses may happen,
also non-fragmented packets may be interleaved with fragments, etc.

Cheers,

Carles


> Regards,
>
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications

v2.23.0 | Report a Bug | By Email