Presentation is loading. Please wait.

Presentation is loading. Please wait.

JTC1 Ad Hoc May 2011 agenda 10 May 2011 May 2011 Authors: July 2010

Similar presentations


Presentation on theme: "JTC1 Ad Hoc May 2011 agenda 10 May 2011 May 2011 Authors: July 2010"— Presentation transcript:

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

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

3 Participants have a duty to inform in relation to patents
July 2010 doc.: IEEE /0xxxr0 May 2011 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 May 2011 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 May 2011 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 May 2011 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 May 2011 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 May 2011 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 July 2010 doc.: IEEE /0xxxr0 May 2011 The JTC1 Ad Hoc has a very general proposed agenda for the Palm Springs meeting Tuesday PM1 Call to Order Select recording secretary Approve agenda Conduct meeting according to agenda Recess Wednesday AM1 Call to Order Select recording secretary Conduct meeting according to agenda Recess Thursday AM1 Call to Order Select recording secretary Conduct meeting according to agenda Recess Andrew Myles, Cisco Andrew Myles, Cisco

10 The JTC1 Ad Hoc has a detailed list of agenda items to be considered
May 2011 The JTC1 Ad Hoc has a detailed list of agenda items to be considered Approve agenda Approve minutes from March in Singapore Review extended goals Review status of liaisons previously sent to SC6 Review “draft liaison” presentation for SC6 meeting in June Consider update on WAPI progress Discuss “ is secure” presentation for SC6 meeting in June Review “identifier conflict” presentation for SC6 meeting in June Andrew Myles, Cisco

11 The JTC1 Ad Hoc has a detailed list of agenda items to be considered
May 2011 The JTC1 Ad Hoc has a detailed list of agenda items to be considered Review possible NPs to be discussed at SC6 meeting in June Review “802.1 replacement” presentation for SC6 meeting in June Discuss “ replacement” presentation for SC6 meeting in June Discuss new PSDO agreement Discus NB submissions to SC6 Review and approve any liaisons and presentations to SC6 Discuss delegation for SC6 meeting Discuss SC6 processes Discuss planning teleconferences for SC6 meeting Discuss Class A liaison to SC6 Andrew Myles, Cisco

12 The JTC1 Ad Hoc will consider approving its agenda
May 2011 The JTC1 Ad Hoc will consider approving its agenda Motion to approve agenda The JTC1 Ad Hoc approves the agenda for its meeting in Palm Springs in May 2011, as documented on pages 9-11 of <this slide deck> Moved: Seconded Result Andrew Myles, Cisco

13 The JTC1 Ad Hoc will consider approval of previous minutes
May 2011 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 Singapore in March 2011, as documented in Moved: Seconded Result Andrew Myles, Cisco

14 May 2011 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 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 Andrew Myles, Cisco

15 May 2011 The WG has liaised various Sponsor Ballot drafts to ISO/IEC JTC1/SC6 Task Group Liaised after LA Orlando Beijing SD Liaised after Hawaii Liaised after Dallas Sing. Status Jan 10 Mar 10 May 10 July 10 Sept 10 Nov 10 Jan 11 Mar 11 May 11 TGmb - D6.0 D8.0 TGs D10.0 TGu D11.0 D13.0 Ratified TGv D9.0 D15.0 TGz D7.0 D12.0 Ratifed Andrew Myles, Cisco

16 May 2011 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 :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 Andrew Myles, Cisco

17 May 2011 The JTC1 ad hoc will review possible presentation to SC6 related to the liaison relationship A presentation has been drafted that summarises various elements of the liaison relationship between SC6 and IEEE 802 See r0 The presentation concludes How can the formal liaison process between the WG and SC6 be improved? Do SC6 NBs want to continue receiving Sponsor Ballot drafts from WG? Does SC6 believe it needs to ratify IEEE standards? The JTC1 ad hoc will review the presentation Andrew Myles, Cisco

18 May 2011 It was recognised by the ad hoc in September 2009 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

19 May 2011 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 was received to the IEEE 802 liaison to SC6 in Nov 2009 (see N14142) This liaison noted that the claims that IEEE is not secure are unfounded The liaison also suggests that WAPI should be submitted to IEEE 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) Andrew Myles, Cisco

