| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Working Group Reflector ---
Thanks, Graham. In short, yes, Option 5 was added as the discussion on Option 3 clarified (modified?) that option to be a STA provided ID. Also, Option 5 was added because it is using an ID that is not a MAC address (or not used as an RA/TA MAC address), and also that the ID is not carried in only encrypted frames (like the D0.2 option) and can therefore apply to pre-association/non-associated cases. It is my understanding of our discussion in the last meeting in Baltimore that this combination of choices was desired to be a potential option to support the pre-association use cases. As for your Option 6, below, my only question back to you, is whether you are asking to again consider/run straw poll for any option that requires the non-AP STA to use a MAC address that was assigned or created via an external mechanism (that is, that the non-AP STA didn’t pick for itself, using whatever internal method it has for doing that now for RCM). If there is sufficient interest, we can certainly make sure we have covered schemes that include such MAC address assignment/requirements. But, I got the impression from the discussion last week that we were reaching consensus in the group that such schemes would not be accepted/adopted by many client devices. Finally, to your last point (“A Poll to have pre-schemes at all”): We have done that. Multiple times, most recently in the November session, we asked: Do you support TGbh working on adding a new mechanism to support identification prior to association (or at Association Request)? Results: 17/4/3. I have been proceeding assuming that this is still the consensus of the group, and trying to drive us to pick one or more solutions. I thought your 11=12/0119 document was an excellent break down of the options in an attempt to find consensus on such a direction. Clearly, we haven’t found the right answer, yet, based on the straw polls run in Baltimore. Perhaps Option 5 will be a break-through. Otherwise, I agree that we are at a position of having strong agreement to do _something_, but no agreement on even the general direction of what that something should be, and that means we need more discussion, or we need to agree to give up on pre-association schemes. Mark From: G Smith <gsmith@xxxxxxxxxxxxxxxxxxx> Just noticed Option 5 is slightly different to option 3 in that the ID is supplied by the network. In option 3 the ID was supplied by the STA. The reasoning behind that was that we already had a network generated ID. Anyhow, if we want to make the list completely complete, then we should also add MAAD.
Maybe a way ahead is to simply see if there is any way forward at all wrt pre-schemes. A Poll to have pre-schemes at all Then A poll along the lines of “pre-schemes with or without computations” Graham From: G Smith Hi Mark, Re: 5th Option This is the same as the 3rd Option. It was already polled. Graham From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx> --- This message came from the IEEE 802.11 Working Group Reflector --- All, With 10 days’ notice, as mentioned at the closing plenary yesterday, I am announcing TGbh teleconferences on the following Tuesdays, at 9:30 am ET, for 2 hours:
Agenda and call in details will follow, shortly. Also note that I will be able to attend or chair the call on Jan 31, so one of the Vice Chairs will step in (thanks, Peter and Stephen!). I anticipate that further discussion on the “5th option”, as described below, will be our next item of discussion on the way forward topic. REMINDER: I am looking for a volunteer to champion/lead this discussion. And, we need to complete the review of the latest proposed resolutions for comments on the D0.2 text. 5th option:
Thanks. Mark To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 To unsubscribe from the STDS-802-11 list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1 |