Re: [6tisch] Comment to draft-wang-6tisch-6top-coapie-01.txt

Qin Wang <qinwang6top@yahoo.com> Tue, 21 July 2015 19:46 UTC

Return-Path: <qinwang6top@yahoo.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 3DFA21B2AC1 for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 12:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 AL7X3d75M5M3 for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 12:46:17 -0700 (PDT)
Received: from nm18-vm0.bullet.mail.bf1.yahoo.com (nm18-vm0.bullet.mail.bf1.yahoo.com [98.139.213.138]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F1F61B2B82 for <6tisch@ietf.org>; Tue, 21 Jul 2015 12:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1437507972; bh=FsTNIpqvMmlZIpi9am4VEyz6w4ohiXdy8k6VCpGkw08=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=QzXc0bAmkYahUFGSRzFvQ6HTFW3eWzywK/j/Z9GF7CJmf/xZvNwFm5B3Wsh5+cjXL+AxRVtHKkywi+UZT62wTysDuq54pmF8Ar0jCx/jIf9041ntMzUrmzadoFF4UF3DXKroZmgDpMrf5XlY5CfLjH2qHpIsCDhojhasQh5UTVuPU2ZQKCT3Mqld3LsoDQ6+S4BU+HkzGZ0xFJZ1S2ioal7g61O2DMB6KLP7tzeW0mL13CO6hkEg2JoXyuHfJ/87WpNCHqFAOEy87k4AePZS75RilCAl4bLCfSwuHahP/M3PtuKRo8PlxkXo17ujUe8wQ+Y5iP9caDPoSdOLomqOzw==
Received: from [98.139.215.140] by nm18.bullet.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 19:46:12 -0000
Received: from [98.139.212.220] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 19:46:12 -0000
Received: from [127.0.0.1] by omp1029.mail.bf1.yahoo.com with NNFMP; 21 Jul 2015 19:46:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 330909.31489.bm@omp1029.mail.bf1.yahoo.com
X-YMail-OSG: YHyroBoVM1l27NZwmYTw.uLwoRjG86I2rQEcpMeV0Pt7H1P3Ht6ZxyeC3VMPkIP sLKKXwRTV0MM7laD7G5.kgD6sa_R7ljA1qlNqThNnk_7HVjqMVKjgW28K_q3vWeJkEZ_xuV9..82 1IECdxgxc.TQXMyJauk6NWId84UAQruHleFDDA4qABUxXvge3AFp_yVQOg_s2dEN2EQT3v0cRYpB IHyxGVwVK2KJRqy6CBo2Q9Ma25.seXuWa5vDZckByHDvh2pL4Idfnghz8BOTD.4cu7zU5.cmPTTq AW79G3SYPP8S6GCu2EP_GC390bC0SsRBT0SpZr0ltqhzoPIdIp4rcEgFffeXzFJb5.TM4RAyycRo 7AaEFkTAPu_LeXRLagMGGtDcClMFry8Vlm1UmS6EB1wY0jNeFV5P2LuJ808cV5TzThZvJ_4PStKR na5IwYEJgM1z4koCo49CSygtZMiIJKr88VOFE81RjJ1xQ7qMwOxiZVz4T
Received: by 66.196.80.148; Tue, 21 Jul 2015 19:46:11 +0000
Date: Tue, 21 Jul 2015 19:44:09 +0000
From: Qin Wang <qinwang6top@yahoo.com>
To: Tero Kivinen <kivinen@iki.fi>
Message-ID: <557195717.2108288.1437507849890.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <21934.29961.675947.133987@fireball.acr.fi>
References: <21934.29961.675947.133987@fireball.acr.fi>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_2108287_1727917155.1437507849881"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/IvLic6_9h6qp7fkjDsJgpqtAf7M>
Cc: Thomas Watteyne <watteyne@eecs.berkeley.edu>, "6tisch@ietf.org" <6tisch@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [6tisch] Comment to draft-wang-6tisch-6top-coapie-01.txt
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Qin Wang <qinwang6top@yahoo.com>
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: Tue, 21 Jul 2015 19:46:20 -0000

Tero, Many thanks for the information.
Pascal, regarding to the group ID of payload IE, where we are? Have we submitted some kind of request to IEEE802.15.4 WG as described in the section 13.4, https://mentor.ieee.org/802.15/dcn/10/15-10-0235-15-0000-802-15-operations-manual.docx? Have we got some answer? I may missed something. 
ThanksQin
 


     On Wednesday, July 22, 2015 12:36 AM, Tero Kivinen <kivinen@iki.fi> wrote:
   

 Qin Wang writes:
> Before going to 802.15.9, I would like to discuss more about the
> coapie approach. In the 802.15.4e, the range (0x2-0x9) of group ID
> for payload IE is unmanaged.

Not anymore. Now allocations are handled by IEEE 802.15 WPAN Assigned
Numbers Authority (ANA), and it has all of them marked as reserved:

Element ID  Assigned to              Assigned by    ID (decimal)
0          Encapsulated Service      802.15.4e-2012  0
            Data Unit (ESDU)        
1          MLME (nested)            802.15.4e-2012  1
2          Vendor specific          802.15.4-corr1  2
3          Multiplexed (MP) IE      802.15.9        3
4          Omnibus Payload Group IE  Wi_SUN          4
5          Reserved                                  5
6          Reserved                                  6
7          Reserved                                  7
8          Reserved                                  8
9          Reserved                                  9
A          Reserved                                  10
B          Reserved                                  11
C          Reserved                                  12
D          Reserved                                  13
E          Reserved                                  14
F          List termination          802.15.4e-2012  15

This is from the Payload IE Group IDs tab from the
https://mentor.ieee.org/802.15/dcn/13/15-13-0257-06-0000-802-15-4-ana-database.xlsx
document.

Link to the latest ANA database should be found from the
http://www.ieee802.org/15/ANA.html page (hmm... it seems to have link
to -05 revision, need to send request to fix that).

If you read the ANA rules (in that page, or from the IEEE 802.15
Working Group Operations Manual
https://mentor.ieee.org/802.15/dcn/10/15-10-0235-15-0000-802-15-operations-manual.docx)
you will notice that yes, IETF might request to get one payload IE
number to be shared for all IETF protocols.

Of course you could also use Vendor specific IE, which starts with
3-octet vendor OUI, and then rest of it free for vendor specific use. 

> I thought IEEE802.15.4 WG had discussed how to use those Group ID,
> and also taken the requirement from 6tisch into consideration, and
> IEEE802.15.4 WG will assign a group ID to 6tisch. Am I wrong?

The numbers are now allocated by ANA, but as there is already vendor
specific IE, and the 802.15.9 multiplexed IE which would most likely
work fine for 6tisch, I am not sure whether ANA would approve such
request. 
-- 
kivinen@iki.fi