Re: [lp-wan] Fw: re-order header field request
"weigengyu" <weigengyu@vip.sina.com> Wed, 21 June 2017 15:16 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 56486129C6C for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 08:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 NEZVLGkuKIy9 for <lp-wan@ietfa.amsl.com>; Wed, 21 Jun 2017 08:16:23 -0700 (PDT)
Received: from smtp-6-45.vip.sina.com.cn (r3-68.sinamail.sina.com.cn [202.108.3.68]) by ietfa.amsl.com (Postfix) with SMTP id 9D45612EB36 for <lp-wan@ietf.org>; Wed, 21 Jun 2017 08:11:31 -0700 (PDT)
Received: from unknown (HELO WeiGengyuPC)([221.219.54.237]) by vip.sina.com with ESMTP 21 Jun 2017 23:10:54 +0800 (CST)
X-Sender: weigengyu@vip.sina.com
X-Auth-ID: weigengyu@vip.sina.com
X-SMAIL-MID: 220945221785
Message-ID: <59F856E1230C43D5A7CE1018F7C2DCA8@WeiGengyuPC>
From: weigengyu <weigengyu@vip.sina.com>
To: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
Cc: lp-wan@ietf.org
Date: Wed, 21 Jun 2017 23:10:53 +0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="response"
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/EEIDQXYX2o6WzPcNbymBl0Q5FSE>
Subject: Re: [lp-wan] Fw: 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 15:16:26 -0000
Hi Carles, Suppose that one packet is partitioned into two fragments. Because the Dtag indicates two fragments belonged to one packet, the Rule ID in the second fragment is repeated, or redundent, isn't it? If the Rule ID is not exist in the second fragment, the receiver can process it according to the Dtag which is the same in two fragments. Is there any confusions at the receiver side? 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:07 PM To: weigengyu Subject: Re: [lp-wan] Fw: 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] 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