Re: [6tisch] Question on draft-ietf-6lo-routing-dispatch-00

Tengfei Chang <tengfei.chang@gmail.com> Wed, 06 January 2016 16:23 UTC

Return-Path: <tengfei.chang@gmail.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBDB1ACE51; Wed, 6 Jan 2016 08:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, SPF_PASS=-0.001] autolearn=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 ej0EbkO9epMN; Wed, 6 Jan 2016 08:23:08 -0800 (PST)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (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 E54581A9123; Wed, 6 Jan 2016 08:23:07 -0800 (PST)
Received: by mail-yk0-x22b.google.com with SMTP id k129so298237580yke.0; Wed, 06 Jan 2016 08:23:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SYEay3hFd36dycJd2SRqzGrmweO3XQPtY6GFyTx52K4=; b=M3s834k9rXLAeUATNri33bhX7vRKIZ2kDGvDbdyeLKzXNJy70KVW7zcjuo3D7NteFV GevQrprT1dI+O4twkvRXz2u9wGI8Cm27dFfxPQFK3+Qpw3KlgOZI3NqVMkmRGeiJwBhk TPjSCNTPuiUBn6l+Ie8Agvok9qB35OxuOTCiZ6P/982j5amP2eB6F/4wiOsCUOJ4XW5E XKwJI7TVi9Jd70kKZoEEbpby9QtpQK7ltuRL61xra7mFEsVlTbgXhuin8rzwUV+hRjac UPXDg/N7rJjH0UQcPJLdbzgjlQu9KGeXsKwvGsoqnLni3DBdcq5XFc/Pg276tRl6xyN1 42tA==
MIME-Version: 1.0
X-Received: by 10.13.206.193 with SMTP id q184mr72283272ywd.100.1452097387151; Wed, 06 Jan 2016 08:23:07 -0800 (PST)
Received: by 10.37.201.5 with HTTP; Wed, 6 Jan 2016 08:23:07 -0800 (PST)
In-Reply-To: <87a35100c4054862bb85e1f0b66cd778@XCH-RCD-001.cisco.com>
References: <CAAdgstTyZnBNxckLX87g78b7o-_f+43vyft4LTyON1MKtMxkwQ@mail.gmail.com> <e12a3fb245fe40a9ab4d6e8ab2ff9aba@XCH-RCD-001.cisco.com> <CAAdgstR2L4RthZnckGzQzCHqHJuOE5VbJ4HBqNq1UK=acMvfrQ@mail.gmail.com> <87a35100c4054862bb85e1f0b66cd778@XCH-RCD-001.cisco.com>
Date: Wed, 06 Jan 2016 17:23:07 +0100
Message-ID: <CAAdgstQ9rEu9+uja5dGsnYoP0wZyT+imkorDWpGL4_nHWvGFRQ@mail.gmail.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary="001a114e4f48f0cb480528acc4ca"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/XTN9O_AkuHQPpTY-bqmNDPnZW-0>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6tisch] Question on draft-ietf-6lo-routing-dispatch-00
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 16:23:10 -0000

Yes, I see. Thanks for the explanation!

Tengfei

