1 / 5

Comment from 802.11 WG

Comment from 802.11 WG. Comment: 4.2 and 4.3 not enough time for Sponsor Ballot indicated. Response: Changed 4.2: Expected Date of Submission for Initial Sponsor Ballot to 2014-03. Comments from 802.11 WG (cont’d).

bryga
Télécharger la présentation

Comment from 802.11 WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Comment from 802.11 WG • Comment: 4.2 and 4.3 not enough time for Sponsor Ballot indicated. • Response: Changed 4.2: Expected Date of Submission for Initial Sponsor Ballotto 2014-03 21-12-0032-00-0000

  2. Comments from 802.11 WG (cont’d) Comment: 5.2 Is multicast and group the same thing? So the parsing of the sentence is a bit confusing. • Suggested change to Scope statement: This amendment defines support for: group management using multicast frames, handover of users from one group to another in the same access network, and secure multicast MIH (Media-Independent Handover) protocol exchange. Response: Multicast and group may not be the same thing, but our purpose is to support management of multicast groups. The scope has been revised as follows: “To add support in Media-Independent Handover (MIH) framework for management of multicast groups.” 21-12-0032-00-0000

  3. Comments from 802.11 WG (cont’d) Comment: 5.4 suggest that you move the first 2 sentances to 5.5, and put “this amendment will not contain a Purpose Statement”. Response: We moved the first sentence to 5.5, but would like to revise the purpose as follows: “The purpose of this standard is to enable the handover for a group of users across the same or multiple different access networks. Additionally, this standard will define mechanisms to secure multicast MIH protocol exchanges.” 21-12-0032-00-0000

  4. Comments from 802.11 WG (cont’d) Comment: 5.5 Add text from 5.4. • insert “Std.” to “IEEE 802.15.4” • Check that the proper version of the PAR is being used. Response: • Added one sentence from 5.4 to 5.5. (Pl. refer to next slide) • Added “Std.” to “IEEE 802.15.4” (Pl. refer to next slide) • Proper version of the PAR will be generated via ‘MyProject’and will be circulated 21-12-0032-00-0000

  5. Comment from LMSC Chair • Comment: I am having difficulty understanding why a group of users would be need to be handed over from one network to another--i.e., what would cause such a need?.  Please explain in a little more detail the 5.5 Need for the Project scenario in which a group of mesh nodes is subjected to a wholesale network change (or perhaps provide another explanatory scenario). • Response: Section 5.5 has been revised as follows: There are several handover scenarios where a large group of terminals need to perform a handover as a group. An example scenario is Std. IEEE 802.15.4 mesh networks in which a group of mesh nodes requires handover from one segment of a network to another in the same or a different network for failover and restoration purposes. The failover can occur, for example, when a concentrator/gateway node loses its connectivity to its backbone network. In such a scenario, the mesh nodes under the concentrator/gateway node need to be handed over from one segment to another. Other examples are downlink-only technologies such as Digital Video Broadcasting (DVB) and Terrestrial Digital Multimedia Broadcasting (T-DMB) where a specific group of users need to be handed over from one network to another. This amendment is necessary in order to support such scenarios since the current standard only supports unicast commands which are inefficient when a group of users needs to be supported simultaneously. 21-12-0032-00-0000

More Related