1. JTC1 Ad Hoc July 2010 agenda 12 July 2010 July 2010 Authors: July 2010
doc.: IEEE /0xxxr0
July 2010
JTC1 Ad Hoc July 2010 agenda
12 July 2010
Authors:
Andrew Myles, Cisco
Andrew Myles, Cisco

2. July 2010
doc.: IEEE /0xxxr0
July 2010
This presentation will be used to run the JTC1 Ad Hoc meetings in San Diego in July 2010
This presentation contains a proposed running order for the IEEE JTC1 Ad Hoc committee meeting in July 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
July 2010
doc.: IEEE /0xxxr0
July 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
July 2010
doc.: IEEE /0xxxr0
July 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. July 2010
doc.: IEEE /0xxxr0
July 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. July 2010
doc.: IEEE /0xxxr0
July 2010
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 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
July 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. July 2010
doc.: IEEE /0xxxr0
July 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
July 2010
doc.: IEEE /0xxxr0
July 2010
The JTC1 Ad Hoc has a very general proposed agenda
Tuesday PM2
Call to Order
Select recording secretary
Approve agenda
Conduct meeting according to agenda
Recess
Thursday AM2
Call to Order
Select recording secretary
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
July 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
Review status of 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
July 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 San Diego in July 2010, as documented on pages 9-10 of 10/0xxxr0
Moved:
Seconded
Result
Andrew Myles, Cisco

12. The JTC1 Ad Hoc will consider approval of previous minutes
July 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 Beijing in May 10, as documented in xxx-00-0jtc-may-2010-minutes.doc
Moved:
Seconded
Result
Andrew Myles, Cisco

13. The JTC1 Ad Hoc reaffirmed its general goals in Sept 09
July 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. July 2010
The WG has liaised various Sponsor Ballot drafts to ISO/IEC JTC1/SC6
No technical comments have been received in relation to any of the Sponsor Ballot drafts liaised to JTC1/SC6
Task Group
Liaised after LA
Orlando
Beijing
TGp
D10.0
D11.0 -
TGu
D8.0
D9.0
TGv
TGz
D7.0
Andrew Myles, Cisco

15. July 2010
The China NB provided some comments in May in relation to recent liaisons to SC6
In May it was noted that the China NB provided some non technical comments related to IEEE WG liaisons
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. The 802.11 WG authorised the WG Chair to respond to the comments
July 2010
The WG authorised the WG Chair to respond to the comments
In May the WG authorised the Chair to respond to the China NB comments using 10/ as a base
The liaison that was sent is documented on the following two pages
The liaison was posted to the SC6 reflector on 9 June 2010
No response has been received
Andrew Myles, Cisco

17. The 802.11 WG liaison to SC6 was posted on 9 June 2010
July 2010
The WG liaison to SC6 was posted on 9 June 2010
Text of Liaison (part 1)
The IEEE Working Group would like to thank ISO/IEC JTC1/SC6 for passing on the comments from the China National Body contained in SC6 document N14251 in relation to the IEEE Working Group’s liaisons contained in SC6 documents N We would also like to thank the China National Body for its comments. This liaison letter contains information that may help resolve some of the China National Body’s comments and concerns.
Item 1 in N14251 correctly notes that the IEEE Working Group wants to establish strong ties with ISO/IEC JTC1/SC6. This liaison letter is an example of the ongoing communication between the two organizations that will help maintain those strong ties.
Item 2 in N14251 notes that the deadlines for comments by SC6 National Bodies on the four Sponsor Ballot drafts liaised in SC6 documents N were too short. This is a problem that arises from the use of differing standard development timescales and methodologies by the two organizations. We would like to suggest a mechanism to overcome this problem.
The IEEE Working Group proposes that no deadline be imposed on comments from SC6 National Bodies on Sponsor Ballot drafts, reflecting the value that we place on any such comments. The IEEE Working Group will process any comments received from SC6 National Bodies at the time they are received in relation to the current draft, regardless of any deadlines. If the comments are received after the relevant standard has been ratified then the comments will be processed as part of our normal revision process.
We intend to update SC6 of our planned standards development schedule on a regular basis to allow SC6 National Bodies to plan future comment activities. The current schedule for IEEE Working Group activities related to various amendments and the upcoming revision is available at
Andrew Myles, Cisco

