IEEE 802 JTC1 Standing Committee Sept 2014 agenda

IEEE 802 JTC1 Standing Committee Sept 2014 agenda
July 2010 doc.: IEEE /0xxxr0 IEEE 802 JTC1 Standing Committee Sept 2014 agenda 15 Sept 2014 Authors: Name Company Phone Andrew Myles Cisco Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 This presentation will be used to run the IEEE 802 JTC1 SC meetings in Athens in Sept 2014 This presentation contains a proposed running order for the IEEE 802 JTC1 Standing Committee meeting in Athens in Sept 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 Andrew Myles, Cisco

Participants have a duty to inform in relation to patents
July 2010 doc.: IEEE /0xxxr0 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 Andrew Myles, Cisco

There are a variety of patent related links
July 2010 doc.: IEEE /0xxxr0 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 IEEE-SA Standards Board Operations Manual Material about the patent policy is available at If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit This slide set is available at Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 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 Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 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 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 Andrew Myles, Cisco

Links are available to a variety of other useful resources
July 2010 doc.: IEEE /0xxxr0 Links are available to a variety of other useful resources Link to IEEE Disclosure of Affiliation Links to IEEE Antitrust Guidelines Link to IEEE Code of Ethics Link to IEEE Patent Policy Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 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 Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC1 SC has three slots at the Athens interim meeting, but may only need one slot Tuesday 16 Sept, PM1 Wednesday 17 Sept, PM1 Thursday 18 Sept, 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 Recess Call to Order Select recording secretary <- important! Conduct meeting according to agenda Adjourn Note: Probably any motions today Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 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 July 2014 in San Diego Review extended goals From formalisation of status as SC in March 2014 Review status of SC6 interactions Review liaisons of drafts to SC6 Review notifications of projects to SC6 Review status of FDIS ballots Prepare for SC meeting in London in October 2014 Consider any motions Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC1 SC will consider approving its agenda for the Athens meeting Motion to approve agenda The IEEE 802 JTC1 SC approves the agenda for its meeting in Athens in Sept 2014, as documented on slide 10 of <this slide deck> Moved: Seconded: Result: Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC1 SC will consider approval of the minutes of its San Diego meeting Motion to approve minutes The IEEE 802 JTC1 SC approves the minutes for its meeting in San Diego in July 2014, as documented in Moved: Seconded: Result: Andrew Myles, Cisco Andrew Myles, Cisco

July 2010 doc.: IEEE /0xxxr0 The goals of the IEEE 802 JTC1 SC were reaffirmed by the IEEE 802 EC in March 2014 The IEEE 802 JTC 1 SC has agreed goals from November 2010 … 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 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 … that were reaffirmed by 802 EC in Mar 2014 when formalising status of IEEE 802 JTC1 SC Andrew Myles, Cisco Andrew Myles, Cisco

The IEEE 802 WGs continue to liaise drafts to SC6 for their information
IEEE 802 has agreed (see N15606) to liaise to SC6 drafts of standards/amendments that are likely to be ratified under the PSDO agreement Generally, IEEE 802 will liaise drafts during the Sponsor Ballot process, but may also do so during the Letter Ballot process So far drafts have been liaised by: WG 802.1 WG Andrew Myles, Cisco

IEEE 802.11 WG has liaised a variety of drafts to SC6
Doc ISO/IEC/IEEE doc Latest Versions 802.11p :2012 Feb 10 10.0 802.11s Mar 11 8.0 802.11u Nov 10 11.0 13.0 802.11v Sep 10 9.0 12.0 14.0 15.0 802.11z Aug 10 7.0 802.11aa :2012/Amd 2: 2014 Nov 11 6.0 802.11ac In PSDO process Nov 13 2.0 3.0 4.0 5.0 802.11ad :2012/Amd 3: 2014 Jul 12 802.11ae :2012/Amd 1:2014 802.11af 802.11mb 802.11mc Jun 14 Andrew Myles, Cisco

