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

Tengfei Chang <tengfei.chang@gmail.com> Sun, 17 January 2016 19:50 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 7B06A1A1A8A for <6tisch@ietfa.amsl.com>; Sun, 17 Jan 2016 11:50:59 -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 dN4jIORmc4Ky for <6tisch@ietfa.amsl.com>; Sun, 17 Jan 2016 11:50:57 -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 1966F1A0430 for <6tisch@ietf.org>; Sun, 17 Jan 2016 11:50:57 -0800 (PST)
Received: by mail-yk0-x233.google.com with SMTP id k129so570956713yke.0 for <6tisch@ietf.org>; Sun, 17 Jan 2016 11:50:57 -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=60f53EvHNhiAxZQvnF8km5bNfANjQKRWRU9fDlNGwAo=; b=f95yyqM2RExMmJC9FPUEHR4AHxb6VFlMLyJwGCG4WD4Zf1AtPdkOH285bgRgDbL8G4 MaS8ozNRqaAXHTpdHTm+L2BMxGaxggNrOMhL1APdZYe/Iapi5eujVAZXblz8JJsjxSe/ lGonuZIM22rJfzM5JUNElR5zs0SsiROGvXwExlCNFMtCrutTfM4s5L8mWCpXPBHf/qOY GSKb4FR1gawNTEhyDGzyPPdV319k3qDL5tbBKHrwLGyo3y3PtDm1F4PwprUhEAsxu/4o OSFbLqvYax/+VR1pIy8vevezwzzVDY5Kxvhz4+ztsATQ7FmUm5rmwbgDomXccGMCtx5S B/Nw==
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=60f53EvHNhiAxZQvnF8km5bNfANjQKRWRU9fDlNGwAo=; b=IXJV3kJjBoVsalqTt4wbg98p+FHcmxT3jwYeDAoA8IHA5HaOWhN3HCIyyMRx8L4O1j 6eRtlnhxkoRrAPCRM4s3x7SYsuIYUvEBCR4I8mOl6VE8mWgKqfwgCVqG58UkBQwjVqIm GKi248CtuhXIsxF8178p8HKAvxKByX5vBAGmfsFFfCcrZJjsqSjAEkc9nw1tarWZjdoN K0KHj/11X8ECU5nGvZ8MyGflEJsYILUu6Vfgsr264Xw0KmSAV+wVsqry+iEorj2UNGnQ UpOvQnts2hEuzZjqMWyaTkdQGqN/dpVX44WN/WBsoT9F85UuOAF/iWrS2hMFEK8YPp4Q cXsA==
X-Gm-Message-State: ALoCoQnq4uKv8CC2s8KP9uAMGI1WESm9A+VZPNzMshhyATWI4GbF5vcz9iIxf5tNR97uyUc+tanRC3Ca5vtHkuoFqkjFUT4JSg==
MIME-Version: 1.0
X-Received: by 10.37.230.133 with SMTP id d127mr3698887ybh.134.1453060256342; Sun, 17 Jan 2016 11:50:56 -0800 (PST)
Received: by 10.37.201.5 with HTTP; Sun, 17 Jan 2016 11:50:56 -0800 (PST)
In-Reply-To: <645244049.3673071.1452546283479.JavaMail.yahoo@mail.yahoo.com>
References: <86A12C46-388F-4099-9347-C7EAEF123E4B@kinneyconsultingllc.com> <645244049.3673071.1452546283479.JavaMail.yahoo@mail.yahoo.com>
Date: Sun, 17 Jan 2016 20:50:56 +0100
Message-ID: <CAAdgstRsut4X1MF5n5XVXKotj5Jrhy3EUNTvqP5nFZS1G8ihCA@mail.gmail.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
To: Qin Wang <qinwang6top@yahoo.com>
Content-Type: multipart/alternative; boundary="94eb2c0a91e86aaa3805298cf477"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/I0J5FIl84L4NuQo9pYElKVFCC4w>
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: Sun, 17 Jan 2016 19:50:59 -0000

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