1. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 1 IEEE 802 JTC1 Standing Committee July 2013 agenda 16 July 2013 Authors: NameCompanyPhoneemail Andrew MylesCisco +61 2 84461010 +61 418 656587 amyles@cisco.com

2. doc.: IEEE 802.11-13/0711r0 Submission July 2013 This presentation will be used to run the IEEE 802 JTC1 SC meetings in Geneva in July 2013 This presentation contains a proposed running order for the IEEE 802 JTC1 Standing Committee meeting in July 2013, including –Proposed agenda –Other supporting material It will be modified during the meeting to include motions, straw polls and other material referred to during the meeting Andrew Myles, CiscoSlide 2

3. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 3 Participants have a duty to inform in relation to patents All participants in this meeting have certain obligations under the IEEE- SA Patent Policy (IEEE-SA SB Bylaws subclause 6.2). 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 or patent 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 patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged; there is no duty to perform a patent search

4. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 4 There are a variety of 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.htmlhttp://standards.ieee.org/board/pat/pat-material.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.orgpatcom@ieee.org –or visit http://standards.ieee.org/board/pat/index.htmlhttp://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat- slideset.ppt

5. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 5 A call for potentially essential patents is not required in the IEEE 802 JTC1 SC 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

6. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 6 The IEEE 802 JTC1 SC will operate using general guidelines for IEEE-SA 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.

7. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 7 Links are available to a variety of other useful resources Link to IEEE Disclosure of Affiliation –http://standards.ieee.org/faqs/affiliationFAQ.htmlhttp://standards.ieee.org/faqs/affiliationFAQ.html Links to IEEE Antitrust Guidelines –http://standards.ieee.org/resources/antitrust-guidelines.pdfhttp://standards.ieee.org/resources/antitrust-guidelines.pdf Link to IEEE Code of Ethics –http://www.ieee.org/web/membership/ethics/code_ethics.htmlhttp://www.ieee.org/web/membership/ethics/code_ethics.html Link to IEEE Patent Policy –http://standards.ieee.org/board/pat/pat-slideset.ppthttp://standards.ieee.org/board/pat/pat-slideset.ppt

8. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 8 The IEEE 802 JTC1 SC will operate using accepted principles of meeting etiquette IEEE 802 is a world-wide professional technical organization Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization. Individuals are to address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter.

9. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Call to Order Select recording secretary <- important! Approve agenda Details on next page Conduct meeting according to agenda Recess Call to Order Select recording secretary <- important! Conduct meeting according to agenda Recess The IEEE 802 JTC1 SC has three normal slots at the Geneva plenary meeting Andrew Myles, Cisco Call to Order Select recording secretary <- important! Conduct meeting according to agenda Adjourn Tuesday 16 July, PM1 Wednesday 17 July, PM1 Thursday 18 July, PM1

10. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC has a detailed list of agenda items to be considered In no particular order: Approve minutes –From interim meeting in May 2013 in Hawaii Review extended goals –From IEEE 802 ExCom in Nov 2010 Review outcomes of SC6 meeting Korea –Review attendance –Review WG1 and WG7 agendas –Review liaisons of drafts to SC6 –Review notifications of projects to SC6 –Review IEEE 802 overviews –Review withdrawal of IEEE 802 related ISO/IEC standards Andrew Myles, CiscoSlide 10

11. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC has a detailed list of agenda items to be considered In no particular order:.. review outcomes of SC6 meeting Korea –Review ISO/.IEC ballots on IEEE 802 standards –Review collaboration agreement –Review TEPA-AC discussions –Review TLSec discussions –Review TAAA discussions –Review outcomes of security discussions –Review WAPI discussions –Review TISec discussions –Review WLAN Cloud discussions –Review Optimization technology in WLAN discussions –Review IEEE 1888 discussions Andrew Myles, CiscoSlide 11

12. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC has a detailed list of agenda items to be considered In no particular order: Consider other topics –Discuss EUHT status –Discuss numbering of 8802-1 amendments –Discuss next SC6 meeting –Discuss PSDO status Consider any motions Consider activity in September Andrew Myles, CiscoSlide 12

13. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 13 The IEEE 802 JTC1 SC will consider approving its agenda Motion to approve agenda The IEEE 802 JTC1 SC approves the agenda for its meeting in Geneva in July 2013, as documented on pages 11-12 of Moved: Seconded: Result:

14. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC will consider approval of previous minutes Motion to approve minutes The IEEE 802 JTC1 SC approves the minutes for its meeting in Hawaii in May 2013, as documented in 11-13-0655-r0 Moved: Seconded: Result: Andrew Myles, CiscoSlide 14

15. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC will consider approval of previous minutes (special EUHT meeting) Motion to approve minutes The IEEE 802 JTC1 SC approves the minutes for its meeting related to EUHT in Hawaii in May 2013, as documented in 11-13-0640r0 Moved: Seconded: Result: Andrew Myles, CiscoSlide 15

16. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 16 The IEEE 802 JTC1 SC reaffirmed its general goals in Sept 09, but they were extended in Nov 2010 Agreed (with changes from Nov 2010) goals Provides a forum for 802 members to discuss issues relevant to both: –IEEE 802 –ISO/IEC JTC1/SC6 Recommends positions to ExCom on ISO/IEC JTC1/SC6 actions affecting IEEE 802 –Note that 802 LMSC holds the liaison to SC6, not 802.11 WG Participates in dialog with IEEE staff and 802 ExCom on issues concerning IEEE ’s relationship with ISO/IEC Organises IEEE 802 members to contribute to liaisons and other documents relevant to the ISO/IEC JTC1/SC6 members Extensions The extensions to our goals came out of the 802 ExCom ad hoc held in November 2010 on the Friday evening

17. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The attendance at the SC6 meeting in Korea from P- Member NBs was disappointing Only four out of twenty P-Members attended SC6 meeting –China, Korea, US, Switzerland In addition, three P-Members attended the closing plenary via teleconference –UK, Netherlands, Austria Technically a NBs is supposed to be warned if it “has been persistently inactive and has failed to make a contribution to 2 consecutive meetings, either by direct participation or by correspondence” (JTC1 Directives) The list of P-Members in this category probably include: –Greece, Russian Federation, Kazakhstan, Luxembourg, Tunisia, Kenya, Belgium, Finland, Czech Republic Other P-Members not in attendance were: –Canada, Spain, Germany, Japan Andrew Myles, CiscoSlide 17

18. doc.: IEEE 802.11-13/0711r0 Submission July 2013 A number of liaison organisations also attended the SC6 meeting in Korea IEEE 802 –Bruce Kraemer was HoD –Dan Harkins (802.11) –Bill Carney (802.11) –Jodi Haasz (IEEE staff) –Tony Jeffree (802.1) –Meng Zhao (IEEE staff) IEEE 1888 Ecma International ISOC –Sean Turner Andrew Myles, CiscoSlide 18

19. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The final SC6/WG1 agenda had a number of items of interest to IEEE 802 The final agenda was N15670 Items of interest to IEEE 802 included: –5.3.1 Drafts for review — IEEE 802 drafts liaised to SC6 –5.3.2 Liaison Overviews — Presentations about status of 802, 802.1, 802.3, 802.11 –5.3.3 Ballot Submissions — Submission under PSDO of 802.1X/AE/AR/AB/AS, 802.11aa/ad/ae, 802.3 –5.3.4 Summary of Voting — Votes summaries under PSDO of 802.1X/AE/AR/AB/AS, 802.11aa/ad/ae, 802.3 –5.3.5 Ballot Comments & Responses — IEEE responses to comment during ballots –5.3.6 Procedures — Mainly related to collaboration procedures –5.3.7 Network security — Discussion of 802.1X ve TePA/KA4, TePA-AC, TAAA, TLSec Andrew Myles, Cisco Slide 19

20. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The final SC6/WG7 agenda had a number of items of interest to IEEE 802 The final agenda was N15660 Items of interest to IEEE 802 included: –16. Collaboration with IEEE-SA on IEEE 1888 –17. Other WG 7 related Issue — Discussion of TISec — Discussion of “WLAN Cloud” — Discussion of “Optimization technology in WLAN” Andrew Myles, Cisco Slide 20

21. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802.11 WG has liaised various Sponsor Ballot drafts to ISO/IEC JTC1/SC6 Normally the 802.11 WG liaises Sponsor Ballot documents. However, the WG told SC6 it would liaise 802.11ac as soon as it passed a LB; we continue to do so! Andrew Myles, CiscoSlide 21 Task Group After Hawaii After Atlanta After San Diego After Palm Sp After San Antonio After Van. After Orlando After Hawaii Mar 12May 12July 12Sept 12Nov 12Jan 13Mar 13May 13 TGaeRatified------- TGaaRatified------- TGac-D3.0--D4.0D5.0-- TGadD6.0/D7.0D8.0D9.0-Ratified--- TGmbRatified------- TGaf--------

22. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 802 has started a process of notifying SC6 of new projects Notifications this year are: –N15543 (21 Jan 2013) notified formation of four study groups — IEEE 802, "OmniRAN" EC Study Group — IEEE 802.3 "Next Generation BASE-T" Study Group — IEEE 802.3 "Distinguished Minimum Latency Traffic in a Converged Traffic Environment" Study Group — IEEE 802.15 "Layer 2 Routing" Study Group –N15665 (13 June 2013) notified formation of one study group — IEEE 802.11 HEW Study Group IEEE 802 WG Chairs are asked to inform Bruce Kraemer (IEEE 802 Liaison to SC6 when new activities start Andrew Myles, CiscoSlide 22

23. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 delegation in Korea provided an overview of current IEEE 802 activities Overviews provided N15655: Overview of IEEE 802 N15654: Overview of IEEE 802.1 N15653: Overview of IEEE 802.3 N15652: Overview of IEEE 802.11 Andrew Myles, CiscoSlide 23

24. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 802 suggested updating the list of IEEE 802 related ISO/IEC standards Andrew Myles, CiscoSlide 24 ProjectNumberYearNameRecommendation 05.01.008802-12011SPECIFIC LANS OverviewRetain. IEEE 802 will provide a replacement based upon the revision of 802 O&A (anticipated in 2014) 05.01.018802-1-SPECIFIC LANS Cooperative agreement with IEEE 802 Cancel project. Delete the draft. 05.02.008802-21998SPECIFIC LANS Logical Link Control 90.93 Retain in stabilized state 05.03.008802-32000SPECIFIC LANS CSMA/CD Edn. 6Retain. Will be superseded as soon the next revision of IEEE 802.3 is ratified by ISO/IEC. The ballot process on 802.3-2012 in ISO/IEC JTC1 has started 05.05.008802-51998SPECIFIC LANS Token Ring. Edn.3Retain in stabilized state 05.11.008802-112005LANS. Wireless MAC/PHY specifications Edn. 2 Withdraw. Has been superseded by ISO/IEC 802-11:2012 05.21.0111802-12005LAN GUIDELINES LLC AddressesWithdraw standard. This has been transferred to the IEEE Registration Authority. The registry will be referenced in the revision of 8802-1 05.22.0111802-22005LAN GUIDELINES Standard group MAC addresses Withdraw standard. This has been transferred to the IEEE Registration Authority. The registry will be referenced in the revision of 8802-1 05.25.0011802-51997Media Access Control (MAC) Bridging of Ethernet v2.0 in Local Area Network Retain in stabilized state. 05.31.0015802-11995COMMON LANS MAC serviceRetain. IEEE 802 will provide a replacement based upon 802.1AC (anticipated in 2014) 05.33.0015802-31998COMMON LANS MAC bridgesRetain. IEEE 802 will provide a replacement based upon the revision of 802.1Q (anticipated in 2014)

25. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 suggestion to updating the list of IEEE 802 related ISO/IEC standards was accepted Resolution 6.1.4 SC 6 approves the withdrawal of standards as shown below. SC 6 has transferred the registration function to the IEEE Registration Authority. These standards are no longer up-to-date. Note: –The IEEE Registration Authority page that documents the material/registry for LLC addresses: — http://standards.ieee.org/develop/regauth/llc/index.html http://standards.ieee.org/develop/regauth/llc/index.html –For Standard Group MAC addresses: — http://standards.ieee.org/develop/regauth/grpmac/index.html http://standards.ieee.org/develop/regauth/grpmac/index.html Andrew Myles, CiscoSlide 25 Designation #TitleProject editor 11802-1:2005LAN Guidelines LLC AddressesP. Cowell 11802-2:2005LAN Guidelines Standard group MAC addressesP. Cowell

26. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 802 has submitted ten standards for ratification under the PSDO IEEE 802 standard 60 day pre-balllot 5 month FDIS ballot 802.11Passed in 2012 802.11aaPassed in Feb 2013Not started 802.11adPassed in Feb 2013Not started 802.11aePassed in Feb 2013Not started 802.1XPassed in 2013Closes 16 Oct 2014 802.1AEPassed in 2013Closes 16 Oct 2014 802.1ABPassed in May 2013Not started 802.1ARPassed in May 2013Not started 802.1ASPassed in May 2013Not started 802.3Passed in 2013Waiting on 802.3 WG Andrew Myles, CiscoSlide 26

27. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 802.11-2012 has been ratified as ISO/IEC 8802- 11:2012 Andrew Myles, CiscoSlide 27 60 day pre-ballot: passed in 2012 FDIS ballot: passed in 2012 All comments have been submitted to TGmc for processing Additional comments from Swiss NB in N15623 (a response to the IEEE 802/SC6 collaboration procedure) have also been referred to TGmc The China NB stated in N15591 that they will continue disapproving ISO/IEC 8802-11 until their comments are revolved –It is appears this statement has little real effect — It does not affect any ISO/IEC processes — China is probably required under WTO rules to respect ISO/IEC 8802-11:2012 as an international standard — The reality is that ISO/IEC 8802-11:2012 is being widely used in China today, including 802.11i based security

28. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.1X closes in October 2013 Andrew Myles, CiscoSlide 28 60 day pre-ballot: passed in 2013 Submission in N15515 Voting results in N15555 –Comments from China NB replied to by IEEE 802 in N15607 –The China NB stated in Korea that they will reply in detail to the IEEE 802.1 WG response at a later time FDIS ballot: closes 16 October 2013

29. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.1AE closes in October 2013 Andrew Myles, CiscoSlide 29 60 day pre-ballot: passed in 2013 Submission in N15516 Voting results in N15556 –Comments from China NB replied to by IEEE 802 in N15608 –The China NB stated in Korea that they will reply in detail to the IEEE 802.1 WG response at a later time FDIS ballot: closes 16 October 2013

30. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.11ae is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 30 60 day pre-ballot: passed in Feb 2013 Submission in N15552 Voting results in N15599 –Comments from China replied to by IEEE 802 in N15647 — The China NB comments are based on their disapproval of IEEE 802.11-2012 — IEEE 802 referred China NB to disposition of comments on IEEE 802.11-2012 –Comments from Japan in N15664 — These comments expressed a concern about having too many amendments outstanding — Japan NB has informally accepted idea that IEEE 802 should be responsible for all maintenance processes FDIS ballot: waiting for start

31. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.11ad is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 31 60 day pre-ballot: passed in Feb 2013 Submission in N15553 Voting results in N15601 –Comments from China replied to by IEEE 802 in N15647 — The China NB comments are based on their disapproval of IEEE 802.11-2012 — IEEE 802 referred China NB to disposition of comments on IEEE 802.11-2012 –Comments from Japan in N15664 — These comments expressed a concern about having too many amendments outstanding — Japan NB has informally accepted idea that IEEE 802 should be responsible for all maintenance processes FDIS ballot: waiting for start

32. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.11aa is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 32 60 day pre-ballot: passed in Feb 2013 Submission in N15554 Voting results in N15602 –Comments from China replied to by IEEE 802 in N15647 — The China NB comments are based on their disapproval of IEEE 802.11-2012 — IEEE 802 referred China NB to disposition of comments on IEEE 802.11-2012 –Comments from Japan in N15664 — These comments expressed a concern about having too many amendments outstanding — Japan NB has informally accepted idea that IEEE 802 should be responsible for all maintenance processes FDIS ballot: waiting for start

33. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.1AB is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 33 60 day pre-ballot: passed in Feb 2013 Submission in N15588 Voting results in N15626 –Comments from China replied to in N15659 FDIS ballot: waiting for start

34. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.1AR is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 34 60 day pre-ballot: passed in May 2013 Submission in N15589 Voting results in N15627 –Comments from China replied to in N15659 FDIS ballot: waiting for start

35. doc.: IEEE 802.11-13/0711r0 Submission July 2013 FDIS on 802.1AS is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot Andrew Myles, CiscoSlide 35 60 day pre-ballot: passed in May 2013 Submission in N15590 Voting results in N15628 –Comments from China replied to in N15659 FDIS ballot: waiting for start

36. doc.: IEEE 802.11-13/0711r0 Submission July 2013 802.3-2012 passed the pre-ballot, and is awaiting a response from 802.3 Maintenance TF Andrew Myles, CiscoSlide 36 60 day pre-ballot: passed in May 2013 Submission in N15595 Voting results in N15632 –Comments from China awaiting response from 802.3 Maintenance TF, which will be considered at Geneva plenary meeting FDIS ballot: waiting for 802.3 WG comment response

37. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The only comment on 802.3-2012 came from China NB China NB comment China NB thanks for IEEE’s contribution of 802.3-2012 (in 6N15595). As always China encourages and supports standard collaboration between IEEE and ISO. However, based on the following reasons, China NB cannot support the three proposals. IEEE 802.3-2012 does not contain security related standards. As an information network standard, the lack of security protocols is a major concern. The standard is not robust. The standard referenced IEEE 802.1AE, which has security concerns. China NB has made many comments on this issue to SC6 and IEEE as in SC6N15556. However, IEEE has not made any satisfactory attempts to change China’s negative vote. Since China’s objection to the base/associated standards still stands, we cannot support other standards that rely on previous standards on security. In addition, China NB also has concerns that the FDIS process is reducing the quality and reputation of ISO/IEC standards. We will bring our concerns to the attention of ISO/IEC central offices. Andrew Myles, CiscoSlide 37

38. doc.: IEEE 802.11-13/0711r0 Submission July 2013 In Sept 2012, SC6 agreed to give IEEE 802 WGs responsibility for revision of ISO/IEC 8802 standards SC6 agreed on a resolution with respect to 802.11 (Res 6.1.9) that gave 802.11 WG responsibility for revision of ISO/IEC 8802-11 standards –As empowered by clause A1.2.1 of the PSDO agreement between ISO and IEEE, SC6 decides to allocate responsibility for the revision process of the ISO/IEC 8802-11 standard to the IEEE 802.11 WG while the IEEE 802.11 WG has an ongoing revision process for the IEEE 802.11 standard. –A condition of this motion is that SC6 and its NBs have access to an established mechanism to contribute to the revision process in the IEEE 802.11 WG SC6 passed similar resolutions with respect to 802.1 (Res 6.1.10) & 802.3 (Res 6.1.11) In addition, SC6 passed a cooperation resolution (Res 6.1.12) –SC 6 invites the IEEE 802 WG’s to exchange information about new work items that are within the scope of SC 6 and the respective IEEE 802 WG for information and potential coordination Andrew Myles, CiscoSlide 38

39. doc.: IEEE 802.11-13/0711r0 Submission July 2013 In March 2013, IEEE 802 liaised a proposed collaboration and revision process to SC6 IEEE 802 agreed on a response to the requirement for IEEE 802 to propose a way for … – “SC6 and its NBs (to) have access to an established mechanism to contribute to the revision process in the IEEE 802.11” … as well as IEEE 802.1 and IEEE 802.3 The proposal also responds to the invitation for the: – “IEEE 802 WG’s to exchange information about new work items that are within the scope of SC 6 and the respective IEEE 802 WG for information and potential coordination” The revised proposed document was approved in March 2013 and subsequently liaised to SC6 –See N15606 Andrew Myles, CiscoSlide 39

40. doc.: IEEE 802.11-13/0711r0 Submission July 2013 In Korea in June 2013, SC6 accepted the proposed IEEE 802/SC6 collaboration procedures The Swiss NB commented positively in N15623 on the proposed collaboration procedures SC6 also responded positively and unanimously passed a resolution to that effect –SC 6 thanks IEEE 802 for providing (as documented in 6N15606) SC 6 NBs access to mechanisms to contribute to the revision process in the IEEE 802.1/3/11 Working Groups and encourages SC 6 NBs and experts to utilize these mechanisms. Great job by the IEEE 802 team! Andrew Myles, CiscoSlide 40

41. doc.: IEEE 802.11-13/0711r0 Submission July 2013 TePA-AC, the 802.1X replacement, was approved as a Chinese National Standard in Oct 12 In previous SC6 meetings the China NB have proposed a protocol called TePA-AC, which is roughly an 802.1X replacement At the SC6 meeting in February 2012, an IWNCOMM representative presented TePA-AC again, emphasising its use of TePA, and concluding –“Network access control is widely used in many network environments. –TePA-AC in N14399 is different from IEEE 802.1x.” IWNCOMM claimed that TePA-AC covered a different application space from 802.1X The discussion concluded with the China NB informing SC6 that further standardisation work on TePA-AC would continue in BWIPS –BWIPS is the organisation under CESI that standardised WAPI –TEPA-AC is a Chinese National standard as GB / T 28455-2012 as of 1 Oct 12; the “T” means it is recommended, ie not mandatory (227 pages in Chinese) Andrew Myles, CiscoSlide 41

42. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The Swiss NB has contributed a document to SC6 comparing “TePAKA4 and IEEE 802.1X Security” Hans-Rudolf Thomann from the Swiss NB has generated a document (N15523) titled, “A Comparative Analysis of TePAKA4 and IEEE 802.1X Security” The IEEE 802 responded (6N15646) with an alternative analysis that concluded –There is no reason to consider unjustifiable alternatives to existing technology which work fine in practice The Swiss NB followed up with another paper (N15662) that suggested inviting the IEEE 802 LMSC to continue the evaluation of the IEEE LAN/MAN security architecture jointly with Sc6. Dan Harkins will report on the subsequent technical discussion –Hint: it did not reach any consensus Andrew Myles, CiscoSlide 42

43. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The China NB submitted a paper to SC6 claiming that an attack on 802.1X possible, which is not true! The China NB have claimed (N15513) an attack on 802.1X is possible and presented it in Korea The IEEE 802 delegation responded with a paper (N15558) refuting the claim Dan Harkins will report on the subsequent technical discussion –Hint: it did not reach any consensus Andrew Myles, CiscoSlide 43

44. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There is no further standardisation news in China related to TLSec, the proposed 802.1AE replacement In previous SC6 meetings the China NB have proposed a protocol called TLSec, which is roughly an 802.1AE replacement At the SC6 meeting in February 2012, an IWNCOMM representative presented TLSEc again, emphasising its use of TePA, and concluding –“It is necessary to do more research on LAN layer 2 security. –TLSec in N14402 is different from IEEE 802.1AE” IWNCOMM asserted that China Telecom were supporting this work The discussion concluded with the China NB informing SC6 that further standardisation work on TLSec would continue in BWIPS –BWIPS is the organisation under CESI that standardised WAPI –There is no evidence that it has been standardised yet Andrew Myles, CiscoSlide 44

45. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The China NB submitted a paper to SC6 documenting the implementation & verification of TLSec The China NB submitted a paper (N15617) to SC6 documenting the implementation & verification of TLSec It contains insufficient detail to comment much and there no substantive discussion at the SC6 meeting in Korea in June 2013 Andrew Myles, CiscoSlide 45

46. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There is no standardisation news related to TAAA in China, the proposed LRWN security replacement In previous SC6 meetings the China NB have proposed a protocol called TAAA, which is roughly WAPI for Long Range Wireless Networks At the SC6 meeting in February 2012, an IWNCOMM representative presented TAAA again, emphasising its use of TePA, and concluding –“TAAA applies to various LRWN. –The details of the solution may be discussed further.” It appears from the subsequent discussion that a LRWN could include both LTE & 802.16 There is no evidence of any standardisation work in China on TAAA It is also not clear why a LRWN needs its own special security mechanism and why it doesn’t just have the same requirements as any other wireless network Andrew Myles, CiscoSlide 46

47. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The China NB submitted a paper to SC6 documenting implementation & verification of TAAA –See N15615 It contains insufficient detail to comment much and there was no substantive discussion at the SC6 meeting in Korea in June 2013 Andrew Myles, CiscoSlide 47

48. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The discussion about the various Chinese security proposals became somewhat contentious The Swiss NB suggested a resolution to invite the IEEE 802 to continue discussions. For example: –Sc6 notes with interest the contents of 6N15523, 6N15613, 6N15646 and 6Nxxx (this presentation) and kindly invites the IEEE 802 LMSC to continue the evaluation of the IEEE LAN/MAN security architecture jointly with Sc6. The US NB rep took an alternative view suggesting the ongoing discussion was wasting everyone's time for years, and proposing a different resolution –Noting the various TEPA based proposals that have been discussed within SC6 during the last nine years have all been shown after extensive discussions during many meetings and in many documents to provide no more than functional subsets of existing ISO/IEC standards, draft ISO/IEC standards, or ratified standards from other internationally recognised SDOs, SC6 resolves to disallow documents or discussions related to the proposals known as TAAA, TEPA-AC, TLSec, TISec and WAPI being placed on any SC6 agenda until SC6 NBs formally approves an associated NP proposal. Andrew Myles, CiscoSlide 48

49. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Ultimately the SC6 Chair brokered an acceptable solution meaning no more TEPA discussions … Neither of the proposed resolutions was ultimately accepted Instead, the SC6 Chair ruled that topics can only be discussed 1-2 times before a NP form must be submitted for consideration On this basis, it appears there can be no further discussion of any of the TEPA based proposals with an NP form –WAPI, TEPA-AC, TLSec, TISec, TAAA, … If an NP form is every provided then the IEEE 802 can undertake another review of the proposals At this point it seems unlikely that a justified NP form can be submitted because the China NB justifications have all been successfully rebutted It also seems unlikely that the China NB will gather a list of named experts from at least five NBs … China + Switzerland are the only participants so far Andrew Myles, CiscoSlide 49

50. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Andrew Myles, CiscoSlide 50 The “WAPI story” has been going on for a very, very, very long time... Brief summary of highlights/lowlights 2003: WAPI mandated for use in China, implemented by named firms 2004: Mandate withdrawn after China agrees to standardise WAPI first 2005: WAPI submitted to ISO/IEC fast track ballot in parallel to IEEE submitting 802.11i, after much controversy and appeals 2006: WAPI fails ISO/IEC fast track ballot and 802.11i passes, amid much controversy and appeals 2009: WAPI mandated in handsets and for SPs in China 2009: WAPI submitted to ISO/IEC as NP 2010: WAPI NP ballot passes but comments not resolved Nov 2011: China NB announced that they had withdrawn the WAPI NP Feb 2012: SC6 formally cancelled the WAPI NP

51. doc.: IEEE 802.11-13/0711r0 Submission July 2013 WAPI will have ample government funding for the foreseeable future WAPI has had support from some parts of the Chinese Government for a long time It appears this support is continuing with the opening of a National Engineering Laboratory in Xi’an in late 2012 –See http://tech.sina.com.cn/t/2012-12-10/01357870879.shtmlhttp://tech.sina.com.cn/t/2012-12-10/01357870879.shtml The focus of the lab (Google Translate) is to “fight for more international standards to adopt China's WAPI security technologies” The attendance at the opening of the lab indicated support for its work from: –“National Information Security Management research institutions” –“industry experts” –“China's electric power, petroleum, finance, transportation” industries Andrew Myles, CiscoSlide 51

52. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Any un-cancelling of the WAPI NP probably requires a new NP ballot The China NB suggested at the time of cancellation they may resubmit WAPI “when a more favorable standardization environment is available” –This assertion was repeated at the SC6 meeting in Korea in June 2013 The JTC1 Directives are not particularly clear on the process for a project to be re-established once it has been cancelled The best hint comes from the latest NP Ballot form, which includes an option for: –“THIS PROPOSAL RELATES TO THE RE-ESTABLISHMENT OF A CANCELLED PROJECT AS AN ACTIVE PROJECT” This form and the latest JTC1 Directives suggest if there was a proposal to re-establish WAPI then: –It would have be sent to a new NP ballot of SC6 NBs –Assuming the ballot passed, any resulting negative comments would have to be resolved and balloted by the JTC1 NBs Andrew Myles, CiscoSlide 52

53. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There is a claim that the WAPI NP could be cancelled by a simple vote of SC6 NBs At the SC6 meeting in Korea it was asserted that ISO staff have asserted the WAPI NP could be uncancelled by a simple vote of SC6 NBs –Although it was also noted that the comments on the old NP form would still need to be resolved The US NB rep asserted that this was contrary to the JTC1 Directives and a new NP ballot would be required Regardless of the rules, it certainly would seem strange to not completely revise an NP form that was submitted in 2009 –Much of the material in the 2009 NP form is very out of date –It would be even more difficult to resolve comments on the 2009 NP form given the claims about WAPI in the market place have now been proved false by the passage of time –At least three of the five NBs that stated in 2009 they would provide experts never have done so Andrew Myles, CiscoSlide 53

54. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There is no further standardisation news in relation to TISec, a proposed IPSec replacement China NB are proposing TISec as a TEPA based replacement of IPSec –See N15369 It appears that TISec is also on the Standards Track in China –See attached The presentation was briefly discussed in WG1 in Sept 2012 but was primarily promoted in WG7, which is the group defining a new Internet  The IEEE 802 delegation’s primary observation in Sept 2012 was that TISec appears to directly copy ESP from RFC 4303, with some minor modifications TISec is of interest to IEEE 802 because of parallels to issues being dealt with related to WAPI, TEPA-AC, TLSEc, TAAA, etc Andrew Myles, CiscoSlide 54

55. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There was much discussion in WG7 in Korea in relation to TISec ISOC sent a liaison (N15596) to SC6 in relation to TISec (N15635), the proposed replacement for IPSEc –It noted that TISec has similar functionality to IPSec –It noted that an application for a protocol number by BWIPS had been refused by IESG The China NB has submitted a response (N15618) –The China NB’s paper’s conclusion is — TISec is a new IP layer security protocol based on tri-element peer authentication. TISec focuses on authentication method and data relay technology in VPN applications. We propose to start a PWI in SC6/WG7, and welcome the experts from IETF WG to have a discussion here Andrew Myles, CiscoSlide 55

56. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The China NB were very upset by discussions related to TISec in Korea ISOC then submitted a further liaison (N15645) requesting that SC6 not continue further work on TIsec –The IPSec experts (Sean Turner, and Dan Harkins) were very impressive in making their case and clearly out pointed the Chinese experts The China NB was very upset by these discussions –They accused ISOC of unethical behaviour in mentioning the rejection of the code point application. The China NB were under the impression their application was confidential, which it was not –They did not want the discussion to count against the SC6 Chair’s rule that items can only be discussed 1-2 times before an NP form must be submitted. They asserted it should not count because they did not put TISec on the agenda Andrew Myles, CiscoSlide 56

57. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Ultimately SC7 liaised an inane message back to ISOC about TISec after the meeting in Korea The China NB attempted to send a liaison to ISOC with negative connotations but in the end the following text was liaised –ISO/IEC JTC 1/SC 6/WG 7 thanks ISOC for presentation and discussion on the TIsec related issues at the SC 6/WG 7 June 2013 meeting in Seoul, Korea. –SC 6 kindly requests ISOC to note that there is no formal current project on this topic in SC 6 Most importantly ISOC are now aware of this and other WG7 activities Andrew Myles, CiscoSlide 57

58. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The recent standardisation of UHT or EUHT in China exacerbated fears about these standards … Nufront and the China NB had previously proposed standardisation of UHT (11n extension) & EHUT (11ac replacement) by SC6 –EUHT is also known as N-UHT The IEEE 802 delegation expressed concern about various aspects of this proposal at the San Diego SC6 meeting in June 2011 It was also feared that type approval regulations will be used to mandate UHT/EUHT, similar to those used for WAPI It was expected that EUHT would be raised at SC6 meetings in 2012 … but it was not Since the SC6 meeting in Feb 12, MIIT has announced that UHT and EUHT have been approved as voluntary Chinese National Standardsapproved –This occurred after a somewhat unusual process in CCSA that effectively ignored the concerns of many Chinese and non-Chinese companies –The actual text appears to be unavailable as of July 2013 Andrew Myles, CiscoSlide 58

59. doc.: IEEE 802.11-13/0711r0 Submission July 2013 … with additional fears related to EUHT linked to opening up of the 5GHz band in China Reports indicate that due to opposition from important stakeholders within China's radio spectrum regulatory community: –The lower two bands (5150 - 5250, 5250 - 5350) will be allocated as planned <- GOOD NEWS –The middle band (5470 - 5725) may remain unallocated <- BAD NEWS More specifically: –Military authorities are unsatisfied with MIIT's conclusions that appropriate steps have been taken to address radar interference issues, and MIIT / SRRC plans to conduct further research in this area; –There is also speculation that some stakeholders in the wireless community would like to see some of the 5 GHz band licensed to other technologies, such as LTE-HI, a Chinese PAN communication standard currently being drafted It is possible that EUHT might be one of the technologies that might be licensed, and indeed it appears that it might be likely after comments during the Nufront presentation to IEEE 802.11 WG in May 2013 Andrew Myles, CiscoSlide 59

60. doc.: IEEE 802.11-13/0711r0 Submission July 2013 It appears that EUHT is being implemented There is recent news that suggests EHUT is being implemented –See http://info.china.alibaba.com/detail/1076224301.htmlhttp://info.china.alibaba.com/detail/1076224301.html –the NR6806 for EUHT RF chip, its receiver dynamic range is 110dB, launch dynamic range is 30dB, variable bandwidth design, support QAM ​​ 256, integrated LNA and PA compatible WiFi support MIMO and smart antennas, but also the industry's multimode RF chips only the support EUHT and WiFi, a very wide range of applications. Andrew Myles, CiscoSlide 60

61. doc.: IEEE 802.11-13/0711r0 Submission July 2013 There is no news on EUHT standardisation in ISO/IEC but some activity in IEEE 802.11 WG There is no further news on standardisation of EUHT in ISO/IEC and it was not discussed at the SC6 meeting in Korea in June 2013 Nufront presented to the IEEE 802.11 WG and conducted a Q&A in Hawaii in May 2013 –See 595r0 & 595r1 for presentation595r0595r1 –See 640r0 for Q&A minutes640r0 It is likely that Nufront will present again to IEEE 802.11 WG in relation to EUHT, and more explicitly coexistence with IEEE 802.11 Andrew Myles, CiscoSlide 61

62. doc.: IEEE 802.11-13/0711r0 Submission July 2013 SC6/WG7 decided to delay decisions on two PWI proposals related to WLAN SC6/WG7 discussed two proposals for PWIs related to WLAN –N15692: WLAN Cloud — Allows sharing of APs by SPs –N15691: Optimization technology in WLAN — Defines protocol for sending WLAN sniffing data to central database It appears the IEEE 802 delegation was not in attendance when the items were initially discussed However, later in the week the US NB rep successfully argued that PWIs should not be started in WG7 because the items maybe within the scope of WG1 Andrew Myles, CiscoSlide 62

63. doc.: IEEE 802.11-13/0711r0 Submission July 2013 SC6/WG7 decided to delay decisions on two PWI proposals related to WLAN It was decided that the items should be discussed in a joint meeting between WG1 and WG7 in Ottawa in February 2014 The approved SC6 resolution was –SC 6 instructs its Secretariat to circulate the documents below for study and comment prior to the interim WG 7 meeting in October 2013. –Due to the nature of the topic, the scope should be clarified between WG 1 and WG 7. –SC 6 Secretariat is instructed to arrange a joint session between WG 1 and WG 7 at the next SC 6 meeting in Canada to discuss these topics in more detail and particularly the question of scope. –SC 6 encourages China NB to submit additional documents regarding the details of the proposals and the scope. Andrew Myles, CiscoSlide 63

64. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 1888 was discussed in SC6/WG7 in Korea for possible submission to SC6 under the PSDO IEEE 1888 is a ratified standard for “UGCCNet: Ubiquitous Green Community Control Network Protocol)” An IEEE 1888 WG delegation proposed the submission of IEEE 1888 to SC6 under the PSDO agreement There was significant discussion in SC6/WG7 comparing IEEE 1888 to ISO/IEC 17811-x (DCM: Device Control and Management) It was agreed that there should be further discussions Andrew Myles, CiscoSlide 64

65. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The proposed submission of IEEE 1888 raises a meta question for IEEE-SA A meta question for IEEE-SA is that of under what conditions it should allow IEEE-SA WGs to make use of the PSDO? –Overuse risks diminishing the reputation of IEEE-SA –Particularly if the submitted standards are of insufficient quality to be “International standards” –But also because submission of many standards makes it easier to make the claim that IEEE is not an international SDO Should IEEE 802 request IEEE-SA to develop a set of criteria for IEEE standards before they are submitted to ISO/IEC –Is the standard appropriate as an ISO/IEC “international” standard? –It is in IEEE-SA’s interest to submit the standard to ISO.IEC under the PSDO? Who should judge these criteria? –The WG making the proposed submission? –IEEE-SA? Andrew Myles, CiscoSlide 65

66. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The SC may discuss possible criteria for ISO/IEC submission of IEEE standards under the PSDO Possible criteria for submission under PDSO Does it meet the needs of a significant or important set of stakeholders? –ie useful Does it meets the needs of stakeholders situated in multiple countries –ie international scope Is it known to be able achieve its goals in real implementations –Ie viable Has it undergone sufficient development and review by all stakeholders –ie maturity Is it likely be used –ie relevant Is its submission in the interest of IEEE-SA? Andrew Myles, CiscoSlide 66

67. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The SC may consider a motion in relation criteria for submission of IEEE standards under the PSDO Motion The IEEE 802 JTC1 SC recommends to IEEE 802 EC that it request IEEE-SA develop a set of criteria that must be satisfied before standards are submitted to ISO/IEC under the PSDO Moved: Seconded: Andrew Myles, CiscoSlide 67

68. doc.: IEEE 802.11-13/0711r0 Submission July 2013 ISO/IEC staff have provided guidance on numbering in ISO/IEC of amendments to IEEE 802.1 standards Jodi Haasz (IEEE staff) reports –At the last JTC 1 Standing Committee meeting that I attended in March, I had the action item to contact ISO about the numbering of IEEE 802.1 documents adopted by JTC 1, specifically those that were amendments (e.g. 802.1ARcb). –I received the following response from Henry, below: — "Your amendment would be shown as IEEE 802.1ARcb. We would have to adopt as ISO/IEC ISO/IEC/IEEE 8802-1AR AMD1. There really is no way around this. The parent of the amendment has to read exactly the same way as the main document record and the only suffix permitted for an amendment is AMD 1, 2 etc... — The compromise I can think of is where we adopt IEEE 802.1ARcb as ISO/IEC ISO/IEC/IEEE 8802-1AR AMD1 and make sure to include in the title "adoption of IEEE 802.1ARcb"". Presumably this would apply to ISO/IEC 802-11 amendments too –ie 802.11ad would become 802.11 AMD X Andrew Myles, CiscoSlide 68

69. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The next SC6 meeting will be held in Canada in February 2014 Meeting ISO/IEC JTC1/SC6 Host Standards Council of Canada Date Week of 17 February 2014 Location Offices of Ericsson in Ottawa Andrew Myles, CiscoSlide 69

70. doc.: IEEE 802.11-13/0711r0 Submission July 2013 ISO and IEEE are renegotiating the PSDO, and requested comments in Nov 2012 – no update The ISO and IEEE are renegotiating the PSDO IEEE 802 may want to provide comments to IEEE staff Does this group have any comments? From Nov 2012 –IEEE should ensure only groups with an established track record may propose use of PSDO; 802.1/3/11 would all qualify –The default state should be that all revisions are undertaken by the source IEEE group, but that group must provide a way for NB reps to participate and contribute –Revisions should be better defined to include any activity that ultimately leads to the next edition of a standard, including amendments and corrections –A revision should also include any work that relies on an IEEE standard ratified under the PSDO and yet adds to, changes or replaces its functions, particularly if it does so in a way that effectively generates independent and incompatible standards There has been no further news on this topic since Nov 2012 Andrew Myles, CiscoSlide 70

71. doc.: IEEE 802.11-13/0711r0 Submission July 2013 IEEE 802 JTC1 SC will consider any motions The motions will be constructed during the week Andrew Myles, CiscoSlide 71

72. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC will at the September interim Andrew Myles, CiscoSlide 72

73. doc.: IEEE 802.11-13/0711r0 Submission July 2013 Are there any other matters for consideration by IEEE 802 JTC1 SC? Andrew Myles, CiscoSlide 73

74. doc.: IEEE 802.11-13/0711r0 Submission July 2013 The IEEE 802 JTC1 SC will adjourn for the week Motion: The IEEE 802 JTC1 SC, having completed its business in Geneva in July 2013, adjourns Moved: Seconded: Result: Andrew Myles, CiscoSlide 74