Date: 2011-05-19 tgs Motto


Download 464 b.
Sana14.08.2018
Hajmi464 b.


Date: 2011-05-19

  • Date: 2011-05-19


TGs Motto: Perfection is achieved not when there is nothing left to add but when there is nothing left to take away.

  • TGs Motto: Perfection is achieved not when there is nothing left to add but when there is nothing left to take away.

  • telecon

  • April 21, 2011

  • Chair: Dee Denteneer (Philips)

  • Vice Chair: Guido Hiertz (Philips)

  • Technical Editor: Kazuyuki Sakoda (Sony)

  • Secretary: Guenael Strutt (Motorola)



Warning: Do not leave your laptops unattended!

  • Warning: Do not leave your laptops unattended!

    • The meeting is not responsible for your unwatched stuff.
  • Wear your badge at all times in the meeting area!

  • Individual membership

    • In all IEEE standards meetings, membership is by individual, hence you do not represent a company or organization.
  • Photographs and Recordings

    • No sound recordings are permitted at 802.11 WG or TG meetings.
    • No photographs allowed without WG Chair permission.
  • Media – Press and Analyst briefings

    • Only the 802.11/.15/.18/.19/.22 WG Chair and WG Vice-Chairs are allowed to give verbal statements/interviews to the media on behalf of their respective IEEE working group.


Note the links from the items in red in the left column of all pages of the Working Group meeting agenda.

  • Note the links from the items in red in the left column of all pages of the Working Group meeting agenda.

    • Affiliation Frequently Asked Questions: http://standards.ieee.org/faqs/affiliationFAQ.html
    • Anti-Trust: http://standards.ieee.org/resources/antitrust-guidelines.pdf
    • IEEE Ethics: http://www.ieee.org/web/membership/ethics/code_ethics.html
    • Letter of Assurance Form: http://standards.ieee.org/board/pat/loa.pdf
    • IEEE Patent Committee: http://standards.ieee.org/board/pat/index.html
    • IEEE Patent Policy: http://standards.ieee.org/board/pat/pat-slideset.ppt
    • Patent FAQ: http://standards.ieee.org/board/pat/faq.pdf




All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development.

    • All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development.
    • Patent Policy is stated in these sources:
    • IEEE-SA Standards Boards Bylaws
    • http://standards.ieee.org/guides/bylaws/sect6-7.html#6
    • IEEE-SA Standards Board Operations Manual
    • http://standards.ieee.org/guides/opman/sect6.html#6.3
    • Material about the patent policy is available at
    • http://standards.ieee.org/board/pat/pat-material.html


If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance:

  • If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance:

    • Either speak up now or
    • Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or
    • Cause an LOA to be submitted




Go to http://newton/11/attendance

  • Go to http://newton/11/attendance

  • https://murphy.events.ieee.org/imat/ (Documents: http://802server.events.ieee.org/ or 172.16.0.10 or just http://newton)

    • Sign-in
    • Claim attendance credit for each session.
      • Only “sign-in” and “claim credit” for yourself, do NOT “sign-in” for others.
  • You have to log in every session!



Various resolutions, Kaz

  • Various resolutions, Kaz

    • 11-11-0519r4: P802.11s sponsor ballot 3rd recirc comments (Motion 92)
  • Authentication-deaunthentication, Dan

      • 11-11/0561r0: SB3re RFI-Gate Comment Resolutions


Issue : a) deauthentication, relates to CID4108: D11.02 lacks normative description on deauthentication process for mesh STAs. This is not acceptable from my perspective. It needs to be described as I wrote an email to Dan this morning.

  • Issue : a) deauthentication, relates to CID4108: D11.02 lacks normative description on deauthentication process for mesh STAs. This is not acceptable from my perspective. It needs to be described as I wrote an email to Dan this morning.



Motion 126: moved to accept the text changes in document 11-11/836r1 “auth-deauth-in-mbss” and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 126: moved to accept the text changes in document 11-11/836r1 “auth-deauth-in-mbss” and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Issue : b) "Mesh Data frame" or "mesh Data frame", relates to CID4124: CRC adopted the resolution to change them to mesh Data frame globally. I think it is not a good idea. I did not implement this change in D11.02. If necessary, we should add some text in clause 7, in particular 7.1.1 (Conventions), to describe the definition of Mesh Data frame. It is defined in clause 3, so it may not be necessary to spell out in clause 7, but it should be safe to do so.

  • Issue : b) "Mesh Data frame" or "mesh Data frame", relates to CID4124: CRC adopted the resolution to change them to mesh Data frame globally. I think it is not a good idea. I did not implement this change in D11.02. If necessary, we should add some text in clause 7, in particular 7.1.1 (Conventions), to describe the definition of Mesh Data frame. It is defined in clause 3, so it may not be necessary to spell out in clause 7, but it should be safe to do so.



