1. MDA assorted comments Date: 2006-07-19 Authors: 6/24/2018 6/24/2018
doc.: IEEE r00
6/24/2018
MDA assorted comments
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
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

2. Abstract MDA has still left 68 unresolved comments
6/24/2018
doc.: IEEE r00
6/24/2018
Abstract
MDA has still left 68 unresolved comments
Lots of them are “editorial”, and we consider some of these in this presentation
1675, 2238, 3469, 3208, 1519, 1520, 4134, 1299, 5654, 2186, 3670, 539, 1046, 5028, 5039, 3810, 862, 5168, 5625, 560, 268, 3553
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

3. 1675, 2238, 3469 6/24/2018 Problems with use of “flow”
doc.: IEEE r00
6/24/2018
1675, 2238, 3469
Problems with use of “flow”
However, removed per 268/r2
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

4. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 3808
“With the current format, it seems that many calculation is necessary to detect the overlap of the MDAOP. It should be better to change the format to be "implementation friendly".
This is done per Contribution 551r1 accepted in Montreal
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

5. ID 1519, 1520 “What is the time unit for "TX-RX Times Report"?
6/24/2018
doc.: IEEE r00
6/24/2018
ID 1519, 1520
“What is the time unit for "TX-RX Times Report"?
“What is the time unit for "Interference Times “
This is done per Contribution 551r1 accepted in Montreal: (32 usec)
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

6. ID 4134 6/24/2018 In fact relates to p95.33
doc.: IEEE r00
6/24/2018
ID 4134
“"such that the following are satisfied", but there are no conditions specified. (p96.33)
In fact relates to p95.33
Change to “An MDAOP is a period of time within every Mesh DTIM interval that is set up between a transmitter and a receiver.” Once an MDAOP is setup,
Suggestion: Look up sentence in 1.04
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

7. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 1299
the sentence: "The IEs that are used for MDA may be carried in action frames." is disturbing, because it implies that they may be carried in other frames as well. Basically, an MP has no clue which frames could contain these elements.
In 1.03
Change to:
Delete Clause in Draft 1.03
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

8. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 5654
The second step(2)) of MDAOP setup procedure is redundant. The information is available in the third step(3)).
ACCEPT
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

9. ID 2186 Delete first sentence: An MDAOP set …. In their TX-RX times”
6/24/2018
doc.: IEEE r00
6/24/2018
ID 2186
"The teardown is assumed successful once the ACK is received, or maximum retry attempts are exceeded." conflicts with the statement at the beginning of the clause.
Delete first sentence: An MDAOP set …. In their TX-RX times”
Change last sentence: The transmitter transmits teardown messages until an ack is received, or until a maximum retry attempts is exceeded.
Basically: “DEFER” see last slide: issues. Ack is not right terminology here (teardown is broadcast)
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

10. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 3670
This paragraph is written poorly with double negative and somewhat tutorial language
Include “,”s before except and after set up the MDAOP and replace “to not initiate” with “to defer”; replace “hear” with “receive”
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

11. 6/24/2018
doc.: IEEE r00
6/24/2018
An MDAOP is a period of time within every Mesh DTIM interval that is set up between the MDAOP owner and the addressed MP. Once an MDAOP is setup,
The MDAOP owner uses CSMA/CA and backoff to obtain a TXOP as described in and using parameters MDACWmin, MDACWmax, and MDAIFSN. The ranges of values allowed for MDACWMin, MDACWMax, and MDAIFSN parameters are identical to those allowed for EDCA.
The MDAOP is advertised by both the MDAOP owner and the addressed MP. All MDA supporting MPs other than the MDAOP owner shall defer initiating new transmissions during the TXOP initiated in the MDAOP.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

12. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 1049
In bullet 2, once an MDAOP is established, MPs other than the MP that set up the MDAOP should avoid transmitting during the entire MDAOP, and not just the TXOP within the MDAOP.
Reject: Other MPs may transmit once the MDAOP owner is finished even before the MDAOP has finished.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

13. ID 3668 Delete last sentence of this paragraph in 9.14.2 6/24/2018
doc.: IEEE r00
6/24/2018
ID 3668
What is meant by "QoS flow"?
Delete last sentence of this paragraph in
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

14. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 539
Concerning the early termination of a TXOP, it is proposed that "if the MP intends to end the TXOP with enough time before the end of the MDAOP, it is responsible for relinquishing the remaining MDAOP time by using any of the methods that reduce NAV as defined in ". There are not mechanisms for terminating a TXOP in If an MP terminates a TXOP by sending a special frame (say by sendinding a CF-end), it will cause all NAVs of all neighbors to be reset. This would would result in follisions.
Belongs to MDAOP termination group; see comment 1301
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

15. ID 1046 Accept: belongs to MDAOP termination group; see comment 1301
6/24/2018
doc.: IEEE r00
6/24/2018
ID 1046
Valid EDCA frame exchanges as defined in ma should not contain QoS+CF-Poll frames and CF-End frames
Accept: belongs to MDAOP termination group; see comment 1301
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

16. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 5028, 5039
How to set MDAOP Set ID ?
The MDAOP Set ID field is an eight bit unsigned number that represents the ID for the requested Set. It is determined by the MDAOP Set owner. When used in combination with the MAC address of the MDAOP set owner, the MDAOP Set ID uniquely identifies the MDAOP Set
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

17. ID 3810 6/24/2018 Why "MDAOP Set Owner" field is necessary?
doc.: IEEE r00
6/24/2018
ID 3810
Why "MDAOP Set Owner" field is necessary?
Reject: MDAOP set ID plus MDAOP Set Owner together uniquely identify the MDAOP set
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

18. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 862
Is it MDAOP Set Teardown or MDAOP Teardown (as in table s48). Fix one way or the other throughout draft
MDAOP Set Teardown, p39 lines 13 and 17.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

19. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 5168
This paragraph include procedure.
Separate the sentence into two, one for the definition of this, i.e., one is "The Mesh Deterministic Access frame format uses the Action frame body format" the other part is the rest of this sentence other sentences. Then, the latter one shall be moved to clause 9 or 11A.
Counter: This paragraph was already rewritten and no additional changes seem necessary to resolve the comment.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

20. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 5171
For MDA elements, this figure says "One or more MDA elemente", but octets is fixed value, i.e., 5.
But in 1.03
Counter: This paragraph was already rewritten and no additional changes seem necessary to resolve the comment.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

21. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 5625
An MDAOP setup request may be refused or must be refused? What are the criteria if it is refused sometimes but is not refused some other times? Fairness is an issue for MDA. Even though is trying to address this problem, more details/associated mechansisms are required.
Change: “An MDAOP setup request shall be refused …”
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

22. 6/24/2018
doc.: IEEE r00
6/24/2018
ID 530, 268, 3553
Ids ask for more elaborate request codes and a table. In fact, trimmed down in 1.03 as compared to 1.0
Make a table of more reply codes (Overlap, MAF limit, not supported)?
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.

23. Reliable ack? of teardown, i.e. Reuse TSPEC for MDA
6/24/2018
doc.: IEEE r00
6/24/2018
Reliable ack? of teardown, i.e.
Reuse TSPEC for MDA
Do we need a teardown? Or can we just broadcast a teardown (and similarly for a reservation)
Check the draft for consistency on MDAOP owner and MDAOP-Set owner, MDAOP Teardown and MDAOP-Set Teardown, etc. Where MDAOP-Set is preferred.
Make a table of reply codes.
Dee Denteneer, Philips et al.
Dee Denteneer, Philips et al.