doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 1 IEEE 802 Presentation for Xi’an Meeting Date: Authors:

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 2 Abstract This presentation contains the IEEE presentation for the meeting July 22-24, 2008, between China’s National Body (NB) delegates to JTC1/SC6 and representatives from IEEE

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 3 Agenda Review IEEE Goals Constraints on IEEE Invitation Some Alternatives Discussion

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 4 Review Meeting Purpose –Search for mutually agreed upon approach with China NB to standardize WAPI within ISO/IEC Outcome not guaranteed –Time exists for a second meeting before Montreux SC6 meeting if we do not succeed –Unknown whether an approach can be found that will meet the constraints of both IEEE and China NB This meeting is based on the assumption that both IEEE and China NB want to find a resolution

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 5 IEEE Goals Maintain integrity of the ISO/IEC standard –In particular maintain synchronization of ISO/IEC and IEEE Increase participation in IEEE worldwide, including by Chinese technical communities Seek a ratification strategy for WAPI that meets the constraints of both IEEE and China NB

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 6 IEEE Organization IEEEIEEE SAIEEE 802IEEE

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 7 IEEE Constraints IEEE is governed by IEEE Standards Association (IEEE- SA) and IEEE 802 rules –Meetings of IEEE 802 and its working groups are the only forums authorized by the IEEE-SA for developing LAN/MAN standards IEEE 802 has a liaison relationship with ISO/IEC JTC1/SC6/WG1 –IEEE 802 is authorized to submit standards to ISO/IEC JTC1/SC6/WG1 for fast track ratification –IEEE 802 is authorized to exchange liaison requests from ISO/IEC JTC1/SC6/WG1 –Any other formal standards development processes must be authorized by the IEEE-SA IEEE has a relationship with ISO through the PSDO –IEEE may request that the ISO Secretary General initiate fast track ballot of IEEE 802 standards –IEEE may engage in joint development of standards with ISO –IEEE SA rules still govern all joint development of standards by IEEE 802

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 8 Suggested Process Both the previously established process and PSDO indicate that the technical development of IEEE and ISO/IEC standards is undertaken initially within IEEE IEEE suggests the following process –Quickly begin technical work within IEEE –Create an IEEE amendment for the WAPI elements that are within scope of IEEE –Fast track the amendment with ISO/IEC when complete This will be the most effective process –The PSDO does not specify implementation details for either ISO or IEEE –Implementing the PSDO will require cascading rules changes within IEEE-SA, IEEE 802, and IEEE –The rules changes must be completed before technical work can begin –This is likely to take years that are better spent on technical work of integrating WAPI into IEEE and ISO/IEC

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 9 Invitation IEEE strongly desires increased participation by Chinese technical experts IEEE document provides a formal invitation calling for participation by WAPI technical experts in IEEE for the purpose of developing an amendment including WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 10 Some Alternatives Standardization of WPI as an amendment to IEEE , and standardization of WAI as an amendment to another standard (e.g., IEEE 802.1X) Standardize WPI in IEEE , and include WAI as an Informative Annex of IEEE Add WAPI as an Informative Annex to IEEE Ratification of WAPI as a stand-alone standard outside of the ISO/IEC 8802 series –Within SC6 –Within IEEE 802 Produce WAPI as a recommend practice

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 11 Alternative 1: WPI in IEEE , WAI in Another Standard (Workable) Advantages –All WAPI components have normative definition for all IEEE equipment built, worldwide Maximizes user benefit and choice –It appears this approach is feasible under IEEE-SA, IEEE 802, and IEEE rules and procedures Disadvantages –China NB has expressed reservations in the past about standardizing components of WAPI in different forums This appears to be a workable approach

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 12 Alternative 2: WPI in IEEE , WAI Informative (Unworkable) IEEE view of advantages –All WAPI still defined in a single document IEEE view of disadvantages –WAPI still split into multiple components –WAI definition would not be normative –WAI is outside the scope of IEEE , so such an approach would be unlikely to be approved by the membership of IEEE , and the sponsor (IEEE 802), and the IEEE-SA This does not appear to meet the objective of ratification of an amendment incorporating WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 13 Alternative 3: WAPI as an Informative Annex to IEEE (Unworkable) IEEE view of advantages –WAPI can be inserted as an annex intact IEEE view of disadvantages –No part of WAPI would be normative –WAI is outside the scope of IEEE , so such an approach would be unlikely to be approved by the membership of IEEE , and the sponsor (IEEE 802), and the IEEE-SA This does not appear to meet the objective of ratification of an amendment incorporating WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 14 Alternative 4: WAPI as a Stand-Alone Standard developed within SC6 (Unworkable) Advantages –WAPI would be a normative international standard, defined in a single document Disadvantages –Does not satisfy the ISO aim of one standard per technology domain –ISO/IEC would not benefit from including any WAPI technology –The Letters of Assurance on IPR apply only to the IEEE standard and its amendments This does not appear to meet the objective of ratification of an amendment incorporating WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 15 Alternative 4: WAPI as a Stand-Alone Standard developed within IEEE 802 (Unworkable) Advantages –WAPI would be a normative international standard, defined in a single document Disadvantages –Does not satisfy the ISO aim of one standard per technology domain –ISO/IEC would not benefit from including any WAPI technology –The Letters of Assurance on IPR apply only to the IEEE standard and its amendments This does not appear to meet the objective of ratification of an amendment incorporating WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 16 Alternative 5: WAPI as an IEEE Recommended Practice (Unworkable) Advantages –WAPI would be defined in a single document Disadvantages –WAPI would not be a normative standard –WAI is outside the scope of IEEE , so such an approach would be unlikely to be approved by the membership of IEEE , and the sponsor (IEEE 802), and the IEEE-SA –The Letters of Assurance on IPR apply only to the IEEE standard and its amendments This does not appear to meet the objective of ratification of an amendment incorporating WAPI technology

doc.: IEEE /0858r0 Submission July 2008 Jesse Walker, Intel CorporationSlide 17 Discussion?