JTC1 Ad Hoc Mar 2011 agenda 18 Mar 2011 doc.: IEEE 802.11-11/0311r2

advertisement
doc.: IEEE 802.11-11/0311r2
JTC1 Ad Hoc Mar 2011 agenda
18 Mar 2011
Authors:
Name
Company
Andrew Myles Cisco
Submission
Phone
email
+61 284461010
andrew.myles@cisco.com
Slide 1
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
This presentation will be used to run the JTC1 Ad
Hoc meetings in Singapore in Mar 2011
• This presentation contains a proposed running order for the IEEE 802.11
JTC1 Ad Hoc committee meeting in March 2011, 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
Submission
Slide 2
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
Participants have a duty to inform in relation to
patents
• All participants in this meeting have certain obligations under the IEEESA Patent Policy (IEEE-SA SB Bylaws subclause 6.2). Participants:
– “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of
each “holder of any potential Essential Patent Claims of which they are
personally aware” if the claims are owned or controlled by the participant or the
entity the participant is from, employed by, or otherwise represents
— “Personal awareness” means that the participant “is personally aware that the holder
may have a potential Essential Patent Claim,” even if the participant is not personally
aware of the specific patents or patent claims
– “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of
“any other holders of such potential Essential Patent Claims” (that is, third
parties that are not affiliated with the participant, with the participant’s employer,
or with anyone else that the participant is from or otherwise represents)
– The above does not apply if the patent claim is already the subject of an
Accepted Letter of Assurance that applies to the proposed standard(s) under
consideration by this group
• Early identification of holders of potential Essential Patent Claims is
strongly encouraged; there is no duty to perform a patent search
Submission
Slide 3
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
There are a variety of patent related links
• All participants should be familiar with their obligations under the IEEESA Policies & Procedures for standards development.
• Patent Policy is stated in these sources:
– IEEE-SA Standards Boards Bylaws
— http://standards.ieee.org/guides/bylaws/sect6-7.html#6
– IEEE-SA Standards Board Operations Manual
— http://standards.ieee.org/guides/opman/sect6.html#6.3
• Material about the patent policy is available at
– http://standards.ieee.org/board/pat/pat-material.html
• If you have questions, contact the IEEE-SA Standards Board Patent
Committee Administrator at patcom@ieee.org or visit
http://standards.ieee.org/board/pat/index.html
• This slide set is available at http://standards.ieee.org/board/pat/patslideset.ppt
Submission
Slide 4
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
A call for potentially essential patents is not
required in the JTC1 Ad Hoc
• 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
Submission
Slide 5
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc 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.
Submission
Slide 6
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
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
Submission
Slide 7
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc 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.
Submission
Slide 8
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc has a very general proposed
agenda for the Singapore meeting
Tuesday AM1
Wednesday AM1
Thursday AM2
• Call to Order
• Call to Order
• Call to Order
• Select recording
secretary
• Select recording
secretary
• Select recording
secretary
• Approve agenda
• Conduct meeting
according to agenda
• Conduct meeting
according to agenda
• Recess
• Adjourn
• Conduct meeting
according to agenda
• Recess
Submission
Slide 9
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc has a detailed list of agenda items
to be considered
Tuesday AM1:
• Approve agenda
• Approve minutes from Jan in LA
• Review extended goals
• Review status of liaisons previously sent to SC6
• Discuss responses to identifier conflict liaison previously sent to SC6
• Update on status of ISO/IEC 8802-11:2005
• Update on status of ISO/IEC 8802-3:2000
• Update on WAPI progress
Submission
Slide 10
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc has a detailed list of agenda items
to be considered
Wednesday AM1:
• Discuss a proposed 802.1X/AE related liaison
Submission
Slide 11
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc has a detailed list of agenda items
to be considered
Thursday AM2:
• Review and approve any liaisons to SC6
• Approve delegation for next SC6 meeting
Submission
Slide 12
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc will consider approving its
agenda
Motion to approve agenda
• The JTC1 Ad Hoc approves the agenda for its meeting in Singapore in
March 2011, as documented on pages 9-13 of <this slide deck>
• Moved:
• Seconded
• Result
Submission
Slide 13
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc will consider approval of previous
minutes
Motion to approve minutes
• The JTC1 Ad Hoc approves the minutes for its meeting in LA in January
2011, as documented in 11-11-0248-00-0jtc-jtc1-ad-hoc-jan-2011minutes.doc
• Moved:
• Seconded
• Result
Submission
Slide 14
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 Ad Hoc reaffirmed its general goals in
Sept 09, but they were extended in Nov 2010
Agreed (with changes from Nov 2010) goals
• Provides a forum for 802 members to discuss issues relevant to both:
– IEEE 802
– ISO/IEC JTC1/SC6
• Recommends positions to ExCom on ISO/IEC JTC1/SC6 actions
affecting IEEE 802
– Note that 802 LMSC holds the liaison to SC6, not 802.11 WG
• Participates in dialog with IEEE staff and 802 ExCom on issues
concerning IEEE ’s relationship with ISO/IEC
• Organises IEEE 802 members to contribute to liaisons and other
documents relevant to the ISO/IEC JTC1/SC6 members
Extensions
• The extensions to our goals came out of the 802 ExCom ad hoc held in
November 2010 on the Friday evening
Submission
Slide 15
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The 802.11 WG has liaised various Sponsor Ballot
drafts to ISO/IEC JTC1/SC6
Task
Group
Liaised
after
LA
Liaised
after
Orlando
Liaised
after
Beijing
Liaised
after
SD
Liaised
after
Hawaii
Liaised
after
Dallas
Liaised
after
Dallas
Jan 10
Mar 10
May 10
July 10
Sept 10
Nov 10
Jan 11
TGmb
-
-
-
-
-
D6.0
-
TGs
-
-
-
-
-
D8.0
-
TGu
D8.0
-
-
D11.0
-
D13.0
-
TGv
D9.0
-
D11.0
D13.0
D15.0
-
-
TGz
D7.0
-
D9.0
D12.0
D13.0
-
-
Submission
Slide 16
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
No technical comments have been received on any
of the drafts liaised to ISO/IEC JTC1/SC6
• No formal technical comments have been received
• A Swiss NB representation has noted a possible input informally
– I have discovered three years ago some flaws in 8802-11:2005, in the basic
MAC protocol specs (the sequence number handling) which I would like to verify
in the actual draft version, and report to you if it is still there
– Note: it has since been reported that the alleged problem has already been fixed
in IEEE 802.11-207
Submission
Slide 17
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
Two responses were received to the IEEE 802.11
liaison to SC6 related to identifier conflicts
• IEEE 802.11 WG liaised a document to SC6 in early Dec 10 noting a
conflict between WAPI and 802.11 identifiers
– 11-10-1359-01-0jtc-liaison-letter-to-sc6-in-relation-to-identifiers.doc
• Both the Swiss and Chinese NBs have responded
– The responses are similar
Submission
Slide 18
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The Swiss NB has responded to the IEEE 802.11
liaison related to identifier conflicts
• The Swiss NB has submitted a response to SC6 in relation to identifier
conflict s between WAPI and 802.11k
– See embedded document to right
• The Swiss NB counter proposal is:
– Perform additional checks when encountering an IE 68, to distinguish the WAPI
and 11k IEs.
– Document dual use in the ANA registry.
– For implementations combining WAPI and 802.11k, ISO/IEC 20011 should
allocate another identifier for the 11k IE and other values for the two related
status codes, following the ANA-mechanisms.
– Any identifiers required by future extensions of ISO/IEC 20011 or any other Sc6
work referring to and requiring interoperability or coexistence with IEEE 802.11
shall be properly registered using the ANA-mechanisms.
Submission
Slide 19
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The Chinese NB has responded to the IEEE 802.11
liaison related to identifier conflicts
• The Chinese NB has submitted a response to SC6 in relation to identifier
conflict s between WAPI and 802.11k
– See embedded document to right
• The Chinese NB comments summarised are:
– IEEE 802.11k caused the problem by conflicting with WAPI, which existed
before 11k
– It is unreasonable for WAPI to change given “billions” of deployed systems since
2003
– A pragmatic approach is to allocate the IE to both 11k and WAPI, with a note
that additional parsing is required to differentiate the use of the IE
– Going forward the IEEE becomes the registration authority for 8802-11
Submission
Slide 20
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc developed a rough consensus for
of a response to the Swiss & Chinese NBs in Jan 11
• A rough consensus developed during discussions in LA
– Endorse the addition of PC text in the ISO 20011 draft to account for the IE
collision between WAPI and 802.11k.
– Assign NEW IEs out of the ANA registry and forward them to SC6 and
encourage them to transition to these new IEs going forward while using the PC
text recommendation in the transition. (this does not require a request from SC6
to the 802.11 ANA)
Submission
Slide 21
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider a proposed response
to N14544 and N14511
• A possible liaison has been developed to reflect the consensus
– See embedded document
• The ad hoc will:
– Discuss the liaison on Tuesday
– Consider approval of a final version of the liaison on Thursday
Submission
Slide 22
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
SC6 is currently determining the status of 880211:2005
• ISO/IEC reviews the status of standards after 5 years using a “systematic
review” processs
• It was reported in Jan 2011 that 8802-11:2005 (IEEE 802.11- 2003) was
subjected to this process
– See embedded document to right
• The recommend action was “confirm”
– Withdraw: 0
– Revise/Amend: 1 (Jamaica)
– Confirm: 11 (Belgium, China, Czech Rep, Ireland, Italy, Korea, Netherlands,
Nigeria, Norway, Spain, USA)
– Abstain: 21
– Stabilize: 0
Submission
Slide 23
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
IEEE 802.3 has asked SC6 for 8802-3:2000 to be
withdrawn
• It has been confirmed that ISO/IEC 8802-3:2000 is also part of the
systematic review process in SC6
• The IEEE 802.3 WG has sent a liaison to SC6 asking that ISO/IEC 88023:2000 be withdrawn
– See embedded document
• The reasons were:
– ISO/IEC 8802-3:2000 is very out of date
– The PSDO cooperation agreement of March 2008 formalized the full recognition
by ISO and JTC1 of IEEE Standards for reference purposes in the development
of ISO and JTC1 standards
• It has previously been decided that 802.11 WG would not make the
same request to ensure ISO/IEC 8802-11 unambiguously had
“international” status given the WAPI issue
– IEEE 802.3 does not currently have a similar issue
Submission
Slide 24
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
It was recognised by the ad hoc in Sept 09 that
WAPI is of vital interest to the JTC1 Ad Hoc
• It was agreed by the JTC1 ad hoc in Hawaii in Sept 09 that WAPI
remains an important and constant issue for consideration
• This is the case for a variety of reasons, possibly including:
– WAPI appears to duplicate functionality of 802.11i
– The promoters of WAPI assert that 802.11i is insecure
– It is unclear how or whether 802.11i and WAPI can coexist
–…
Submission
Slide 25
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The new project proposal for WAPI in ISO/IEC
JTC1/SC6 was approved in early 2010
• WAPI was submitted by the China to ISO/IEC JTC1/SC6
as a New Project proposal for a stand alone standard
• No response has yet been received from the IEEE 802 liaison to SC6 in
Nov 2009 (09/1254r1)
– This liaison noted that the claims that IEEE 802.11 is not secure are unfounded
– The liaison also suggests that WAPI should be submitted to IEEE 802.11 for
consideration
– This liaison was discussed at the SC6 meeting in Jan 10 but no reply was
received
• The SC6 National Bodies subsequently approved the New Project
– 10 out of 18 NB’s voted “yes” (10 required)
– 5 NB’s stated they would participate in the project (5 required)
Submission
Slide 26
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
There was some discussion of WAPI at the SC6
meeting in London, and a comment ballot started
• A new version of WAPI was proposed
– The previous version was written as an amendment
– The new version is written as a standalone standard
— It references 8802-11:2005, which is actually IEEE 802.11-2003
– The new version is called 20011 instead of as 8802-11 amendment
• Dispositions were also provided to comments by NB’s related to the
WAPI NP proposal
– Only comments were from US and UK
– The proposed responses to the comments
were subject to a ballot closing on 6 Jan 11
Submission
Slide 27
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
No response has been received in relation to IEEE
802 rebuttal of false assertions about 802.11 security
• IEEE 802 liaised a document to SC6 in early Jan 10 noting various
erroneous claims about 802.11 in the WAPI NP proposal comment
resolution document
– 11-10-1358-02-0jtc-liaison-letter-to-sc6-in-relation-to-n14436.doc
• No response has been received as of March 2011
• The IEEE 802.11 WG has been encouraged to participate in SC6 and
any comment resolution meeting
• It is assumed that any IEEE 802 representatives at the SC6 meeting in
June will represent the views in this liaison
Submission
Slide 28
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
No response has been received in relation to US NB
comments on the proposed NP dispositions
• Only one NB provided a response to the proposed comment disposition
– US: see document to right
• No response has been received to these comments
• It is assumed they will be addressed at the SC6 meeting in June in San
Diego
Submission
Slide 29
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The status of the “WAPI copyright issue” is
unknown
• Previous versions of the WAPI specification contained IEEE copyrighted
material
• The IEEE staff were working with ISO and SAC to resolve the copyright
issues
• It is unknown whether the copyright issues are now resolved given the
recent rewrite of WAPI
Submission
Slide 30
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
There were a number of items of particular interest
to IEEE 802 discussed at the London SC6 meeting
• The Chinese NB made proposals in London (Sept 10) for alternatives to:
– 802.11 – new PHY and MAC (NuFront)
– 802.1X – proposal is based on TePA (IWNCOMM)
– 802.1AE – proposal is TLSec (IWNCOMM)
– 802.16 security – proposal is TAAA (IWNCOMM)
• It was proposed that SC6 start Study Periods to examine these
proposals before formal projects are started
• However, the documents were submitted too late for any formal
resolutions to start Study Periods
802.11
Submission
802.1X
802.1AE
802.16 security
Slide 31
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The Chinese NB security related proposals were all
based on TePA
• SC27 has approved TePA (Triple-Element Peer Authentication )
• TePA is essentially the authentication part of WAPI
• TePA is defined as an amendment to 9798-3 (Information technology -Security techniques -- Entity authentication -- Part 3: Mechanisms using
digital signature techniques)
• The security proposals (replacements of 802.1X, 802.1AE and 802.16
security) are all directly or indirectly based on TePA
Submission
Slide 32
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The China NB has confirmed that they will be
making multiple NP proposals
• The actual NP proposals or motions are not yet available but the NP
topics are on the agenda for the San Diego meeting in June 2011
– See SC6/WG1 agenda embedded
• The SC6/WG1 agenda includes
– 5.4. Other proposals related with LAN
—
—
—
—
5.4.1 Access control ← 802.1X security replacement
5.4.2 PHY MAC Spec ← 802.11 replacement
5.4.3 Further enhancement on LAN Security ← 802.1AE replacement
5.4.4 MAC Security Specifications ← 802.16 security replacement
• It is not clear if there are associated motions
• Any motions will considered by SC6
– The proposed SC6 agenda is currently very generic
Submission
Slide 33
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider material related to
SC6 proposals to replace 802.1X/AE
• Two members of the 802.1 Security Task Group reviewed, during the
Nov 10 plenary, the contribution to ISO/IEC JTC1 SC6 promoting a
replacement to 802.1X/AE
• They concluded the contribution was misleading and inaccurate
– … comments on IEEE Std 802.1AE-2006/IEEE Std 802.1X-2010 are either
inaccurate or could be misleading in a number of major respects particularly
when presented those who are not familiar with the current state of the art of
both bridging and security technology
Submission
Slide 34
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider material related to
SC6 proposals to replace 802.1X/AE
• A possible liaison has been developed based on the 802.1 Security Task
Group tiger team review
– See embedded document
• The ad hoc will:
– Discuss the liaison on Wednesday
– Consider approval of a final version of the liaison on Thursday
Submission
Slide 35
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The next ISO/IEC JTC1/SC6 meeting is being held in
June 11 in San Diego
• SC6 has a meeting every 9 months or so
– The last meeting was held in Sept 10 in London
– The next meeting is scheduled for 20-24 June 11 in San Diego
– The following meeting is in China in March 2012
• IEEE 802 will appoint attendees during the March 2011 plenary meeting
• Official positions will be established in March, and possibly May
Submission
Slide 36
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
All decision and positions related to China will be
reviewed by the IEEE International Ad-hoc
• The IEEE SA BoG has determined that the IEEE International ad hoc
committee is required to review:
– any documents related to China that will be represented as an IEEE position
– any decisions related to China
Submission
Slide 37
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider approval of IEEE 802
delegates to the SC6 meeting in San Deigo
• The next SC6 meeting is in San Diego on 20-24 June 2011
• Volunteers as delegates to the SC6 meeting so far include:
– Bruce Kraemer (HoD)
– Others?
• Maybe we should empower Bruce to add to the delegation as required
• A number of regular IEEE 802 attendees are likely to attend the SC6
meeting as part of NB delegations
Submission
Slide 38
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider approval of IEEE 802
delegates to the SC6 meeting in San Deigo
• The ad hoc will consider the following motion
– The IEEE 802 JTC1 ad hoc recommends to IEEE 802 ExCom that Bruce
Kraemer be appointed Head of Delegation of the IEEE 802 delegation to the
SC6 meeting in San Diego in June 2011. The ad hoc also recommends that as
Head of Delegation that he have the authority to add other interested parties to
the delegation
– Moved
– Seconded
– Result: 10/0/0/
– Action: will be considered by IEEE 802 ExCom on Friday
Submission
Slide 39
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to the identifier conflict
• On Tuesday the ad hoc refined a proposed liaison related to the identifier
conflict with WAPI
– See 11-11-404r0
• The ad hoc will undertake a final review
Submission
Slide 40
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to the identifier conflict
• The ad hoc will consider a motion to allocate an IE identifier and two
status codes
– The IEEE 802 JTC1 ad hoc recommends to the IEEE 802.11 ANA that two
status codes and an IE identifier be allocated for use by ISO/IEC
JTC1/SC6/WG1 in the proposed WAPI standard
– Moved
– Seconded
– Result
Submission
Slide 41
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to the identifier conflict
• The ad hoc will consider a motion to approve a liaison to SC6
– The IEEE 802 JTC1 ad hoc recommends to the IEEE 802.11 WG, IEEE 802
ExCom and IEEE International ad hoc that:
— The content of 11-11-404r0 be sent to ISO/IEC JTC1/SC6 with an appropriate cover
letter
— Bruce Kraemer be given authority to make editorial changes, including the insertion of
allocated ANA values
– Moved
– Seconded
– Result
Submission
Slide 42
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to 802.1X/AE activities in SC6
• On Tuesday the ad hoc refined a proposed liaison related to the
proposed NP for an IEEE 802.1X/AE replacement
– See 11-11-442r0
– See 11-11-442r1 (includes some editorial changes)
• The ad hoc will undertake a final review
Submission
Slide 43
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to 802.1X/AE activities in SC6
• The ad hoc will consider a motion to approve a liaison to SC6
– The IEEE 802 JTC1 ad hoc recommends to the IEEE 802.11 WG, IEEE 802
ExCom and IEEE International ad hoc that:
— The content of 11-11-442r1 be sent to ISO/IEC JTC1/SC6 with an appropriate cover
letter
— Paul Nikolich be given authority to make editorial changes
– Moved
– Seconded
– Result
Submission
Slide 44
Andrew Myles, Cisco
Mar 2011
doc.: IEEE 802.11-11/0311r2
The JTC1 ad hoc will consider motions to approve a
liaison related to 802.1X/AE activities in SC6
• The ad hoc will consider a motion to approve a liaison to SC6
– The IEEE 802 JTC1 ad hoc recommends to the IEEE 802.11 WG, IEEE 802
ExCom and IEEE International ad hoc that copies of IEEE 802.1X and IEEE
802.1AE be sent to SC6 with an appropriate cover letter from Paul Nikolich.
Paul Nikolich is also authorized to send any draft amendments to these
documents if relevant .
– Moved
– Seconded
– Result
Submission
Slide 45
Andrew Myles, Cisco
Download