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

"weigengyu" <weigengyu@vip.sina.com> Wed, 21 June 2017 14:54 UTC

Return-Path: <weigengyu@vip.sina.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 3465B12EB3A for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 07:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.46
X-Spam-Level:
X-Spam-Status: No, score=-1.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439, URIBL_BLOCKED=0.001] autolearn=no 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 5TH2BlVUelp6 for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 07:54:26 -0700 (PDT)
Received: from smtp-6-48.vip.sina.com.cn (r3-66.sinamail.sina.com.cn [202.108.3.66]) by ietfa.amsl.com (Postfix) with SMTP id 7461312EABA for <lp-wan@ietf.org>; Wed, 21 Jun 2017 07:51:57 -0700 (PDT)
Received: from unknown (HELO WeiGengyuPC)([221.222.221.189]) by vip.sina.com with ESMTP 21 Jun 2017 22:51:52 +0800 (CST)
X-Sender: weigengyu@vip.sina.com
X-Auth-ID: weigengyu@vip.sina.com
X-SMAIL-MID: 67629066439
Message-ID: <1C1F6BA607D54CE2AE61A0CDA5F6E0B2@WeiGengyuPC>
From: weigengyu <weigengyu@vip.sina.com>
To: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
Cc: lp-wan <lp-wan@ietf.org>, Arun <arun@ackl.io>, Ana Minaburo <ana@ackl.io>, Laurent Toutain <laurent@ackl.io>
References: <386f3ac3-cc15-3fe7-8a7e-04d5be66c0ce@ackl.io> <ec067ef04c60b3fa38ea4887aa455314.squirrel@webmail.entel.upc.edu> <331F64BD15B741A986014F6C1AA51C75@WeiGengyuPC> <bb800cdb12109667145b6d6f0adda50a.squirrel@webmail.entel.upc.edu>
In-Reply-To: <bb800cdb12109667145b6d6f0adda50a.squirrel@webmail.entel.upc.edu>
Date: Wed, 21 Jun 2017 22:51:52 +0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/R7E3s6P8kW0aYmz-VWOmp9tiQ7M>
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 14:54:29 -0000

Hi,

> Note that not all IPv6 packets will require fragmentation,
> and then losses may happen,
> also non-fragmented packets may be interleaved with fragments, etc.

It seems that there may not apply two rules for one IP packets.
Or all fragments belonged to one pakcet should have the same Rule ID and the 
Dtag.

If one fragment is lost, the packet can not be assembled.
The packet will be assembled only after all fragments received correctly.

Fragments belonged to different packets will be assigned with different 
Dtags.

Anything wrong?

Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Carles Gomez Montenegro
Sent: Wednesday, June 21, 2017 2:13 PM
To: weigengyu
Cc: lp-wan ; Arun ; Ana Minaburo ; Laurent Toutain
Subject: Re: [lp-wan] re-order header field request


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

_______________________________________________
lp-wan mailing list
lp-wan@ietf.org
https://www.ietf.org/mailman/listinfo/lp-wan