1. Suggested comment resolution on Mesh DTIM element
March 2007
Suggested comment resolution on Mesh DTIM element
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Kazuyuki Sakoda

2. Abstract MAC Comments are categorized by labeling “Issue Identifiers”
March 2007
Abstract
MAC Comments are categorized by labeling “Issue Identifiers”
Currently, there are 19 Issue identifiers regarding MAC comments.
One of the issue identifiers is “DTIM”.
22 CIDs are labeled as “DTIM” issues.
Following slides present comments on these DTIM issues and suggested resolution.
Kazuyuki Sakoda

3. Background of DTIM element and power management
March 2007
Background of DTIM element and power management
Mesh power management is designed to reuse existing mechanism defined in the base standard.
Both of BSS and IBSS power management mechanisms are reused for mesh.
Tried to reuse the existing information elements as much as possible.
Mesh power management mechanism and/or utilization of information elements needs to maintain the BSS/IBSS operation.
MAP works as AP and MP
In the base standard, existing information elements are defined only for BSS or IBSS operations.
Kazuyuki Sakoda

4. Summary of comments on mesh DTIM
March 2007
Summary of comments on mesh DTIM
DTIM element is a confusing term
Sometimes cited as “mesh DTIM”, and sometimes cited as “DTIM”.
Sometimes not clear if DTIM is meant for DTIM count field in a TIM element.
Suggested to replace with “Mesh DTIM”.
DTIM is not an appropriate name, since “DTIM element” does not indicate “Traffic Indication”.
Needs clarification on the utilization of TIM/DTIM elements
Transmission rules are not clear.
Difficult to understand how to use DTIM element and TIM element.
DTIM element does not include traffic indication Map.
Definition of a new terms
“Mesh DTIM interval” is a new term, and not defined anywhere in the draft spec.
Some more editorial suggestions are made.
Kazuyuki Sakoda

5. Some discussion outcome from Hillsboro Ad-hoc group (1)
March 2007
Some discussion outcome from Hillsboro Ad-hoc group (1)
It must be better to define a solid information element for mesh DTIM and power management operations.
The new information element contains not only “DTIM count” and “DTIM period”, but also “traffic indication map” (consists of exactly the same fields as TIM element).
Rename the “DTIM element” to “Mesh TIM element”.
“Mesh TIM element” is used only for MPs power management.
“TIM element” is used only for BSS power management.
Kazuyuki Sakoda

6. Some discussion outcome from Hillsboro Ad-hoc group (2)
March 2007
Some discussion outcome from Hillsboro Ad-hoc group (2)
Before:
Unsync MP’s power management relies on both TIM element and DTIM element.
After:
Now it only relies on Mesh TIM element.
Figure S35: Mesh TIM element
Kazuyuki Sakoda

7. Suggested changes to the draft spec
March 2007
Suggested changes to the draft spec
Replace DTIM element with Mesh TIM element
Change all the references to DTIM element to Mesh TIM element.
Assign AID value to neighboring MP.
Suggested text is available as following.
suggested-comment-resolution-on-mesh-dtim-element.doc
Kazuyuki Sakoda

8. March 2007
Motion
Move to accept the resolution to CID74, 368, 369, 892, 894, 895, 1372, 2005, 2148, 3503, 3543, 3801, 3965, 4153, 4464, 4682, 4771, 4903, 4933, 5012, 5015, 5016, and 5017, as proposed in document 11-07/0280r2.
Moved by:
Second by:
Result (Yes/No/Abstain):
Kazuyuki Sakoda