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

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

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

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

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

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

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

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

9. The IEEE 802 JTC1 SC has two slots at the Hawaii interim meeting
July 2010
doc.: IEEE /0xxxr0
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
Andrew Myles, Cisco

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

11. The IEEE 802 JTC1 SC will consider approving its agenda
July 2010
doc.: IEEE /0xxxr0
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 10 of <this slide deck>
Moved:
Seconded:
Result:
Andrew Myles, Cisco
Andrew Myles, Cisco

12. The IEEE 802 JTC1 SC will consider approval of previous minutes
July 2010
doc.: IEEE /0xxxr0
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 r0
Moved:
Seconded:
Result:
Andrew Myles, Cisco
Andrew Myles, Cisco

13. July 2010
doc.: IEEE /0xxxr0
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 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
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 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: WG
18 Nov 2013: ac D7.0 (now ratified by IEEE)
18 Nov 2013: af 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
The SC will hear an update on plans for liaising additional IEEE drafts to SC6
Previously, Mick Seaman took an action to enquire of Tony Jeffree as to which drafts IEEE would like to liaise to SC6
It appears that the IEEE 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
The SC will hear an update on plans for liaising additional IEEE drafts to SC6
The current plan for the IEEE WG is that only revisions will be sent through the PSDO process
Previously, Geoff Thompson and Bruce Kraemer took an action to enquire of David Law as to which additional drafts IEEE would like to liaise to SC6 as part of PSDO process
Subsequently, David Law and Adam Healy sent the Chair an
We are thinking of proposing to IEEE in July that we move to the model of liaising all drafts amendments to SC6 in the future for comment
Can you explain the process that IEEE already uses to do this?
I believe that IEEE submits these drafts at sponsor - is that correct?
This will be discussed again in July
Andrew Myles, Cisco

18. The SC will hear an update on plans for liaising additional IEEE 802
The SC will hear an update on plans for liaising additional IEEE drafts to SC6
There a couple of amendments that could be sent through the PSDO process immediately
802.11ac
802.11af
Should the WG agree to start the PSDO process for ac and af?
It needs an IEEE 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
The SC will discuss the possibility of liaising IEEE drafts to SC6
Previously, WG has been liaising drafts to SC31
Is there any update on the possibility of the WG liaising drafts 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.”
This issue will be discussed on Thursday
Andrew Myles, Cisco

20. The SC will discuss the possibility of liaising additional IEEE 802
The SC will discuss the possibility of liaising additional IEEE drafts to SC6
The WG decided to submit 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 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 Gigabit Plastic Optical Fibre (POF) Study Group
IEEE Mb/s Operation over a Single Twisted Pair Study Group
Andrew Myles, Cisco

22. Comments resolved by IEEE
IEEE 802 has pushed 4 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.3
Passed 16 Feb 2014
Not required
Andrew Myles, Cisco

