Re: [6tisch] Typeof sixtop subIE:short or long

Tengfei Chang <tengfei.chang@gmail.com> Mon, 18 January 2016 19:19 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 3ED3D1B3C29 for <6tisch@ietfa.amsl.com>; Mon, 18 Jan 2016 11:19:51 -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_55=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 0t5p8tBScsCi for <6tisch@ietfa.amsl.com>; Mon, 18 Jan 2016 11:19:49 -0800 (PST)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (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 118EE1B3C2A for <6tisch@ietf.org>; Mon, 18 Jan 2016 11:19:40 -0800 (PST)
Received: by mail-yk0-x233.google.com with SMTP id a85so545558383ykb.1 for <6tisch@ietf.org>; Mon, 18 Jan 2016 11:19:40 -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=yleN4a8DK7mUE8Bzz+Pj6Jn82KglEBMIwh22q1iEz8U=; b=ZO3kvOwC8ZT8QHUfZLmjfbVEF4wABbb3KGshrsVClAOdZh5ikiMG76AQl6nvJxvndG xhPSpJtSCcd3iPNCcg82q5OIWBMGwV7EgrfWMgl9Z2mXjSTkjPj4fLeaXhaJE/L9HLxA /BYIrC01bV0CivptL0xH/CFTft/9kXXEBMLsjs7/Cvr390QTx5/u9oM+weeSGGivlzTk JQij50gBD6mEmqHuu09BKlAZDgK2tp2CU3/aj/GcoXPodWNzSRXYu1eBtnMx2U9jUPmA JDa4suIp4mxskHwVqfc4YcC3gg1e/t4K1m0wesHaNrcIUAuwmOJiQsKnF/skcc0WjHu4 b6Xw==
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=yleN4a8DK7mUE8Bzz+Pj6Jn82KglEBMIwh22q1iEz8U=; b=QslOnOnmDzOvSWOddX9RadZCKtp1c+7JEJ4bK2P+PgXwBDc6iLuNFRrtpQ6aEUDFFz DupC5F5NpeMDxJ+n6/5ePjxm5LcYG9E/8L1wZ0mxsyITmxBXXP7qPR5EIqLEi+yGiCPm vr+9NMSpJ21/s6dV5izvkim4QBnPtMXBD7T6CX9TPoM97e4lbT7ic0XqVVqrYrXqeWUv 1wB4i1v2H9XF7Y5RfGwRhw9AiYNszSfo5oR7u7tQIWd6kZ3CzwxhoNmY+M+qkXLUhBLy DcmJeqzYMpbom6RNI53Tw3ioG6xkCnjwLUlVr+vLs5K0wZatXM+cayGrHtyES1QaSpN3 +bmQ==
X-Gm-Message-State: ALoCoQllSnL9geNG0BCuKN46cPDHg0xaiP75KLH8ma8JCRQtZFVIOYEKec1Jz8nnIXN6eg71tribpz7wKXPiqzWbSVJZu4JmAg==
MIME-Version: 1.0
X-Received: by 10.37.230.133 with SMTP id d127mr5578411ybh.134.1453144779360; Mon, 18 Jan 2016 11:19:39 -0800 (PST)
Received: by 10.37.201.5 with HTTP; Mon, 18 Jan 2016 11:19:39 -0800 (PST)
In-Reply-To: <CAAdgstRsut4X1MF5n5XVXKotj5Jrhy3EUNTvqP5nFZS1G8ihCA@mail.gmail.com>
References: <86A12C46-388F-4099-9347-C7EAEF123E4B@kinneyconsultingllc.com> <645244049.3673071.1452546283479.JavaMail.yahoo@mail.yahoo.com> <CAAdgstRsut4X1MF5n5XVXKotj5Jrhy3EUNTvqP5nFZS1G8ihCA@mail.gmail.com>
Date: Mon, 18 Jan 2016 20:19:39 +0100
Message-ID: <CAAdgstTrMq8RALPKi+EpXsx5JWdO2CxBTUsX7YBcw1QQx1A_3A@mail.gmail.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
To: Qin Wang <qinwang6top@yahoo.com>
Content-Type: multipart/alternative; boundary="94eb2c0a91e86192160529a0a200"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/jvwDXYzcv21wloNdvo6f9JCZ78w>
Cc: thejaswi Chandrashekhar <c.thejaswi@samsung.com>, Palattella Maria Rita <6tisch@ietf.org>, Plugtests <Plugtests.Plugtests@etsi.org>
Subject: Re: [6tisch] Typeof sixtop subIE:short or long
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: Mon, 18 Jan 2016 19:19:51 -0000

Hi all,

Sorry to ask question again on the recommends document! I still have a
question about why the payload IE is terminated by a termination IE?

According to the IEEE802.15.4e-2012 on section 5.2.4.22.


*5.2.4.22 IE List Termination IE*
*......*
* If an unformatted payload follows the Payload IE list, then the payload
IE list is terminated with a list termination IE (ID = 0xf) that has a
content length of zero. Otherwise the terminator may be omitted*

Since there is no payload following the 6P payload IE, the terminator
may be omitted. Is there specific reason why we don't do that?
Let me know if this is already discussed somewhere so I can refer to.
Thanks!

Regard,
Tengfei


On Sun, Jan 17, 2016 at 8:50 PM, Tengfei Chang <tengfei.chang@gmail.com>
wrote:

> Thanks all for the comments! Then we will use the recommended format
> (second one) on the plugtest!
>
> Tengfei
>
> On Mon, Jan 11, 2016 at 10:04 PM, Qin Wang <qinwang6top@yahoo.com> wrote:
>
>> I think both of the two format are fine. But, if IEEE802.15 recommends
>> the second one, I think we should choose the second.
>>
>> Thanks
>> Qin
>>
>>
>> On Monday, January 11, 2016 11:17 AM, "pat.kinney@kinneyconsultingllc.com"
>> <pat.kinney@kinneyconsultingllc.com> wrote:
>>
>>
>> Thank you for the figures, I agree on both, especially the second one.
>> The advantages of the recommended approach are: one octet shorter for case
>> of single subtype ID and 256 available subtype ID addresses for any length.
>>
>> Sincerely, Pat
>>
>> On 11, Jan2016, at 9:19, Tengfei Chang <tengfei.chang@gmail.com> wrote:
>>
>> Hi Pat, all,
>>
>> I would like to make sure whether this format will be the right format
>> for the plugtest and everyone will agree. The attached is the document
>> 15-15-0939-02.
>>
>> There are two options for the format we will use in the plugtest:
>>
>> 1. we use what defined in
>> https://tools.ietf.org/html/draft-wang-6tisch-6top-sublayer-04, which
>> use the format defined in
>> IEEE802.15.4e-2012, section 5.2.4.3 (page 81). If we decide to use this
>> one, we need short/ long type of the subIE.
>>
>>
>> *Bits: 0-10*
>> *11-14*
>> *15*
>> *Octets: 2*
>> *32-35*
>> *36-39*
>> *40-47*
>> *Octets*
>> *Bits: 0-10*
>> *11-14*
>> *15*
>> Payload IE Content Length
>> Group ID
>> Type (0b1)
>> Length
>> Sub-type ID
>> Type
>> Ver
>> Code
>> SFID
>> other field
>> Length
>> (0x00)
>> Group ID (0xf)
>> Type (0b1)
>> Payload IE
>> Payload IE Content
>> Payload Termination IE
>>
>>
>> 2. we use what define in document 15-15-0939-02, which use the format
>> defined in last page of the document:
>> For example the 6P command defined in sublayer draft:
>>
>> the payload will be:
>>
>> *Bits: 0-10*
>> *11-14*
>> *15*
>> *16-23*
>> *24-27*
>> *28-31*
>> *32-39*
>> *octets*
>> *Bits: 0-10*
>> *11-14*
>> *15*
>> Payload IE Content Length
>> Group ID
>> Type (0b1)
>> Sub-type ID
>> Ver
>> Code
>> SFID
>> other field
>> Length
>> (0x00)
>> Group ID (0xf)
>> Type (0b1)
>> Payload IE
>> Payload IE Content
>> Payload Termination IE
>>
>> Do we agree on the second one?
>>
>> Tengfei
>>
>> On Fri, Jan 8, 2016 at 5:56 PM, Tengfei Chang <tengfei.chang@gmail.com>
>> wrote:
>>
>> I see. Thanks a lot Pat for the information! I found the document you
>> mentioned. I will update the format in the Golden Images.
>>
>> Have a good day!
>> Tengfei
>>
>> On Fri, Jan 8, 2016 at 5:25 PM, pat.kinney@kinneyconsultingllc.com <
>> pat.kinney@kinneyconsultingllc.com> wrote:
>>
>> Tengfei;
>>
>> The IEEE 802.15 IG 6T recommended a format for sub-IEs in document
>> 15-15-0939-02 sent to this reflector on 30 November 2015.  The following is
>> an excerpt from that document:
>> "Accordingly, the IEEE 802.15 IG 6T recommends that the IETF use an
>> alternate scheme that restricts each Payload IE to only one sub-type ID and
>> content, i.e. no nesting.  The advantages of this recommended scheme is
>> that it eliminates one octet from the total Payload IE, it allows a full
>> 256 sub-type IDs, and each sub-type length can be up to 2046 octets.”
>> Therefore, if 6tisch adopts the above recommendation, there would be no
>> long or short types.
>>
>> Pat
>>
>> Pat Kinney
>> *Kinney Consulting LLC*
>> IEEE 802.15 WG vice chair, SC chair
>> ISA100 co-chair, ISA100.20 chair
>> O: +1.847.960.3715
>> pat.kinney@kinneyconsultingllc.com
>>
>> On 8, Jan2016, at 10:14, Tengfei Chang <tengfei.chang@gmail.com> wrote:
>>
>> Hello all,
>>
>> As I mentioned on the Call, the 6top sublayer draft seems didn't  define
>> the type of subIE used by 6P command ,long or short type?  Let me know if I
>> missed it from the draft! Thanks you!
>>
>> Regard,
>> Tengfei
>> _______________________________________________
>> 6tisch mailing list
>> 6tisch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> <15-15-0939-02-0000-IETF_6tisch_IE_Information.docx>
>>
>>
>> _______________________________________________
>> 6tisch mailing list
>> 6tisch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>>
>