Motion 127: moved for CID4124, to change the resolution to: Principle, insert the following paragraph after the seventh paragraph in 7.1.1 (Conventions): "A QoS Data frame that is transmitted by a mesh STA is referred to as a Mesh Data frame.“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 127: moved for CID4124, to change the resolution to: Principle, insert the following paragraph after the seventh paragraph in 7.1.1 (Conventions): "A QoS Data frame that is transmitted by a mesh STA is referred to as a Mesh Data frame.“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Issue : h) clarification on ASRA bit setting in clause 7.3.2.92, relates to CID4270: As we discussed with some of you in Palm Springs, I think the current text in 7.3.2.92 needs to be amended in someway as it does not make sense. We may want to correct the error before the publication of the 802.11s.

  • Issue : h) clarification on ASRA bit setting in clause 7.3.2.92, relates to CID4270: As we discussed with some of you in Palm Springs, I think the current text in 7.3.2.92 needs to be amended in someway as it does not make sense. We may want to correct the error before the publication of the 802.11s.



Motion 128: moved For, CID4270, to make the text changes proposed on the following two slides, and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 128: moved For, CID4270, to make the text changes proposed on the following two slides, and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Change the text in clause 7.3.2.92, page 46, line 60-63, in D11.02, to read: 

  • Change the text in clause 7.3.2.92, page 46, line 60-63, in D11.02, to read: 

  • For a mesh STA the ASRA field is used as an emergency indicator. If a mesh STA requires emergency services, the ASRA field is set to 1, otherwise it is set to 0.



Modify the last two paragraphs in clause 11.23.6 to read: 

  • Modify the last two paragraphs in clause 11.23.6 to read: 

  • In a mesh STA when dot11ESNetwork is true, the mesh STA can reach emergency services and ESR shall be set to 1. When that mesh STA receives a Mesh Peering Open frame, that includes the Interworking element with the ASRA bit equal to 1, it allows access to emergency services, forwarding frames to a emergency server.

  • Note: The ASRA bit set to 1, informs the mesh STA to prioritize resources for the emergency call, to proactively find a better path before the link conditions deteriorate below a certain threshold, and/or to change some of the mesh STA's behavior (for example, to disable any power save features).

  •  

  • In a mesh STA when dot11ESNetwork is false, it is unable to support the mesh peering of emergency services and ESR shall be set to 0. When that mesh STA receives a Mesh Peering Open frame, that includes the Interworking element with the ASRA bit equal to 1, it is unable to support the mesh peering of emergency services and does not forward frames.



Issue : c) definition of mesh gate, relates to CID4127: The adopted resolution seems to change the flavor of mesh gate in someway. We may want to review the text for safety measure.

  • Issue : c) definition of mesh gate, relates to CID4127: The adopted resolution seems to change the flavor of mesh gate in someway. We may want to review the text for safety measure.



Motion 129: moved for CID4124, to change the resolution to: Principle, change the definition of mesh gate in Clause 3 to: " mesh gate: Any entity that has mesh station (STA) functionality and provides access to the distribution services, via the wireless medium (WM) for the mesh basic service set (MBSS).“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 129: moved for CID4124, to change the resolution to: Principle, change the definition of mesh gate in Clause 3 to: " mesh gate: Any entity that has mesh station (STA) functionality and provides access to the distribution services, via the wireless medium (WM) for the mesh basic service set (MBSS).“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


  • d) definition of mesh peering, relates to CID4128: As active mesh peering protocol is taken away from D11.02, we need to change the text here anyway. I made a proposal which is included in D11.02 already, but we may want to review the text for safety measure.



  • Concerns:



Motion 130: moved for CID4128, to change the resolution to: Principle, change the definition of mesh peering in Clause 3 to: " mesh peering: A logical relationship between two mesh stations (STAs) that is required for direct communication over a single instance of the wireless medium (WM). A mesh peering is established with a mesh peering protocol. “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 130: moved for CID4128, to change the resolution to: Principle, change the definition of mesh peering in Clause 3 to: " mesh peering: A logical relationship between two mesh stations (STAs) that is required for direct communication over a single instance of the wireless medium (WM). A mesh peering is established with a mesh peering protocol. “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Issue : e) definition of unreachable destination, relates to CID4133: The adopted resolution seems to be wrong in my understanding. I did not implement this change in D11.02. We may want to review the text for safety measure.

  • Issue : e) definition of unreachable destination, relates to CID4133: The adopted resolution seems to be wrong in my understanding. I did not implement this change in D11.02. We may want to review the text for safety measure.



Motion 131: moved for CID4133, to change the resolution to: Principle, change the definition of unreachable destination in Clause 3 to: "unreachable destination : A destination mesh station (STA) towards (for) which the link to the next hop of the mesh path to this destination mesh STA is no longer usable. “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 131: moved for CID4133, to change the resolution to: Principle, change the definition of unreachable destination in Clause 3 to: "unreachable destination : A destination mesh station (STA) towards (for) which the link to the next hop of the mesh path to this destination mesh STA is no longer usable. “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


  • f) use of shall, relates to CID4169: Adopted resolution text seems not to be actionable. We may want to review the text for safety measure.



