SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 11/08/2017Revised (if Applicable):

Document Number: 6337
SNARF for: Line Item Revision to SEMI E132: Specification for Equipment Client Authentication And Authorization

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.
c. Users would like to configure the equipment’s SessionPing behavior through the interface. Specifically the retry count, and the ping frequency.

2. Users have requested a function to allow change of the EndPoint URL.

3. Users have requested an action be included with error codes to make it clear when a session should be closed or not. For example error code 6005 action code: close session.

4. EnhancedEstablishSession seems to conflict with the ACL entries. ACL entries determine what a client can and cannot do. Some users have requested that this method be removed so that clients can only use the EstablishSession method.

5. It is not clear to some that a closed session also ends the authenticated connection.



b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information:

c. Estimate technical difficulty of the activity.
II: Some Difficulty - Disagreements on known requirements exist but developing consensus is possible

___________________________________________________________________________
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:

The ballot will propose changes to address the issues identified above:

Modify E132 to solve the problems identified including:

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

Add a new message to configure the SessionPing retry count and retry interval.

Add functionality to allow the client to change the endpoint URL for an existing session.

Define the expected action for error codes so that it is clear when a session should and should not be closed. Make this clear for both client to equipment and equipment to client use cases. Make it clear whether the session closes automatically or not because of the error.

Remove the EnhancedEstablishSession method.

The ballot will also include any minor changes identified during the ballot creation.

Clarify how closing a session closes any authenticated connection.


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: 11/08/2017b. 1st Draft by:
c. (Optional) Informational Ballot by: d. Letter Ballot by: 02/07/2018
e. TC Chapter Approval By:11/08/2018

_____________________________________________________________________________
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.)


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:
patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s).

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

b. For Revision, Reapproval, Reinstatement, or Withdrawal of existing Standard(s) and Safety Guideline(s):
there is previously 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:

IP Consideration note:
NON-ASSERTION AGREEMENT between SEMI and Asyst Technologies has been signed with for US Patents #11/340101, #11/107508, #09/899833, and 09/496009, in 2008.

__________________________________________________________________________
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 GCS11/08/2017
Recorded in TC Minutes11/08/2017

__________________________________________________________________________

10. SNARF Extension Dates:
TC Chapter Extension Granted on
Extension Expires on