FAST TRACKING IN THE IEEE Prepared by Robby Robson Chair, LTSC robby@computer.org June, 2005 This work is licensed under the Creative Commons Attribution-NoDerivs License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nd/2.0 or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.

Definition of Fast Tracking Adopting an existing standard or specification as an IEEE standard Using a process designed to shorten the time to approval February 23, 2005 LTSC / AICC Report - Plugfest 9

Purpose of Fast Tracking Turn de facto standards into de jure standards Establish a comprehensive source of standards in a particular area Validate and add legitimacy to an existing specification (aids adoption) End up with SINGLE version of a standard February 23, 2005 LTSC / AICC Report - Plugfest 9

Digression into IEEE Process WORKING GROUP & SPONSOR PROCESS NEEDS SPONSOR APPROVAL TO ENTER SPONSOR BALLOT IEEE STANDARDS ASSOCIATION PROCESS BALLOT NEEDS 75% PARTICIPATION and 75% APPROVAL TO SUCCEED February 23, 2005 LTSC / AICC Report - Plugfest 9

Fast Track - The Easy Case Adopt a document by putting a wrapper around it. PAR SCOPE states scope of existing specification PAR PURPOSE states the intention is to adopt the specification as an IEEE standard Terms, definitions, errata may be inserted in front matter Body of document is unchanged Distribution rights are assigned to the IEEE (??) February 23, 2005 LTSC / AICC Report - Plugfest 9

Fast Track - Approval Process Working group & Sponsor must approve fast tracking attempt Ballot group is formed as usual. Participation from contributing organization encouraged Ballot comments addressing existing document are disposed by making no change. (Ballot comments about added front matter may result in changes) After single recirculation, if 75% approve the standard is sent to RevCom. February 23, 2005 LTSC / AICC Report - Plugfest 9

Fast Track - The Harder Case Adopt an existing specification while allowing at least editorial changes to the document PAR SCOPE states scope of existing specification PAR PURPOSE states the intention is to adopt a functionally equivalent version of the specification as an IEEE standard Rights and maintenance responsibilities must be negotiated with IEEE Should clarify in advance what will be done if technical errors are discovered February 23, 2005 LTSC / AICC Report - Plugfest 9

Fast Track - Harder Case - Approval Process Working group & Sponsor must approve fast tracking attempt Ballot group is formed as usual. Participation from contributing organization encouraged. Can be invited experts. Ballot comments are resolved in a manner decided in advance. It may involve the contributing organization. Many comments may be disposed with no change by referring to the PAR. After recirculation, if 75% approve the standard is sent to RevCom. February 23, 2005 LTSC / AICC Report - Plugfest 9

Not So Fast Track - Variants Collaborating organization has an existing specification. Works with sponsor to put it into IEEE format and then submits for fast track. Rights are negotiated in advance. Submits as base document. WG puts into IEEE format. Changes are permitted. Contributing organization may then choose to adopt IEEE version or not February 23, 2005 LTSC / AICC Report - Plugfest 9

LTSC / AICC Report - Plugfest 9 Recommended Actions Create model “easy case” and “hard case” Fast Track PARS and comment resolution language Create model copyright agreements* Create diagrams / slides for addition to Standards Online Create model flow diagrams and agreements for “not-so-fast track” variants * Fits with other recommendations concerning intellectual property rights. February 23, 2005 LTSC / AICC Report - Plugfest 9