Motion 132: moved for CID4169, to change the resolution to: Principle, “Replace "Because a mesh STA does not establish a mesh peering with a mesh STA using a different BSSBasicRateSet, all mesh STAs in an MBSS" with "All mesh STAs in an MBSS ".“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 132: moved for CID4169, to change the resolution to: Principle, “Replace "Because a mesh STA does not establish a mesh peering with a mesh STA using a different BSSBasicRateSet, all mesh STAs in an MBSS" with "All mesh STAs in an MBSS ".“ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Issue : g) TXOP starts, relates to 4171: Adopted resolution text seems not to match with the description in the base standard. I did not implement this change in D11.02. We may want to review the text for safety measure.

  • Issue : g) TXOP starts, relates to 4171: Adopted resolution text seems not to match with the description in the base standard. I did not implement this change in D11.02. We may want to review the text for safety measure.



Motion 133: moved for CID4171, to change the resolution to: Principle, “ “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

  • Motion 133: moved for CID4171, to change the resolution to: Principle, “ “ and direct the editor to include the changes into the Draft when preparing Draft 12.0, prior to the opening of the recirculation ballot.

    • Mover: Seconder:
    • Yes: No: Abstain:


Issue : i) In front matter page iv, D11.02 still lacks the list of major contributors. Probably, it needs to be filled in before we exit sponsor ballot process.

  • Issue : i) In front matter page iv, D11.02 still lacks the list of major contributors. Probably, it needs to be filled in before we exit sponsor ballot process.

  • E.g. CRC Dan, Jarrko, Michael, check for officers Dee, Guido, Guenael, Kaz, check former officers

  • Peter Yee, John Pietro (1X), Ashish Shukla (CS), Rene Purndai, Stephen McCann (Emergency), Meiyuan Zhao, Jesse Walker (4way handshake), David Hunter, Javier Cardona, Michelle Gong

  • Harish Ramamurthy, Youko Omori, Liwen Chu, Steve Emmiot, Tony Braskich, Bahareh Sadeghi, Sandesh Goel, Amy Zhang, Yongho Zheok, Zhen Xie, Mathilde, Jan Kruys, Alexander Safonov, Jorgeta, Hrishikesh Gossain, Kevin Hayes, Shantanu



Open ends: timings

  • Open ends: timings



Other items to discuss

  • Other items to discuss

  • Adjourn sine die

  • TGs Motto: Perfection is achieved not when there is nothing left to add but when there is nothing left to take away.



  • Updated PAR at http://standards.ieee.org/board/nes/projects/802-11s.pdf.

    • Original PAR for IEEE 802.11 ESS Mesh: 11-04/54r2. Original Five Criteria for IEEE 802.11 ESS Mesh: 11-04/56r1.
  • Comment Resolution Spreadsheet:

    • 11-10/ 32r3 Resolution of Letter Ballot #159 Comments


TGs Chairmen

  • TGs Chairmen

    • Dee Denteneer,
    • Guido R. Hiertz (temporary Chairman), September 2009
    • Stuart J. Kerry (temporary Chairman), June 2009
    • Donald Eastlake 3rd, May 2004 – December 2009
  • TGs Technical Editors:

    • Kazuyuki Sakoda (Sony), Draft 2.03 … D3.0 …
    • Anthony Maida (3eTI), Drafts 2.01 & D2.02
    • Avinash Joshi (Motorola), Drafts 1.09 … D2.0
    • W. Steven Conner (Intel). Drafts 0.01 … D1.08 (also chair of the first Mesh Study Group Session)


Task Group “s” Meeting Minutes

  • Task Group “s” Meeting Minutes

    • January 2010, Los Angeles, CA, 11-10/102r0
    • November 2009, Atlanta, Georgia, 11-09/1223/0
    • September 2009, Waikoloa, Hawai‘i, 11-09/1016r0
    • December 2009, San Francisco, California, 11-09/902r0
    • May 2009, Montreal, Quebec, 11-09/595r0
    • March 2009, Vancouver, British Columbia, 11-09/312r0
    • January 2009, Los Angeles, California, 11-09/110r0
    • November 2008, Dallas, Texas, 11-08/1431r0
    • September 2008, Waikoloa, Hawaii, 11-08/1078r0
      • September 2008, ad hoc Meeting, Līhu‘e, Kaua‘i, Hawai‘i, 11-08/1038r0
    • December 2008, Denver, Colorado, 11-08/835r0



Do'stlaringiz bilan baham:


Ma'lumotlar bazasi mualliflik huquqi bilan himoyalangan ©fayllar.org 2017
ma'muriyatiga murojaat qiling