1 / 39

TGah MAC Ad Hoc Agenda and Report

TGah MAC Ad Hoc Agenda and Report. Authors:. Date: 2013-15-07. Agenda for July 2013 –Geneva, CH. Call the meeting to order. Designation of a secretary for the minutes. Reminder on Affiliation, IEEE 802 and IEEE 802.11 IPR policies and procedures; call for awareness.

shakti
Télécharger la présentation

TGah MAC Ad Hoc Agenda and Report

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. TGah MAC Ad Hoc Agenda and Report Authors: Date: 2013-15-07 Merlin, Liu, Shao

  2. Agenda for July 2013 –Geneva, CH • Call the meeting to order. • Designation of a secretary for the minutes. • Reminder on Affiliation, IEEE 802 and IEEE 802.11 IPR policies and procedures; call for awareness. • Reminder to record attendance. • Proposed agenda: • Reminder of the Ad-hoc operating rules • Call for submissions for comment resolution • Call for submissions other than for comment resolution • Address submissions for comment resolution • Address submissions not for comment resolution • Adjourn Merlin, Liu, Shao

  3. Submissions and notes Merlin, Liu, Shao

  4. Interpretive guide • Text coloring: • Black = pending agenda item • Red = item partially addressed • Green = item completed • Gray = item not addressed in the session indicated at the top of the slide Merlin, Liu, Shao

  5. Submissions for Comment Resolution (1) • MAC, YonghoSeok • 11-13-0769-00-00ah-CC9-clause-10-1-4-3-4-and-8-3-4a-2-1-comment-resolution • 763, 921, 902, 105, 901 (No comments) • 11-13-0770-00-00ah-CC9-clause-10-43b-and-8-4-2-170d-comment-resolution • 76, 92, 243, 409, 61 (No comments) • 11-13-0771-00-00ah-CC9-cluase-9-3-2-8-comment-resolution • 665, 663, 664 (No comments) • 11-13-0772-00-00ah-CC9-cluase-9-3-6-and-9-32n-comment-resolution • 701, 703, 704, 865, 515, 881, 255 (Note: Minor editorial corrections; will become r1) • 11-13-0773-00-00ah-CC9-cluase-9-7-6-6-and-9-19-2-4-comment-resolution • 248, 306, 883, 75, 247, 882, 884 (Note: Technical change on 882 will become r1) • 11-13-0774-00-00ah-CC9-cluase-9-17b-comment-resolution • 414, 965, 964, 269, 907, 77, 120, 833, 78 (833 deferred, as indicated in r1) (resolved on Wed AM1) David Halasz (Qualcomm)

  6. Submissions for Comment Resolution (1b) • 11-13-0775-00-00ah-CC9-cluase-9-19-2-7-comment-resolution • 909, 910, 121, 307 (no comments) • 11-13-0776-00-00ah-CC9-cluase-9-19-4a-1-comment-resolution • 593, 594, 854, 908, 911, 249, 165, 122, 46, 853 (Tech Change on 908, will be r1) • 11-13-0777-00-00ah-CC9-cluase-9-19-4a-2-comment-resolution • 596, 48, 602, 309, 49, 215, 309, 595, 855 (note: Minor editorial, will become r1; No comments) TUE PM2 • 11-13-0778-00-00ah-CC9-cluase-9-19-4a-5-comment-resolution • 599, 310, 311, 367(No Comments) • 11-13-0779-00-00ah-CC9-EDCA-channel-access-comment-resolution • 866, 863 (Minor editorial, will be r1) • 11-13-0780-00-00ah-CC9-miscellaneous-comment-resolution • 344, 401, 773, 774, 877, 870 (No comments) Merlin, Liu, Shao

  7. Submissions for Comment Resolution (1c) WED AM1 • Discussion on n 833 11-13-0774-03-00ah-CC9-cluase-9-17b-comment-resolutio • (No comments) • 11-13-0781-00-00ah-CC9-probe-resp-bandwidth-selection-comment-resolution • 868 (No comments) • 11-13-0782-00-00ah-CC9-SST-sounding-comment-resolution • 867 Merlin, Liu, Shao

  8. Submissions for Comment Resolution (2) • MAC, Minyoung Park • Comment resolutions on subclause 9.32h • 11-13-0783-00-00ah • CIDs 58, 107, 916, 917 (No comments) • Comment resolution on subclause 9.19.4a.3 • 11-13-0784-00-00ah • CIDs 123, 366,966, 967 • (discussion, will be r1) • Comment resolution on subclause 10.3.7 • 11-13-0785-00-00ah • CID 186, 482 (Will be r1) David Halasz (Qualcomm)

  9. Submissions for Comment Resolution (3) • MAC, Hongyuan Zhang • 11-13-0716-00-00ah-d01-MIMO-Control-Field-comment-resolutions • For MAC CIDs 106, 359, 830—i.e. for 8.4.1.47. David Halasz (Qualcomm)

  10. Submissions for Comment Resolution (4) • YounghoonKwon • Doc. Number: 808 • Title: cc09 comment resolution for clause 8.3.4a.1.2 • Addressing CIDs: 104, 223, 899 (MAC) • Doc. Number: 809 • Title: cc09 comment resolution for clause 9.19.4a.6 • Addressing CIDs: 52, 557, 788 (MAC) • Doc. Number: 810 • Title: cc09 comment resolution for clause 9.32n.3.2 • Addressing CIDs: 513, 514, 714, 715 (MAC) • Doc. Number: 811 • Title: cc09 comment resolution for CID 520 • Addressing CID: 520 (MAC) David Halasz (Qualcomm)

  11. Submissions for Comment Resolution (5) • Wang Haiguang • CC9-Comments-Resolution-CIDs-546+906 • IEEE-802.11-13/0827r0 • CIDs 546, 906 • CC9-Comments-Resolution-CIDs-176+177+178+179+180+181+776 • IEEE-802.11-13/0830r0 • CIDs 176, 177, 178, 179, 180, 181, 776 • CC9-Comments-Resolution-CIDs-887 • IEEE-802.11-13/0831r0 • CIDs 887 David Halasz (Qualcomm)

  12. Submissions for Comment Resolution (6) Alfred Asterjadhi 11-13-0812-00-00ah-CC9-Resolution-CIDs-8+10+17+19+321+581 11-13-0814-00-00ah-CC9-Resolution-CIDs-14+253+484+485+486 11-13-0815-00-00ah-CC9-Resolution-CIDs-15+59+168 11-13-0816-00-00ah-CC9-Resolution-CIDs-18+119+360+532+533+660+661+662+869 11-13-0817-00-00ah-CC9-Resolution-CIDs-20+111+336+625+814 11-13-0818-00-00ah-CC9-Resolution-CIDs-23+275+276+277+278 11-13-0820-00-00ah-CC9-Resolution-CIDs-32+54+187+188+240+417+543+821 11-13-0821-00-00ah-CC9-Resolution-CIDs-254+303+304+305+324+363+364+745+841+961+962+985 11-13-0822-00-00ah-CC9-Resolution-CIDs-746+747+748+924 11-13-0823-00-00ah-CC9-Resolution-CIDs-74+562+914+915 11-13-0824-00-00ah-CC9-Resolution-CIDs-12+560+561+563 11-13-0825-00-00ah-CC9-Resolution-CIDs-27 David Halasz (Qualcomm)

  13. Submissions for Comment Resolution (7) • Mitsuru Iwaoka • 11/13-0793 CC9 Comment Resolutions for CID 395,396,399,400,524,525,529,547,624 • For MAC comments of CID 395,396,399,400,524,525,529,547 and 624 • The resolution of CID 547 may depend on CID 74 and 562, and need some days to upload. David Halasz (Qualcomm)

  14. Submissions for Comment Resolution (8) • Yuan Zhou • DCN 0832- CC9-Comments-Resolution-CID-927 • DCN 0833- CC9-Comments-Resolution-CIDs-85+460+928               • DCN-0834- CC9-Comments-Resolution-CIDs-473+474  David Halasz (Qualcomm)

  15. Submissions for Comment Resolution (9) • ChittabrataGhosh • 11-13-0813-00-00ah-cc09-comment-resolution-for-clause-8-4-2-170b.docs • 11-13-0819-00-00ah-cc09-comment-resolution-for-clause-9-32j.docx • 11-13-XXXX-00-00ah-cc09-comment-resolution-for-clause-CIDs169-170.docx David Halasz (Qualcomm)

  16. Submissions for Comment Resolution (10) • Ron Murias • 13/0848 "CC9 Comment resolution for MAC CIDs related to Grouping" • Addresses 98, 618, 619, 897, 929 MAC related CIDs David Halasz (Qualcomm)

  17. Submissions for Comment Resolution (11) • JeongkiKim • 11-13-0838-00-00ah-cc9-comment-resolution-for-CID224 • 11-13-0839-00-00ah-cc9-comment-resolution-for-CID143-144-245 David Halasz (Qualcomm)

  18. Submissions for Comment Resolution (12) • Jinsoo Choi • 13/0851 CC9-subclause-8-3-4-15b-comment-resolution • CID 149, 246, 404 • 13/0857 CC9-subclause-8-4-1-6-comment-resolution • CID 80, 405, 406, 959 David Halasz (Qualcomm)

  19. Submissions for Comment Resolution (13) • Shou Kang (Haiguang will present) • 11-13-0887-00-00ah subclause 9.32g.3 (uploaded) • CIDs 36,38, 39, 40, 63, 968 • 11-13-0888-00-00ah subclause 9.32g.4 (uploaded) • CIDs 257,258,988 • 11-13-0889-00-00ah subclause 8.2.4.1.3 (uploaded) • CID 93 • 11-13-0891-00-00ah subclause 9.32n.3 and 9.32n.3.1 (not uploaded yet) • CID 749,750, 751, 981,982,983,984, 261,262 and 263 (these three CIDs are handled by Kaiying but may be combined) David Halasz (Qualcomm)

  20. MAC ad hoc Straw Polls Merlin, Liu, Shao

  21. Straw Poll 1 Template - Text Y: N: A: (Session: AM/PM N) Merlin, Liu, Shao

  22. MAC ad hoc Pre-Motions to be brought for vote in TGahtask group Merlin, Liu, Shao

  23. Pre-Motion 1 • Do you agree with the resolution of the following CIDs: • 11-13-0769-00-00ah-CC9-clause-10-1-4-3-4-and-8-3-4a-2-1-comment-resolution • 763, 921, 902, 105, 901 • 11-13-0770-00-00ah-CC9-clause-10-43b-and-8-4-2-170d-comment-resolution • 76, 92, 243, 409, 61 • 11-13-0771-00-00ah-CC9-cluase-9-3-2-8-comment-resolution • 665, 663, 664 • 11-13-0772-01-00ah-CC9-cluase-9-3-6-and-9-32n-comment-resolution • 701, 703, 704, 865, 515, 881, 255 • 11-13-0773-01-00ah-CC9-cluase-9-7-6-6-and-9-19-2-4-comment-resolution • 248, 306, 883, 75, 247, 882, 884 • 11-13-0774-01-00ah-CC9-cluase-9-17b-comment-resolution • 414, 965, 964, 269, 907, 77, 120,78, (833 deferred) (continues on the next slide) • (Session: Mon PM2) Merlin, Liu, Shao

  24. Pre-Motion 1 (Continued) • 11-13-0775-00-00ah-CC9-cluase-9-19-2-7-comment-resolution • 909, 910, 121, 307 • 11-13-0776-01-00ah-CC9-cluase-9-19-4a-1-comment-resolution • 593, 594, 854, 908, 911, 249, 165, 122, 46, 853 • Pre motion passed with unanimous consent Merlin, Liu, Shao

  25. Pre-Motion 2 • Do you agree with the resolution of the following CIDs: • 11-13-0777-01-00ah-CC9-cluase-9-19-4a-2-comment-resolution • 596, 48, 602, 309, 49, 215, 309, 595, 855 • 11-13-0778-00-00ah-CC9-cluase-9-19-4a-5-comment-resolution • 599, 310, 311, 367 • 11-13-0779-01-00ah-CC9-EDCA-channel-access-comment-resolution • 866, 863 • 11-13-0780-00-00ah-CC9-miscellaneous-comment-resolution • 344, 401, 773, 774, 877, 870 • Pre motion passed with unanimous consent Merlin, Liu, Shao

  26. Pre-Motion 3 • Do you agree with the resolution of the following CIDs: • CID 833 in 11-13-0774-03-00ah-CC9-cluase-9-17b-comment-resolutio • 11-13-0781-00-00ah-CC9-probe-resp-bandwidth-selection-comment-resolution • 868 • 11-13-0782-00-00ah-CC9-SST-sounding-comment-resolution • 867 • Pre-motion passes with unanimous consent Merlin, Liu, Shao

  27. Pre-Motion 4 • Do you agree with the resolution of the following CIDs: • 11-13-0783-00-00ah • CIDs 58, 107, 916, 917 • 11-13-0784-01-00ah • CIDs 123, 366, 966, 967 • 11-13-0785-01-00ah • CID 186, 482 Pre-motion passes with unanimous consent Merlin, Liu, Shao

  28. References • [1] 11-11-0239-02-00ah-proposed-selection-procedure.docx • [2] 11-11-1137-06-00ah-specification-framework-for-tgah.docx • [3] 11-11-0905-05-00ah-tgah-functional-requirements-and-evaluation-methodology.docx • [4] 12/0602 TGah-Spec-Development-Process (TBD) • [5] 11-10-0001-13-0wng-900mhz-par-and-5c.docx • [6] 11-12-0651-00-00ah-TGah-Sub-Groups.pptx • [7] 12/591r8 TGah Agenda, May 2012 • [8] 12/672r0 PHY ad hoc Agenda Merlin, Liu, Shao

  29. Appendix Policies Merlin, Liu, Shao

  30. Instructions for the WG Chair The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: • Show slides #1 through #4 of this presentation • Advise the WG attendees that: • The IEEE’s patent policy is consistent with the ANSI patent policy and is described in Clause 6 of the IEEE-SA Standards Board Bylaws; • Early identification of patent claims which may be essential for the use of standards under development is strongly encouraged; • There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under development. • Instruct the WG Secretary to record in the minutes of the relevant WG meeting: • That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; • That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard • Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. • The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance. • It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 12 and 12a on inclusion of potential Essential Patent Claims by incorporation or by reference. Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board. Merlin, Liu, Shao

  31. Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. Participants: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents orpatent claims • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) • The above does not apply if the patentclaim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2 • Early identification of holders of potential Essential Patent Claims is strongly encouraged • No duty to perform a patent search Slide #1 Merlin, Liu, Shao

  32. Patent Related Links 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 you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide #2 Merlin, Liu, Shao

  33. Call for Potentially Essential Patents • 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 Slide #3 Merlin, Liu, Shao

  34. Other Guidelines for IEEE WG Meetings • All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. • Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. • Don’t discuss specific license rates, terms, or conditions. • Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • Technical considerations remain primary focus • Don’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets. • Don’t discuss the status or substance of ongoing or threatened litigation. • Don’t be silent if inappropriate topics are discussed … do formally object. --------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Slide #4 Merlin, Liu, Shao

  35. Member Affiliation • It is defined in the IEEE-SA Standards Board Bylaws, 5.2.1.5 as: “An individual is deemed “affiliated” with any individual or entity that has been, or will be, financially or materially supporting that individual’s participation in a particular IEEE standards activity. This includes, but is not limited to, his or her employer and any individual or entity that has or will have, either directly or indirectly, requested, paid for, or otherwise sponsored his or her participation. • http://standards.ieee.org/faqs/affiliationFAQ.html Merlin, Liu, Shao

  36. Declaration of Affiliation • Revision: May 2007 Standards Board Bylaw 5.2.1.1 • 5.2.1.1 Openness • Openness is defined as the quality of being not restricted to a particular type or category of participants. All meetings involving standards development an all IEEE Sponsor ballots shall be open toa all interested parties. Each individual participant in IEEE Standards activities shall disclose his or her affiliations when requested. A person who knows or reasonably should know, that a participant’s disclosure is materially incomplete or incorrect should report that fact to the Secretary of the IEEE-SA Standards Board and the appropriate Sponsors. • http://standards.ieee.org/faqs/affiliationFAQ.html Merlin, Liu, Shao

  37. Affiliation Policy • Requirement to declare affiliation at all standards development meetings and recorded in the minutes • Affiliation not necessarily same as employer • Declaration requirement may be familiar to some 802 WGs, though WG declaration process may evolve • 11. What if I refuse to disclose my affiliation? • As outlined in IEEE-SA governance documents, you will lose certain rights. In a working group where voting rights are gained through attendance, no attendance credit will be granted if affiliation isn’t declared. Similarly, voting rights are to be removed if affiliation isn’t declared. • Affiliation declaration will be added to Sponsor ballot • http://standards.ieee.org/faqs/affiliationFAQ.html Merlin, Liu, Shao

  38. Review of ad hoc operating rules • The following summary is derived from 11-12/239r2 • Pre-Motion: A pre-motion (doesn’t require voting rights) result of >=75% is required within an Ad Hoc to approve the resolution of all or part of an issue and forward that resolved item to the Taskgroup where it becomes a motion that requires >=75% approval to modify the specification framework or the draft specification. • Note: the term Pre-Motion was introduced by11ac ad hoc operating rules to create a distinction between straw polls which intent is to result in a Motion at the Taskgroup, and strawpolls which intent is to only gauge the opinion of the members on a particular topic and are not intended to results in a motion at the Taskgroup. • Stalemate: In the case a consensus can not be reached within an Ad Hoc group (a stalemate that prohibits further progress), the subject is moved to the Taskgroup if an Ad Hoc straw poll vote to move the subject to the Taskgroup achieves >50% approval. Merlin, Liu, Shao

  39. Review of ad hoc operating rules Transfer to another ad hoc: A motion passing with >50% in the Taskgroup shall be sufficient to move an issue previously assigned to an Ad Hoc group to any Ad Hoc group. A straw poll vote of >50% is required in an Ad Hoc group to refuse an issue from the Taskgroup. Transfer to another ad hoc: An issue may be sent from one Ad Hoc to another if both the sending Ad Hoc and the receiving Ad Hoc approve straw polls for taking the respective actions with >50% approval. A notice should be sent to the reflector indicating the approval of a straw poll to move an issue. To be accepted into the Draft specification, proposals from Ad Hoc group require a motion that passes with >=75% Taskgroup approval Merlin, Liu, Shao

More Related