IEEE 802.11 WG will continue to consider drafts for liaison
In San Diego: We decided ah draft is not sufficiently mature for liaising We decided ai draft is not sufficiently mature for liaising There was no discussion of aj, ak, ax drafts In Athens: Do we want to revisit the decisions on ah/ai? Are any other drafts ready? Andrew Myles, Cisco

IEEE 802.1 WG has liaised a variety of drafts to SC6
Doc Description Latest Versions 802.1Xbx Approved for PSDO process May 14 D1.0 D1.2 802 In PSDO process Mar 14 D1.9 802.1Q-Rev Jan 14 D2.0 802.1AX-Rev ??? D?.? Andrew Myles, Cisco

IEEE 802.1 WG will continue to consider drafts for liaison
In San Diego: We decided 802.1AC-Rev is not ready for liaising 802.1AX-Rev should be liaised – has it? In Athens: Are any other drafts ready? Andrew Myles, Cisco

The SC may discuss the possibility of liaising IEEE 802
The SC may discuss the possibility of liaising IEEE drafts to SC6 IEEE was adopted by ISO under JTC 1/SC 31. Is there any update on the possibility of moving responsibility for WG liaising drafts from SC 31 to SC6? Jodi Haasz (IEEE staff) is still in discussions with ISO to move the liaison to SC6 No reps attended the SC meeting in San Diego Andrew Myles, Cisco

IEEE 802 continues to notify 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, IEEE 802 notified SC6 of the approval of the following: IEEE GbE Study Group IEEE Next Generation 60 GHz (NG60) Formation IEEE Smart Grid Task Group Formation IEEE 802 EC Study Group for a recommended practice on privacy Note: also notified that IEEE Working Group will be drafting a PAR and CSD for an IEEE 802 amendment on Local Address space usage plan and Company ID based local MAC addresses. Andrew Myles, Cisco

Comments resolved by IEEE
IEEE 802 has pushed ten standards completely through the PSDO ratification process IEEE 802 standard 60 day pre-balllot 5 month FDIS ballot Comments resolved by IEEE 802.11 Passed (2012) Passed in 2012 Liaised in Nov 2013 802.1X Passed (2013) Passed (21 Oct 2013) Liaised in Jan 2014 802.1AE 802.1AB Passed (May 2013) Passed (18 Dec 2013) Liaised in May 2014 802.1AR 802.1AS 802.3 Passed (16 Feb 2014) Not required 802.11aa Passed (Feb 2013) Passed (28 Jan 2014) Liaised in July 2014 802.11ad 802.11ae Andrew Myles, Cisco

IEEE 802.11-2012 has been ratified as ISO/IEC/IEEE 8802-11:2012 & 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/IEEE :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 liaised as 6N15832 in Nov 2013 Andrew Myles, Cisco

IEEE 802.1X-2010 has been ratified as ISO/IEC/IEEE 8802-1X:2013 & FDIS comment resolutions liaised
60 day pre-ballot: passed & comments liaised Submission of IEEE 802.1X-2010 in N15515 in Dec 2012 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 X:2013 Andrew Myles, Cisco

IEEE 802.1AE-2006 has been ratified as ISO/IEC/IEEE 8802-1AE:2013 & FDIS comment resolutions liaised
60 day pre-ballot: passed & comments liaised Submission of IEEE 802.1AE-2006 in N15516 in Dec 2012 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 AE:2013 Andrew Myles, Cisco

IEEE 802.1AB-2009 has been ratified as ISO/IEC/IEEE 8802-1AB:2014 & FDIS comment resolutions liaised
60 day pre-ballot: passed & comments liaised Submission of IEEE 802.1AB-2009 in N15588 in March 2013 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 WG in March 2014, and liaised to SC6 in May 2014 as N15944 The standard was published as ISO/IEC/IEEE AB:2014 on 15 March 2014 Andrew Myles, Cisco

IEEE 802.1AR-2009 has been ratified as ISO/IEC/IEEE 8802-1AR:2014 & FDIS comment resolutions liaised
60 day pre-ballot: passed & comments liaised Submission of IEEE 802.1AR-2009 in N15589 in March 2013 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 WG in March 2014, and liaised to SC6 in May 2014 as N15947 Standard was published as ISO/IEC/IEEE AR:2014 on 15 March 2014 Andrew Myles, Cisco

IEEE 802.1AS-2011 has been ratified as ISO/IEC 8802-1AS:2014 & FDIS comment resolutions liaised
60 day pre-ballot: passed & comments liaised Submission of IEEE 802.1AS-2011 in N15590 in March 2013 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 WG in March 2014, and liaised to SC6 in May 2014 as N15948 Standard was published as ISO/IEC/IEEE AS:2014 on 15 March 2014 Andrew Myles, Cisco

IEEE 802.3-2012 has been ratified as ISO/IEC/IEEE 8802-3:2014 & FDIS comment resolutions liaised
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 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 was published as ISO/IEC/IEEE :2014 Andrew Myles, Cisco

IEEE 802.11ae-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 1:2014 & FDIS comments liaised
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 liaised 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 were approved by 802 in July 2014 See Standard was published as :2012/Amd 1:2014 Andrew Myles, Cisco

IEEE 802.11aa-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 2:2014 & FDIS comments liaised
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 liaised 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 were approved by 802 in July 2014 See Standard was published as :2012/Amd 2: 2014 Andrew Myles, Cisco

IEEE 802.11ad-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 3:2014 & FDIS comments liaised
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 liaised 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 were approved by 802 in July 2014 See Standard was published as :2012/Amd 3: 2014 Andrew Myles, Cisco

IEEE 802 has ten standards in the pipeline for ratification under the PSDO
IEEE 802 standard 60 day pre-balllot 5 month FDIS ballot Comments resolved 802.11ac Closes 22 Sept 2014 - 802.11af 802.1AEbw Passed (Jan 2014) Waiting for start 802.1AEbn 802.1Xbx Waiting for IEEE pub 802.1Q-Rev 802 Closes 6 Oct 2014 802.22 Passed (May 2014) 802.22a Waiting for Andrew Myles, Cisco

IEEE 802.11ac-2013 is waiting for the close of the pre-ballot
60 day pre-ballot: waiting for pre-ballot to close The request to submit IEEE ac-2013 for approval under the PSDO was liaised in July 2014 The pre-ballot closes on 22 Sept 2014 FDIS ballot: Andrew Myles, Cisco

IEEE 802.11af-2013 is waiting for the close of the pre-ballot
60 day pre-ballot: waiting for pre-ballot to close The request to submit IEEE af-2013 for approval under the PSDO was liaised in July 2014 The pre-ballot closes on 22 Sept 2014 FDIS ballot: Andrew Myles, Cisco

IEEE 802.1AEbw-2013 passed pre-ballot in Jan 2014, and is waiting for FDIS ballot to start
60 day pre-ballot: passed & comments liaised Pre-ballot on IEEE 802.1AEbw-2013 (N15810) 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 WG in March 2014, and were liaised to SC6 as N15946 FDIS ballot: waiting for FDIS ballot to start The FDIS should open shortly but no firm date has been given As of 25 August 2014 Andrew Myles, Cisco

IEEE 802.1AEbn-2011 passed pre-ballot in Feb 2014, and is waiting for FDIS ballot to start
60 day pre-ballot: passed & comments liaised Pre-ballot on IEEE 802.1AEbn-2011 (N15809) 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 WG in March 2014, and were liaised to SC6 as N15945 FDIS ballot: waiting for FDIS ballot to start The FDIS should open shortly but no firm date has been given As of 25 August 2014 Andrew Myles, Cisco

IEEE 802.1Xbx-2014 will be submitted to PSDO process after IEEE ratification & publication
60 day pre-ballot: waiting for IEEE ratification & publication The submission of IEEE 802.1Xbx-2014 after publication under the PSDO was approved by 802 EC in July 2014 As of 25 August it was still in Sponsor Ballot FDIS ballot: Andrew Myles, Cisco

IEEE 802.1Q-Rev-2014 will be submitted to PSDO process after IEEE ratification & publication
60 day pre-ballot: waiting for IEEE ratification & publication The submission of IEEE 802.1Q-Rev-2014 after publication under the PSDO was agreed by 802 EC in July 2014 It is on the 15 October RevCom Early Consideration Agenda FDIS ballot: Andrew Myles, Cisco

