contents that are messages). Discussion: The text is below: with the commenter, change “messages” to “frames” at L47. Proposed resolution: Accepted CID 2277 2277 75.45 4.3.16.5.9 Frame definitions help enable distribution of frames (and, perhaps, messages inside frames). Replace "messages" with "frames". Discussion: The cited text is below: Proposed resolution: Revised Replace “messages” with “MSDUs” at 75.45. Frames are the transport mechanism for MSDUs, which are indeed distributed over multiple instances. CID 2276 2276 75.39 4.3.16.5.8 802.11 defines channel switching frames, not messages. Replace "messages" with "frames". Discussion: The text is below: Mesh channel switching is described in 10.9.8.4, P1462L10. 2014-02-28 discussion: information the impending channel switch is propagated. Could change “messages” to “events”. Suggest getting input from mesh experts. Input from Kaz Sakoda and Guido Hiertz: “…Although "MSDU" may be more correct than "message" I believe the intention was to explain to the reader that the distributed, non-centralized nature of a mesh network needs the propagation of some kind of announcement to all entities to inform them about the upcoming transitioning process.” And “I be quiet happy with keeping message or using notification” Proposed resolution: Revised Change from “of channel switching messages” to “of channel switch notifications” CID 2285 (GEN)
N.2.2 Deriving medium time AP use the following procedure to derive medium time in its ADDTS Response frame. There are two to consider: 1) the traffic requirements of the application, and 2) the expected error performance of the medium. The application requirements are captured by the following TSPEC parameters: Nominal MSDU Size and Mean Data Rate. The medium requirements are captured by the following parameters: Surplus Bandwidth Allowance, Minimum PHY Rate and, for aggregation, Nominal MSDU Aggregation. The following formula describes how Medium Time, in units of 32 μs periods per second, may be calculated: At 3035.63, “Opt pecified if Minimum Data Rate is specified” (2 occurrances) At 3036.24, “The ACM subfield for these categories set to 0.” At 3036. 31 “AC parameters chosen by the AP further account for any unadmitted traffic” At 3043. 38, “the scheduler consider these retransmissions” At 3044.64, “The values for SBA as shown in Table N-2 (SBA vs Packets/s) are based upon a one second time period and hence are used in the TSEC for EDCA Admission Control. The value used in an HCCA TSPEC be different, as will now be explained. At 3047.8, “For CBR traffic the minimum and maximum Service Intervals set to the same value. For example, most voice traffic requires a minimum and maximum service interval value of 20 ms.” At 3047. 12, “In the case of VBR traffic, such as video, Minimum Service Interval set to zero” At 3048.7, “For an HCCA for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the same value but it is allowable to just specify the Mean Data Rate noting that the Minimum and Maximum Service Intervals are the same. For an EDCA TSPEC, for CBR traffic the Minimum, Mean and Maximum Data Rate fields contain the same value but it is allowable to just specify the Mean Data Rate.” At 3048. 42, “hen summing streams for EDCA Admission Control, the EDCA Overhead Factor needs to be taken into account” References: