| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Thank you for your comment received from the IEEE-SA RAC within the IEEE P802.11aq 3rd re-circulation sponsor ballot.
On Friday August 7th 2017, the IEEE P802.11aq Comment Resolution Committee (CRC) met, by teleconference, to discuss this comment
and have provided a DRAFT resolution as follows (in quoted italics):
“Rejected: No proposed change is required. The following is a response to the comment:
The group considers that randomizing the MAC address, as described in clause 12.2.10, is a perfectly
reasonable part of the pre-association discovery scope. This avoids
revealing privacy compromising information to STAs that are observing the 802.11aq traffic.
This is in line with IEEE Std 802c, clause 8.4.1 that states "The locally administered bits of local MAC
addresses are arbitrarily assignable under the condition that local MAC addresses are unique within a LAN
(which may be a bridged LAN or virtual bridged LAN) unless they are assigned to distinct VLANs in which
bridges support Independent VLAN Learning, per Annex F.1.2 (“Duplicate MAC Addresses”) of IEEE Std
802.1Q. Any failure of such uniqueness invalidates the fundamental premises of IEEE 802 network operation
and may lead to disruption."
Furthermore, IEEE Std 802c, clause 8.4.5 also states "In some cases, administrators may wish to assign
local MAC addresses in an arbitrary fashion (for example, randomly) and yet maintain compatibility
with other assignment protocols operating on the same LAN. For such purposes, a local MAC address
may be assigned as an Administratively Assigned Identifier (AAI)"
IEEE Std 802c provides compatibility for users of the local address space and it enables local administrators
who wish to assign addresses arbitrarily and maintains compatibility with other address assignment protocols.
IEEE Std 802c, clause 8.4.1, does apply in the IEEE P802.11aq case; whereas clause 8.4.5 does not apply. IEEE Std 802c
allows for multiple address assignment protocols to exist in a compatible manner on a single LAN. If there is only
one address assignment technique operating on the LAN, as is the case for IEEE 802.11aq, there is no incompatibility
with IEEE Std 802c.
A CSD was not created for IEEE P802.11aq, as a CSD was not required at the commencement of the IEEE P802.11aq project.
However, at the time a 5 criteria (5C) submission was created and can be found within the document
https://mentor.ieee.org/802.
internally by IEEE 802.”
In addition, the IEEE P802.11aq CRC also discussed a possible change to the IEEE P802.11aq PAR. However, it is the understanding of
the IEEE P802.11aq CRC that such a change would result in the reset of the sponsor ballot cycle, which the group is not willing to undertake.
At this stage, the IEEE P802.11aq CRC have not completed the analysis of all the comments received within the 3rd re-circulation sponsor ballot
and so this is a DRAFT response that the IEEE P802.11aq CRC have requested me to share with yourself and the RAC, so that you can provide
feedback if you wish.
For your information the next scheduled IEEE P802.11aq CRC teleconference will be on Friday August 11th 2017 at noon ET. Details are available
on the IEEE 802.11 teleconference calendar :http://www.ieee802.org/11/. Please note that I’ll be on vacation for this particular teleconference
and therefore it will be chaired by the IEEE P802.11aq vice-chair.
Kind regards
Stephen McCann
IEEE P802.11aq chair
Southampton UK
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-tgaq and then press the LEAVE button.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________