18. The 802.11 WG liaison to SC6 was posted on 9 June 2010
July 2010
The WG liaison to SC6 was posted on 9 June 2010
Text of Liaison (part 1)
Item 3 in N14251 notes that the China National Body was unable to review the Sponsor Ballot drafts because it did not have access to earlier ratified standards and amendments. We apologize for neglecting to notify the SC6 National Bodies how to access IEEE standards and amendments. All necessary standards and amendments may always be purchased using IEEE Xplore at The same documents are available for no charge six months after publication through the IEEE Get802 program at but in the spirit of cooperation we can provide copies of documents needed in the review process gratis as requested.  
Item 4 in N14251 notes there are a number of outstanding issues in relation to the cooperation process between IEEE and ISO/IEC JTC1/SC and suggests that the IEEE Working Group not submit any standards for adoption by ISO/IEC JTC1/SC6 until these issues have been resolved. Previously, we indicated that the IEEE Working Group was planning to submit IEEE using the PSDO process. This standard will not be ready for submission to ISO/IEC JTC1/SC6 until late We hope that any outstanding process issues can be resolved well before that time.
Item 5 & 6 in N14251 makes a variety of comments that flow from the IEEE’s copyright of the IEEE standard. The IEEE Working Group agrees that the issues raised need to be resolved to the satisfaction of both the IEEE and ISO/IEC. We understand that IEEE staff and ISO/IEC staff are currently working to resolve the copyright and related issues. We hope any remaining issues can be resolved soon to remove any barrier to future cooperation between IEEE Working Group and ISO/IEC JTC1/SC6.
Please distribute this note among the membership of SC6 as you deem appropriate.
Yours sincerely,
Andrew Myles, Cisco

19. July 2010
All base amendments are now freely available through the Get802 programme
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 is now also vaialble through the Get802 programme
802.11p, u, v, z have all been liaised to SC6
Andrew Myles, Cisco

20. SC6 has issued a draft agenda for its meeting on 27-29 Sept in London
July 2010
SC6 has issued a draft agenda for its meeting on Sept in London
Draft agenda
2. Welcome
3. Roll Call of Delegates
4. Approval of Agenda
5. SC6 WG1 Active Work Items
5.1. Magnetic Field Area Network
5.2. ISO/IEC 29157
5.3. ISO/IEC PDTR
5.4. WLAN Security
5.6. High Rate 60GHz PHY, MAC and HDMI PAL
5.7. NFC
5.7.1 Ad Hoc Group Meetings report and discussions on NFC Series of Standards
5.7.2 Liaison report
5.8. TV White Spaces (ECMA-392)
5.9. Study Group report on PLC Harmonization
6. Liaison Statements
7. Other Business
8. Development, Review and Approval of WG1 Resolutions
Andrew Myles, Cisco

21. July 2010
The SC6 meeting includes at least a couple of items of items of potential interest
The details of the individual items are not yet known
Items of interest to IEEE WG may include
5.4. WLAN Security
Likely to be related to WAPI
5.6. High Rate 60GHz PHY, MAC and HDMI PAL
???
Does anyone have any insight on the 60GHz item?
Andrew Myles, Cisco

22. July 2010
The JTC1 Ad Hoc may choose to recommend an IEEE 802 representative to the SC6 meeting
It is believed Bruce Kraemer is planning to attend the SC6 meeting as an IEEE representative
Motion:
The JTC1 Ad Hoc recommends to the IEEE WG and IEEE 802 ExCom that Bruce Kraemer be appointed as the IEEE 802 represtative at the ISO/IEC JTC1/SC6 meeting in London on Sept
Moved
Seconded
Andrew Myles, Cisco

23. July 2010
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 i
The promoters of WAPI assert that i is insecure
It is unclear how or whether i and WAPI can coexist …
Andrew Myles, Cisco

24. The new project proposal for WAPI in ISO/IEC JTC1/SC6 was approved
July 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
There is an item on the SC6/WG1 meeting in Sept
Andrew Myles, Cisco

25. The IEEE have an ongoing interest in the WAPI project
July 2010
The IEEE have an ongoing interest in the WAPI project
The IEEE staff are still working issues in the WAPI draft related to copyright
IEEE staff are working with ISO and SAC on resolving the issue
It is believed that WAPI draft is being rewritten to resolve the isues
The WG may have an opportunity to review drafts from the new project for compatibility with and for security
Should we ask at the appropriate time?
The WG may need to consider WAPI when considering when and how to submit further amendments to ISO/IEC JTC1 as part of
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

26. July 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 the WAPI standard in SC6?
Does anyone have any further information on the regulations related to WAPI in China or elsewhere?
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 security issues related to i or WAPI?
When should WG notify SC6 about the numbering conflict?
When a draft becomes available?
Does anyone have information about other “amendments to ” being developed in China or elsewhere? …
Andrew Myles, Cisco

27. Are there any other matters for discussion?
July 2010
Are there any other matters for discussion?
Andrew Myles, Cisco