contents that are messages). Discussion: The text is below: with the commenter, change to at L47. “messages” “frames” Proposed resolution: Accepted CID 2277 2277 75.45 4.3.16.5.9 Frame definitions help Replace "messages" with enable distribution of "frames". frames (and, perhaps, messages inside frames). Discussion: The cited text is below: Proposed resolution: Revised Replace with at 75.45. “messages” “MSDUs” 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 Replace "messages" with switching frames, not "frames". messages. 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 to Suggest getting input from mesh experts. “messages” “events”. Input from Kaz Sakoda and Guido Hiertz: "MSDU" may be more correct than "message" I believe the intention was to explain to the “…Although 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 be quiet happy with keeping message or using notification” “I Proposed resolution: Revised Change from channel switching messages” to channel switch notifications” “of “of CID 2285 (GEN)
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)
11-14-0263-03-000m-more-lb199-gen-comment-resolutions.docx