IEEE 802-2014 is waiting for the start of the pre-ballot
60 day pre-ballot: waiting for start of pre-ballot The submission of IEEE under the PSDO was approved by 802 EC in July 2014 It was submitted to SC6 on 21 August 2014 and we are waiting for the pre-ballot to start FDIS ballot: Andrew Myles, Cisco

IEEE 802.3.1-2013 is waiting for the close of the pre-ballot
60 day pre-ballot: waiting for ballot to close The request to submit IEEE for approval under the PSDO was liaised in August 2014 The pre-ballot closes on 6 Oct 2014 FDIS ballot: Andrew Myles, Cisco

Pre-ballot on 802.22 passed pre-ballot in May 2014, now waiting for FDIS ballot to start
60 day pre-ballot: passed & comments liaised Pre-ballot on (N15925) passed in May 2014 Voting results in N15954 Passed 8/1/10 FDIS comment responses were approved by WG in July 2014, and were liaised to SC6 as N16001 FDIS ballot: waiting for FDIS ballot to start The FDIS should open shortly but no firm date has been given As of 25 August 2014 Andrew Myles, Cisco

802.22aa will be sent to PSDO when 802.22 completes the PSDO process
60 day pre-ballot: not submitted yet It was agreed by consensus in San Diego in July 2014 that submission of a should wait until is ratifies by ISO/IEC FDIS ballot: Andrew Myles, Cisco

IEEE 802.22 WG has asked SC6 to allocate revision responsibility for IEEE 802.22
IEEE 802.1/3/11 standards are being liaised to ISO/IEC JTC1/SC6 for ratification under the PSDO based on an agreement by SC6 that the relevant IEEE 802 WG has responsibility for the revision process The agreement by SC6 is based on the existence of an established mechanism (N15606) for NBs to contribute to the revision process in the IEEE 802 WG The agreement was ratified by resolutions in SC6 in relation to each of IEEE 802.1/3/11 IEEE WG sent a request for a similar agreement in relation to IEEE in July 2014 The request will be addressed at the SC6 meeting in October 2014 Andrew Myles, Cisco

A number of security presentations based on TePA have been considered by SC6
Proposal Equivalent Chinese standard? NP proposal in WG1? Implemented? TEPA-AC Subset of X Yes Not yet Not known TLSec Subset of 802.1AE Not yet; BWIPS driving Yes, in lab TAAA security No? WAPI Subset of i based security Yes, passed, but withdrawn Yes, required in handsets & SP APs but rarely used TISec Subset/copy of IPSec Not yet (in WG7) Andrew Myles, Cisco

There has been no further action on any of the TePA based proposals
The China NB has been promoting 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 inform JTC1 & SC6 NBs of our concerns Andrew Myles, Cisco

The security discussion between IEEE 802 and the Swiss NB has not progressed recently
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 Thomman how 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 Hans told the SC’s Chair that he had not progressed, as of mid August Andrew Myles, Cisco

Individuals in China and HK were pushing an alternative security agenda
Kingston Zhang (HK SAR, observer in SC6) and a number of Chinese individual experts presented to SC27 in April 2014 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 participants indicated: The presentation didn't gain traction The picture slide implying CSA support was removed after am objection This is important to IEEE 802 only because it indicates the threat to our security standards has not gone away Andrew Myles, Cisco

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 show that IEEE Security standards satisfy the Chinese needs for Internet security Andrew Myles, Cisco

A number of other proposals relevant to IEEE 802
A number of other proposals relevant to IEEE are being considered by SC6 Proposal Equivalent Chinese standard? NP proposal in WG1? Implemented? UHT 802.11n extension Yes No Not known EUHT 802.11ac competitor – really a LTE lite in unlicensed spectrum solution Prototype WLAN Cloud Similar to existing functionality in APs or using HS2.0 Failed PWI proposal in WG7 Optimization technology in WLAN Number of proprietary sniffer systems Andrew Myles, Cisco

