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

Tero Kivinen <kivinen@iki.fi> Tue, 21 July 2015 16:36 UTC

Return-Path: <kivinen@iki.fi>
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 CC1111A8A39 for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 09:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 jhAyNiEBOi8C for <6tisch@ietfa.amsl.com>; Tue, 21 Jul 2015 09:36:30 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 965281A8BB1 for <6tisch@ietf.org>; Tue, 21 Jul 2015 09:36:29 -0700 (PDT)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.1/8.14.8) with ESMTPS id t6LGaQjD029007 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Jul 2015 19:36:26 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.1/8.14.8/Submit) id t6LGaPsH024001; Tue, 21 Jul 2015 19:36:25 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <21934.29961.675947.133987@fireball.acr.fi>
Date: Tue, 21 Jul 2015 19:36:25 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Qin Wang <qinwang6top@yahoo.com>
In-Reply-To: <11134325.1860961.1437490472600.JavaMail.yahoo@mail.yahoo.com>
References: <21934.16929.897976.905775@fireball.acr.fi> <11134325.1860961.1437490472600.JavaMail.yahoo@mail.yahoo.com>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
X-Edit-Time: 16 min
X-Total-Time: 16 min
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/PXZTw56gg3X-z6bjjIiHfjpRboo>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>
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
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 16:36:32 -0000

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