Re: [STDS-802-11] 2012 November Minutes for TG REVmc session now posted

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Hi, Dorothy. I believe we agreed on the call that the resolution applied to both CID 76 and CID 21. That’s how I have them in the database. So – Done!

Mark

From: *** IEEE stds-802-11 List *** [mailto:STDS-802-11@xxxxxxxx] On Behalf Of Dorothy Stanley
Sent: Monday, December 03, 2012 12:42 PM
To: STDS-802-11@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11] 2012 November Minutes for TG REVmc session now posted

--- This message came from the IEEE 802.11 Working Group Reflector --- Thanks Jon for the Nov meeting notes, and the to-be-posted- Nov 30 telecon notes.

All,

On the Nov 30 TGmc telecon, we agreed to a resolution for CID 21 (Changing from
"(OUI-36 and IAB)" to "(OUI-36)".

Note that CID 76 is the same as CID 21, so Mark (Hamilton) - as these are both MAC comments, can
you provide the same proposed resolution to CID 76 as CID 21?

Thanks,

Dorothy

21	Adrian Stephens	0	2012	8.4.1.31	467		T	N	467.00		8.4.1.31						The Organization Identifier field is described as: "using 36-bit length identifiers (OUI-36 and IAB)". However, OUI-36 and IAB are distinct namespaces intended for different purposes. Accordin to the RAC, the IAB is only to be used to EUI-48 identifiers, and its use as an organizational identifier (i.e., not in the context of a 48-bit MAC address) contravenes this constraint. The extension of the Organization Identifier field to more than 3 octets was done to permit P1609 to use its already-allocated IAB. However, what they needed to have allocated was an OUI-36, not an IAB.	There are two parts to this. 1. How to respond to P1609 having the wrong kind of assignment. While this is strictly not our problem, we do need to support any solution that the RAC identify in this case. 2. How to adjust our definition of Organization Identifier. This can be done by removing the reference to IAB. The example also refers (implicitly) to an IAB (the P1609 IAB), which is likely to confuse. This should be changed to a fictitious symbolic number such as 0x001BC5wwxy.		MAC		Discuss	See CID 76				2012/11/5 15:22	MAC
76	Lee Armstrong	0	2012	8.4.1.31	467		G	N	467.00		8.4.1.31						(a copy from Adrian) The Organization Identifier field is described as: "using 36-bit length identifiers (OUI-36 and IAB)". However, OUI-36 and IAB are distinct namespaces intended for different purposes. According to the RAC, the IAB is only to be used to EUI-48 identifiers, and its use as an organizational identifier (i.e., not in the context of a 48-bit MAC address) contravenes this constraint. The extension of the Organization Identifier field to more than 3 octets was done to permit P1609 to use its already-allocated IAB. However, what they needed to have allocated was an OUI-36, not an IAB.	There has been recent response from the RAC on this in which they admit to an error in value assignment, will discuss when it comes up in the meetings.		MAC		Discuss	[MAH] Hmm. I do not read the cited text as saying these namespaces are the same, only that they are two examples of 36 bit identifiers. However, the usage within a subclause and field called "Organization identifier" and using phrases like "organizationally unique identifier" certainly imply OUI use, and I agree that is not the same as IAB use. It should be possible to make this subclause (and field) more generic, to carry either an OUI or an IAB allocation. This may not solve P1906's use of the field though (or their use of their assignment, for that matter!). Another thing to consider: P802 (P802-REV/D1.5) says that an OUI-36 is carried within an EUI-48 in the first 4 octets plus the least significant nibble of the 5th octet. While the Organization Identifier field is not really a representation of the EUI-48, it seems perhaps confusing that in the OI, an OUI-36 would have the final assigment bits in the most significant half, but within the EUI-48 they are in the least significant half. It might be too late to do anything about this, though, without destroying backward compatibility.				2012/11/5 15:33	MAC

On Sat, Dec 1, 2012 at 4:14 PM, Jon Rosdahl <jrosdahl@xxxxxxxx> wrote:

--- This message came from the IEEE 802.11 Working Group Reflector ---

Hello

I have posted the minutes for the 2012 November TG REVmc session on Mentor:

https://mentor.ieee.org/802.11/dcn/12/11-12-1225-00-000m-minutes-for-november-plenary-san-antonio.docx

They are subject to review and approval at the January Interim Session.

Comments welcome,

Regards,

Jon

-------------------------------------------------------------------------------
Jon Rosdahl 10871 North 5750 West
hm:801-756-1496 Highland, UT 84003
cell:801-376-6435
office: 801-492-4023

A Job is only necessary to eat!
A Family is necessary to be happy!!

_______________________________________________________________________________

If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.

Instead, go to http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11 and then press the LEAVE button.

If there is no LEAVE button here, try http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-RO.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________

_______________________________________________________________________________

If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.

Instead, go to http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11 and then press the LEAVE button.

If there is no LEAVE button here, try http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-RO.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________

If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.