There is still no news on EUHT standardisation in ISO/IEC … and next steps are unclear
There is no further news on standardisation of EUHT in ISO/IEC: it was not discussed in Korea in June 2013 or in Ottawa in February 2014 Nufront presented to the IEEE WG and conducted a Q&A in Hawaii in May 2013 See 595r0 & 595r1 for presentation, and 640r0 for Q&A minutes Nufront presented to IEEE WG and this SC in relation to EUHT, and more explicitly coexistence with IEEE in Sept 2013 EUHT Status Description EUHT Technology Document Interference and Co-existence Issues of EUHT network Process Recommendations on Coexistence Interference Analysis It was hoped that Nufront would return in March 2014 to participate in HEW, but they did not … and noting has happened since The individuals involved have apparently been reallocated to other work Andrew Myles, Cisco

In 2013, 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

In Feb 2014, 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 a sniffer and the database Andrew Myles, Cisco

It was “decided” in Feb 2014 to address the proposals in WG7 but neither PWI was approved
No formal decision was made by the joint WG1/WG7 meeting, or by the SC6 plenary meeting … … but apparently the WG1 and WG7 Chairs made a decision that both activities should take place in WG7 ... to which the US NB objected on procedural grounds, but was ignored A resolution to start a PWI on “Optimization technology in WLAN” in WG7 failed Failed 2/3/2, and no further action was taken N15911 was subsequently removed from the SC6 document sever A resolution to send the WLAN Cloud document out for comment before the May 2014 interim WG7 meeting passed Comments were requested by 30 April … Andrew Myles, Cisco

SC6/WG7 discussed the “WLAN Cloud” document in late May 2014
The IEEE WG responded to the call for comments on the WLAN Cloud document in March 2014 See N15931 The China NB responded in May 2014 See N15951 – “The Research Report on Framework and Interface of WLAN Virtual Network” The China NB responded with a revision in May 2014 See N15966 – “The Research Report on Framework and Interface of WLAN Virtual Network” This version also solved a copyright issue with a diagram copied from an IETF RFC All these documents were apparently discussed in May 2014 at the WG7 meeting in Beijing Andrew Myles, Cisco

The latest version of “WLAN Cloud” seems to ignore the IEEE 802
The latest version of “WLAN Cloud” seems to ignore the IEEE WG liaison N15966 seems to propose the following Multiple SPs … … using a single AP … with a single SSID … directing clients onto SP specific VLANs It does not acknowledge the IEEE WG liaison that states this is already possible It makes an additional claim that HS2.0 “cannot support private network though it can support WLAN users access Internet.” This assertion is not justified Andrew Myles, Cisco

It is not clear what the China NB are planning next wrt the “WLAN Cloud” proposal
A China NB rep sent the following to the IEEE 802 JTC1 SC Chair Based on current discussion, I think we have reached the following common points: 1) WLAN virtuallization is needed by the market 2) Hostspot 2.0 can almost do the same function and get some trial site already 3) This proposal's technologies is different from hotspot 2. 4) This proposal is just another technical approach to solve the problem just like tftp vs. ftp, etc. But now, we have to reach a point to make a decision if we shall push another technical approach forward? It appears the China NB is starting to realise the WLAN Cloud proposal is not needed It is not clear what the China NB are planning next There has been no indication as of 26 August Andrew Myles, Cisco

It has been claimed that “WLAN Cloud” is required for CMCC to upgrade existing equipment
An from a China NB rep to the SC Chair states” Now, I can give you some facts about market issues: CMCC has placed more than 4 million fit APs and many ACs already. They will place more this kind of devices this year. All kinds of devices is hard to upgrade to hotspot 2.0 via only software upgrade There are many government, corporation also placed more than millions of fit APs and many ACs already. How to protect the existed investment is an important issue for CMCC. CMCC is paying attention on the progress about hotspot 2.0 now, but I don't know if hotspot2.0 has give some solution to protect the existed investment. This proposal can contribute a solution existed to protect the existed investment because what we need to do is just to upgrade software of fit APs and ACs. It seems the underlying issue for this representative is a mechanism to upgrade existing gear Note; there is no reason HS2.0 can’t be a software upgraded Andrew Myles, Cisco

