| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Youhan: I think you comment on the order is strictly from a spec-consistency perspective (not to have contradictory order in REVmd versus .11ax). However, the order in which elements are included in a frame is generally not an issue – as implementation
would be parsing elements based element id (and extended element id, if it applies) and not based on the order. Cheers -- ganesh “It is amazing what you can accomplish if you don’t care who gets the credit.” – Harry Truman From: *** 802.11 TGax - HEW - High Efficiency WLAN *** <STDS-802-11-TGAX@xxxxxxxxxxxxxxxxx>
On Behalf Of Youhan Kim Hi, Osama, Robert, 11ax D7.0 is adding new information/elements to AssocReq frames, etc., whose order is overlapping w/ those in REVmd D5.0.
For example, 11ax D7.0 is adding the HE Capabilities element is at order #45, Channel Switch Timing is at order #46, etc to the AssocReq frame. But REVmd D5.0 already has MSCS Descriptor as order #45. Similar issues exist in AssocResp, ReassocReq and ReassocResp. While there aren’t any comments submitted on D7.0 for these, I would suggest the group to address these issues for a smooth publication of IEEE 802.11ax. Is this something the Editor (Robert) could address as an editorial update, or do
you need someone to submit a formal text update request document? Thanks. Youhan To unsubscribe from the STDS-802-11-TGAX list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 To unsubscribe from the STDS-802-11-TGAX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGAX&A=1 |