23. IEEE 802 has 9 standards in the pipeline for ratification under the PSDO
IEEE 802 standard
60 day pre-balllot
5 month FDIS ballot
Comments resolved
802.1AB
Passed (May 2013)
Passed (18 Dec 2013)
Finished & approved by the WG in Beijing
802.1AR
802.1AS
802.11aa
Passed (Feb 2013)
Passed (28 Jan 2014)
Finished in Beijing
Will be considered by WG in Hawaii
802.11ad
802.11ae
802.1AEbw
Passed (Jan 2014)
802.1AEbn
802.22
Passed (May 2014)
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 :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

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 X: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 AE: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 WG in March 2014, and liaised to SC6 in May 2014 as N15944
The standard was published as ISO/IEC AB: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 WG in March 2014, and liaised to SC6 in May 2014 as N15947
Standard was published as ISO/IEC AR: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 WG in March 2014, and liaised to SC6 in May 2014 as N15948
Standard was published as ISO/IEC AS: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
Standard will be published as :2012/Amd 1:2014
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
Standard will be published as :2012/Amd 3: 2014
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
Standard will be published as :2012/Amd 2: 2014
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 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 :2014
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 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 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 (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 will be here to assist
Note: the IEEE 802 liaison will need to suggest that SC6 pass a motion wrt 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
China NB thanks for IEEE’s contribution of IEEE (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 SC6N 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
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
Possible outline …
IEEE 802 thanks the China NB for its comment during the 60 day ballot on IEEE as part of its consideration according to the PSDO agreement
It appears the China NB objects to IEEE using a security mechanism based on the use of ISO/IEC/IEEE X because the China NB believes its comments in the previous FDIS ballot on ISO/IEC/IEEE X have not been satisfactorily resolved
It is up to the China NB to determine whether their comments on previous FDIS ballots have been satisfactorily resolved or not.
However, we note IEEE 802 have responded fully to every comment received from all NBs during all 60 day and FDIS ballots undertaken as part of the PSDO agreement defined approval process
Andrew Myles, Cisco

40. The SC will discuss a response to the China NB comment on IEEE 802.22
Possible outline
IEEE 802 do not believe there are any outstanding issues related to ISO/IEC/IEEE X, and note that this standard is being successfully implemented globally today in billions of devices.
However, the IEEE 802 encourage China NB security experts to provide further details of any issues related to ISO/IEC/IEEE X at any time, preferably at a face to face meeting of the IEEE Working Group.
The IEEE Working Group meeting schedule is available from the IEEE Working Group Chair
Andrew Myles, Cisco

41. The SC will discuss a response to the China NB comment on IEEE 802.22
Possible outline
The China NB also asserted that the quality and reputation of ISO/IEC standards have been diminished by the use of PSDO defined approval process
No evidence has been provided to justify this assertion, and so it is difficult for the IEEE 802 to respond in any meaningful way.
However, the IEEE 802 note the PSDO agreement between IEEE and ISO has given ISO/IEC JTC1 NBs, as important stakeholders of the widely implemented and used suite of IEEE 802 standards, an effective mechanism for input and approval.
The IEEE 802 believes the PSDO process has been very effective and encourages all NBs to make greater use of the opportunity to participate in the development and approval of the IEEE/ISO/IEC 8802 series of standards
Andrew Myles, Cisco

42. 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
She reports that the comments were referred to the ISO Central Secretariat
She noted to the ISO Central Secretariat that IEEE 802 were unable to respond to these China NB comments
Responsibility for resolution now lies with ISO
Andrew Myles, Cisco

43. A number of security presentations based on TePA have been considered by SC6
Proposal
Equivalent
Chinese standard?
What type?
NP proposal in WG1?
Implemented?
TEPA-AC
Subset of X
Yes (can we get a translation?)
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
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

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

45. 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 u)
WAPI will have ample government funding for the foreseeable future
Andrew Myles, Cisco

46. 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 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
There has been no further progress
Andrew Myles, Cisco

47. Individuals in China and HK are still pushing an alternative security agenda
Kingston Zhang (HK SAR, observer in SC6) 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

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

49. 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
PWI proposal in WG7
Optimization technology in WLAN
None obvious;
Andrew Myles, Cisco

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

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

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

53. It was “decided” 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
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 Virtual AP document out for comment before the May 2014 interim WG7 meeting passed
Comments were requested by 30 April …
Andrew Myles, Cisco

54. SC6/WG7 are planning to discuss the Virtual AP document in late May 2014
The IEEE WG responded to the call for comments on the Virtual AP 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”
It seems to totally ignore the IEEE 802 submission noting that the problem has already been solved
WG7 will discuss this issue during their meeting in Beijing on May 2014
The IEEE 802 Liaison to SC6 has reached out to WG7 Chair to confirm the IEEE submission is on the agenda, and when it will ne discussed; there is a possibility that an IEEE 802 rep might be able to attend the WG7 meeting in Beijing.
Andrew Myles, Cisco

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

56. The SC will probably need to select a new IEEE 802 liaison to SC6
Bruce Kraemer has acted as the IEEE 802 liaison officer to SC6 for some years
It is possible/likely that Bruce will unavailable to continue this role
Who would like to take over?
Note: it is probably inappropriate for Andrew Myles to take this role because of a perceived conflict with his “other hat”
Andrew Myles, Cisco

57. IEEE 802 JTC1 SC will consider any motions
The IEEE 802 JTC1 SC recommends to the IEEE WG that be liaised to SC6 as the IEEE WG response to SC6 NB comments on the recent FDIS ballots on aa/ad/ae
Moved
Seconded
Result
Andrew Myles, Cisco

58. The IEEE 802 JTC1 SC will prepare for the October SC6 meeting at the July 2014 Plenary meeting
Resolution from SC6 on scheduling for Oct meeting suggests we need to have our submissions to SC6 ready out of the July 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
The agenda for July will be constructed as SC6 agenda items become clear
Andrew Myles, Cisco

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

60. ISO/IEC JTC1 is changing
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
Proposed motion (for ratification 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 arrange for any “IEEE 802 experts” to be added to any Working Group lists in ISO/IEC JTC1
Moved
Seconded
Result
Yell, if you would like to be appointed
Andrew Myles, Cisco

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

62. 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 Hawaii in May 2014, adjourns
Moved:
Seconded:
Result:
Andrew Myles, Cisco
Andrew Myles, Cisco