The SC will consider next steps in relation to the “WLAN Cloud” proposal in WG7
At the July meeting it was decided that we would wait until the SC6/WG7 agenda was updated before deciding on next steps on the “WLAN Cloud” proposal Note: SC6 is unlikely to find enough interest to justify any further work; they need at least 5 experts This meeting will discuss any new information Andrew Myles, Cisco

SC6/WG7 discussed the “Optimization technology in WLAN” document in late May 2014
The China NB uploaded a new “Optimization technology in WLAN” document in May 2014, replacing the version previously removed from te SC6 server See N15961 – “Optimization Technology in WLAN” This document was apparently discussed in May 2014 at the WG7 meeting in Beijing It appears to add some material based on the discussion in Ottawa But it is really confusing … appearing to include a series of quasi-quotes from IEEE 802 reps at the Ottawa meeting However, we do not know whether there were any outcomes from the WG7 meeting in Beijing Andrew Myles, Cisco

The SC will consider next steps in relation to the “Optimization technology in WLAN” proposal in WG7
At the July meeting it was decided that we would wait until the SC6/WG7 agenda was updated before deciding on next steps on the “Optimization technology in WLAN” proposal Note: SC6 is unlikely to find enough interest to justify any further work; they need at least 5 experts This meeting will discuss any new information Andrew Myles, Cisco

The next SC6 meeting will be held in the UK in October 2014
ISO/IEC JTC1/SC6 Host BSI Date Week of October 2014 (week after WFA meeting in Berlin) Location Offices of BSI in London Andrew Myles, Cisco

It appears a Canada NB rep is volunteering to be the WG1 convenor
The current WG1 convenor is Seung-Ok Lim from Korea NB It is not known if he is planning to resign … … however, Dr Wael Badawy from the Canada NB has nominated to take his place See N16014 Andrew Myles, Cisco

The IEEE 802 JTC1 SC will prepare final submissions for the London SC6 meeting this week
Resolution from SC6 on scheduling for Oct meeting suggests we need to have our final submissions to SC6 ready out of the Sept meeting … Following the ISO/IEC Directives, JTC 1 Supplement and JTC 1 Standing Document on Meetings, SC 6 establishes the following deadlines for contributions for the 2014 SC 6 meetings in UK: Documents for the meetings, particularly those raising new issues/new agenda items or those for which approval at the meeting is desired, must be delivered to the Secretariat no later than for posting on the SC 6 web server. Documents received by the Secretariat after will be circulated for information but will not be considered, unless they fall into the exceptions specified in JTC 1 Standing Document on Meetings, in which case the deadline is … based on input from NBs that were due by 5 Sept 2014 Andrew Myles, Cisco

The SC6/ WG7 agenda for London includes three items of interest to IEEE 802.11 WG
The draft WG7 agenda includes 16. Other WG 7 related Issues Optimization technology in WLAN WLAN virtual network Collaboration with IEEE Working Group There is no further detail Andrew Myles, Cisco

The SC6/ WG1 agenda for London does not contain much
An outline agenda has been published for WG1 … … and no interesting uploaded documents … but it will only start on Tuesday Based on discussion in Ottawa, the US NB may attempt to transition WG1 to operating with less F2F meetings … … but that is not really an IEEE 802 issue Andrew Myles, Cisco

The SC may need to select a new IEEE 802 liaison and HoD to SC6 eventually
Bruce Kraemer has acted as the IEEE 802 liaison officer and HoD to SC6 for some years but it is likely that Bruce will be unavailable to continue these roles in the long term; he notes: I am still available to help 802 at SC6 in October. I will continue to encourage you to find a new HoD. If you at least identified an HoD-in training I would be more enthusiastic in serving as HoD one “last” time. Who would like to take over? Adrian Stephens could take over the Liaison role (formally) and could be HoD in London because he is local Or we could call on Tony Jeffree who is also local as HoD in London We can delay any decisions until September if required, but it is probably worth while empowering the IEEE 802 EC Chair this week to appoint a HoD at the appropriate time Andrew Myles, Cisco

