1 / 74

IEEE 802 JTC1 Standing Committee July 2013 agenda

IEEE 802 JTC1 Standing Committee July 2013 agenda. 16 July 2013. Authors:. 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

bing
Download Presentation

IEEE 802 JTC1 Standing Committee July 2013 agenda

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. IEEE 802 JTC1 Standing CommitteeJuly 2013 agenda • 16 July 2013 Authors: Andrew Myles, Cisco

  2. 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, Cisco

  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 Andrew Myles, Cisco

  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.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 Andrew Myles, Cisco

  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 Andrew Myles, Cisco

  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. Andrew Myles, Cisco

  7. Links are available to a variety of other useful resources • Link to IEEE Disclosure of Affiliation • http://standards.ieee.org/faqs/affiliationFAQ.html • Links to IEEE Antitrust Guidelines • http://standards.ieee.org/resources/antitrust-guidelines.pdf • Link to IEEE Code of Ethics • http://www.ieee.org/web/membership/ethics/code_ethics.html • Link to IEEE Patent Policy • http://standards.ieee.org/board/pat/pat-slideset.ppt Andrew Myles, Cisco

  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. Andrew Myles, Cisco

  9. The IEEE 802 JTC1 SC has three normal slots at the Geneva plenary meeting Tuesday 16 July, PM1 Wednesday17 July, PM1 Thursday 18 July, PM1 • 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 • Call to Order • Select recording secretary <- important! • Conduct meeting according to agenda • Adjourn Andrew Myles, Cisco

  10. 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, Cisco

  11. 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, Cisco

  12. 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, Cisco

  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 <this slide deck> • Moved: • Seconded: • Result: Andrew Myles, Cisco

  14. 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, Cisco

  15. 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, Cisco

  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 Andrew Myles, Cisco

  17. 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, Cisco

  18. 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, Cisco

  19. 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 veTePA/KA4, TePA-AC, TAAA, TLSec Andrew Myles, Cisco

  20. 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

  21. 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, Cisco

  22. 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, Cisco

  23. 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, Cisco

  24. IEEE 802 suggested updating the list of IEEE 802 related ISO/IEC standards Andrew Myles, Cisco

  25. 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 • For Standard Group MAC addresses: • http://standards.ieee.org/develop/regauth/grpmac/index.html Andrew Myles, Cisco

  26. IEEE 802 has submitted ten standards for ratification under the PSDO Andrew Myles, Cisco

  27. IEEE 802.11-2012 has been ratified as ISO/IEC 8802-11:2012 • 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 Andrew Myles, Cisco

  28. FDIS on 802.1X closes in October 2013 • 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 Andrew Myles, Cisco

  29. FDIS on 802.1AE closes in October 2013 • 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 Andrew Myles, Cisco

  30. FDIS on 802.11ae is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  31. FDIS on 802.11ad is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  32. FDIS on 802.11aa is waiting to start after IEEE 802.11 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  33. FDIS on 802.1AB is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  34. FDIS on 802.1AR is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  35. FDIS on 802.1AS is waiting to start after IEEE 802.1 WG replied to comments during pre-ballot • 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 Andrew Myles, Cisco

  36. 802.3-2012 passed the pre-ballot, and is awaiting a response from 802.3 Maintenance TF • 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 Andrew Myles, Cisco

  37. 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, Cisco

  38. 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, Cisco

  39. 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, Cisco

  40. 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, Cisco

  41. 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, Cisco

  42. 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, Cisco

  43. 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, Cisco

  44. 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, Cisco

  45. 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, Cisco

  46. 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, Cisco

  47. The China NB submitted a paper to SC6 documenting implementation & verification of TAAA • 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, Cisco

  48. 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, Cisco

  49. 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, Cisco

  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 Andrew Myles, Cisco

More Related