Embed Size (px)
DESCRIPTION
doc.: IEEE /0795r0 Submission July 2014 Andrew Myles, CiscoSlide 3 Participants have a duty to inform in relation to patents All participants in this meeting have certain obligations under the IEEE- SA Patent Policy (IEEE-SA SB Bylaws 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
Citation preview
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 1
IEEE 802 JTC1 Standing CommitteeJuly 2014 agenda
15 July 2014
Authors:
Name Company Phone email
Andrew Myles Cisco +61 2 84461010+61 418 656587 [email protected]
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
This presentation will be used to run the IEEE 802 JTC1 SC meetings in San Diego in July 2014
• This presentation contains a proposed running order for the IEEE 802 JTC1 Standing Committee meeting in San Diego in July 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
Slide 2
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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 [email protected]– 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
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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.
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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.
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
• Call to Order
• Select recording secretary <- important!
• Approve agenda
• Conduct meeting according to agenda
• Recess
The IEEE 802 JTC1 SC has three slots at the San Diego plenary meeting, but may only need one slot
Andrew
Myles, Cisco
• Call to Order
• Select recording secretary <- important!
• Conduct meeting according to agenda
• Adjourn
• Note: Probably any motions today
Tuesday15 July, PM1
Thursday17 July, PM1
• Call to Order
• Select recording secretary <- important!
• Conduct meeting according to agenda
• Recess
Wednesday16 July, PM1
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The IEEE 802 JTC1 SC has a detailed list of agenda items to be considered
In no particular order:• Approve minutes
– From interim meeting in May 2014 in Hawaii
• 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
Slide 10
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew
Myles, Cisco
Slide 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 San
Diego in July 2014, as documented on slide 10 of <this slide deck>• Moved:• Seconded:• Result:
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The IEEE 802 JTC1 SC will consider approval of the minutes of its Hawaii meeting
Motion to approve minutes• The IEEE 802 JTC1 SC approves the minutes for its meeting in Hawaii in
May 2014, as documented in 11-14-0725-r0• Moved:• Seconded:• Result:
Andrew
Myles, Cisco
Slide 12
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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 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
… that were reaffirmed by 802 EC in Mar 2014 when formalising status of IEEE 802 JTC1 SC
Slide 13
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
In recent times, IEEE 802 has liaised a variety of drafts to SC6 since Nov 2013
Slide 14
802.11 802.1 802.3 802.22 802.15802.11ac D7.0(Nov 2013)
802.1Xbr D1.2(Nov 2013)
TBD(see later)
802.22-2011(Jan 2014)
TBD(see later)
802.11af D6.0(Nov 2013)
802 D1.9(May 2014)
802.11mc D3.0(Jul 2014)
802.1Q D2.0(May 2013)
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The SC will hear an update on plans for liaising additional IEEE 802.1 drafts to SC6
802 O&A • IEEE 802 O&A was previously liaised to SC6 in May 2014• Since then D2.0 has been approved and is in the publication process• Is the plan to send it to SC6 under PSDO in November?
Other 802.1 drafts/standards• What other drafts/standards should be liaised to SC6? And when?
Slide 15
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The SC will hear an update on plans for liaising additional IEEE 802.3 drafts to SC6
802.3 drafts/amendments• The current plan for the IEEE 802.3 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 802.3 would like to liaise to SC6 as part of PSDO process
• Subsequently, David Law and Adam Healy sent the Chair an e-mail:– We are thinking of proposing to IEEE 802.3 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 802.11 already uses to do this?– I believe that IEEE 802.11 submits these drafts at sponsor - is that correct?
• This will be discussed again by IEEE 802.3 in July 2014
Slide 16
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC will hear an update on plans for liaising additional IEEE 802.11 drafts to SC6
802.11ac/af standards for PSDO ratification• 802.11ac and 802.11af have both been published
– IEEE 802.11ac-2013– IEEE 802.11af-2014
• It is probably time to start the PSDO process• Motion
– The IEEE 802 JTC1 SC recommends to the IEEE 802.11 WG that IEEE 802.11ac-2013 and IEEE 802.11af-2014 are submitted to ISO/IEC JTC1/SC6 for ratification under the PSDO process
– Moved– Seconded– Result
Andrew
Myles, Cisco
Slide 17
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC will hear an update on plans for liaising additional IEEE 802.11 drafts to SC6
802.11ai draft• IEEE 802.11ai D2.0 passed LB in April 2014• Should we liaise it to SC6 as part of the agreement with SC6 related to
the PSDO?– Technically we do not have to liaise it until Sponsor Ballot– Should we wait until D3.0?
• Motion– The IEEE 802 JTC1 SC recommends to the IEEE 802.11 WG that IEEE
802.11ai D2.0 is liaised to ISO/IEC JTC1/SC6 for its information– Moved– Seconded– Result
Andrew
Myles, Cisco
Slide 18
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC will hear an update on plans for liaising additional IEEE 802.11 drafts to SC6
802.11ah draft• IEEE 802.11ah D2.0 passed LB in Jul 2014• Should we liaise it to SC6 as part of the agreement with SC6 related to
the PSDO?– Technically we do not have to liaise it until Sponsor Ballot– Should we wait until D3.0?
• Motion– The IEEE 802 JTC1 SC recommends to the IEEE 802.11 WG that IEEE
802.11ah D2.0 is liaised to ISO/IEC JTC1/SC6 for its information– Moved– Seconded– Result
Andrew
Myles, Cisco
Slide 19
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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?– 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.”
• Jul 2014: asked Jodi for update?
Slide 20
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The SC will discuss the possibility of liaising additional IEEE 802.22 drafts to SC6
802.22 amendments• The 802.22 WG has submitted 802.22 under the PSDO• However, the WG has not yet decided which amendments to liaise to
SC6• Hopefully that question will be discussed this week …
Slide 21
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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
Slide 22
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
IEEE 802 has pushed seven standards completely through the PSDO ratification process
IEEE 802standard
60 daypre-balllot
5 monthFDIS 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 Passed (2013) Passed (21 Oct 2013) Liaised in Jan 2014
802.1AB Passed (May 2013) Passed (18 Dec 2013) Liaised in May 2014
802.1AR Passed (May 2013) Passed (18 Dec 2013) Liaised in May 2014
802.1AS Passed (May 2013) Passed (18 Dec 2013) Liaised in May 2014
802.3 Passed (2013) Passed (16 Feb 2014) Not required
Slide 23
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.11-2012 has been ratified as ISO/IEC/IEEE 8802-11:2012 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 24
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 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
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1X-2010 has been ratified as ISO/IEC/IEEE 8802-1X:2013 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 25
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 8802-1X:2013
N15607
N15771
N15871
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1AE-2006 has been ratified as ISO/IEC/IEEE 8802-1AE:2013 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 26
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 8802-1AE:2013
N15608
N15770
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1AB-2009 has been ratified as ISO/IEC/IEEE 8802-1AB:2014 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 27
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 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15944
• The standard was published as ISO/IEC/IEEE 8802-1AB:2014 on 15 March 2014
N15659
N15829
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1AR-2009 has been ratified as ISO/IEC/IEEE 8802-1AR:2014 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 28
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 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15947
• Standard was published as ISO/IEC/IEEE 8802-1AR:2014 on 15 March 2014
N15659
N15830
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1AS-2011 has been ratified as ISO/IEC 8802-1AS:2014 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 29
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 802.1 WG in March 2014, and liaised to SC6 in May 2014 as N15948
• Standard was published as ISO/IEC/IEEE 8802-1AS:2014 on 15 March 2014
N15659
N15831
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.3-2012 has been ratified as ISO/IEC/IEEE 8802-3:2014 & FDIS comment resolutions liaised
Andrew
Myles, Cisco
Slide 30
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 was published as ISO/IEC/IEEE 8802-3:2014
N15724
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
IEEE 802 has six standards in the pipeline for ratification under the PSDO
IEEE 802standard
60 daypre-balllot
5 monthFDIS ballot
Comments resolved
802.11aa Passed (Feb 2013) Passed (28 Jan 2014) FDIS ballot comments to be approvedby IEEE 802 EC
in July 2014802.11ad Passed (Feb 2013) Passed (28 Jan 2014)
802.11ae Passed (Feb 2013) Passed (28 Jan 2014)
802.1AEbw Passed (Jan 2014) - Probably in 5 month ballot?
802.1AEbn Passed (Jan 2014) - Probably in 5 month ballot?
802.22 Passed (May 2014) - Waiting for comment resolutions
Slide 31
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1ae-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 1:2014 & FDIS comments are in process
Andrew
Myles, Cisco
Slide 32
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 were approved by 802.11 WG in May 2014– See 11-14-0552-00 - needs to be approved by IEEE 802 EC in July 2014
• Standard was published as 8802-11:2012/Amd 1:2014
N15647
N15883
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1aa-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 2:2014 & FDIS comments are in process
Andrew
Myles, Cisco
Slide 33
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 were approved by 802.11 WG in May 2014– See 11-14-0552-00 - needs to be approved by IEEE 802 EC in July 2014
• Standard was published as 8802-11:2012/Amd 2: 2014
N15647
N15884
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
IEEE 802.1ad-2012 has been ratified as ISO/IEC 8802-11:2012/Amd 3:2014 & FDIS comments are in process
Andrew
Myles, Cisco
Slide 34
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 were approved by 802.11 WG in May 2014– See 11-14-0552-00 - needs to be approved by IEEE 802 EC in July 2014
• Standard was published as 8802-11:2012/Amd 3: 2014
N15647
N15885
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Pre-ballot on IEEE 802.1AEbw passed pre-ballot in Jan 2014, and comment resolution is complete
Andrew
Myles, Cisco
Slide 35
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 802.1 WG in March 2014, and were liaised to SC6 as N15946
FDIS ballot: in process• Checking status with Jodi
N15858
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Pre-ballot on IEEE 802.1AEbn passed pre-ballot in Feb 2014, and comment resolution is complete
Andrew
Myles, Cisco
Slide 36
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 802.1 WG in March 2014, and were liaised to SC6 as N15945
FDIS ballot: in process• Checking status with Jodi
N15857
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Pre-ballot on 802.22 passed pre-ballot in May 2014, but comment resolutions still in process
Andrew
Myles, Cisco
Slide 37
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
• The IEEE 802 JTC1 SC has developed a response but it needs to be approved by the IEEE 802,22 WG and the IEEE 802 EC before liaising to SC6
FDIS ballot: not started• Checking status with Jodi
N15954
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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
Slide 38
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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
Slide 39
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC agreed in May 2014 on a response to the China NB comment on IEEE 802.22
Response (part 1/3) • IEEE 802 thanks the China NB for its comment during the 60 day ballot
on IEEE 802.22 as part of its consideration according to the PSDO agreement
• In the comment, the China NB objected to IEEE 802.22 using a security mechanism based on the use of ISO/IEC/IEEE 8802-1X because the China NB believes its comments in the previous FDIS ballot on ISO/IEC/IEEE 8802-1X 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 has responded fully to every comment received from all ISO/IEC SC6 and JTC1 NBs during all 60 day and FDIS ballots undertaken as part of the PSDO defined process
Andrew
Myles, Cisco
Slide 40
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC agreed in May 2014 on a response to the China NB comment on IEEE 802.22
Response (part 2/3)• IEEE 802 does not believe there are any outstanding issues related to
ISO/IEC/IEEE 8802-1X, and notes that this standard is being successfully implemented globally today in billions of devices.
• IEEE 802 encourages any users of the standard, including China NB security experts, to provide further details of any issues related to ISO/IEC/IEEE 8802-1X at any time
• This can be done by e-mail or at a face to face meeting of the IEEE 802.1 Working Group.
• The IEEE 802.1 Working Group meeting schedule is available from the IEEE 802.1 Working Group Chair (Glenn Parsons, [email protected])
Andrew
Myles, Cisco
Slide 41
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC agreed in May 2014 on a response to the China NB comment on IEEE 802.22
Response (part 3/3)• In the comment, the China NB also asserted that the quality and
reputation of ISO/IEC standards have been diminished by the use of PSDO defined approval processes
• No evidence has been provided to justify this assertion, so it is difficult for IEEE 802 to respond in any meaningful way.
• However, IEEE 802 notes the PSDO agreement between IEEE and ISO has given ISO/IEC JTC1 NBs, as important stakeholders of the widely implemented and used ISO/IEC/IEEE 8802 series of standards, an effective mechanism for both review and approval.
• 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 ISO/IEC/IEEE 8802 series of standards
Andrew
Myles, Cisco
Slide 42
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
IEEE 802.22 WG needs to ask 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 for NBs to contribute to the revision process in the IEEE 802 WG– This process is documented in N15606
• The agreement was ratified by resolutions in SC6 in relation to each of IEEE 802.1/3/11
• IEEE 802.11 WG need to ask for a similar agreement in relation to IEEE 802.22
Slide 43
N15606
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
A liaison is required to ask SC6 for revision responsibility for 802.22
Proposed liaison to SC6 (part 1/2)• The IEEE 802.22 WG is currently making use of the PSDO agreement
between ISO and IEEE to enable ISO/IEC JTC1 NBs to review and ratify IEEE 802.22 standards as ISO/IEC/IEEE 8802-22 standards
• The IEEE 802.22 WG is using the same processes as those being used to enable the review and ratification the ISO/IEC/IEEE 802-1/3/11 series of standards, including those processes specified in 6N15606
• ISO/IEC JTC1/SC6 has made the use of those processes the basis of resolutions within SC6 to allocate responsibility for the revision process of the ISO/IEC 8802-1/3/1 series of standards to the relevant IEEE 802 WG
Slide 44
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
A liaison is required to ask SC6 for revision responsibility for 802.22
Proposed liaison to SC6 (part 1/2)• The IEEE 802.22 WG requests that SC6 adopts the following similar
resolution with respect to the ISO/IEC/IEEE 8802-22 series of standards– As empowered by clause A1.2.1 of the PSDO agreement between ISO and
IEEE, SC 6 decides to allocate responsibility for the revision process of the ISO/IEC/IEEE 8802-22 series of standards to the IEEE 802.22 WG while the IEEE 802.22 WG has an ongoing revision process for the IEEE 802.22 standard. A condition of this resolution is that SC 6 and its NBs have access to an established mechanism to contribute to the revision process in the IEEE 802.22 WG.
• Note that this proposed resolution is in the same form as Resolutions 6.1.9/1011 that were approved in September 2012 at the ISO/IEC JTC 1/SC 6 plenary meeting in Gratkorn/Graz, Austria
Slide 45
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The SC will consider a recommendation to the IEEE 802.22 WG and IEEE 802 EC for a SC6 liaison
Motion• The IEEE 802 JTC1 SC recommends to the IEEE 802.22 WG and the
IEEE 802 EC that a liaison, based on slides 44-45, be sent to ISO/IEC JTC1/SC6 asking they allocate responsibility for the revision process of the ISO/IEC/IEEE 8802-22 series of standards to the IEEE 802.22 WG
• Moved• Seconded• Result
Slide 46
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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 802.1X
Yes (can we get a translation?)
Not yet Not known
TLSec Subset of 802.1AE
Not yet; BWIPS driving
Not yet Yes, in lab
TAAA 802.16 security
No? Not yet Yes, in lab
WAPI Subset of 802.11i based security
Yes Yes, passed, but withdrawn
Yes, required in handsets & SP APs but rarely used
TISec Subset/copy of IPSec
No? Not yet(in WG7)
Not known
Slide 47
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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
Slide 48
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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
Slide 49
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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
Slide 50
N15845
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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 threat to our security standards has not gone away
Andrew
Myles, Cisco
Slide 51
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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 802.1 Security standards satisfy the Chinese needs for Internet security
Andrew
Myles, Cisco
Slide 52
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
A number of other proposals relevant to IEEE 802.11 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
Yes No Prototype
WLAN Cloud Similar to existing functionality in APs or using HS2.0
No PWI proposal in WG7
Not known
Optimization technology in WLAN
None obvious; No PWI proposal in WG7
Not known
Slide 53
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
There is no news on EUHT standardisation in ISO/IEC … it may be dead• 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 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– The individual involved have apparently been reallocated to other work
Slide 54
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
SC6/WG7 previously decided to delay decisions on two PWI proposals related to WLAN in 2013
• 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
Slide 55
N15692
N15691
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
In Ottawa 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 sniffer and database
Slide 56
6N15913
6N15911
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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• 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 …
Slide 57
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
SC6/WG7 discussed the Virtual AP document in late May 2014
• The IEEE 802.11 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”
• 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
Slide 58
N15951
N15966
N15931
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The latest version of Virtual AP seems to ignore the IEEE 802.11 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 802.11 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
Slide 59
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
It is not clear what the China NB are planning next
• A China NB rep sent the following e-mail 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 Virtual AP proposal is not needed
• It is not clear what the China NB are planning next
Slide 60
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
What should the IEEE 802.11 WG do about “Virtual AP”?
Andrew
Myles, Cisco
Slide 61
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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 out the discussion in Ottawa– But it is really confusing
• However, we do not know whether there were any outcomes
Andrew
Myles, Cisco
Slide 62
N15961
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
What should the IEEE 802.11 WG do about “Optimization technology in WLAN” ?
Andrew
Myles, Cisco
Slide 63
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
The next SC6 meeting will be held in the UK in October 2014
Meeting• ISO/IEC JTC1/SC6
Host• BSI
Date• Week of 20-24 October 2014
(week after WFA meeting in Berlin)
Location• Offices of BSI in London
Slide 64
N15789 N15955
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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 2014-09-05 for posting on the SC 6 web server. Documents received by the Secretariat after 2014-09-05 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 2014-09-30
Slide 65
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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 802.11 Working Group
• There is no further detail
Andrew
Myles, Cisco
Slide 66
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC6/ WG1 agenda for London does not yet exist
• There is no agenda published for WG1 …• … and no interesting uploaded documents• The US NB may attempt to transition WG1 to less F2F meetings …• … but that is not really a IEEE 802 issue
Andrew
Myles, Cisco
Slide 67
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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”
– Adrian Stephens is local! – Or we could call on Tony Jeffree who is also local
• We can delay this decision 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
Slide 68
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC will consider a motion in relation to appointment of the IEEE 802 HoD
• Motion– The IEEE 802 JTC1 SC recommends to the IEEE 802 EC that the IEEE 802
Chair be empowered to appoint the IEEE 802 HoD to the ISO/IEC JTC1/SC6 meeting in London in October 2014
– Moved– Seconded– Result
Andrew
Myles, Cisco
Slide 69
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The SC will consider a motion in relation to empowerment of the IEEE 802 HoD
• Motion– The IEEE 802 JTC1 SC recommends that the IEEE 802 HoD to the SC6
meeting in February 2014 be authorised to:— Appoint the IEEE 802 delegation— Approve any necessary submissions— Call any necessary preparation teleconferences
Andrew
Myles, Cisco
Slide 70
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
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.
Slide 71
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Andrew Myles, Cisco
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 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
• Yell, if you would like to be appointed
Slide 72
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
Are there any other matters for consideration by IEEE 802 JTC1 SC?
Andrew
Myles, Cisco
Slide 73
doc.: IEEE 802.11-14/0795r0
Submission
July 2014
The IEEE 802 JTC1 SC will adjourn for the week
Motion:• The IEEE 802 JTC1 SC, having completed its business in San Diego in
July 2014, adjourns• Moved:• Seconded:• Result:
Andrew
Myles, Cisco
Slide 74
