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

Tengfei Chang <tengfei.chang@gmail.com> Wed, 20 January 2016 13:22 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 37F361A8884; Wed, 20 Jan 2016 05:22:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] 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 qUT75fEP5ark; Wed, 20 Jan 2016 05:22:11 -0800 (PST)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (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 6D6FA1A8883; Wed, 20 Jan 2016 05:22:11 -0800 (PST)
Received: by mail-yk0-x234.google.com with SMTP id x67so8898552ykd.2; Wed, 20 Jan 2016 05:22:11 -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=Vrw3VbK/xiDe+vuzTmJgB3r321PbmCIEzm9dXbNvM7g=; b=fyWQyUMNe8pj3g5Gh1eH/KBsUW6wLYgRSr4OEnFx4/MBBo8bXVip5k/VDVSQF0eXvp /MSMLAUJFf7+XAHJ3r06zLQMRTk7dcAwy/kWcxJalC0qqPlrGn0evv1u/HFuNUtnDufx cy4ir1DHoWPUmjEIY9wRMJPNY9rqcwNx/gcnXjheLxMtqttwy4vQK15S7KscPmdPfuiH YbgBtMHXhMDJlU961wHTn+KPHbW9Bt0brqc6tmW8mzeg67PfpXRpw+2Q5RiKQBctibO2 g1x7JDlOnDvL4RxK/iisqDYbArwiEAKxCWc0qdpAsfe5ngPT5ihPtkcAVQAvG8S1WmbP xd+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Vrw3VbK/xiDe+vuzTmJgB3r321PbmCIEzm9dXbNvM7g=; b=hsDz0r6FL4XOhJSxY6jDQEB9U+G+6Ba9dzRhKu50U9ujtDCtop0BLyxDzJgFC/6cZp M1/xRbOWbKyjgQRaaXuRNOlyguS+yBFT59+4/w4fatUH62KgHiukBLhJ4NJEBUo1FAbT 1zJ76VvQ0/lgqYZ0BZNePAEa15ar4qBYTz+8rh0EDL9njckNQDg9T4N5bhAPucaSXJMX JBWv5FYWYF1bw12McfHmrkc5pTtrwyIWkYMSvJIBls3W6ey4uskivQMzQFOVJGY+WZm/ r6zT4tpJCb6Fsb+1zPZiTtfovp7x1RO0kz6yCXtQkPPHdjzbG/CZs7p8tAD+15ABClUB pS1A==
X-Gm-Message-State: ALoCoQntb8Ecs0FcaBlm6flWa4l4cGq5HsRrVtnNvJtfgKIMtyeJNCEPTgzi9eG+otqNEy9B/HR0pXOGCLsbiZiw8zt+ldveMg==
MIME-Version: 1.0
X-Received: by 10.129.134.193 with SMTP id w184mr20943415ywf.31.1453296130788; Wed, 20 Jan 2016 05:22:10 -0800 (PST)
Received: by 10.37.201.5 with HTTP; Wed, 20 Jan 2016 05:22:10 -0800 (PST)
In-Reply-To: <f49c3ea76c394235a690a0dee54cda12@XCH-RCD-001.cisco.com>
References: <CAAdgstTwS5bSuRfLwh_ntf1MNek+nMR2wDOPjkuCedvpuJ3VwA@mail.gmail.com> <f49c3ea76c394235a690a0dee54cda12@XCH-RCD-001.cisco.com>
Date: Wed, 20 Jan 2016 14:22:10 +0100
Message-ID: <CAAdgstTzq-d8X=Gxay3sTVXrE7eck=b3w92xsJh-ujxtVhdc7Q@mail.gmail.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary="001a114efd6ea118300529c3dfcb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/rJbU_SH6j-YXvDGd2CFEyT1CMpM>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "6lo@ietf.org" <6lo@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 13:22:13 -0000

Thanks pascal for explaining!

Yes, I vote to impose an order for the headers in the packet. It helps to
understand the format of packet generally. Thanks a lot!

Tengfei

On Wed, Jan 20, 2016 at 10:52 AM, Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> 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
>
>
>
>
>