1. JTC1 ad hoc May 2010 agenda 17 May 2010 May 2010 Authors: May 2010
doc.: IEEE /0524r0
May 2010
JTC1 ad hoc May 2010 agenda
17 May 2010
Authors:
Andrew Myles, Cisco
Andrew Myles, Cisco

2. May 2010
doc.: IEEE /0524r0
May 2010
This presentation will be used to run the JTC1 Ad Hoc meetings in Beijing in May 2010
This presentation contains a proposed running order for the IEEE JTC1 Ad Hoc committee meeting in May 2010, 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
May 2010
doc.: IEEE /0524r0
May 2010
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 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
Andrew Myles, Cisco
Andrew Myles, Cisco

4. There are a variety of patent related links
May 2010
doc.: IEEE /0524r0
May 2010
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. May 2010
doc.: IEEE /0524r0
May 2010
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
Andrew Myles, Cisco
Andrew Myles, Cisco

6. May 2010
doc.: IEEE /0524r0
May 2010
The JTC1 ad hoc will operate using general guidelines for IEEE WG 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
May 2010
doc.: IEEE /0524r0
May 2010
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. May 2010
doc.: IEEE /0524r0
May 2010
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.
The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control.
The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners.
It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form.
Andrew Myles, Cisco
Andrew Myles, Cisco

9. The JTC1 Ad Hoc has a very general proposed agenda
May 2010
doc.: IEEE /0524r0
May 2010
The JTC1 Ad Hoc has a very general proposed agenda
Tuesday PM2
There was no JTC1 ad hoc meeting
The normal Tuesday session was replaced by a special session on Chinese standards
Thursday AM2
Call to Order
Select recording secretary
Approve agenda
Conduct meeting according to agenda
Adjourn
Andrew Myles, Cisco
Andrew Myles, Cisco

10. The JTC1 Ad Hoc has a detailed list of agenda items to be considered
May 2010
The JTC1 Ad Hoc has a detailed list of agenda items to be considered
The agenda items that will be addressed this week are:
Approval of minutes from previous meetings
Review goals of JTC1 ad hoc
Review status of Sponsor Ballot drafts sent to ISO/IEC JTC1/SC6
Discuss possible liaison to ISO/IEC JTC1/SC6 regarding Sponsor Ballot draft review process
Review WAPI status in ISO/IEC JTC1/SC6
Discuss any other JTC1/SC6 liaison matters
Andrew Myles, Cisco

11. The JTC1 ad hoc will consider approving its agenda
May 2010
The JTC1 ad hoc will consider approving its agenda
Motion to approve agenda
The JTC1 ad hoc approves the agenda for its meeting in Beijing in May 2010, as documented on pages 9-10 of 10/0524r0
Moved:
Seconded
Result
Andrew Myles, Cisco

12. The JTC1 ad hoc will consider approval of previous minutes
May 2010
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 Orlando in Mar 10, as documented in jtc-march-2010-minutes.doc
Moved:
Seconded
Result
Andrew Myles, Cisco

13. The JTC1 ad hoc reaffirmed its general goals in Sept 09
May 2010
The JTC1 ad hoc reaffirmed its general goals in Sept 09
Agreed goals
Provides a forum for 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 (and IEEE 802)
Note that 802 LMSC holds the liaison to SC6, not WG
Participates in dialog with IEEE staff and 802 ExCom on issues concerning IEEE’s relationship with ISO/IEC
Organises IEEE members to contribute to liaisons and other documents relevant to the ISO/IEC JTC1/SC6 members …
Andrew Myles, Cisco

14. May 2010
The WG failed to liaised four recent Sponsor Ballot drafts to ISO/IEC JTC1/SC6
The WG has agreed with JTC1/SC6 to liaise Sponsor Ballot drafts to JTC1/SC6 as a matter of course
A variety of drafts were liaised to JTC1/SC6 after LA in Jan 10
No comments were received from JTC1/SC6
Unfortunately a process failure in IEEE WG meant that three further drafts were not liaised to JTC1/SC6 after the Orlando meeting
The IEEE WG leadership are addressing the process issue to ensure it does not happen again
Task Group
Liaised after
LA meeting
Not liaised after
Orlando meetin
TGp
D10.0
D11.0
TGu
D8.0 -
TGv
D9.0
TGz
D7.0
Andrew Myles, Cisco

15. May 2010
The China NB has provided some comments in relation to recent liaisons to SC6
No technical comments were received in relation to any of the Sponsor Ballot drafts liaised to JTC1/SC6
However, the SC6 Secretariat passed on some non technical comments received from the China National Body (NB)
The full set of comments are embedded to the right
The China NB comments can be summarised as follows:
The China NB welcomes the liaison of Sponsor Ballot drafts to SC6
The deadlines for review of the drafts is too short
The amendments on which the drafts are based are unavailable
The IEEE should not submit any amendments or standards for ratification by JTC1 until the procedures have been agreed
ie use of PSDO vs use of some other procedures
The China NB is concerned that there is a trend of less cooperation between IEEE and SC6
Andrew Myles, Cisco

