SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 04/18/2016Revised (if Applicable):

Document Number: 6009
SNARF for: Line Item Revision to Specifications E132, SPECIFICATION FOR EQUIPMENT CLIENT AUTHENTICATION AND AUTHORIZATION and E132.1 SPECIFICATION FOR SOAP BINDING FOR EQUIPMENT CLIENT AUTHENTICATION AND AUTHORIZATION (ECA)

Originating Global Technical Committee: Information & Control
Originating TC Chapter: North America
Task Force (TF) in which work is to be carried out: Diagnostic Data Acquisition Task Force NA
Note: If a new task force is needed, also submit a task force organization form (TFOF)

___________________________________________________________________________
1. Rationale:
a. Describe the need or problem addressed by this activity.
(Indicate the customer, what benefits they will receive, and if possible, quantify the impact on the return on investment [ROI] if the Document is implemented.)
Several recommendations have been requested to enhance E132, including the following:
1. Session Ping Behavior:
a. If a SessionPing returns an error, the behavior is not defined. It is not clear whether an equipment should continue attempting more SessionPing messages, or close the session.
b. Clients cannot configure the # of session pings until a session is closed, or the ping time interval. The # of session ping failures is currently hard-coded at 3. The session ping interval is not standardized.
2. GetMaxSessions is defined inconsistently with other SOAP actions (‘:’ Instead of ‘.’). This is an obvious typographical error in the message definition. It could not be fixed without changing the web service file and break compatibility.
3. Allow the use of WS-Security as an alternative to SSL


b. Estimate effect on industry.
1: Major effect on entire industry or on multiple important industry sectors - identify the relevant sectors
Sector or Company Information:

c. Estimate technical difficulty of the activity.
III: Difficult - Limited expertise and resources exist and/or achieving consensus is difficult

___________________________________________________________________________
2. Scope:
a: Describe the technical areas to be covered or addressed by this Document development activity. For Subordinate Standards, list common concepts or criteria that the Subordinate Standard inherits from the Primary Standard, as well as differences from the Primary Standard:
Refine the SessionPing behavior by declaring how the equipment should behave when the client returns an error in the SessionPing response. Add new messages to the admin client session to configure the equipment’s SessionPing

Fix the GetMaxSessions definition to be consistent with all other definitions, using the ‘.’ Instead of ‘:’.

Allow clients to use WS-Security, as an alternative to SSL.

b: Expected result of activity
Line-item revision to an existing Standard or Safety Guideline

For a new Subordinate Standard, identify the Primary Standard here:


Modification of an existing part of Standard(s) or Safety Guideline(s) including Appendices, Complementary Files, and Supplementary Materials

For Standards, identify the Standard Subtype below:
Specification

Miscellaneous (describe below):

___________________________________________________________________________
3. Projected Timetable for Completion:

a: General Milestones
a. Activity Start: 04/01/2016b. 1st Draft by: 10/01/2016
c. (Optional) Informational Ballot by: d. Letter Ballot by: 01/01/2017
e. TC Chapter Approval By:04/01/2017

_____________________________________________________________________________
4. Liaisons with other Global Technical Committees/TC Chapters/Subcommittees/TFs:
a. List SEMI global technical committees, TC Chapters, subcommittees, or task forces in your or other Regions/Locales that should be kept informed regarding the progress of this activity. (Refer to SEMI Standards organization charts and global technical committee charters and scopes as needed.)
I&C Global Technical Committee, Korea I&C DDA TF

b. List any planned Type I Liaisons with external nonprofit organizations (e.g., SDO) that should receive Draft Documents from Standards staff for feedback during this activity and be notified when the Letter Ballot is issued (refer to Procedure Manual § 7):


c. Intercommittee Ballots:
will not be issued

Identify the recipient global technical committee(s):

___________________________________________________________________________
5. Safety Considerations:
The resulting document is expected:
NOT to be a Safety Guideline

NOTE FOR "to be a Safety Guideline": When all safety-related information is removed from the Document, the Document is NOT technically sound and complete - Refer to Section 15.1 of the Regulations for special procedures to be followed.

NOTE FOR "NOT to be a Safety Guideline": When all safety-related information is removed from the Document, the Document is still technically sound and complete.

___________________________________________________________________________
6. Intellectual Property Considerations:
Note: Both a: and b: below should be checked for Revision of existing Standard(s) and Safety Guideline(s).

a. For a new Standard or Safety Guideline and for any part to be modified or added in a Revision of published Standards and Safety Guidelines:


If "patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s) " is selected above, then also check one:


b. For Revision, Reapproval, Reinstatement, or Withdrawal of existing Standard(s) and Safety Guideline(s):
there is no known material patented technology necessary to use or implement the Standard(s) and Safety Guideline(s)

c. The body of the Document and any Appendices, Complementary Files, Related Information sections, or Various Materials that may or may not be a part of the Document by reference:



NOTE FOR ‘the use of patented technology or the incorporation of Copyrighted Item(s) is NOT required’: If in the course of developing the Document, it is determined that the use of patented technology or Copyrighted Item(s) is necessary for the Document, the provisions of Regulations § 16 must be followed.

NOTE FOR ’will incorporate Copyrighted Item’: A copyright release letter must be obtained from the copyright owner prior to publication.

___________________________________________________________________________
7. Comments, Special Circumstances:
None.

__________________________________________________________________________
8. TC Member Review:
is not required for this SNARF.

Member Review Start Date; None.
Member Review End Date: None.

NOTE FOR ‘TC Member Review’ is required by the Regulations for a period of at least two weeks
before approval of a new, or a major revision of an existing, Standard or Safety Guideline. (Refer to Regulations ¶ 8.2.1)
__________________________________________________________________________

9. SNARF Approval Dates:
TC Chapter or GCS04/06/2016
Recorded in TC Minutes

__________________________________________________________________________

10. SNARF Extension Dates:
TC Chapter Extension Granted on
Extension Expires on
SNARF abolished at 4/3/2019 I&C TC meeting