20 May 2011 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 :2005, which is actually IEEE The new version is called instead of as amendment Draft 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 Andrew Myles, Cisco

21 May 2011 An unofficial response has been received to IEEE 802 rebuttal of false assertions about security IEEE 802 liaised a document to SC6 in early January 2011 It noted various erroneous claims about in the WAPI NP proposal comment resolution document; see N14551 The US NB made similar comments in N14549 No official response has been received as of May 2011 but responses are included in a revised draft disposition of comments See N14620 for revised draft disposition of comment Most concerns were dismissed on basis they were not appropriate during WD stage; similar comments by the US NB were also dismissed It is planned that the IEEE 802 representatives at the SC6 meeting in June will: Represent the views in N14551 Object to the concerns being dismissed Andrew Myles, Cisco

22 May 2011 The JTC1 ad hoc will review a presentation for SC6 called “ is secure” The fundamental issue in the WAPI NP justification is the claim that i is insecure; this claim is false A presentation has been drafted based on two related IEEE 802 liaisons to SC6 (N14142 in Dec 2009 and N14551 in Jan 2011) See r0 for draft The requests in the presentation are Remove all existing allegations of insecurity of i from official SC6 output documents Alternatively, provide credible evidence of any insecurity in i Halt any new project activity that relies on the invalid assertion that i is insecure as part of its justification The JTC1 ad hoc will review the presentation Andrew Myles, Cisco

23 May 2011 The JTC1 ad hoc will review a presentation for SC6 related to the identifier conflict issue A presentation has been drafted that summarises the identifier conflict issue based on N14643 See r0 for draft It concludes by asking: Please confirm whether or not SC6 requires the IE and the status codes to remain reserved? The JTC1 ad hoc will review the presentation Andrew Myles, Cisco

24 May 2011 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: – new PHY and MAC (NuFront) 802.1X – proposal is based on TePA (IWNCOMM) 802.1AE – proposal is TLSec (IWNCOMM) 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 X AE security Andrew Myles, Cisco

25 The Chinese NB security related proposals were all based on TePA
May 2011 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 (Information technology -- Security techniques -- Entity authentication -- Part 3: Mechanisms using digital signature techniques) The security proposals (replacements of 802.1X, 802.1AE and security) are all directly or indirectly based on TePA Andrew Myles, Cisco

26 May 2011 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 ← replacement 5.4.3 Further enhancement on LAN Security ← 802.1AE replacement 5.4.4 MAC Security Specifications ← 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 Andrew Myles, Cisco

27 May 2011 The JTC1 ad hoc will discuss a possible “802.1 replacement” presentation to SC6 IEEE sent a liaison in March 2011 commenting on the proposals to standardise replacements of 802.1X/AE See N14648 The tiger team of the WG has been working on a document based on the liaison for presentation to SC6 in San Diego in June See <tbd> for draft The JTC1 ad will review and discuss the presentation Andrew Myles, Cisco

28 May 2011 The JTC1 ad hoc may discuss a possible “ replacement” presentation to SC6 It is likely that a proposal will be made in SC6 by the China NB on behalf of Nufront Software to define a new MAC and PHY The NP has been justified on alleged deficiencies Low efficiency MAC High complexity High power consumption Complex networking – difficult to support large number of users No one has volunteered to develop a liaison or presentation yet The JTC1 ad will discuss the need for a liaison Andrew Myles, Cisco

29 The JTC1 ad hoc may discuss the new PSDO agreement
A new PSDO agreement has been signed between IEEE and ISO See <tbd> The JTC1 ad hoc will briefly review the document and any changes Andrew Myles, Cisco

30 The JTC1 ad hoc may review NB submissions to SC6
It is believed that submissions will be sent by US NB UK NB ... The submissions may be reviewed if they are available Andrew Myles, Cisco

31 May 2011 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 Andrew Myles, Cisco

32 The UK NB has suggested that all 8802 series standards be withdrawn
May 2011 The UK NB has suggested that all 8802 series standards be withdrawn The UK NB has submitted a document suggesting the withdrawal of all 8802 series standards The reasons given are that: Most of the standards are obsolete or outdated The PSDO formalized the full recognition by ISO and JTC1 of IEEE Standards for reference purposes in the development of ISO and JTC1 standards Andrew Myles, Cisco

