20 CCITT\COMVII\CONTR\192E1.DOC CCITT\COMVII\CONTR\192E1.DOC 21 CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITEE P2 Protocol Protocol Implementation Conformance Statement (PICS) Proforma Draft Recommendation X.481 GENEVA, 2-13 SEPTEMBER 1991 P2 Protocol Protocol Implementation Conformance Statement (PICS) Proforma (GENEVA, SEPTEMBER 1991) CONTENTS Introduction 1 Scope 2 Normative References 3 Definitions 4 Abbreviations 5 Conventions 6 Conformance Introduction This Recommendation is one of a set of Recommendations for Message Handling. The entire set provides a comprehensive blueprint for a Message Handling System (MHS) realized by any number of cooperation open system. The purpose of an MHS is to enable users to exchange messages on a store-and-forward basis. A message submitted on behalf of one user, the originator, is conveyed by the Message Transfer System (MTS) and subsequently delivered to the agents of one or more additional users, the recipients. Access Units (AUs) link the MTS to communication systems of other kinds (e.g., postal systems). A user is assisted in the preparation, storage, and display of messages by a user agent (UA). Optionnally, it is assisted in the storage of messages by a Message Store (MS). The MTS comprises a number of Message Transfer Agents (MTAs) which collectively perform the store-and-forward message transfer function. To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a given OSI protocol. Such a statement is called a Protocol Implementation Conformance Statement (PICS). This Recommendation includes the PICS proforma for the P2 protocol as defined in the Recommendations X.420. 1 Scope This CCITT Recommendation provides the PICS proforma for the P2 protocol as specified in X.420. This PICS proforma is in compliance with the relevant requirements, and in accordance with the relevant guidance for PICS proforma, given in ISO/IEC 9642-2. Detail of the use of this proforma is provided in the annex A of this Recommendation. The scope of this Recommendation is the specification of the conformance statements for an Interpersonal Messaging Sytem User Agent (IPMS-UA) and Interpersonal Messaging System Message Store (IPMS-MS) 2 Normative references CCITT X.400 Message Handling: System and Service overview CCITT X.402 Message Handling Systems: Overall Architecture CCITT X.408 Message Handling System: Encoded information type conversion rules CCITT X.420 Message Handling System: Interpersonal Messaging System. ISO/IEC 9646-1990, Information technology - Open systems 1 interconnection - Conformance testing methodology and framework - Part 1 : General concepts. (See also CCITT Recommendation X.290(1991)) ISO/IEC 9646-1990, Information technology - Open systems 2 interconnection - Conformance testing methodology and framework - Part 2 : Abstract test suite specification. (See also CCITT Recommendation X.291(1991)) MHS Implementors Guide version 5 3 Definitions This CCITT Recommendation uses terms defined in CCITT Recommendations X.420. This CCITT Recommendation uses the following terms defined in ISO/IEC 9646-1: - PICS proforma; - Protocol Implementation Conformance Statement (PICS). 4 Abbreviations Abbreviations defined in CCITT X.400 series Recommendations are used in this document. 5 Conventions The PICS proforma is designed as an annex to this Recommendation. 6 Conformance The supplier of a protocol implementation which is claimed to conform to X.420 is required to complete a copy of the PICS proforma provided in annex A and is required to provide the information necessary to identify both the supplier and the implementation. ANNEX A (To Recommendation X.481) (This annex forms an integral part of this Recommendation) P2 Protocol Protocol Implementation Conformance Statement (PICS) Proforma Copyright release for PICS Proforma Users of this document may freely reproduce the PICS Proforma in this annex so that it can be used for its intended purpose and may further publish the completed PICS. P2 Protocol Protocol Implementation Conformance Statement (PICS) Proforma CONTENTS A.1 Identification of the implementation A.1.1 Identification of PICS A.1.2 Identification of the Implementation and/or System A.1.3 Identification of the system supplier and/or test laboratory client A.2 Identification of the Protocol A.3 Global Statement of Conformance A.4 Instructions for Completing the PICS Proforma A.5 Abbreviations A.6 Capabilities and Options A.6.1 Initiator/Responder Capability A.6.2 Supported application contexts A.6.3 Major Capabilities A.6.4 Timers and Protocol parameters A.6.5 Supported PDUs A.6.6 Supported PDU Parameters A.6.7 Negociation Capabilities A.6.8 Protocol Error Handling A.6.9 Other information A.7 Multi-Layer dependencies A.7.1 Upper layers A.7.2 Lower layers A.1 Identifications A.1.1Identification of PICS Ref.No. Question Response 1 Date of Statement 2 PICS Serial Number 3 SCS Cross Reference A.1.2Identification of the Implementation and/or System Ref.No. Question Response 1 Implementation Name 2 Version Number 3 Machine Name 4 Machine Version Number 5 Operating System Name 6 Operating System Version 7 Special Configuration (1) 8 Other Information (1) please enter here one of the following configurations: conf1: IPMS-UA collocated with an MTA. conf2: remote IPMS-UA. conf3: IPMS-UA making use of a Message Store. conf4: IPMS-MS. A.1.3Identification of the sytem supplier and/or test laboratory client Ref.No. Question Response 1 Organization Name 2 Contact Name(s) 3 Address: 4 Telephone Number 5 Telex Number 6 Fax Number 7 E-Mail Address 8 Other Information A.2 Identification of the Protocol Ref.No. Question Response 1 Title, Reference Number and date of publication of the protocol standard 2 Protocol Version Numbers 3 Addenda implemented 4 Implemented Defects Reports (Ref.No.) A.3 Global statement of conformance Ref.No. Question D I 1 Are all mandatory m [ ] capabilities implemented? Note - Answering "No" to this section indicates non- conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. Such informations shall be provided in section A.6.9 "Other information". A.4 Instructions for completing the pics proforma A.4.1Definition of support A capability is said to be supported if the Implementation Under Test (IUT) is able: - to generate the corresponding service parameters (either automatically or because the end user explicitly requires that capability); - to interpret, handle and when required make available to the end user the corresponding service paramater(s). A capability is referred to as either an originator capability "O" (when the MHS end-user is acting as originator) or a recipient capability "R" (when the MHS end-user is acting as recipient). A protocol element is said to be supported for origination if the IUT is able to generate it under some circumstances (either automatically or because end-user explicitly requires a related capability). A protocol element is said to be supported for reception if it is correctly interpreted and handled and also, when required, made available to the end-user. A.4.2D (Defined) column This column indicates the level of support required for conformance to the CCITT Recommendation. The values are as follows: m - mandatory support is required; o -optional support is permitted for conformance to the Recommendation. If implemented it must conform to the specifications and restrictions contained in the Recommendation. These restrictions may affect the optionality of other items; c -the item is conditional, the support of this item is subject to a predicate which is referenced in the note column; n/a - the item is not applicable. If Security, Physical Delivery or Message Store options are not supported the corresponding items shall be considered as not applicable. A.4.3I (Implemented) column This column shall be completed by the supplier or implementor, when a "[ ]" is present, to indicate the level of implementation of each item. The proforma has been designed such that the only entries required in that column are: Y - yes, the item has been implemented; N - no, the item has not been implemented; - - the item is not applicable. In the PICS proforma tables, every leading items marked 'm' should be supported by the IUT. Sub-items marked 'm' should be supported if the corresponding leading feature is supported by the IUT. All entries within the PICS proforma shall be made in ink. Alterations to such entries shall be made by crossing out, not erasing nor making the original entry illegible, and writing the new entry alongside. All such alterations to records shall be initialled by the staff making them. A.4.4Permitted Range of value/value supported columns In the column marked "PERMIT. RANGE OF VALUES", the upper- bounds values (e.g. length and occurences) have been stated according to the standard. For each line for which an entry in this column is made, the constraints or supported values should be indicated in the "VALUES SUPPORTED" column. The minimum and maximum lengths and numbers of occurences shall be entered for originator. The maximum length and number of occurences shall be entered for reception. A.4.5Note column The 'note' column has to be read as follows: Notexx - refers to Note xx; pxx - refers to predicate xx (see section A.4.7); #yy - refers to section A.6.6.4.yy. d - a default value is defined in the recommendation. When absent in the PDU, both Originator and Recipient shall interpret it as having the default value specified in the Recommendation. PHY - physical item. SEC - security item. X.500- see X.500 series of Recommendations for a complete definition. A.4.6Item reference numbers Each line within the PICS proforma which requires implementation details to be entered is numbered at the left hand edge of the line. This numbering is included as a mean of uniquely identifying all possible implementation details within the PICS proforma. The means of referencing individual responses is done by the following sequence: a)a reference to the smallest subclause enclosing the relevant item; b)a solidus character, '/'; c)the reference number of the row in which the response appears; An example of the use of this notation would be A.6.3/1, which refers to the Authorising Users Indication element of service. A.4.7Predicate definitions If the classification of an Element of Service (EoS) or a Protocol ELement (PEL) is subject to a predicate support of the item is mandatory is the related predicate is true. Otherwise support of the item is optional. Within that annex predicates are clearly defined or are defined as follow: px = "Item_number".Y or px = S.Y.Z where S - (Service) takes the value A.6.3 Y - takes the values "O" for originator or "R" for recipient Z - is the number of the element of service in section A.6.3 List of predicates p1 = p17 or p16 p2 = Blind copy recipient indication EoS supported in ORIGINATION (S.O.3) p3 = Obsoleting indication EoS supported in ORIGINATION (S.O.14) p4 = Cross-referencing indication EoS supported in ORIGINATION (S.O.5) p5 = Expiry date indication EoS supported in ORIGINATION (S.O.6) p6 = Reply request indication EoS supported in ORIGINATION (S.O.18) p7 = Reply request indication EoS supported in ORIGINATION (S.O.19) p8 = Auto-forwarded indication EoS supported in ORIGINATION (S.O.2) p9 = p10 or p12 p10 = Incomplete copy indication EoS supported in ORIGINATION (S.O.9) p11 = Incomplete copy indication EoS supported in RECEPTION (S.R.9) p12 = Language indication EoS supported in ORIGINATION (S.O.11) p13 = ipm-return PEL supported in RECEPTION (A.6.6.4.1/1.2.3.R) p14 = ipm-return PEL supported in ORIGINATION (A.6.6.4.1/1.2.3.O) p15 = Receipt notification request indication EoS supported in RECEPTION (S.R.17) p16 = Receipt notification request indication EoS supported in ORIGINATION (S.O.17) p17 = Non Receipt notification request indication EoS supported in ORIGINATION (S.O.13) p19 = Importance indication EoS supported in ORIGINATION (S.O.8) p20 = Authorizing users indication EoS supported in ORIGINATION (S.O.1) p22 = Forwarded IP-message indication EoS supported in ORIGINATION (S.O.7) p23 = at least one of the EXTENSION fields is supported in ORIGINATION p24 = at least one of the EXTENSION fields is supported in RECEPTION p25 = the implementation is a conf3 or conf4 (see A.1.2/7 for definitions) examples: p19 = S.O.8 means that p19 is true if the Importance indication element of service is supported. p19 = A.6.3/8.O has the same meaning. p13 = A.6.6.4.1/1.2.3.R means that p13 is true if the ipm- return protocol element is supported in reception. A.4.8Additional comments 1 -Parameters which are not supported for reception should normally not be regarded as a protocol violation. 2 -In the following tables, every leading parameter marked "m" should be supported by the IUT in order to fullfil the static conformance requirements. Sub- parameters marked "m" should be supported if the corresponding leading parameter is supported by the IUT. 3 -For ORNames relating to a user of the own system ("local ORName") the IUT might choose to make certain restrictions on the supported forms of ORAddresses. Users of another system ("remote ORName"), however, shall be adressable without any restrictions. 4 -Each line within the PICS proforma which requires implementation detail to be entered is numbered. This numbering is included as a mean of uniquely identifying all possible implementation detail within the PICS proforma. A.5 Abbreviations The following abbreviations are used in this PICS proforma: D Defined I Implemented m mandatory N NO n/a Not Applicable o optional c conditional d default O/R O = Origination / R = Reception PHY PHYsical Delivery SEC SECurity Y YES EoS Element of Service PEL Protocol ELement A.6 Capabilities and options Introduction In this part of the PICS Proforma the supported application contexts, the major capabilities of the supported application contexts and functions are identified. Further the PDUs and Operations are identified. And finally the Operation Arguments and PDU Parameters are identified. Mapping between X.400 keys and pics entries: X.400 PICS BASIC MT SERVICE m ESSENTIAL OPTIONAL m ADDITIONAL OPTIONAL PER MESSAGE o ADDITIONAL OPTIONAL CONTRACTUAL o A.6.1Initiator/Responder Capability "N/A" A.6.2Supported Application Contexts and Options Supported Application Contexts "N/A" Supported Options Ref.No. Question D D I (ISO) (CCITT ) 1 Are all Security o o [ ] capabilities implemented? 2 Are all Physical o o [ ] Delivery capabilities implemented? A.6.3Major Capabilities Note: Within the following tables "O/R" means "Origination/Reception". Message Transfer, Physical Delivery, Security and Message Store elements of service have been listed into separate tables. IPM elements of service Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 1 Authorizing users O o [ ] B.5 indication R m [ ] 2 Auto-forwarded O o [ ] B.6 indication R m [ ] 3 Blind copy recipient O o [ ] B.8 indication R m [ ] 4 Body part encryption O o [ ] B.9 indication R m [ ] 5 Cross-referencing O o [ ] B.18 indication R m [ ] 6 Expiry date indication O o [ ] B.29 R m [ ] 7 Forwarded IP-message O o [ ] B.31 indication R m [ ] 8 Importance indication O o [ ] B.35 R m [ ] 9 Incomplete copy O o [ ] B.36 indication R o [ ] 10 IP message O m [ ] B.37 identification R m [ ] 11 Language indication O o [ B.38 R m [ ] 12 Multi-part body O o [ ] B.46 R m [ ] 13 Non receipt O o [ ] B.48 notification request indication R m [ ] 14 Obsoleting indication O o [ ] B.52 R m [ ] 15 Originator indication O m [ ] B.55 R m [ ] 16 Primary and copy O m [ ] B.62 recipients indication R m [ ] 17 Receipt notification O o [ ] B.67 request ndication R o [ ] IPM elements of service (continued) Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 18 Reply request O o [ ] B.72 indication R m [ ] 19 Reply IP message O m [ ] B.73 indication R m [ ] 20 Sensitivity indication O o [ ] B.80 R m [ ] 21 Subject indication O m [ ] B.88 R m [ ] 22 Typed body O m [ ] B.90 R m [ ] Message Transfer services Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 23 Access management O m [ ] B.1 R m [ ] 24 Alternate recipient O o [ ] B.3 allowed R o [ ] 25 Alternate recipient O n/a [ ] B.4 assignment R o [ ] 26 Content type O m [ ] B.12 indication R m [ ] 27 Conversion prohibition O m [ ] B.13 R m [ ] 28 Conversion prohibition O o [ ] B.14 in case of loss of information R o [ ] 29 Converted indication O n/a [ ] B.15 R m [ ] 30 Deferred delivery O m [ ] B.19 R n/a [ ] 31 Deferred delivery O o [ ] B.20 cancellation R n/a [ ] 32 Delivery notification O m [ ] B.21 R n/a [ ] 33 Delivery time stamp O n/a [ ] B.22 indication R m [ ] 34 Designation of O o [ ] B.24 recipient by directory name R n/a [ ] 35 Disclosure of other O o [ ] B.25 recipients R m [ ] 36 DL Expansion history O n/a [ ] B.26 indication R m [ ] 37 DL Expansion O o [ ] B.27 prohibited R n/a [ ] 38 Explicit conversion O o [ ] B.30 R n/a [ ] Message Transfer services (continued) Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 39 Grade of delivery O m [ ] B.32 selection R m [ ] 40 Hold for delivery O n/a [ ] B.33 R o [ ] 41 Implicit conversion O n/a [ ] B.34 R o [ ] 42 Latest delivery O o [ ] B.39 designation R n/a [ ] 43 Message identification O m [ ] B.41 R m [ ] 44 Multi destination O m [ ] B.45 delivery R n/a [ ] 45 Non delivery O n/a [ ] B.47 notification R m [ ] 46 Original encoded O m [ ] B.54 information types indication R m [ ] 47 Originator requested O o [ ] B.56 alternate recipient R n/a [ ] 48 Prevention of non O o [ ] B.61 delivery notification R n/a [ ] 49 Probe O o [ ] B.63 R n/a [ ] 50 Redirection disallowed O o [ ] B.68 by originator R n/a [ ] 51 Redirection of O n/a [ ] B.69 incomming messages R o [ ] 52 Requested delivery O m [ ] B.76 method R n/a [ ] 53 Restricted delivery O n/a [ ] B.77 R o [ ] 54 Return of content O o [ ] B.78 R n/a [ ] Message Transfer services (continued) Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 55 Submission time stamp O m [ ] B.89 indication R m [ ] 56 Use of distribution O o [ ] B.92 list R n/a [ ] 57 User/UA capabilities O m [ ] B.93 registration R m [ ] Physical Delivery services This table shall be filled in only if Physical Delivery is supported (see A.6.2/2). Message Transfer services (continued) Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 58 Additional physical O o [ ] B.2 rendition R o [ ] 9 Basic physical O o [ ] B.7 rendition R m [ ] Note. 2 60 Counter collection O o [ ] B.16 R m [ ] Note. 2 61 Counter collection O o [ ] B.17 with advice R o [ ] 62 Delivery via bureaufax O o [ ] B.23 service R o [ ] 63 EMS (Express Mail O o [ ] B.28 Service) R m [ ] Note. 2 64 Ordinary mail O o [ ] B.53 R m [ ] Note. 2 65 Physical delivery O o [ ] B.57 notification by MHS R o [ ] 66 Physical delivery O o [ ] B.58 notification by PDS R m [ ] Note. 2 67 Physical forwarding O o [ ] B.59 allowed 68 Physical forwarding O o [ ] B.60 prohibited R m [ ] Note. 2 Message Transfer services (continued) Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 69 Registered mail O o [ ] B.70 R o [ ] 70 Registered mail to O o [ ] B.71 addresses in person R o [ ] 71 Request for forwarding O o [ ] B.75 address R o [ ] 72 Special delivery O o [ ] B.81 R m [ ] Note. 2 73 Undeliverable mail O o [ ] B.91 with return of physical message R m [ ] Note. 2 Note.2: Only for PDAU else n/a Security services This table shall be filled in only if Security is supported (see A.6.2/1). Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 74 Content O o [ ] B.10 confidentiality R o [ ] 75 Content integrity O o [ ] B.11 R o [ ] 76 Message flow O o [ ] B.40 confidentiality R n/a [ ] 77 Message origin O o [ ] B.42 authentication R o [ ] 78 Message security O o [ ] B.43 labelling R o [ ] 79 Message sequence O o [ ] B.44 integrity R o [ ] 80 Non repudiation of O o [ ] B.49 delivery R o [ ] 81 Non repudiation of O o [ ] B.50 origin R o [ ] 82 Non repudiation of O o [ ] B.51 submission R o [ ] 83 Probe origin O o [ ] B.64 authentication R n/a [ ] 84 Proof of delivery O o [ ] B.65 R o [ ] 85 Proof of submission O o [ ] B.66 R n/a [ ] 86 Report origin O o [ ] B.74 authentication R o [ ] 87 Secure access O o [ ] B.79 management R o [ ] MS elements of service This table shall be filled in only if predicate p25 is TRUE. Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 87 MS register O n/a [ ] B.4n R o [ ] 88 Stored message alert O n/a [ ] B.82 R o [ ] 89 Stored message auto- O n/a [ ] B.83 forward R o [ ] 90 Stored message O n/a [ ] B.84 deletion R m [ ] 91 Stored message O n/a [ ] B.85 fetching R m [ ] 92 Stored message listing O n/a [ ] B.86 R m [ ] 93 Stored message summary O n/a [ ] B.87 R m [ ] A.6.4Timers and Protocol parameters N/A A.6.5Supported PDUs Clause Ref. Ref. MHS ELEMENT OF SERVICE O/R D I (X.400) No. 1 Interpersonnal Message O m [ ] 7 (IPM) R m [ ] 2 Interpersonnal O m [ ] 8 Notification (IPN) R c [ ] p1