Re: [6tisch] The "BEFORE" and "AFTER"

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 20 January 2016 09:53 UTC

Return-Path: <pthubert@cisco.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 050901B3982; Wed, 20 Jan 2016 01:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 DiwqWbk4as7R; Wed, 20 Jan 2016 01:53:17 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 408AF1ACD98; Wed, 20 Jan 2016 01:53:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9408; q=dns/txt; s=iport; t=1453283597; x=1454493197; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=d3QN2oMIgJoz2CUlHp5BrBjymxpYwCjFl2Zs7Xh7zUM=; b=W2wp1ulR6WB0o5rdzN6PJUsFvwGzCuuU/CGEAFjINfK8KzA3aDadEKVF Al0JLXGSytaAPJl2pm74g4DZ35con03/EyVoU+5VdhROQ78B6ztxBNmoP T7uDuUIE7KBZY1STxw7Zj8ZXalrmXqGbq0bhK5oW8QYQSHNWOfqekCrni U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAgCbWJ9W/51dJa1egm5MUm0GiFGwYYITAQ2BY4YPAhyBJzgUAQEBAQEBAYEKhDQBAQEEIwpMEAIBCBEEAQEoAwICAjAUCQgCBAENBQiIE695jz4BAQEBAQEBAQEBAQEBAQEBAQEBAQEVhjqEdIUHgmGBSQWXGgGIO4UcjwiOWwEgAQFChAlyhiqBCAEBAQ
X-IronPort-AV: E=Sophos;i="5.22,320,1449532800"; d="scan'208,217";a="228004374"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jan 2016 09:53:16 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u0K9rGwl014304 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Jan 2016 09:53:16 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 20 Jan 2016 03:53:15 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Wed, 20 Jan 2016 03:53:15 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Tengfei Chang <tengfei.chang@gmail.com>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6tisch] The "BEFORE" and "AFTER"
Thread-Index: AQHRU1tqtnDmos6Mek2lEt0tEDasGp8EKL4Q
Date: Wed, 20 Jan 2016 09:52:42 +0000
Deferred-Delivery: Wed, 20 Jan 2016 09:52:31 +0000
Message-ID: <f49c3ea76c394235a690a0dee54cda12@XCH-RCD-001.cisco.com>
References: <CAAdgstTwS5bSuRfLwh_ntf1MNek+nMR2wDOPjkuCedvpuJ3VwA@mail.gmail.com>
In-Reply-To: <CAAdgstTwS5bSuRfLwh_ntf1MNek+nMR2wDOPjkuCedvpuJ3VwA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.6.33]
Content-Type: multipart/alternative; boundary="_000_f49c3ea76c394235a690a0dee54cda12XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/YDDH0cwt4juolUZnbNUGnrgWpyQ>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [6tisch] The "BEFORE" and "AFTER"
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, 20 Jan 2016 09:53:19 -0000

This is correct Tengfei, and quite classical.

Headers are like a stack placed in front of the packet. One builds an LOWPAN-IPHC – compressed packet that does not have any RPL artifact in it. Then the RPL artifacts are added as 6LoRH headers. We have not imposed an order yet but it makes sense to place the RPI first if any, then the RH3 if any, then the 6LoRH.

Would you wish that we impose an order to simplify the parsing?

Pascal

From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Tengfei Chang
Sent: mercredi 20 janvier 2016 09:20
To: 6tisch@ietf.org
Subject: [6tisch] The "BEFORE" and "AFTER"

Dear all,

As recently more discussion in the ML about the format of packet, sometimes we say some header after/before the IPv6 header. I would like to clarify this.

1. For me, I say with the way that mac header is the first header in the packet and then, several Routing Headers are AFTER mac header (no mesh header/fragmenet header in between).  IPHC header is AFTER those Routing Headers.

2. However, with the view of constructing a packet, IPHC is first added into packet, then RHs are placed AFTER IPHC, MAC header is constructed at the end. (I feel pascal is using this way to describe the order of header, right?)

What's the way when we describe something like this?

Thanks
Tengfei