33 The Chinese NB has provided comments on 802.11s
May 2011 The Chinese NB has provided comments on s The Chinese NB has provided comments on TGs See N14709 These comments have been forwarded to TGs for processing It is suggested that the IEEE WG reply with a liaison as follows The IEEE Working Group thanks the Chinese NB for providing comments in N14708 related to the s draft. The comments will be considered by the TGs comment resolution committee in the near future. We will inform SC6 when the comment resolutions are available for review Andrew Myles, Cisco

34 The JTC1 ad hoc will approve any necessary motions
May 2011 The JTC1 ad hoc will approve any necessary motions Motion The JTC1 ad hoc recommends to the IEEE WG that 11-xxx represent the position of the IEEE WG for presentation to ISO/IEC JTC1/SC6 with respect to the liaison relationship between SC6 and IEEE 802 Moved Seconded Andrew Myles, Cisco

35 The JTC1 ad hoc will approve any necessary motions
May 2011 The JTC1 ad hoc will approve any necessary motions Motion The JTC1 ad hoc recommends to the IEEE WG that 11-xxx represent the position of the IEEE WG for presentation to ISO/IEC JTC1/SC6 with respect to the allegations of the insecurity of contained in the WAPI NP proposal and proposed dispositions in ISO/IEC JTC1/SC6 Moved Seconded Andrew Myles, Cisco

36 The JTC1 ad hoc will approve any necessary motions
May 2011 The JTC1 ad hoc will approve any necessary motions Motion The JTC1 ad hoc recommends to the IEEE WG that r0 represent the position of the IEEE WG for presentation to ISO/IEC JTC1/SC6 with respect to the identifier conflict issue Moved Seconded Andrew Myles, Cisco

37 The JTC1 ad hoc will approve any necessary motions
May 2011 The JTC1 ad hoc will approve any necessary motions Motion The JTC1 ad hoc recommends to the IEEE WG that Bruce Kraemer be empowered to approve any presentations to ISO/IEC JTC1/SC6 on behalf of IEEE 802 during the ISO/IEC JTC1/SC6 face to face meeting in San Diego in June 2010 Moved Seconded Andrew Myles, Cisco

38 The JTC1 ad hoc will approve any necessary motions
May 2011 The JTC1 ad hoc will approve any necessary motions Motion The JTC1 ad hoc recommends to the IEEE WG that a liaison be sent to ISO/IEC JTC1/SC6 containing the following text “The IEEE Working Group thanks the Chinese NB for providing comments in N14708 related to the s draft. The comments will be considered by the TGs comment resolution committee in the near future. We will inform SC6 when the comment resolutions are available for review” Moved Seconded Andrew Myles, Cisco

39 May 2011 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 June 11 in San Diego The following meeting is in China in March 2012 Attendees will be appointed during the May 2011 interim meeting Bruce Kraemer (HoD) Dorothy Stanley (802.11) Dan Harkins (802.11) Bill Carney (802.11) Brian Weis (802.1) Mick Seaman (802.1) Lei Wang (802.16) Rolf De Vegt (802.11) Andrew Myles, Cisco

40 The JTC1 ad hoc will discuss SC6 processes
May 2011 The JTC1 ad hoc will discuss SC6 processes Bruce Kramer will lead a discussion of SC6 processes See <tbd> Andrew Myles, Cisco

41 May 2011 The JTC1 ad hoc will conduct at least one teleconference in preparation for SC6 in June The date and time of the teleconference(s) is <tbd> One teleconference is likely to be with the security team The 802 delegation will meet on Sunday afternoon in San Diego Andrew Myles, Cisco

42 The JTC1 ad hoc may discuss a Class A liaison with SC6
Bruce Kraemer may lead a discussion of IEEE 802 becoming a Class A liaison to SC6 Andrew Myles, Cisco


Download ppt "JTC1 Ad Hoc May 2011 agenda 10 May 2011 May 2011 Authors: July 2010"

Similar presentations


Ads by Google