14 May, 2001 IEEE P802.15-01/166r2

IEEE P802.15

Wireless Personal Area Networks

Project / IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Title / MAC Amendments
Date Submitted / [14 May, 2001]
Source / [James P. K. Gilb]
[Mobilian]
[11031 Via Frontera, Suite C] / Voice: [858-217-2201]
Fax: [858-217-2301]
E-mail: [ ]
Re: / []
Abstract / [Amendments to the PHY layer of 00000d02P802.15.3__Draft-Standard.pdf]
Purpose / [To record the amendments to the PHY layer for the purpose of modifying the baseline draft standard.]
Notice / This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release / The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
  1. Delete subclause 8.2.4.1 and all references explicit token pass as it applies to GTS. (ED note: change figure 6, also, TIFS may also need to be deleted.). – DONE 4/6/01, deletions from 8.2.4.2, delete figure 47 and 48.
  2. Add clarification that command frames can only be sent either in a stream slot that is allocated for master-station communication or during the CAP. – DONE 4/6/01, sub-clause 7.2.8
  3. Add clarification that user bits/bytes are time units in the channel allocation commands – To be resolved by R. Gubbi, check d04 for resolution.
  4. Open issue is what atomic time unit will be used to measure time. Also, if a lower resolution should be used for beacons and other timing units. – TBD
  5. Remove editorial notes at the beginning of clause 7 and 8 indicating that the clauses have not been reviewed or approved. – DONE 4/6/01
  6. At what rate does a DEV (was STA now DEV – device) request association – At the base rate always – DONE 4/6/01, in sub-clause 7.2.1
  7. The beacon is always sent at the base rate – Confirmed – DONE 4/6/01, in sub-clause 7.2.1
  8. Does coordinator know DEV's max data rate – No, needs to be added to association frame. – Will be put in the probe response
  9. Does each DEV know every other DEV's rate set – No, it is informed by the coordinator in a TBD packet. – Add to MAC issues list
  10. How does a DEV renegotiate a data rate? Through the coordinator – checking for command frame – and on a packet by packet basis it can be lowered. – Needs to be added, add to MAC issues list
  11. If you support rate x, do you support all rates < x - yes – DONE, defined in PHY clause
  12. Remove piconet data rate support byte from beacon. – DONE 4/6/01
  13. Does coordinator maintain a database of the maximum data rates of all the participants in the WPANTM – TBD. James Gilb will start the discussion. – Needs to be started
  14. The Superframe format was approved in Tampa and reconfirmed during the Boulder Ad-hoc MAC meeting. The format of the Superframe is Beacon-CAP-CFP. The nature of the CFP according to clauses 8.2.4.2, 8.2.4.3 and 8.2.5 will be resolved by the MAC committee with a potential vote this coming Thursday morning to determine which CFP algorithm will be included in the next rev of the baseline document. – DONE 4/6/01, SCP and VTS deleted, only GTS remains.
  15. Add MAC SAP based on Document P802.15.3-01/060r0. Leave a TBD table that defines the priority parameter. – DONE, table will be in 0.4

Submission Page XXX James P. K. Gilb, Mobilian