On Wed, Jan 6, 2016 at 5:16 PM, Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> I see TengFei:
>
>
>
> The text means a header that is used for the purpose of routing, not
> necessarily a source route header like an IPv6 RH…
>
>
>
> Take care,
>
>
>
> Pascal
>
>
>
> *From:* Tengfei Chang [mailto:tengfei.chang@gmail.com]
> *Sent:* mercredi 6 janvier 2016 16:43
> *To:* Pascal Thubert (pthubert) <pthubert@cisco.com>
> *Cc:* 6tisch@ietf.org; 6lo@ietf.org
> *Subject:* Re: Question on draft-ietf-6lo-routing-dispatch-00
>
>
>
> Hi Pascal,
>
>
>
> Thanks for the replies! And thanks a lot for the slides! That's exactly
> the thing what we are looking for!
>
>
>
> The IPv6ExT is IPv6 Extension Header with the value of 7 of EID which
> indicate the following IPv6 Header(IPHC).
>
>
>
> I misunderstood IPinIP-6LoRH since I saw the first sentence of section 8
> where it says: *The IP-in-IP 6LoRH (IPinIP-6LoRH) is an Elective 6LoWPAN *
> *Routing Heade**r **that provides** a compressed form for the
> encapsulating IPv6 Header **in the case of an IP-in-IP encapsulation.*
>
>
>
> This confused me a little bit since it was called Routing Header (I was
> thinking the source routing header) but, yes, it explained that it's being
> used for compressing form for encapsulating IPv6 Header. Is here any
> different concept for routing header?
>
>
>
> Anyway, with the reply we are understanding now what IPinIP 6LoRH stands
> for. Thanks a lot for the answering!
>
>
>
> Cheer,
>
> Tengfei
>
>
>
>
>
> On Wed, Jan 6, 2016 at 3:46 PM, Pascal Thubert (pthubert) <
> pthubert@cisco.com> wrote:
>
> Hello TengFei : )
>
>
>
> I hope you’re doing good!
>
>
>
> Please see below:
>
> 1. in section 4.2, second paragraph:
>
> *One or more 6LoRHs MAY be placed in a 6LoWPAN packet and MUST always*
>
> *be placed before the LOWPAN_IPHC [RFC6282].*
>
>
>
> What's the situation when Ip-in-Ip encapsulation structure was used?
>
>
>
> <pascal>
>
> The idea is that the original IPv6 packet that may eventually fly over the
> internet or has come from the Internet should be encoded using RFC6282.
> There may be IP in IP in there but then the RPL routers would not see the
> inner IP.
>
> When that packet traverses the RPL network, headers may need to be added
> or removed. If so, anything that needs to be added or removed in the life
> of the packet by a node that is not source or destination must be placed in
> an IP in IP using 6LoRH
> https://tools.ietf.org/html/draft-ietf-6lo-routing-dispatch-00#section-8,
> and the 6LoRH must be placed before the IPHC. There’s no a comprehensive
> study of that here
> https://tools.ietf.org/html/draft-robles-roll-useofrplinfo-02 thanks to
> the efforts of the RPL chairs.
>
> </pascal>
>
>
>
>
>
> 2. section 8: IP-in-IP 6LoRH first paragraph:
>
> *The IP-in-IP 6LoRH (IPinIP-6LoRH) is an Elective 6LoWPAN Routing*
>
> *Header that provides a compressed form for the encapsulating IPv6*
>
> *Header in the case of an IP-in-IP encapsulation.*
>
>
>
> According to the description, it the IPinIP-6LoRH is a combination of
> IPHC+RH3 but in a compressed format?
>
> <pascal>
>
> No, TengFei. The IP in IP 6lorh encodes the outer IP header that must be
> placed to encapsulate. RH3 is encoded as a series of 6Lorhs as described in
> https://tools.ietf.org/html/draft-ietf-6lo-routing-dispatch-00#section-6
>
> </pascal>
>
>
>
> For example: following is the format of packet containing routing header
> which defined in old draft using an Ip-in-Ip encapsulation:
>
> MACheader + IPHC + RH3 + IPv6ExT + IPHC + ICMPv6
>
>
>
> If we are using the 6LoRH, will it turns to :
>
> MACheader + Paging Dispatch(page 1) + IPinIP-6LoRH + IPv6ExT + IPHC +
> ICMPv6
>
>
>
> Is this correct? If not, what it should be? Thanks!
>
>
>
>
>
> <pascal>
>
> Not really:
>
> 1)      The RH3 is expressed as a series of 6LoRH after the IP in IP, one
> 6LoRH per group of contiguous addresses that are compressed to the same
> size Please look at slide 10 in
> https://www.ietf.org/proceedings/94/slides/slides-94-6lo-2.pdf
>
> 2)      What is the IPv6Ext? The only header that RPL may add there is
> RPI in HbH, compressed by 6loRH. And Actually I’d place it before the RH.
> Anything that is not compressed by 6LoRH has to be compressed by RFC 6282
> and must be placed after the IPHC
>
>
>
> <pascal>
>
>
>
> You two take care,
>
>
>
> Pascal
>
>
>
>
>
>
>
>
>