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

Thanks Qin and Pascal;

As you know from subclause 13.4 of IEEE 802.15 WG’s Operation Manual, IEEE 802.15 WG needs a letter (or email attachment) from an IETF authority that could enforce the assurances necessary for the release of ID number assignment(s) from IEEE 802.15.  I was thinking that IANA could be that authority.  I can expedite the request within IEEE 802.15’s ANA once we receive that letter.

Pat

Pat Kinney
Kinney Consulting LLC
IEEE 802.15 WG vice chair, TG chair
ISA100.11a WG chair
O: +1.847.960.3715
pat.kinney@kinneyconsultingllc.com <mailto:pat.kinney@kinneyconsultingllc.com>
On 21, Jul2015, at 17:12, Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:

I wondered the same, Qin.

Pat will know better J

Pascal

From: Qin Wang [mailto:qinwang6top@yahoo.com] 
Sent: mardi 21 juillet 2015 21:44
To: Tero Kivinen
Cc: 6tisch@ietf.org; Pascal Thubert (pthubert); Thomas Watteyne
Subject: Re: [6tisch] Comment to draft-wang-6tisch-6top-coapie-01.txt

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

Thanks
Qin

On Wednesday, July 22, 2015 12:36 AM, Tero Kivinen <kivinen@iki.fi <mailto: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 <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  <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 <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 <mailto:kivinen@iki.fi>

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch