Liaison Form (App B)

Appendix B - Version 1.32, 27 April 2005 ======================================== Standard definitions taken from the IETF approach [RFC2119] MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Appendix B to The FIRST membership process: =========================================== Basic Set of Information ======================== The basic set of information consists of three parts, one mandatory and one optional part are related to the liaison himself, the other mandatory part is related to the task of FIRST. I. Mandatory Fields describing the Liaison ========================================== 1. Liaison Name - Name: - Company name: - Country the liaison is located in (if multiple offices exist, list all countries): 2. Contact Information - Regular telephone number (country code, telephone number, timezone relative to GMT): - Emergency telephone number (country code, telephone number, timezone relative to GMT): - Email address: - Facsimile number (country code, telefax number): - Other telecommunication facilities: - Postal address: - Invoice address (mandatory): - Email address to be included in the FIRST mailing lists: - Email Address: 3. References - FIRST sponsor: - Track record of working relationships with other teams: - Reason for applying for FIRST liaison membership: - What do you expect to contribute to FIRST: 4. Information handling policy - What process will be put in place to protect confidential information obtained from FIRST - Are there legal considerations to take into account with regards to the handling of FIRST confidential data? 5. Cryptography - Policy on use of cryptography to shield exclusivity&integrity in archives and/or in datacommunication, especially e-mail. - PGP must be used to encrypt E-mail where content need to be protected. Please provide: - PGP key of liaison member: - Outline how you will protect your private key. II. Optional Fields =================== 6. Business Hours - Description of business hours: - Procedures for contacting the liaison member outside business hours: 7. Technical Expertise - Operating Systems: - System Platforms: - Networks: - ... 8. Information Server - WWW server: - Mailing lists: - (Anon)FTP server: - NetNews: - ... III. Mandatory Fields describing the actions of FSS =================================================== (to be filled out by FSS!) ========================== 1. Classification - Actual classification ("applying" / "confirmed" / "pending" / "terminated"): - Date of first classification: - Date of last classification change: - Previous classification ("applying" / "confirmed" / "pending"): - Reason for last classification change: 2. Status Updates - Date of last verification: - Method of last verification: - Date of last change announcement received from the team: 3. Open Issues - List of open issues (date of issue recognized, description, approach taken): 4. History - List of all actions carried out in regard to the mandatory and optional fields describing the team (for each action the entry will give date and person):