16. May 2010
The WG could offer to accept comments from ISO/IEC NBs at any time
The China NB raises an important practical difficulty for ISO/IEC NBs when reviewing our drafts
In particular, the timescales used in IEEE reviews are much shorter than those typically used for ISO/IEC reviews
There is not much that can be done about the different review mechanisms and timescales
However, it might be possible for the IEEE to help reduce the ISO/IEC NB’s problem by telling them that:
The IEEE WG is willing to be flexible to allow ISO/IEC NBs an opportunity to comment on Sponsor Ballot drafts by accepting comments from ISO/IEC NB’s at any time
The IEEE WG will consider comments received from ISO/IEC NBs as they are received, assuming they are still relevant to the current draft
If it is too late to consider comments as part of the review process then the comments will be archived for consideration during the standards revision process
Andrew Myles, Cisco

17. May 2010
The WG could note to SC6 that all base amendments are (or will be) freely available
The Chinese NB noted that they did not have access to amendments that have been previously ratified
The reality is that all amendments are freely available
, k, r, y and w are all available through the Get802 programme
802.11n either is or will soon be available through the Get802 programme but is currently available for sale
802.11p, u, v, z have all been liaised to SC6
The WG should tell SC6 about the various ways to access IEEE drafts and standards
Andrew Myles, Cisco

18. 802.11 WG may not need to respond to the comment relating to the PSDO
Previously the IEEE WG informed SC6 (see r1) that would be submitted to SC6 using the PSDO process
The current schedule for ratification is June 2011
Any submission to would probably not occur until late 2011 or early 2012
However, the China NB suggested that WG should not submit any amendments or standards for ratification by JTC1 until the procedures have been agreed by IEEE and SC6
Given the long period until anything is likely to be submitted to JTC1, there is plenty of opportunity for SC6 to discuss problems with the PSDO agreement with the ISO/IEC Secretariat
There is probably no need for the IEEE WG to get involved in this issue, particularly as the PSDO agreement is between the IEEE and ISO/IEC, and not the IEEE WG
Andrew Myles, Cisco

19. May 2010
It is proposed that a small Tiger Team work on a letter for consideration by the WG on Friday
It is proposed that the WG send SC6 a liaison that:
Notes that we have received the comments from the China NB
Thanks the China NB for their comments
Recognises the issue of differing time scales and offers to accept comments from NBs at any time
Explains how drafts and standards may be obtained (mostly for free)
Is there consensus that such a liaison should be sent?
Discussion?
Who would like to join a Tiger Team to write and review the letter
Volunteers?
The letter would be approved by the WG on Friday as a personal motion
Andrew Myles, Cisco

20. May 2010
It was recognised by the ad hoc in Sept 09 that WAPI is of vital interest to the ad hoc
It was agreed by the 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 i
The promoters of WAPI assert that i is insecure
It is unclear how or whether i and WAPI can coexist …
Andrew Myles, Cisco

21. The new project proposal for WAPI in ISO/IEC JTC1/SC6 was approved
May 2010
The new project proposal for WAPI in ISO/IEC JTC1/SC6 was approved
WAPI was submitted by the China to ISO/IEC JTC1/SC6 as a New Project proposal for a stand alone standard
IEEE 802 submitted a liaison to SC6 in Nov 09 in relation to the justification of the project
See r1
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)
It is not known when the new project activities will start
None have been scheduled so far
Andrew Myles, Cisco

22. The IEEE may have an ongoing interest in the WAPI project
The IEEE staff are still considering issues in the WAPI draft related to copyright
The WG may have an opportunity to review drafts from the new project for compatibility with and for security
The WG will need to consider WAPI when considering when and how to submit further amendments to ISO/IEC JTC1 as part of the series
The WG may want to inform SC6 at an appropriate time that the current draft of WAPI uses an IE identifier that conflicts with an IE identifier already allocated to k; it also appears to use other code points that conflict with …
Andrew Myles, Cisco

23. May 2010
Does anyone have anything they would like to discuss in relation to WAPI?
Possible questions:
Does anyone have any further information on the status of WAPI in SC6?
Does anyone know if and how WAPI and can coexist?
Is there any work that can be done to improve coexistence?
Does anyone know of any validated security issues related to i or WAPI?
When should WG notify SC6 about the code-point conflict?
Does anyone have information about other amendments to being developed in China or elsewhere? …
Andrew Myles, Cisco

24. Are there any other matters for discussion?
May 2010
Are there any other matters for discussion?
Andrew Myles, Cisco