1 / 58

IEEE 802 JTC1 Standing Committee May 2014 agenda

IEEE 802 JTC1 Standing Committee May 2014 agenda. 13 May 2014. Authors:. This presentation will be used to run the IEEE 802 JTC1 SC meetings in Hawaii in May 2014.

mei
Download Presentation

IEEE 802 JTC1 Standing Committee May 2014 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 CommitteeMay 2014 agenda • 13 May 2014 Authors: Andrew Myles, Cisco

  2. This presentation will be used to run the IEEE 802 JTC1 SC meetings in Hawaii in May 2014 • This presentation contains a proposed running order for the IEEE 802 JTC1 Standing Committee meeting in Hawaii in May 2014, 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 sub-clause 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 two slots at the Hawaii interim meeting Tuesday 13 May, PM1 Thursday 15 May, PM1 • Call to Order • Select recording secretary <- important! • Approve agenda • Conduct meeting according to agenda • Recess • Call to Order • Select recording secretary <- important! • Conduct meeting according to agenda • Adjourn • Note: Probably any motions today 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 plenary meeting in March 2014 in Beijing • Review extended goals • From IEEE 802 ExCom in Nov 2010 • Review formal status of SC • Review status of SC6 interactions • Review liaisons of drafts to SC6 • Review notifications of projects to SC6 • Review status of FDIS ballots • Consider any motions Andrew Myles, Cisco

  11. 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 Hawaii in May 2014, as documented on pages 10of <this slide deck> • Moved: • Seconded: • Result: Andrew Myles, Cisco

  12. 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 Beijing in March 2014, as documented in 11-14-0570-r0 • Moved: • Seconded: • Result: Andrew Myles, Cisco

  13. 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 IEEE 802 LMSC holds the liaison to SC6, not the IEEE 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 IEEE 802 ExCom ad hoc held in November 2010 on the Friday evening Andrew Myles, Cisco

  14. The formal status of the IEEE 802 JTC1 SC has now been “cleaned up” • Originally the IEEE 802 JTC1 SC was an ad hoc in IEEE 802.11 WG • Its scope was expanded to cover IEEE 802 issues in November 2010 • It appears, based on minutes, that somewhere between Nov 2011 and March 2012 the ad hoc was formally converted to an IEEE 802 SC • However, it is not clear whether this was done under the authority of the IEEE 802 ExCom Chair or IEEE 802 ExCom or … • In March 2014 the IEEE 802 ExCom cleaned up the formalities with the following motion • As per 802 P&P 5.6 "other subgroups" create an EC 802/JTC1 Standing Committee, with Andrew Myles appointed as SC chairman by the Sponsor Chair Andrew Myles, Cisco

  15. In recent times, IEEE 802 has liaised a variety of drafts to SC6 • IEEE 802 has agreed to liaise drafts to SC6 when they are in Sponsor Ballot (and sometimes earlier) • The benefit to IEEE 802 is that it might cause SC6 members to participate in or contribute to IEEE 802 activities before the PSDO process • Since November 2014,the IEEE 802 has liaised the following drafts to SC6 for their information and comment: • 802.11 WG • 18 Nov 2013: 802.11ac D7.0 (now ratified by IEEE) • 18 Nov 2013: 802.11af D6.0 (now ratified by IEEE) • 802.1 WG • 25 Nov 2013: 802.1Xbx D1.2 • 8 May 2014: 802 D1.9 • 8 May 2014: 802.1Q D2.0 Andrew Myles, Cisco

  16. The SC will hear an update on plans for liaising additional IEEE 802.1 drafts to SC6 • Previously, Mick Seaman took an action to enquire of Tony Jeffree as to which drafts IEEE 802.1 would like to liaise to SC6 • It appears that the IEEE 802.1 WG has agreed to send drafts for information including: • 802.1Xbx • 802.1Q • Last time there was some question as to whether the 802 O&A should be liaised now or after Sponsor Ballot • It has been sent Andrew Myles, Cisco

  17. The SC will hear an update on plans for liaising additional IEEE 802.3 drafts to SC6 • Previously, Geoff Thompson and Bruce Kraemer took an action to enquire of David Law as to which drafts IEEE 802.3 would like to liaise to SC6 • Subsequently, David Law and Adam Healy met in Beijing to discuss this question • The current plan is that only revisions will be sent through the PSDO process • This means drafts of revisions will need to be liaised to SC6 Andrew Myles, Cisco

  18. The SC will hear an update on plans for liaising additional IEEE 802.11 drafts to SC6 • There a couple of amendments that could be sent through the PSDO process immediately • 802.11ac • 802.11af • Should the 802.11 WG agree to start the PSDO process for 802.11ac and 802.11af? • It needs an IEEE 802.11 WG motion and an IEEE 802 EC motion • This can be done in July 2014 Andrew Myles, Cisco

  19. The SC will discuss the possibility of liaising IEEE 802.15 drafts to SC6 • Previously, 802.15 WG has been liaising 802.15.4 drafts to SC31 • Is there any update on the possibility of the 802.15 WG liaising 802.15.4 drafts to SC6? • It is rumoured that the ISO Secretariat would like these drafts to be liaise to SC6 • Jodi Haasz (IEEE staff) had had a discussion with Henry Couchieri (ISO staff) to move the liaison to SC6, but has not reported on the results • She noted, “did have the conversation with ISO and have nothing to report as of yet.  I will reach out again.” Andrew Myles, Cisco

  20. The SC will discuss the possibility of liaising additional IEEE 802.22 drafts to SC6 • The 802.22 WG decided to submit 802.22 under the PSDO • Details later, but this process has started • Aside: this would have been a good standard to which to apply the proposed PSDO submission criteria • The 802.22 WG will need to decide on which drafts to submit in the future Andrew Myles, Cisco

  21. In recent times, IEEE 802 has notified SC6 of various new projects • IEEE 802 has agreed to notify SC6 when IEEE 802 starts new projects • The benefit to IEEE 802 is that it might cause SC6 members to participate in or contribute to IEEE 802 activities • Most recently (in 6N15936 in April 2014) IEEE 802 notified SC6 of the approval of the following SGs • IEEE 802.3 Gigabit Plastic Optical Fibre (POF) Study Group • IEEE 802.3 100 Mb/s Operation over a Single Twisted Pair Study Group Andrew Myles, Cisco

  22. IEEE 802 has pushed 4 standards completely through the PSDO ratification process Andrew Myles, Cisco

  23. IEEE 802 has 9 standards in the pipeline for ratification under the PSDO Andrew Myles, Cisco

  24. IEEE 802.11-2012 has been ratified as ISO/IEC 8802-11:2012 and FDIS comment resolutions liaised • 60 day pre-ballot: passed & comments liaised • 60 day pre-ballot passed in 2012 • Responses to comments were liaised to SC6 • FDIS ballot: passed & comments liaised • FDIS passed in 2012 • Standard published as ISO/IEC 8802-11:2012 • FDIS comments liaised in Dec 2013 • All the FDIS comments were submitted to TGmc for processing • Additional comments from Swiss NB in N15623 (a response to the IEEE 802/SC6 collaboration procedure) were also referred to TGmc • All the comments have been considered and resolutions approved as of November 2013 • See 11-13-0123-05 liaised as 6N15832 in Nov 2013 Andrew Myles, Cisco

  25. FDIS ballot on IEEE 802.1X passed in Oct 2103 and all FDIS comment resolutions liaised in Jan 2014 • 60 day pre-ballot: passed & comments liaised • Submission in N15515 • Pre-ballot passed in 2013 • Voting results in N15555 • Comments from China NB replied to by IEEE 802 in N15607 • FDIS ballot: passed & comments liaised • FDIS passed 16/1/12 on 21 Oct 2013 • Voting results in N15771 • China NB only negative vote, with comments from China NB & Switzerland NB • FDIS comments resolved in Dec 2013 • Liaised to SC6 as N15871 in Jan 2014 • Standard has been published as ISO/IEC/IEEE 8802-1X:2013 Andrew Myles, Cisco

  26. FDIS ballot on IEEE 802.1AE passed in Oct 2013 and all FDIS comment resolutions liaised in Jan 2014 • 60 day pre-ballot: passed & comments liaised • Submission in N15516 • Pre-ballot passed in 2013 • Voting results in N15556 • Comments from China NB replied to by IEEE 802 in N15608 • FDIS ballot: passed & comments liaised • FDIS passed 16/1/13 on 21 Oct 2013 • Voting results in N15770 • China NB only negative vote, with comments from China NB & Switzerland NB • FDIS comments resolved in Dec 2013 • Liaised to SC6 as N15871 in Jan 2014 (see previous page for response file) • Standard has been published as ISO/IEC/IEEE 8802-1AE:2013 Andrew Myles, Cisco

  27. FDIS on 802.1AB passed in Dec 2013 and FDIS comment resolution is complete • 60 day pre-ballot: passed & comments liaised • Submission in N15588 • Pre-ballot passed in May 2013 • Voting results in N15626 • Comments from China replied to in N15659 • FDIS ballot: passed & comments in process • FDIS passed 16/1/16 on 18 Dec 2013 • Voting results in N15829 • China NB only negative vote, with comments from China NB & Switzerland NB • FDIS comment responses were approved by 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15944 • The standard was published as ISO/IEC 8802-1AB:2014 on 15 March Andrew Myles, Cisco

  28. FDIS on 802.1AR passed in Dec 2013 and FDIS comment resolution is complete • 60 day pre-ballot: passed & comments liaised • Submission in N15589 • Pre-ballot passed in May 2013 • Voting results in N15627 • Comments from China replied to in N15659 • FDIS ballot: passed & comments in process • FDIS passed 17/2/16 on 18 Dec 2013 • Voting results in N15830 • China NB & Switzerland NB voted “no” and commented • FDIS comment responses were approved by 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15947 • Standard was published as ISO/IEC 8802-1AR:2014 on 15 March Andrew Myles, Cisco

  29. FDIS on 802.1AS passed in Dec 2013 and FDIS comment resolution is complete • 60 day pre-ballot: passed & comments liaised • Submission in N15590 • Pre-ballot passed in May 2013 • Voting results in N15628 • Comments from China replied to in N15659 • FDIS ballot: passed & comments in process • FDIS passed 18/1/16 on 18 Dec 2013 • Voting results in N15831 • China NB voted “no” and China NB & Switzerland NB commented • FDIS comment responses were approved by 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15948 • Standard was published as ISO/IEC 8802-1AS:2014 on 15 March Andrew Myles, Cisco

  30. FDIS on 802.11ae passed in Jan 2014 and comment resolution will finish in May 2014 • 60 day pre-ballot: passed & comments liaised • Pre-ballot on N15552 passed in Feb 2013 • Voting results in N15599 • Comments from China replied to by IEEE 802 in N15647 • Comments from Japan in N15664 were resolved in discussions with commenter • FDIS ballot: passed & comments in process • FDIS passed 14/1/20 on 28 Jan 2014 • Voting results in N15883 • China NB voted “no” and commented they will not recognise result • FDIS comment responses will be considered at this meeting • See 11-14-0552-00 • Standard will be published as <what> Andrew Myles, Cisco

  31. FDIS on 802.11ad passed in Jan 2014 and comment resolution will finish in May 2014 • 60 day pre-ballot: passed & comments liaised • Pre-ballot on N15553 passed in Feb 2013 • Voting results in N15601 • Comments from China replied to by IEEE 802 in N15647 • Comments from Japan in N15664 were resolved in discussions with commenter • FDIS ballot: passed & comments in process • FDIS passed 16/1/17 on 28 Jan 2014 • Voting results in N15885 • China NB voted “no” and commented they will not recognise result • Switzerland commented on editorial matters similar to comments on 802.1X/AE • FDIS comment responses will be considered at this meeting • See 11-14-0552-00 • Standard will be published as <what> Andrew Myles, Cisco

  32. FDIS on 802.11aa passed in Jan 2014 and comment resolution will finish in May 2014 • 60 day pre-ballot: passed & comments liaised • Pre-ballot on N15554 passed in Feb 2013 • Voting results in N15602 • Comments from China replied to by IEEE 802 in N15647 • Comments from Japan in N15664 were resolved in discussions with commenter • FDIS ballot: passed & comments in process • FDIS passed 16/1/18 on 28 Jan 2014 • Voting results in N15884 • China NB voted “no” and commented they will not recognise result • FDIS comment responses will be considered at this meeting • See 11-14-0552-00 • Standard will be published as <what> Andrew Myles, Cisco

  33. FDIS on 802.3-2012 passed in Feb 2014, and no comment resolution is required • 60 day pre-ballot: passed & comments liaised • Pre-ballot on N15595 passed in May 2013 • Voting results in N15632 • Comments from China were responded to by the 802.3 Maintenance TF in Geneva in N15724 • FDIS ballot: passed & comments in process • FDIS passed 16/0/20 on 16 Feb 2014 • Voting results in N15893 • No FDIS comments need to be resolved  • Standard will be published as <what> • The name of the standard will be corrected as an editorial action by ISO editorial staff Andrew Myles, Cisco

  34. Pre-ballot on 802.1AEbw passed pre-ballot in Jan 2014, and comment resolution is complete • 60 day pre-ballot: passed & comments liaised • Pre-ballot on 802.1AEbw (N15xxx) passed in Jan 2014 • Voting results in N15858 • Passed 9/1/7 • Usual comment from China saying they will not recognise the result • FDIS comment responses were approved by 802.1 WG in March 2014, and were liaised to SC6 as N15946 Andrew Myles, Cisco

  35. Pre-ballot on 802.1AEbn passed in Feb 2014, and comment resolution is complete • 60 day pre-ballot: passed & comments liaised • Pre-ballot on 802.1AEbn (N15xxx) passed in Jan 2014 • Voting results in N15857 • Passed 9/1/7 • Usual comment from China saying they will not recognise the result • FDIS comment responses were approved by 802.1 WG in March 2014, and were liaised to SC6 as N15945 Andrew Myles, Cisco

  36. Pre-ballot on 802.22 passed pre-ballot in May 2014 • 60 day pre-ballot: passed & comments liaised • Pre-ballot on 802.22 (N15925) passed in May 2014 • Voting results in N15954 • Passed 8/1/10 • A response to these comments will need be discussed today • Dr.Pyo from 802.22 will be here to assist • Note: the IEEE 802 liaison will need to suggest that SC6 pass a motion wrt 802.22 similar to those on 802.1/3/11, which gave maintenance responsibility to the IEEE 802 WGs; this can be done in July Andrew Myles, Cisco

  37. The China NB contributed a variation on the “usual comment” on IEEE 802.22 • China NB comment on 802.22 • China NB thanks for IEEE’s contribution of IEEE 802.22 (in SC6 N15925). As always, China encourages and supports standard collaboration between IEEE and ISO. However, based on the following reasons, China NB cannot support this proposal. • This standard is to be implemented with IEEE 802.1X which has also been proposed to ISO for FDIS consideration under the PSDO agreement and has been published. China NB has expressed objection to its submission and provided detailed comments as in SC6N14747、SC6N15083 and SC6N15555. IEEE had acknowledged the receiving of China NB’s comments but has not made any satisfactory attempt 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 standard on security. For previous China NB comment, please refer to SC6N15555. Andrew Myles, Cisco

  38. The China NB contributed a variation on the “usual comment” on IEEE 802.22 • China NB comment on 802.22 • In addition, China NB also has concerns that the ongoing FDIS processes are 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

  39. The SC will discuss a response to the China NB comment on IEEE 802.22 • TBD Andrew Myles, Cisco

  40. The SC will discuss a frequent China NB comment • In a number of ballots the China NB has stated “it is regretful for China to be obliged to lose the responsibility and obligation of complying with and adopting the standard” • Jodi Haasz took an action to work with ISO to determine a response to this comment • News? Andrew Myles, Cisco

  41. A number of security presentations based on TePA have been considered by SC6 Andrew Myles, Cisco

  42. There has been no further action on any of the TePA based proposals • The China NB has been threatening NP proposals for the various TePA based proposals • WAPI, TLSec, TEPA-AC, TAAA, TISec • So far no NPs have been proposed • Except WAPI, which was withdrawn in 2012 after much controversy • It is possible that the China NB may now propose NPs after their Snowden presentation in Ottawa in Feb 2014 • However, any such NPs face a variety of difficulties • Snowden is a very weak justification for a problem best handled by open & transparent standards • There are no known technical or market justifications for these NPs • It will be very difficult to identify 5 interested experts from 5 NBs • If any NP is proposed by the China NB then the IEEE 802 will need to respond to it in detail and lobby SC6 NBs Andrew Myles, Cisco

  43. WAPI has not gone away; it may be re-proposed in SC6 despite uncertainty about the process • WAPI was cancelled as an NP proposal in early 2012 • There was been little discussion of WAPI in SC6 since that time but there is a possibility it might be re-proposed • The process for re-proposing WAPI in SC6 is currently uncertain • There is a claim made at the Korea meeting in June 2013 that the WAPI NP could be un-cancelled by a simple vote of SC6 NBs … • … despite some ambiguity, a good case could be made that un-cancelling the WAPI NP requires a new NP ballot • WAPI has not gone away • It has ongoing support in China … • … but WPA2 is being embraced by Chinese SPs anyway • … particularly as part of HS2.0 (based on 802.11u) • WAPI will have ample government funding for the foreseeable future Andrew Myles, Cisco

  44. The security discussion between IEEE 802 and the Swiss NB is proceeding “glacially” • A discussion has been held between the IEEE 802 delegation to SC6 and the Swiss NB over many months on security issues … • … in an attempt to create a better understanding between the two sides • An early agreement (August 2013) was that each side should do some “homework”: • Dan Harkins: how certificates are used and validated in 802.1X/EAP-TLS • Hans Thommanhow certificates are used and validated in TePA • Dan Harkins reviewed his “homework” to this SC in Dallas – a version was subsequently submitted (and presented in February 2014) to SC6 • See N15845 • There were no problems identified by SC6 NB members in Ottawa in N15845 • Hans Rudolf Thomann was asked in Ottawa to prepare the equivalent for TePA, which he agree to complete • There has been no further progress Andrew Myles, Cisco

  45. Individuals in China and HK are still pushing an alternative security agenda • Kingston Zhang (HK NB) and a number of Chinese individual recently presented to SC27 • See 27N13649 • They argued for a “clean slate approach” in SC27, based on a variety of bogus claims about internet security • In particular they proposed that the Future Network project in SC6/WG7 take responsibility for “Path Security for Cloud Computing” • Reports from SC27 indicate: • The presentation didn't gain traction • CSA asked for the picture slide to be removed • This is important to IEEE 802 only be cause it indicates the theat to our security standards has not gone away Andrew Myles, Cisco

  46. A recent Chinese focus on internet security represents a risk and an opportunity for IEEE 802 • Chinese President Xi Jinping elevated cybersecurity to a top national priority on February 27, 2014 with the announcement of the Central Internet Security and Information Leading Group • This decision unifies for the first time all organizations involved in cybersecurity under a single structure • President Xi personally chairs the group, and stated at the group’s inaugural meeting that “There is no national security without Internet security.” • This represents both a risk and opportunity for IEEE 802 security standards • The opportunity is to sho that IEEE 802.1 Security standards satisfy the Chinese needs for Internet security Andrew Myles, Cisco

  47. A number of other proposals relevant to IEEE 802.11 are being considered by SC6 Andrew Myles, Cisco

  48. 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: • it was not discussed at the SC6 meeting in Korea in June 2013 or in Ottawa in February 2014 • Nufront presented to the IEEE 802.11 WG and conducted a Q&A in Hawaii in May 2013 • See 595r0 & 595r1 for presentation • See 640r0 for Q&A minutes • Nufront presented to IEEE 802.11 WG and this SC in relation to EUHT, and more explicitly coexistence with IEEE 802.11 in Sept 2013 • 1147 - EUHT Status Description • 1148 - EUHT Technology Document • 1149 - Interference and Co-existence Issues of EUHT network • 1150 - Process Recommendations on Coexistence Interference Analysis • It was hoped that Nufront would return in March 2014 to participate in HEW, but they did not Andrew Myles, Cisco

  49. SC6/WG7 previously decided to delay decisions on two PWI proposals related to WLAN • SC6/WG7 discussed two proposals for PWIs related to WLAN at the Seoul meeting in 2013 • 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 were maybe within the scope of WG1 Andrew Myles, Cisco

  50. In Ottawa, the appropriate WG for the two PWI proposal related to WLAN was discussed • WG1 and WG7 had a joint meeting in Ottawa in Feb 2014 to discuss the appropriate WG for the two PWI proposals • New presentations were provided • N15913: WLAN Cloud • Proponents were not in attendance • But presented by China NB representative • N15911: Optimization technology in WLAN • Presented by proponents • Cases were made for both to remain in WG7 • WLAN Cloud makes no change to WLAN interface; only the AP to controller interface (maybe they should go to IETF and change CAPWAP?) • Optimization technology in WLAN makes no change to WLAN interface, rather defining an interface between sniffer and database Andrew Myles, Cisco

More Related