1. MCCA Comments Resolution 159 ppt
Jam, 2009
doc.: IEEE s
January, 2010
MCCA Comments Resolution 159 ppt
Date:
Authors:
Dee Denteneer, Philips
Dee Denteneer (Philips)

2. Resolve a number of CIDs on MDA
January, 2010
Resolve a number of CIDs on MDA
CIDs: see doc 10/201
This presentation summarizes the MCCA comment resolutions in the accompanying documents 200 and 201.
Dee Denteneer, Philips

3. January, 2010
3 CIDs
Comment
“It might be useful to allow for group addressed transmission of MCCA Setup Requests. Add group addressed transmission to MCCA Setup Request IE and MCCA Setup Request frame.”
Resolution
“The MCCA specification has been rewritten to allow that the MCCAOP Setup Request element can be transmitted in both indivdually addressed fframes and in group addressed frames. See Clause and ”
Dee Denteneer, Philips

4. January, 2010
6 CIDs
Comment
“"A value of zero indicates a non-repeated MCCAOP in the DTIM interval following the setup". It is unclear what is meant by this. What is set up?.”
Resolution
“The MCCA specification has been rewritten so that so that the reservation always specifies a schedule for repeated frame transmissions, and the exceptional case with MCCAOP Periodicity equal to 0 has been removed from the text.
Dee Denteneer, Philips

5. January, 2010
5 CIDs
Comment
“"HCCA times for which the mesh STA is the transmitter." Mesh STA does not use HCCA..”
Resolution
“In its TX-RX Times, the mesh STA can optionally report HCCA and Beacon times that involve a STA collocated with itself as transmitter or receiver. In its Interfering Times, By design, all reservations in the TX-RX Times of its neighbors are reported in its Interfering Times..”
Dee Denteneer, Philips

6. January, 2010
2 CIDs
Comment
“ The separation should be (DTIM interval - offset) divided by the periodicity instead of DTIM interval divided by periodicity
Resolution
“Good catch; The specification has been reconsidered and the MCCAOP Offset field is now restricted to avoid this situation.
Dee Denteneer, Philips