| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| --- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
All, I have the following proposal to resolve REVme CID 2086. Is there any concerns/feedback on this proposal? Thanks. Mark Comment: In the figure Return path of OCT messages based on OCT parameters says MBp=OSp but this is a type violation. Also "the Multi-band peer parameter shall be set to the value of the Multi-band OCT source parameter of the MLME-OCTunnel.indication primitive. and the Multi-band peer parameter shall be set to the value of the Multi-band OCT source parameter received in the corresponding MLME-OCTunnel.indication primitive. and the Multi-band peer parameter set to the value of the Multi-band OCT source parameter of the MLME-OCTunnel.indication primitive." Proposed resolution: The exact quotes in the Comment cannot be found. Assuming the issues are at: P3011.35, P3011.56 and P3012.28, respectively (without the extra “Multi-band” before “OCT source parameter”). Change these occurrences as: Multi-band peer parameter shall be set to a Multi-band element where the value of the Band ID, Channel Number and BSSID fields are set to the value of the corresponding fields in the OCT source parameter of the MLME-OCTunnel.indication primitive Multi-band peer parameter shall be set to a Multi-band element where the value of the Band ID, Channel Number and BSSID fields are set to the value of the corresponding fields in the OCT source parameter received in the corresponding MLME-OCTunnel.indication primitive Multi-band peer parameter set to a Multi-band element where the value of the Band ID, Channel Number and BSSID fields are set to the value of the corresponding fields in the OCT source parameter of the MLME-OCTunnel.indication primitive. To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1 |