The IEEE 802’s delegation to SC6 in London in October is likely to have four delegates
IEEE 802 Delegation will include Bruce Kraemer (HoD) Jodi Haasz (IEEE staff) Stephen McCann (HoD in training?) Adrian Stephens (HoD in training?) Other known IEEE 802 attendees include John Messenger (UK NB) Andrew Myles (US NB) Please register! Andrew Myles, Cisco

The SC will review updated IEEE 802 materials for the SC6 meeting
In Ottawa, IEEE 802 particular prepared WG updates various documents 6N15837: IEEE-SA 802 Liaison Overview 6N15836: IEEE SC6-Overview - done 6N15843: IEEE Ethernet Working Group Update - done 6N15839: IEEE-SA Liaison Overview - done 6N15844: IEEE Projects: Summary Overview 6N15838: Overview of the IEEE Working Group Activities We will quickly review the updates versions this week Andrew Myles, Cisco

The SC will review the 802 overview
Status Drafted based on previous version by Andrew Bruce is editing as of 26 Aug Andrew Myles, Cisco

The SC will review the 802.1 WG overview
Status Drafted based on previous version by Mick Done Andrew Myles, Cisco

Status Drafted based on previous version by David Done Andrew Myles, Cisco

Status Drafted based on previous version by Adrian Done Andrew Myles, Cisco

Status Not known Andrew Myles, Cisco

ISO/IEC JTC1 is changing the way it organises participation in WGs
The organisational structure in ISO/IEC JTC1 is changing to align its operation with ISO A recent communication from JTC1 states Working Groups are comprised of INDIVIDUAL EXPERTS appointed by National Bodies and Liaison Organizations These experts MUST be entered into Global Directory to be considered a member of the WG and to receive documents National Bodies are responsible for ensuring that their expert appointments are up to date Liaison Organizations work via ITTF to maintain their expert members If the expert is NOT in Global Directory, he/she will not receive documents and will NOT be considered a member of the WG. Andrew Myles, Cisco

The SC Chair has been empowered to appoint experts to the SC6 document access lists
One way of dealing with this change is to empower the SC Chair to appoint experts to WG1 and WG7, with the understanding that anyone who volunteers will be appointed Motion (ratified in May by IEEE 802 EC) The IEEE 802 JTC1 SC recommends to the IEEE 802 EC that the Chair of the IEEE 802 JTC1 SC be empowered to submit the names to ITTF of any IEEE 802 members who volunteer as “experts” to the appropriate Working Group lists in ISO/IEC JTC1 Moved Seconded Result 9/0/0 Andrew Myles, Cisco

No names have been added to the SC6 document access lists at this time
Only a small number of people have asked to be added to the SC6 reflectors … Ian Sherlock Al Petrick Dan Harkins Brian Weis Mick Seaman Stephen McCann John Messenger … … because it is not clear how the SC6 Chair wants to handle such requests … hopefully this will be made clear at the next SC6 meeting in London Andrew Myles, Cisco

Are there any other matters for consideration by IEEE 802 JTC1 SC?
July 2010 doc.: IEEE /0xxxr0 Are there any other matters for consideration by IEEE 802 JTC1 SC? Andrew Myles, Cisco Andrew Myles, Cisco

The IEEE 802 JTC1 SC will adjourn for the week
July 2010 doc.: IEEE /0xxxr0 The IEEE 802 JTC1 SC will adjourn for the week Motion: The IEEE 802 JTC1 SC, having completed its business in Athens in Sept 2014, adjourns Moved: Seconded: Result: Andrew Myles, Cisco Andrew Myles, Cisco

IEEE 802 JTC1 Standing Committee Sept 2014 agenda

Similar presentations

Presentation on theme: "IEEE 802 JTC1 Standing Committee Sept 2014 agenda"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

IEEE 802 JTC1 Standing Committee Sept 2014 agenda

Similar presentations

Presentation on theme: "IEEE 802 JTC1 Standing Committee Sept 2014 agenda"— Presentation transcript:

Similar presentations

About project

Feedback