OSI PICS Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Tandem OSI PICS

Manual

Abstract

This manual is a reference document containing protocol implementation conformance

statement (PICS) information for Tandem OSI-related products. This manual is

intended for anyone who needs information on the conformance of Tandem OSI-related

products to various standards such as ISO, CCITT (ITU), and the like.

Product Version

N.A.

Supported Releases

This manual supports D44.00 and all subsequent releases until otherwise indicated in a new

edition.

Part Number Published Release ID

135046 July 1997 D44.00

Summary of content (492 pages)

PAGE 1
Tandem OSI PICS Manual Abstract This manual is a reference document containing protocol implementation conformance statement (PICS) information for Tandem OSI-related products. This manual is intended for anyone who needs information on the conformance of Tandem OSI-related products to various standards such as ISO, CCITT (ITU), and the like. Product Version N.A. Supported Releases This manual supports D44.00 and all subsequent releases until otherwise indicated in a new edition.
PAGE 2
Document History Part Number Product Version Published 099927 N.A. September 1993 120563 N.A. December 1995 132299 N.A. February 1997 135046 N.A. July 1997 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
PAGE 3
New and Changed Information Changes to this manual are indicated by a change bar in the right margin beside the affected text. The following changes were made to this edition of the manual: • • • Modifications have been made to Section 3, ISO 8802-3 for TLAM, to include implementations added for Tandem TLAM. Modifications have been made to Section 4, X.25 NET2 for X25AM, to include implementations added for Tandem X25AM. Section 20, ISO 9594: 1993 DSP for NSDS, and Section 21, ISO 9594: X.
PAGE 4
New and Changed Information Tandem OSI PICS Manual–135046 iv
PAGE 5
Contents About This Manual xxxi Notation Conventions xxxiii 1. Introduction What Are PICS? 1-1 PICS Definition 1-1 How Are PICS Used? 1-2 PICS Version Information 1-2 Overview of Tandem OSI Products 1-3 Relationship of Products to OSI Reference Model Standards Implemented 1-6 1-5 2. ISO 8802-2 for TLAM PICS for TLAM LLC 2-3 COS Stack Specification Implementation Conformance Statement 2-3 C.1 Logical Link Control (LLC) Protocol Implementation Conformance Statement 2-3 C.1.1 General 2-3 C.1.
PAGE 6
3. ISO 8802-3 for TLAM (continued) Contents 3. ISO 8802-3 for TLAM (continued) D.1.5.1 Presence and Order of Fields 3-5 D.1.5.2 Preamble Field 3-5 D.1.5.3 Start Frame Delimiter Field 3-5 D.1.5.4 Address Fields 3-6 D.1.5.5 Length Field 3-6 D.1.5.6 Data and Pad Fields 3-6 D.1.5.7 Frame Check Sequence (FCS) Field D.1.5.8 Order of Bit Transmission 3-7 D.1.5.9 Overlength Frames 3-7 D.1.5.10 Invalid MAC Frames 3-7 D.1.6 MAC Internal Processes 3-7 D.1.7 Services Provided to PLS 3-8 D.1.
PAGE 7
5. ISO 8073 for OSI/TS (continued) Contents 5. ISO 8073 for OSI/TS (continued) Protocol Supplier (if not the system supplier) 5-4 Reference Protocol Identification 5-4 IUT Identification 5-4 D.3 Index of Indices Used in this Document 5-4 D.4 Base Standard/Recommendation Conformance 5-5 D.5 General Statement of Conformance 5-5 D.6 Protocol Implementation 5-5 D.6.1 Addendum 1—NCMS 5-5 D.6.2 Classes Implemented 5-5 D.7 NCMS Functions 5-5 D.8 Initiator/Responder Capability for Protocol Classes 0-4 5-6 D.
PAGE 8
5. ISO 8073 for OSI/TS (continued) Contents 5. ISO 8073 for OSI/TS (continued) D.13.2 Class 2 (C2::) 5-19 D.13.3 Class 3 (C3::) 5-19 D.13.4 Class 4 (C4 or C4L::) 5-19 D.14 User Data in Received TPDUs 5-19 D.15 Negotiation 5-20 D.15.1 Class Negotiation—Initiator 5-20 D.15.2 Class Negotiation—Responder Side 5-21 D.15.3 TPDU Size Negotiation 5-21 D.15.5 Expedited Data Transport Service 5-23 D.15.6 Non-Use of Checksum ((C4 or C4L) AND T4F29::) 5-23 D.15.
PAGE 9
8. ISO 8327, Version 1 for OSI/AS Contents 8. ISO 8327, Version 1 for OSI/AS PICS for the OSI Session Protocol, Version 1 8-3 F.0 Introduction 8-3 Protocol Versions 8-3 Line Numbering 8-3 Hierarchical Structure of the PICS Proforma 8-3 D Column 8-4 I Column 8-4 Value Column 8-4 F.1 Date of Statement 8-4 F.2 Implementation Details 8-4 F.3 ISO 8327 Protocol Versions Implemented 8-6 F.4 Defect Report Numbers and Amendments Implemented 8-6 F.5 Global Statement of Conformance 8-6 F.
PAGE 10
Contents 8. ISO 8327, Version 1 for OSI/AS (continued) 8. ISO 8327, Version 1 for OSI/AS (continued) F.7.11 Exceptions Functional Unit Procedures 8-11 F.7.12 Activity Management Functional Unit Procedures F.8 Supported SPDU Parameters 8-12 F.8.0 Guidance for Completion 8-12 Note on D Column 8-12 Note (N1) : User-Data-Like Parameters 8-12 Note on Value Column 8-12 F.8.1 Connect (CN) SPDU 8-13 F.8.2 Overflow Accept (OA) SPDU 8-13 F.8.3 Connect Data Overflow (CDO) SPDU 8-14 F.8.4 Accept (AC) SPDU 8-14 F.8.
PAGE 11
8. ISO 8327, Version 1 for OSI/AS (continued) Contents 8. ISO 8327, Version 1 for OSI/AS (continued) F.8.32 F.8.33 F.8.34 F.8.35 F.8.36 Activity Interrupt Ack (AIA) SPDU 8-22 Activity Discard (AD) SPDU 8-22 Activity Discard Ack (ADA) SPDU 8-22 Activity End (AE) SPDU 8-22 Activity End Ack (AEA) SPDU 8-23 9. ISO 8327, Version 2 for OSI/AS PICS for the OSI Session Protocol, Version 2 9-3 F.
PAGE 12
Contents 9. ISO 8327, Version 2 for OSI/AS (continued) 9. ISO 8327, Version 2 for OSI/AS (continued) F.7.5 Expedited Data Functional Unit Procedures 9-9 F.7.6 Typed Data Functional Unit Procedures 9-9 F.7.7 Capability Data Functional Unit Procedures 9-10 F.7.8 Minor Synchronize Functional Unit Procedures 9-10 F.7.9 Major Synchronize Functional Unit Procedures 9-10 F.7.10 Resynchronize Functional Unit Procedures 9-10 F.7.11 Exceptions Functional Unit Procedures 9-11 F.7.
PAGE 13
9. ISO 8327, Version 2 for OSI/AS (continued) Contents 9. ISO 8327, Version 2 for OSI/AS (continued) F.8.26 F.8.27 F.8.28 F.8.29 F.8.30 F.8.31 F.8.32 F.8.33 F.8.34 F.8.35 F.8.
PAGE 14
10. ISO 8823 for OSI/AS (continued) Contents 10. ISO 8823 for OSI/AS (continued) B.4.7 Session Duplex Functional Unit 10-9 B.4.8 Expedited Data Functional Unit 10-9 B.4.9 Typed Data Functional Unit 10-9 B.4.10 Capability Data Exchange Functional Unit 10-9 B.4.11 Minor Synchronize Functional Unit 10-10 B.4.12 Major Synchronize Functional Unit 10-10 B.4.13 Resynchronize Functional Unit 10-10 B.4.14 Activity Management Functional Unit 10-10 B.4.15 Exceptions Functional Unit 10-11 B.4.
PAGE 15
10. ISO 8823 for OSI/AS (continued) Contents 10. ISO 8823 for OSI/AS (continued) B.5.10.2 Receiving 10-18 B.5.11 TE PPDU 10-19 B.5.11.1 Sending 10-19 B.5.11.2 Receiving 10-19 B.5.12 TC PPDU 10-19 B.5.12.1 Sending 10-19 B.5.12.2 Receiving 10-19 B.5.13 TCC PPDU 10-19 B.5.13.1 Sending 10-19 B.5.13.2 Receiving 10-19 B.5.14 RS PPDU 10-20 B.5.14.1 Sending 10-20 B.5.14.2 Receiving 10-20 B.5.15 RSA PPDU 10-20 B.5.15.1 Sending 10-20 B.5.15.2 Receiving 10-20 B.5.
PAGE 16
11. ISO 8650 for OSI/AS (continued) Contents 11. ISO 8650 for OSI/AS (continued) B.11 Supported Parameters 11-6 B.11.1 A-Associated-Request APDU (AARQ) 11-7 B.11.2 A-Associated-Response APDU (AARE) 11-8 B.11.3 A-Release-Request APDU (RLRQ) 11-8 B.11.4 A-Release-Response APDU (RLRE) 11-9 B.11.5 Abort APDU (ABRT) 11-9 12. ISO 8571 for FTAM PICS for OSI/FTAM 12-3 Section 1 Implementation Details 12-3 A.1 Date of Statement 12-3 A.2 Implementation Details 12-3 Section 2 General ISO 8571 Detail 12-4 A.
PAGE 17
12. ISO 8571 for FTAM (continued) Contents 12. ISO 8571 for FTAM (continued) A.11 File Protocol 12-12 A.11.1 GraphicString Support 12-13 A.11.2 FTAM Regime Establishment 12-14 A.11.3 FTAM Regime Termination (Orderly) 12-14 A.11.4 FTAM Regime Termination (Abrupt) by Service User 12-15 A.11.5 FTAM Regime Termination (Abrupt) by Service Provider 12-15 A.11.6 File Selection 12-15 A.11.7 File Deselection 12-15 A.11.8 File Creation 12-16 A.11.9 File Deletion 12-16 A.11.10 Read Attributes 12-16 A.11.
PAGE 18
12. ISO 8571 for FTAM (continued) Contents 12. ISO 8571 for FTAM (continued) A.12.4 Service Class Field Detail 12-27 A.12.5 Functional Unit Field Detail 12-27 A.12.6 Diagnostic Field Detail 12-28 A.12.7 Contents Type Detail 12-28 A.12.7.1 Contents Type List Field 12-28 A.12.7.2 Contents Type Field 12-28 A.12.8 FTAM Quality of Service Details 12-29 A.12.8.1 Initiator 12-29 A.12.8.2 Responder 12-29 A.12.9 Details of Shared ASE Information 12-30 A.12.10 Details of Charging 12-30 A.12.
PAGE 19
13. CCITT X.400: P1 1984 for MHS Contents 13. CCITT X.400: P1 1984 for MHS PICS for the OSI MHS 1984 P1 Protocol 13-3 1. PICS Cover Page Proforma 13-3 2. Supported Functions Proforma 13-3 Instructions for Client 13-3 Mapping Between A/311 Keys and PICS Entries 13-4 3. Initiator/Responder Capability 13-5 Instructions for the Client 13-5 4. Supported PDUs Proforma 13-5 Instructions for the Client 13-5 5.
PAGE 20
14. CCITT X.400: RTS for MHS (continued) Contents 14. CCITT X.400: RTS for MHS (continued) 5.3 PRefuse Element 14-8 Instructions for Client 14-8 RTS Element : PRefuse 14-9 5.4 AbortInformation Element 14-9 Instructions for Client 14-9 RTS Element : AbortInformation 14-9 Annex A.1 14-9 Mapping Between A/311 Keys and PICS Entries 14-9 15. CCITT X.400: P1 1988 for MHS PICS for the OSI MHS 1988 P1 Protocol 15-3 1 Introduction 15-3 2 Scope 15-3 3 Normative References 15-3 4 Definitions 15-3 4.
PAGE 21
15. CCITT X.400: P1 1988 for MHS (continued) Contents 15. CCITT X.400: P1 1988 for MHS (continued) A.5.7 Operation Arguments and PDU Parameters 15-14 A.5.7.1 MTA-bind Arguments 15-15 A.5.7.2 MTA-unbind Arguments 15-17 A.5.7.3 MessageTransfer PDU Parameters 15-17 A.5.7.4 ReportTransfer PDU Parameters 15-20 A.5.7.5 ProbeTransfer PDU Parameters 15-22 A.5.7.6 Supported Data Types and ORNames 15-24 A.5.7.6.1 Common Data Types 15-24 A.5.7.6.2 Extension Data Types 15-29 A.5.7.6.3 OR Names 15-32 A.5.
PAGE 22
16. CCITT X.400: P2 for MHS (continued) Contents 16. CCITT X.400: P2 for MHS (continued) A.4.7 Additional Comments 16-9 A.5 Abbreviations 16-10 A.6 Capabilities and Options 16-11 Introduction 16-11 A.6.1 Initiator/Responder Capability 16-12 A.6.2 Supported Application Contexts 16-12 A.6.3 Major Capabilities 16-12 A.6.4 Timers and Protocol Parameters 16-17 A.6.5 Supported PDUs 16-17 A.6.6 Supported PDU Parameters 16-17 A.6.6.1. IPM 16-17 A.6.6.2. IPN 16-22 A.6.6.3 Message Store Attributes 16-23 A.6.6.
PAGE 23
17. CCITT X.400: P7 for MHS (continued) Contents 17. CCITT X.400: P7 for MHS (continued) A.2 Global Statement of Conformance 17-6 A.3 Instructions for Completing the PICS Proforma 17-6 Predicates List 17-7 A.4 Abbreviations 17-9 A.5 Capabilities and Options 17-9 A.5.1 Initiator/Responder Capability 17-9 A.5.2 Supported Application Contexts 17-10 A.5.3 Major Capabilities 17-10 A.5.4 Timers and Protocol Parameters 17-13 A.5.5 Supported PDUs (Operations) 17-13 A.5.
PAGE 24
18. CCITT X.400: RTSE for MHS (continued) Contents 18. CCITT X.400: RTSE for MHS (continued) A.2 A.3 A.4 A.5 Global Statement of Conformance 18-6 Instructions for Completing the PICS Proforma Abbreviations 18-7 Capabilities and Options 18-7 A.5.1 Initiator/Responder Capability 18-7 A.5.2 Supported Application Contexts 18-8 A.5.3 Major Capabilities 18-8 A.5.4 Timers and Protocol Parameters 18-10 A.5.4.1 Timers 18-10 A.5.4.2 Protocol Parameters 18-10 A.5.4.2.1 RTORQapdu 18-10 A.5.4.2.2 RTOACapdu 18-10 A.5.
PAGE 25
Contents 20. ISO 9594: 1993 DSP for NSDS (continued) 20. ISO 9594: 1993 DSP for NSDS (continued) A.1 Identification of the Implementation 20-6 A.1.1 Identification of PICS 20-6 A.1.2 Identification of the Implementation and/or System 20-6 A.1.3 Identification of the System Supplier and/or Test Laboratory Client 20-7 A.2 Identification of the Protocol 20-7 A.3 Global Statement of Conformance 20-7 A.3.1 DSA Implementation and/or System 20-8 A.3.1.1 DSA Supported Security Levels 20-9 A.3.1.
PAGE 26
Contents 20. ISO 9594: 1993 DSP for NSDS (continued) 20. ISO 9594: 1993 DSP for NSDS (continued) A.6.3.11 ChainedModifyDN Elements 20-21 A.6.3.12 Errors and Parameters 20-23 A.6.3.13 Common Arguments Elements 20-23 A.6.3.14 Common Results Elements 20-25 A.6.3.15 Service Controls 20-25 A.6.3.16 Entry Information Selection 20-25 A.6.3.17 Entry Information 20-25 A.6.3.18 Filter Elements 20-26 A.6.3.19 Filter Item Elements 20-26 A.6.3.20 Paged Results 20-26 A.6.3.21 Continuation Reference 20-26 A.6.3.
PAGE 27
20. ISO 9594: 1993 DSP for NSDS (continued) Contents 20. ISO 9594: 1993 DSP for NSDS (continued) A.6.4.5 Subschema Administration 20-39 A.6.4.5.1 Subschema Administration Object Classes 20-39 A.6.4.5.2 Subschema Administration Attributes 20-40 A.6.4.5.3 Subschema Administration Matching Rules 20-40 A.6.4.6 Access Control 20-40 A.6.4.6.1 Access Control Object Classes 20-40 A.6.4.1.2 Access Control Attributes 20-40 A.6.4.6.3 Access Control Matching Rules 20-40 A.6.4.7. DSA Operational Attributes 20-40 A.6.
PAGE 28
Contents 21. ISO 9594: X.500 DAP for NSDS (continued) 21. ISO 9594: X.500 DAP for NSDS (continued) A.3.2 DUA Implementation and/or System 21-11 A.3.2.1 DUA Supported Security Levels 21-11 A.3.2.2 DUA Product Category 21-11 A.3.2.3 DUA Miscellaneous Capabilities 21-12 A.4 Instruction for Completing the PICS Proforma 21-12 A.4.1 Definition of Support 21-12 A.4.2 Status Columns (PS) 21-13 A.4.3 Support Column 21-13 A.4.4 Note Column 21-13 A.4.5 Predicate Column 21-14 A.4.6 Item Reference Numbers 21-14 A.
PAGE 29
Contents 21. ISO 9594: X.500 DAP for NSDS (continued) 21. ISO 9594: X.500 DAP for NSDS (continued) A.6.3.19 Filter Item Elements 21-27 A.6.3.20 Paged Results 21-27 A.6.3.21 Continuation Reference 21-28 A.6.3.22 Security Parameters 21-28 A.6.3.23 Certification Path 21-30 A.6.3.24 Access Control 21-30 A.6.3.24.1 Access Control Information 21-30 A.6.3.24.2 Protected Items 21-32 A.6.3.24.3 UserClasses 21-32 A.6.3.25 Subtrees 21-32 A.6.4 Directory Schema 21-32 A.6.4.1 Supported Object Classes 21-33 A.6.4.1.
PAGE 30
Contents A. Tandem Manuals for OSI-Related Products A. Tandem Manuals for OSI-Related Products Manuals for TLAM (Tandem LAN Access Method) A-1 Manuals for X25AM (Tandem X.25 Access Method) A-3 Manuals for OSI/TS (Tandem OSI/Transport Services) A-5 Manuals for OSI/AS (Tandem OSI/Application Services) A-7 Manuals for Tandem FTAM (Tandem File Transfer, Access and Management) Manuals for OSI/MHS (Tandem OSI/Message Handling System) A-11 Manuals for NonStop Directory Services (NSDS) A-13 Figures Figure 1-1.
PAGE 31
About This Manual The Tandem OSI PICS Manual is a reference document describing the conformance of Tandem OSI-related products to generally accepted standards published by ISO (International Organization for Standardization), CCITT (International Telegraph and Telephone Consultative Committee), ITU, and the like. The formal description of each Tandem product, called a PICS (protocol implementation conformance statement), strictly follows the format specified in the applicable standard.
PAGE 32
About This Manual Your Comments Invited Table 1. Summary of Contents (page 2 of 2) # Title 15 CCITT X.400: P1 1988 for MHS 16 CCITT X.400: P2 for MHS 17 CCITT X.400: P7 for MHS 18 CCITT X.400: RTSE for MHS 19 CCITT X.435: EDI for MHS 20 ISO 9594: 1993 DSP for NSDS 21 ISO 9594: X.500 DAP for NSDS A Tandem Manuals for OSI-Related Products Note. Some of the standards implemented by Tandem OSI-related products do not yet have an associated PICS proforma available to the public.
PAGE 33
Notation Conventions PICS Notation All text and notation used in published PICS proformas have been reproduced as is, including notes, with the following exceptions: • Minor corrections, changes, and errors are marked with an asterisk and explained below the relevant table, as in the following example: * Numbering conforms to proforma.
PAGE 34
Change Bar Notation Notation Conventions Tandem OSI PICS Manual–135046 xxxiv
PAGE 35
1 Introduction This manual describes the conformance of Tandem OSI-related products to standards published by ISO (International Organization for Standardization), CCITT (International Telegraph and Telephone Consultative Committee), and the like. The formal description of each Tandem product, called a PICS (protocol implementation conformance statement), strictly follows the format specified in the applicable standard.
PAGE 36
How Are PICS Used? Introduction How Are PICS Used? ISO 9646 defines a PICS as “a statement made by the supplier of an OSI implementation or system, stating which capabilities and options have been implemented, for a given OSI protocol.” While this statement may be interpreted in different ways, one generally accepted interpretation is that a PICS is specific to a protocol but insufficient to fully describe a product.
PAGE 37
Overview of Tandem OSI Products Introduction Tandem Product Version The Tandem product version described by the given PICS (for example, C30). Unless otherwise noted, the conformance claimed in a PICS statement applies to the given product version and all subsequent IPMs and product versions. Date PICS Last Updated The date on which the proforma or the PICS contents were last updated by Tandem. Verification Indicates whether the PICS has been verified and, if so, in what manner.
PAGE 38
Overview of Tandem OSI Products Introduction • • • OSI/MHS (OSI/Message Handling System) OSI/FTAM (OSI/File Transfer, Access and Management) NSDS (NonStop Directory Services) Tandem OSI PICS Manual–135046 1 -4
PAGE 39
Relationship of Products to OSI Reference Model Introduction Relationship of Products to OSI Reference Model Figure 1-1 shows the relationship of the Tandem OSI-related products to each other and to the OSI Reference Model. The figure also illustrates the application interfaces provided by each product. These interfaces allow your application to programmatically access the services of a particular product and to perform higher-level protocol functions. Figure 1-1.
PAGE 40
Standards Implemented Introduction Standards Implemented Table 1-1 shows the standards implemented by each Tandem OSI-related product and whether or not a PICS for that standard is included in this manual. Wherever possible, a PICS is included for each ISO or CCITT (International Telegraph and Telephone Consultative Committee) standard implemented. The Tandem products and their associated PICS are listed in the order in which they appear in this manual. Table 1-1.
PAGE 41
2 ISO 8802-2 for TLAM The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard ISO 8802-2 Standard Version ISO 8802-2, 1989-12-31 Proforma Logical Link Control (LLC) PICS COS Stack Specification TA51 Proforma Version COS/ENG-88/001 - Version 1.
PAGE 42
ISO 8802-2 for TLAM This page intentionally left blank.
PAGE 43
PICS for TLAM LLC ISO 8802-2 for TLAM PICS for TLAM LLC COS Stack Specification Implementation Conformance Statement The Implementation Conformance Statement contained in this Annex is the definitive specification of subnetwork-type dependent requirements for conformance to the profile within this COS stack specification. C.1 Logical Link Control (LLC) Protocol Implementation Conformance Statement C.1.
PAGE 44
C.1.3 Identification ISO 8802-2 for TLAM C.1.3 Identification Protocol Supplier (if not the system supplier) Reference Protocol Identification Name: ISO 8802-2: 1989(E) Standard Reference No.: ANSI/IEEE 8022-1989 Number/Revision Date: Addenda applicable: Amendments applicable (defect reports): IUT Identification Name: Tandem LAN Access Method (TLAM) Version #: C20 Date: 15 February 1989 C.1.
PAGE 45
C.1.5 Addressing ISO 8802-2 for TLAM C.1.5 Addressing Standard Clause Standard Type or Range COSSS Clause COSSS Type or Range Ref # Parameter + Type Implemented? 1.5.1 SSAP Address — Null 6.2 m m Y 1.5.2 SSAP Address — Individual 6.2 m m Y 1.5.3 DSAP Address — Individual 6.2 m m Y 1.5.4 DSAP Address — Group 6.2 m m Y 1.5.5 DSAP Address — Global 6.2 m m Y 1.5.6 DSAP Address — Null 6.2 m m Y C.1.
PAGE 46
C.1.6 Supported Parameters ISO 8802-2 for TLAM Symbols not defined above are defined in § C.1.2. Ref # LLC PDU 1.6.1 1.6.2 1.6.3 1.6.4 1.6.5 1.6.6 1.6.7 1.6.8 UI command 1.6.9 1.6.10 1.6.11 1.6.12 1.6.13 1.6.14 1.6.15 1.6.16 XID response 1.6.17 1.6.18 1.6.19 1.6.20 1.6.21 1.6.22 1.6.23 1.6.
PAGE 47
3 ISO 8802-3 for TLAM The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard ISO 8802-3 Standard Version ISO 8802-3, 1990-09-21 Proforma MAC PICS COS Stack Specification TA51 Proforma Version COS/ENG-88/001 - Version 1.
PAGE 48
ISO 8802-3 for TLAM This page intentionally left blank.
PAGE 49
ISO 8802-3 for TLAM PICS for TLAM MAC PICS for TLAM MAC COS Stack Specification Implementation Conformance Statement The Implementation Conformance Statement contained in this Annex is the definitive specification of subnetwork-type dependent requirements for conformance to the profile within this COS stack specification. D.1 MAC Protocol Implementation Conformance Statement D.1.1 General This Implementation Conformance Statement specifies requirements for implementations of ISO 8802-3.
PAGE 50
ISO 8802-3 for TLAM D.1.3 Identification D.1.3 Identification Protocol Supplier (if not the system supplier) Reference Protocol Identification Name: ISO/IEC 8802-3: 1990(E) MAC Sub-layer IEEE 802.3 Standard Reference No. ANSI/IEEE 802.3-1990 Edition Number/Revision Date: Addenda applicable: Amendments applicable (defect reports): IUT Identification Name: Tandem LAN Access Method (TLAM) Version #: C20 Date: 15 February 1989 D.1.4 Protocol Data D.1.4.1 MA_DATA.
PAGE 51
ISO 8802-3 for TLAM D.1.5 MAC Frame Structure The MA_DATA.indication is given to the LLC sub-layer upon the receipt of a frame that is validly formed, received without error, and received with a destination address matching the local MAC entity (see § 2.3.2.2). Note. All section/clause numbers refer to the base standard unless noted. D.1.5 MAC Frame Structure D.1.5.1 Presence and Order of Fields Ref # Standard Order Field Standard Clause COSSS Type or Range Implemented? 1.5.1.1 1 Preamble 3.2.
PAGE 52
ISO 8802-3 for TLAM D.1.5 MAC Frame Structure D.1.5.4 Address Fields Standard Clause Standard Type or Range COSSS Clause COSSS Type or Range Implemented? Ref # Function 1.5.4.1 16 bit addresses 3.2.3 o 6.4.4.1 x N 1.5.4.2 48 bit addresses 3.2.3 o 6.4.4.1 m Y 1.5.4.3 Individual address 3.2.3.1 m m Y 1.5.4.4 Multi-cast grp. addr. (2) 3.2.3.1 o o Y 1.5.4.5 Broadcast address 3.2.3.1 m m(1) Y Note 1: The reception of a frame with a broadcast address is mandatory.
PAGE 53
ISO 8802-3 for TLAM D.1.6 MAC Internal Processes Implemented: Y D.1.5.8 Order of Bit Transmission The implementation shall send each octet of the MAC frame (with the exception of the frame check sequence), low order bit first. The implementation shall send the bits of the FCS in the order χ31, χ30, ..., χ1, χ0 (see § 3.2.8). Implemented: Y D.1.5.9 Overlength Frames How does the implementation deal with incoming frames that are no longer than maxFrameSize, but are otherwise correctly formed (see § 4.2.4.
PAGE 54
ISO 8802-3 for TLAM D.1.7 Services Provided to PLS D.1.7 Services Provided to PLS Please indicate if the implementation provides the following services to the PLS sublayer (see § 4.3.3 of the base standard). Function Provided? ReceiveBit Y TransmitBit Y Transmitting Y D.1.8 Services Provided to LLC Please indicate if the implementation provides the following services to the LLC sublayer (see § 4.3.2 of the base standard). Function Provided? TransmitFrame Y ReceiveFrame Y D.1.
PAGE 55
ISO 8802-3 for TLAM D.1.9 MAC Parameter Values Parameters From § 4.4.2.1 Parameter Value from § 4.4.2.1 Impl. Value maxFrameSize 1518 octets 1518 minFrameSize 64 octets(512 bits) 64 Note 1: The IEEE 802.3 standard does not give the interFrameGap value any latitude in § 4.4.2.1; however, § 4.2.3.2.2 states that this is the minimum value. An implementation may use a higher value for internal design reasons, but it is noted that this will result in a decrease of throughput.
PAGE 56
ISO 8802-3 for TLAM D.1.
PAGE 57
4 X.25 NET2 for X25AM The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard X.25 (1984) Standard Version X.25 Version 1984 Proforma NET2 X.25; a European Community (EC) document Proforma Version Datex-P, X.
PAGE 58
X.25 NET2 for X25AM This page intentionally left blank.
PAGE 59
X.25 NET2 for X25AM PICS for X25AM NET2 PICS for X25AM NET2 Equipment EDP System TNSII, TXP, EXP, VLX, CLX, Cyclone Interface Comm. SUBSYSTEM X.25 Software: C20 X25OBJ Phys. Interf. X.21bis X.21 Yes Yes (6100-family controller only) Line Speed 2400 bit/s 4800 bit/s 9600 bit/s 19200 bit/s 48000 bit/s 64000 bit/s Yes Yes Yes Yes Yes Yes (but no THRUPUT negotiation) Max.
PAGE 60
X.25 NET2 for X25AM PIXIT Level 2 PIXIT Level 2 IUT K System Parameter (window) Default = 4 Sysgen Dependent IUT Retransmission Timer T1 Default = 3 secs Sysgen Dependent IUT Retransmission Counter N2 Default = 10 Sysgen Dependent IUT Max. Length of I-Frames N1 (Packetsize + Header info) Default Packetsize = 128 Sysgen Dependent I-Frames: Restart Packet These I-Frames will be preselected in the tester to perform tests within ABM condition.
PAGE 61
X.25 NET2 for X25AM PIXIT Level 3 PIXIT Level 3 (Questions not applicable) Test LCN Unassigned LCN IUT Address IUT Window size Clear Request Solicitation Data Packets 1. Q= M= D= Data 2. 3. 4. 5. 6. 7. 8. 9. 10. Preselected data packets used for data transfer tests.
PAGE 62
X.
PAGE 63
5 ISO 8073 for OSI/TS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard ISO/IEC 8073 (Connection-Oriented Transport Protocol) Standard Version ISO 8073: 1988(E) Proforma ISO/IEC 8073 PDAD3.
PAGE 64
ISO 8073 for OSI/TS This page intentionally left blank.
PAGE 65
PICS for the OSI Connection-Oriented Transport Protocol, Annex D (Normative) ISO 8073 for OSI/TS PICS for the OSI Connection-Oriented Transport Protocol, Annex D (Normative) D.1 General D.1.1 Symbols Used Status Symbols Symbol Meaning M Mandatory O Optional to implement. If implemented, the feature may or may not be used. O. Optional, but support of at least one of the group of options labelled by the same numeral in this PICS proforma is required.
PAGE 66
D.2 Identification ISO 8073 for OSI/TS D.2 Identification PICS for Transport Protocol Protocol Supplier (if not the system supplier) Reference Protocol Identification ISO 8073 : Reference Number : ISO/IEC 8073: 1988(E) Add. 1 : Reference Number : ISO 8073: 1986/Add. 1 : 1988(E) Add. 2 : Reference Number : ISO/IEC 8073: 1988/Add. 2 : 1989(E) CCITT X.224 : Reference Number : X.224 (1988) IUT Identification Name: OSI/TS Version No.: C21 and C30 Date: 8/10/92 D.
PAGE 67
D.4 Base Standard/Recommendation Conformance ISO 8073 for OSI/TS D.4 Base Standard/Recommendation Conformance To what base standard does the implementation claim conformance? ISO/IEC 8073 Yes CCITT X.224 Yes D.5 General Statement of Conformance ISO CCT Are all mandatory features of ISO/IEC 8073 implemented? Are all mandatory features of X.224 implemented? Yes Yes Note: Answering “No” to this question indicates non-conformance to this International Standard/ Recommendation. D.
PAGE 68
D.8 Initiator/Responder Capability for Protocol Classes 0-4 ISO 8073 for OSI/TS The following is mandatory if the predicate is true. Index Item N5 Passive network connection recovery Reference to Add. 1 Status 7.4.3 N2 or N4: M D.8 Initiator/Responder Capability for Protocol Classes 0-4 Index References Status Support IR1 Initiating CR TPDU 14.5 a) O.2 Yes IR2 Responding to CR TPDU 14.5 a) O.2 Yes D.9 Supported Functions D.9.
PAGE 69
D.9.3 Supported Functions for Class 2 (C2::) ISO 8073 for OSI/TS Index Function References T1F6 Connection establishment 6.5 T1F7 Connection refusal 6.6 T1F8 Normal release when operating over CONS (explicit) 6.7.1 T1F9 Association of TPDUs with transport connections when operating over CONS 6.9.1 T1F10 Data TPDU numbering (normal) 6.10 T1F11 Expedited data transfer when operating over CONS (network normal) T1F12 Reassignment after failure when operating over CONS 6.
PAGE 70
D.9.4 Supported Functions for Class 3 (C3::) ISO 8073 for OSI/TS Index Function References T2F13 Demultiplexing when operating over CONS 6.15 T2F14 Explicit flow control (with) 6.16 T2F15 Non-use of checksum 6.17 T2F16 Treatment of protocol errors when operating over CONS T2F17 Multiplexing when operating over CONS 6.22.1 6.15 The following functions are optional if class 2 is supported. Index Function References Status Support T2F18 Concatenation 6.
PAGE 71
D.9.5 Supported Functions for Class 4 (C4 or C4L::) ISO 8073 for OSI/TS The following functions are optional if class 3 is supported. Index Function References Status Support T3F21 Concatenation 6.4 O No T3F22 Data TPDU numbering (extended) 6.10 O Yes D.9.5 Supported Functions for Class 4 (C4 or C4L::) The following functions are mandatory. Index Function References T4F1 TPDU transfer 6.2 T4F2 Segmenting 6.3 T4F3 Reassembling 6.3 T4F4 Separation 6.
PAGE 72
D.10 Supported TPDUs ISO 8073 for OSI/TS The following functions are mandatory if class 4 is operated over CLNS. Index Function References T4F23 Transmission over CLNS 6.1.2 T4F24 Normal release when operating over CLNS (explicit) 6.7.2 T4F25 Association of TPDUs with Transport connections when operating over CLNS 6.9.2 T4F26 Expedited data transfer when operating over CLNS (network normal) 6.11.2 T4F27 Treatment of protocol errors when operating over CLNS 6.22.
PAGE 73
D.11 Supported Parameters of Issued TPDUs ISO 8073 for OSI/TS Index TPDUs References Status ST15 EA Supported on transmission 13.1 C1 or C2 or C3 or C4 or C4L: M ST16 EA Supported on receipt 13.1 C1 or C2 or C3 or C4 or C4L: M ST17 RJ Supported on transmission 13.1 C1 or C3 : M ST18 RJ Supported on receipt 13.1 C1 or C3 : M ST19 ER Supported on receipt 13.1 C0 or C1 or C2 or C3 or C4 or C4L: M State for which classes, if any, ER is supported on transmission.
PAGE 74
D.11.2 Parameter Values for CR TPDU (C1:: or C2:: or C3:: or C4:: or C4L::) ISO 8073 for OSI/TS D.11.1.2 NCM TPDU (SN3::) What are the allowed values of the following parameters for an NCM TPDU. References Add. 1 Values Allowed Values Supported Index Supported Parameters IC1 NC-reference 8.4.3 b) IC2 NC-type 8.4.3 c) New, My, Yours No IC3 NC-preference 8.4.3 d) Highest, Medium, Lowest No IC4 NC-collision 8.3.4 e) Resolution No IC5 NC-recovery 8.3.
PAGE 75
D.11.4 Supported Parameters for Class 1 TPDUs (C1::) ISO 8073 for OSI/TS The following parameters are optional if a CC TPDU is issued in class 0. Index Supported Parameters References Status Support I0CC6 Called TSAP ID 13.3.4 O Yes I0CC7 Calling TSAP ID 13.3.4 O Yes I0CC8 TPDU size 13.3.4 O Yes The following parameter is optional if a DR TPDU is issued in class 0. Index Supported Parameter Reference Status Support I0DR4 Additional information 13.5.4 a) O No D.11.
PAGE 76
D.11.5 Supported Parameters for Class 2 TPDUs (C2::) ISO 8073 for OSI/TS The following parameter is optional if a DR TPDU is issued in class 1. Index Supported Parameter Reference Status Support I1DR4 Additional information 13.5.4 a) O No The following parameter is optional if an ER TPDU is issued in class 1. Index Supported Parameter Reference Status Support I1ER3 Invalid TPDU 13.12.4 a) O No D.11.
PAGE 77
D.11.6 Supported Parameters for Class 3 TPDUs (C3::) ISO 8073 for OSI/TS The following parameter is optional if an ER TPDU is issued in class 2. Index Supported Parameter Reference Status Support I2ER3 Invalid TPDU 13.12.4 a) O No D.11.6 Supported Parameters for Class 3 TPDUs (C3::) The following parameters are optional if a CR TPDU is issued with preferred class 3. Index Supported Parameters References Status Support I3CR6 Called TSAP ID 13.3.4 a) O Yes I3CR7 Calling TSAP ID 13.3.
PAGE 78
D.11.7 Supported Parameters for Class 4 TPDUs (C4 or C4L::) ISO 8073 for OSI/TS D.11.7 Supported Parameters for Class 4 TPDUs (C4 or C4L::) The following parameters are optional if a CR TPDU is issued with preferred class 4. Index Supported Parameters References Status Support I4CR7 Called TSAP ID 13.3.4 a) O Yes I4CR8 Calling TSAP ID 13.3.4 a) O Yes I4CR9 TPDU size 13.3.4 b) O Yes I4CR10 Version number 13.3.4 c) O Yes I4CR11 Protection parameters 13.3.
PAGE 79
D.12 Supported Parameters for Received TPDUs ISO 8073 for OSI/TS If the implementation can reduce credit and does so in the manner outlined in ISO 8073 clause 12.2.3.8.2, then subsequence number in AK TPDUs is mandatory. Otherwise complete item I4AK5. Index Supported Parameter Reference Status Support I4AK5 Subsequence Number 13.9.4 b) O Yes The following parameter is optional if an ER TPDU is issued in class 4: Index Supported Parameter Reference Status Support I4ER3 Invalid TPDU 13.12.
PAGE 80
D.12.2 TPDUs in Class 4 (C4 or C4L::) ISO 8073 for OSI/TS D.12.1.3 DIAG TPDU (SN6::) What are the allowed receive values of the following parameters for a DIAG TPDU. Index Supported Parameters RD1 Code References Add. 1 Values Allowed Values Supported 8.5.3 b) Collision detection resolution, NC no longer needed, NC temporarily not accepted, NC not accepted on long-term No D.12.
PAGE 81
D.13 User Data in Issued TPDUs ISO 8073 for OSI/TS D.13 User Data in Issued TPDUs D.13.1 Class 1 (C1::) Index User Data References Status Support D1ICR Can user data of up to 32 octets be issued in a CR with preferred class 1 13.3.5 O Yes D1ICC Can user data of up to 32 octets be issued in a CC 13.4.5 O Yes D1IDR Can user data of up to 64 octets be issued in a DR 13.5.5 O Yes References Status Support D.13.
PAGE 82
D.15 Negotiation ISO 8073 for OSI/TS For classes 1 to 4, if it is possible to respond to a CR TPDU, then it shall be possible to receive the following. Index TPDU User Data References DRCR 32 octets of user data in a CR TPDU 13.3.5 D.15 Negotiation D.15.1 Class Negotiation—Initiator If it is possible to initiate a CR TPDU in a particular class, then the following holds. Index NC References The preferred class in the CR TPDU may contain any of the classes supported by the implementation 6.5.
PAGE 83
D.15.2 Class Negotiation—Responder Side ISO 8073 for OSI/TS D.15.2 Class Negotiation—Responder Side Allowed Responses Supported Responses 6.5.4 h) Table 3 0 or no response depending on classes supported Conf What classes can you respond with if CR proposes only class 1 6.5.4 h) Table 3 0, 1 or no response depending on classes supported Conf RC1a What classes can you respond with if CR proposes class 1 as preferred class and the alternative class parameter is present 6.5.
PAGE 84
D.15.3 TPDU Size Negotiation ISO 8073 for OSI/TS Allowed Values Supported Values 14.6 e) One of 128, 256, 512, 1024, 2048 Conf What is the largest value of the maximum TPDU size parameter which may be sent in a CC TPDU when class 0 is selected 14.6 e) One of 128, 256, 512, 1024, 2048 Conf T1S1 What is the largest value of the maximum TPDU size parameter in a CR TPDU with preferred class 1 14.
PAGE 85
D.15.5 Expedited Data Transport Service ISO 8073 for OSI/TS Is use of extended format selected in CC, when it has been proposed in CR, supported with preferred class: Index Extended Format References Status Support NEF4 Class 2 6.5.4 k) O Conf NEF5 Class 3 6.5.4 k) O Conf NEF6 Class 4 6.5.5 k) 6.5.5 j) O Conf D.15.
PAGE 86
D.15.8 Use of Network Receipt Confirmation (C1 AND T1F21::) ISO 8073 for OSI/TS D.15.8 Use of Network Receipt Confirmation (C1 AND T1F21::) Index Network Receipt Confirmation References Status Support UNRC1 Is use of network receipt confirmation proposed in CR 6.5.4 q) O No UNRC2 Is use of network receipt confirmation selected in CC when it has been proposed in CR 6.5.4 q) O No References Status Support D.15.
PAGE 87
D.16.3 Actions on Receipt of an Invalid or Undefined Parameter in a TPDU Other Than a CR TPDU ISO 8073 for OSI/TS Index Event References RR3 An invalid value in the class and option parameter shall be treated as a protocol error 13.2.3 RR4 On receipt of the additional option selection parameter, bits 8 to 5 and bits 4 to 1, if not meaningful for the proposed class, shall be ignored. 13.3.
PAGE 88
D.17 Timers and Protocol Parameters ISO 8073 for OSI/TS Index References Status Support OT4 Does IUT support optional timer TS1 when operating in class 3 6.5.4 O Conf OT5 Does IUT support optional timer TS2 when operating in class 0 6.7.5 O Conf OT6 Does IUT support optional timer TS2 when operating in class 1 6.7.5 O Conf OT7 Does IUT support optional timer TS2 when operating in class 2 6.7.5 O Conf OT8 Does IUT support optional timer TS2 when operating in class 3 6.7.
PAGE 89
6 ISO 9542 for OSI/TS The following information describes this PICS.
PAGE 90
ISO 9542 for OSI/TS This page intentionally left blank.
PAGE 91
PICS for the OSI ES-IS Routing Protocol Protocol, Annex A (Normative) ISO 9542 for OSI/TS PICS for the OSI ES-IS Routing Protocol Protocol, Annex A (Normative) A.
PAGE 92
PICS Proforma: IS0 9542(1988) — End System ISO 9542 for OSI/TS Answers to the questionnaire are to be provided in the rightmost column, either by simply marking an answer to indicate a restricted choice (such as Yes or No), or by entering a value or a set or range of values. Items of Exception Information are required by certain answers in the questionnaire and are indicated by an “__X__” cross-reference to be completed.
PAGE 93
PICS Proforma: IS0 9542(1988) — Intermediate System ISO 9542 for OSI/TS Item Are the Following PDUs Supported? Clauses Status Support ESH-s End System Hello 7.1, 7.5 M Yes ESH-r End System Hello 7.1, 7.5 CI:M Yes ISH-r Intermediate System Hello 7.1, 7.6 CI:M Yes RD-r Redirect 7.1, 7.7 RI:M Yes Item Are the Following PDU Fields Supported? Clauses Status Support FxPt ~~Fixed Part Fixed Part 7.2.1-7.2.7 7.2.1-7.2.~~
~~PAGE 94~~
PICS Proforma: IS0 9542(1988) — Intermediate System ISO 9542 for OSI/TS Item Protocol Function CI Clauses Status Support Is configuration information supported? O No RI Is redirection information supported? O No Item Are the Following Functions Supported? ErrP Clauses Status Support Protocol Error Proccssing 6.13 M No HCsV PDU Header Checksum Validation 6.12 M No HCsG PDU Header Checksum Generation 6.12 O No RpCf Report Configuration 6.2, 6.2.
~~PAGE 95~~
PICS Proforma: IS0 9542(1988) — Intermediate System ISO 9542 for OSI/TS Item Are the Following PDU Fields Supported? Clauses Status Support SNMk-s SNPA Mask 7.4.6 Rl:O No ESCT-s ~~Suggested ES Configuration Timer 7.4.7 Cl:O No ESCT-r (ignore) Suggested ES Configuration Timer 7.4.7 ISH-r:M No OOpt-r (ignore) Unsupported or unknown options 7.4.~~
~~PAGE 96~~
~~ISO 9542 for OSI/TS PICS Proforma: IS0 9542(1988) — Intermediate System Tandem OSI PICS Manual–135046 6 -8~~
~~PAGE 97~~
~~7 ISO 8473 for OSI/TS The following information describes this PICS.~~
~~PAGE 98~~
~~ISO 8473 for OSI/TS This page intentionally left blank.~~
~~PAGE 99~~
Introduction ISO 8473 for OSI/TS Introduction ISO 8473 is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This International Standard is positioned with respect to other related standards by the layers defined in ISO 7498. In particular, it is a protocol of the Network Layer.
~~PAGE 100~~
~~Conformance ISO 8473 for OSI/TS Provision of Functions for Conformance.~~
~~PAGE 101~~
~~8 ISO 8327, Version 1 for OSI/AS The following information describes this PICS.~~
~~PAGE 102~~
~~ISO 8327, Version 1 for OSI/AS This page intentionally left blank.~~
~~PAGE 103~~
ISO 8327, Version 1 for OSI/AS PICS for the OSI Session Protocol, Version 1 PICS for the OSI Session Protocol, Version 1 F.0 Introduction To evaluate the conformance of a particular implementation, it is necessary to have a description of the options and parameters which have been implemented. Such a description is called a Protocol Implementation Conformance Statement (PICS). This Annex contains the PICS proforma for the Session protocol as described by ISO 8327 and Addendum 2 of ISO 8327.
~~PAGE 104~~
~~F.1 Date of Statement ISO 8327, Version 1 for OSI/AS D Column The D column reflects the definitions in the International Standard.~~
~~PAGE 105~~
F.
~~PAGE 106~~
F.3 ISO 8327 Protocol Versions Implemented ISO 8327, Version 1 for OSI/AS F.3 ISO 8327 Protocol Versions Implemented 1 Which version of the Session Protocol is described in this PICS? Version 1. 2 What other versions of the Session Protocol does the implementation support? Version 2. F.4 Defect Report Numbers and Amendments Implemented 1 NIST Stable Agreements for OSI Protocols Version 3 Edition 1 December 1989.
~~PAGE 107~~
F.6.2 Protocol Mechanisms ISO 8327, Version 1 for OSI/AS Note. According to conformance rules in ISO 8327: • • • At least one of the functional units Duplex and Half Duplex shall be implemented. If the Capability Data Exchange functional unit is implemented, the Activity Management functional unit shall also be implemented. If the Exceptions functional unit is implemented, the Half-Duplex functional unit shall also be implemented. F.6.
~~PAGE 108~~
F.7 Elements of Procedures Related to SPDUs ISO 8327, Version 1 for OSI/AS F.7 Elements of Procedures Related to SPDUs F.7.0 Guidance for Completion Note on GT and PT SPDUs The use of GT and PT SPDUs in the following tables is implicitly dependent on the associated functional unit.
~~PAGE 109~~
~~F.7.1 Kernel Functional Unit Procedures ISO 8327, Version 1 for OSI/AS F.7.1.1.~~
~~PAGE 110~~
F.7.2 Negotiated Release Functional Unit Procedures ISO 8327, Version 1 for OSI/AS F.7.2 Negotiated Release Functional Unit Procedures Sending Receiving SPDU Procedure SS-Primitive D I SS-Primitive D I 1 Not Finished (NF) S-REL-rsp(–) o Y S-REL-cnf(–) m Y 2 Give Tokens (GT) S-GT-req o Y S-GT-ind o Y 3 Please Tokens (PT) S-PT-req o Y S-PT-ind m Y F.7.
~~PAGE 111~~
F.7.8 Minor Synchronize Functional Unit Procedures ISO 8327, Version 1 for OSI/AS F.7.8 Minor Synchronize Functional Unit Procedures Sending Receiving SPDU Procedure SS-Primitive D I SS-Primitive D I 1 Minor Sync Point (MIP) S-SMIN-req o Y S-SMIN-ind o Y 2 Minor Sync Ack (MIA) S-SMIN-rsp o Y S-SMIN-cnf c5 3 Give Tokens (GT) S-GT-req o Y S-GT-ind o Y 4 Please Tokens (PT) S-PT-req o Y S-PT-ind m Y c2: c3: c4: c5: If F.6.2/1 then o else — If F.6.
~~PAGE 112~~
~~F.7.12 Activity Management Functional Unit Procedures ISO 8327, Version 1 for OSI/AS F.7.~~
~~PAGE 113~~
~~F.8.1 Connect (CN) SPDU ISO 8327, Version 1 for OSI/AS F.8.1 Connect (CN) SPDU (Ref. ISO 8327, Clause 8.3.~~
~~PAGE 114~~
F.8.3 Connect Data Overflow (CDO) SPDU ISO 8327, Version 1 for OSI/AS F.8.3 Connect Data Overflow (CDO) SPDU (Ref. ISO 8327, Clause 8.3.1ter, Table 11ter) (This clause is not applicable to the questionnaire for protocol version 1) Sending Single Items D I 1 PGI “User Data” (see N1) o 2 Enclosure Item c20 c18: c19: c20: c21: If F.3/1 = 1 then — else o If F.3/1 = 1 then — else m If F.3/1 > 1 and F.6.2/7 then o else — If F.3/1 > 1 and F.6.
~~PAGE 115~~
F.8.5 Refuse (RF) SPDU ISO 8327, Version 1 for OSI/AS Sending Receiving Single Items D I Value D I Value 17 PGI “User Data” (see N1) o Y 512 m Y 512 18 Enclosure Item c22 — c23 — c22: If F.3/1 > 1 and F.6.2/7 then o else — c23: If F.3/1 > 1 and F.6.2/8 then m else — F.8.5 Refuse (RF) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 116~~
F.8.7 Disconnect (DN) SPDU ISO 8327, Version 1 for OSI/AS F.8.7 Disconnect (DN) SPDU (Ref. ISO 8327, Clause 8.3.5, Table 15) Sending Receiving Single Items D I Value D I Value 1 PGI “User Data” (see N1) o Y 512 m Y 512 2 Enclosure Item c24 — c25 — F.8.8 Not Finished (NF) SPDU (Ref. ISO 8327, Clause 8.3.6, Table 16) Sending Receiving Single Items D I Value D I Value 1 PGI “User Data” (see N1) o Y 512 m Y 512 2 Enclosure Item c24 — c25 — F.8.
~~PAGE 117~~
F.8.11 Data Transfer (DT) SPDU ISO 8327, Version 1 for OSI/AS F.8.11 Data Transfer (DT) SPDU (Ref. ISO 8327, Clause 8.3.9, Table 18) Sending Receiving Single Items D I Value D I Value 1 User Information Field (see N1) o Y 2MB m Y 2MB 2 Enclosure Item c26 — c27 — F.8.12 Expedited Data (EX) SPDU (Ref. ISO 8327, Clause 8.3.10, Table 19) Sending 1 Single Items D I User Information Field (see N1) o — Receiving Value D I m — Value F.8.13 Typed Data (TD) SPDU (Ref.
~~PAGE 118~~
F.8.16 Give Tokens (GT) SPDU ISO 8327, Version 1 for OSI/AS F.8.16 Give Tokens (GT) SPDU (Ref. ISO 8327, Clause 8.3.14, Table 23) Sending Single Items D I 1 Token Item o 2 PGI “User Data” (see N1) 3 Enclosure Item Receiving Value D I Y m Y c30 — c31 — c28 — c29 — Value F.8.17 Please Tokens (PT) SPDU (Ref. ISO 8327, Clause 8.3.15, Table 24) Sending Single Items D I 1 Token Item o Y 2 PGI “User Data” (see N1) o Y 3 Enclosure Item c28 — c28: c29: c30: c31: If F.
~~PAGE 119~~
F.8.20 Major Sync Point (MAP) SPDU ISO 8327, Version 1 for OSI/AS F.8.20 Major Sync Point (MAP) SPDU (Ref. ISO 8327, Clause 8.3.20, Table 27) Sending Single Items D I 1 Sync Type Item m 2 Serial Number 3 PGI “User Data” (see N1) 4 Enclosure Item Receiving Value D I Y m Y m Y m Y o Y m Y c32 — c33 — 512 Value 512 c32: If F.3/1 > 1 and F.6.2/7 then o else — c33: If F.3/1 > 1 and F.6.2/8 then m else — F.8.21 Major Sync Ack (MAA) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 120~~
F.8.24 Prepare (PR) SPDU ISO 8327, Version 1 for OSI/AS Sending Receiving Single Items D I Value D I Value 3 PGI “User Data” (see N1) o Y 512 m Y 512 4 Enclosure Item c32 — c33 — c32: If F.3/1 > 1 and F.6.2/7 then o else — c33: If F.3/1 > 1 and F.6.2/8 then m else — F.8.24 Prepare (PR) SPDU (Ref. ISO 8327, Clause 8.3.24, Table 31) Sending 1 Single Items D I Prepare Type m Y Receiving Value D I Value m Y F.8.25 Exception Report (ER) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 121~~
F.8.29 Activity Start (AS) SPDU ISO 8327, Version 1 for OSI/AS F.8.29 Activity Start (AS) SPDU (Ref. ISO 8327, Clause 8.3.27, Table 34) Sending Single Items D I 1 Activity Identifier m Y 2 PGI “User Data” (see N1) o Y 3 Enclosure Item c32 — Receiving Value 512 D I m Y m Y c33 — Value 512 F.8.30 Activity Resume (AR) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 122~~
F.8.32 Activity Interrupt Ack (AIA) SPDU ISO 8327, Version 1 for OSI/AS F.8.32 Activity Interrupt Ack (AIA) SPDU (Ref. ISO 8327, Clause 8.3.30) Sending Single Items D 1 PGI “User Data” (see N1) c35 2 Enclosure Item c37 I Receiving Value D I Value c36 — c38 — F.8.33 Activity Discard (AD) SPDU (Ref. ISO 8327, Clause 8.3.31, Table 37) Sending Single Items D I 1 Reason Code o Y 2 PGI “User Data” (see N1) c35 3 Enclosure Item c37 c35: c36: c37: c38: If F.
~~PAGE 123~~
F.8.36 Activity End Ack (AEA) SPDU ISO 8327, Version 1 for OSI/AS F.8.36 Activity End Ack (AEA) SPDU (Ref. ISO 8327, Clause 8.3.32, Table 28) Sending Single Items D I 1 Serial Number m Y 2 PGI “User Data” (see N1) o Y 3 Enclosure Item c37 — c35: c36: c37: c38: If F.3/1 > 1 then o else — If F.3/1 > 1 then m else — If F.3/1 > 1 and F.6.2/7 then o else — If F.3/1 > 1 and F.6.
~~PAGE 124~~
~~F.8.~~
~~PAGE 125~~
~~9 ISO 8327, Version 2 for OSI/AS The following information describes this PICS.~~
~~PAGE 126~~
~~ISO 8327, Version 2 for OSI/AS This page intentionally left blank.~~
~~PAGE 127~~
ISO 8327, Version 2 for OSI/AS PICS for the OSI Session Protocol, Version 2 PICS for the OSI Session Protocol, Version 2 F.0 Introduction To evaluate the conformance of a particular implementation, it is necessary to have a description of the options and parameters which have been implemented. Such a description is called a Protocol Implementation Conformance Statement (PICS). This Annex contains the PICS proforma for the Session protocol as described by ISO 8327 and Addendum 2 of ISO 8327.
~~PAGE 128~~
~~F.1 Date of Statement ISO 8327, Version 2 for OSI/AS D Column The D column reflects the definitions in the International Standard.~~
~~PAGE 129~~
F.3 ISO 8327 Protocol Versions Implemented ISO 8327, Version 2 for OSI/AS 1 Organization Contact name(s) Address Telephone FAX Implementation Name,Version Operating System,Version Hardware F.3 ISO 8327 Protocol Versions Implemented 1 Which version of the Session Protocol is described in this PICS? Version 2. 2 What other versions of the Session Protocol does the implementation support? Version 1. F.
~~PAGE 130~~
~~F.6 Supported Functional Units, Protocol Mechanisms and Initial Role Capabilities ISO 8327, Version 2 for OSI/AS F.6 Supported Functional Units, Protocol Mechanisms and Initial Role Capabilities F.6.~~
~~PAGE 131~~
F.6.3 Initial Role Capabilities ISO 8327, Version 2 for OSI/AS F.6.3 Initial Role Capabilities Capability D I 1 Initiator o Y 2 Responder o Y Note. A conforming implementation must support at least one of the above capabilities. F.7 Elements of Procedures Related to SPDUs F.7.0 Guidance for Completion Note on GT and PT SPDUs The use of GT and PT SPDUs in the following tables is implicitly dependent on the associated functional unit.
~~PAGE 132~~
~~F.7.1 Kernel Functional Unit Procedures ISO 8327, Version 2 for OSI/AS F.7.1 Kernel Functional Unit Procedures F.7.1.1 Sending F.7.1.1.~~
~~PAGE 133~~
F.7.2 Negotiated Release Functional Unit Procedures ISO 8327, Version 2 for OSI/AS F.7.1.2.2 Receiving by Responder SPDU Procedure D I SS-Primitive 1 Connect (CN) m Y S-CON-ind 2 Connect Data Overflow (CDO) c1 N S-CON-ind 3 Finish (FN) m Y S-REL-ind 4 Disconnect (DN) o Y S-REL-cnf 5 Abort (AB) m Y S-U-AB-ind 6 Abort Accept (AA) o Y — 7 Data Transfer (DT) m Y S-DATA-ind F.7.
~~PAGE 134~~
F.7.7 Capability Data Functional Unit Procedures ISO 8327, Version 2 for OSI/AS F.7.7 Capability Data Functional Unit Procedures Sending SPDU Procedure Receiving SS-Primitive D I SS-Primitive D I 1 Capability Data (CD) S-CAP-req o Y S-CAP-ind m Y 2 Capability Data Ack (CDA) S-CAP-rsp m Y S-CAP-cnf c4 Y F.7.
~~PAGE 135~~
F.7.11 Exceptions Functional Unit Procedures ISO 8327, Version 2 for OSI/AS F.7.11 Exceptions Functional Unit Procedures Sending SPDU Procedure 1 Exception Report (ER) 2 Exception Data (ED) Receiving SS-Primitive D I SS-Primitive D I — o N — m Y S-U-EXC-req o Y S-U-EXC-ind m Y c6: If F.7.9/1(a) then m else c7: If F.6.2/1 then o else c8: If F.6.2/1 then m else c9: If F.7.10/1(a) then m else c10: If F.6.2/1 then o else c11: If F.6.2/1 then m else - F.7.
~~PAGE 136~~
F.8 Supported SPDU-Parameters ISO 8327, Version 2 for OSI/AS F.8 Supported SPDU-Parameters F.8.0 Guidance for Completion Note on D Column A “parameter sending” item is marked as not-mandatatory (“o”) if this feature: • • either is attached to a not-mandatory protocol mechanism or reflects free SS-user choices Note (N1) : User-Data-Like Parameters The value to be completed is the maximum length of the SS-user data parameter for the corresponding SS-primitive given in clause F.8.
~~PAGE 137~~
F.8.2 Overflow Accept (OA) SPDU ISO 8327, Version 2 for OSI/AS Sending Single Items D I 13 Session User Requirements o 14 Calling Session Selector 15 Receiving Value D I Y m Y o Y m Y Called Session Selector o Y m Y 16 PGI “User Data” (see N1) o Y m Y 17 Data Overflow c18 N c19 N 18 PGI “Extended User Data” (see N1) c18 512 10240 c19 Value 512 10240 F.8.2 Overflow Accept (OA) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 138~~
~~F.8.~~
~~PAGE 139~~
F.8.6 Finish (FN) SPDU ISO 8327, Version 2 for OSI/AS Sending Single Items D I 4 Transport Disconnect o 5 Session User Requirements 6 Receiving Value D I N m Y o Y m Y Version Number o Y m Y 7 Reason Code (see N1) o Y m Y 8 Enclosure Item c22 — c23 — 10240 Value 10240 F.8.6 Finish (FN) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 140~~
F.8.9 Abort (AB) SPDU ISO 8327, Version 2 for OSI/AS F.8.9 Abort (AB) SPDU (Ref. ISO 8327, Clause 8.3.7, Table 17) Sending Single Items D I 1 Transport Disconnect m Y 2 Reflect Parameters Values o Y 3 PGI “User Data” (see N1) o Y 4 Enclosure Item c24 — Receiving Value D I m Y NIST (See Tandem Note) m Y 10240 m Y c25 — Value 10240 c24: If F.3/1 > 1 and F.6.2/7 then o else c25: If F.3/1 > 1 and F.6.
~~PAGE 141~~
F.8.14 Capability Data (CD) SPDU ISO 8327, Version 2 for OSI/AS F.8.14 Capability Data (CD) SPDU (Ref. ISO 8327, Clause 8.3.12, Table 21) Sending Receiving Single Items D I Value D I Value 1 PGI “User Data” (see N1) o Y 10240 m Y 10240 2 Enclosure Item c28 — c29 — c26: c27: c28: c29: If F.3/1 > 1 and F.6.2/7 then o else If F.3/1 > 1 and F.6.2/8 then m else If F.3/1 > 1 and F.6.2/7 then o else If F.3/1 > 1 and F.6.2/8 then m else - F.8.15 Capability Data Ack (CDA) SPDU (Ref.
~~PAGE 142~~
F.8.18 Minor Sync Point (MIP) SPDU ISO 8327, Version 2 for OSI/AS F.8.18 Minor Sync Point (MIP) SPDU (Ref. ISO 8327, Clause 8.3.18, Table 25) Sending Single Items D I 1 Sync Type Item o 2 Serial Number 3 PGI “User Data” (see N1) 4 Enclosure Item Receiving Value D I Y m Y m Y m Y o Y m Y c33 — 10240 c32 Value 10240 F.8.19 Minor Sync Ack (MIA) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 143~~
F.8.22 Resynchronize (RS) SPDU ISO 8327, Version 2 for OSI/AS F.8.22 Resynchronize (RS) SPDU (Ref. ISO 8327, Clause 8.3.22, Table 29) Sending Single Items D I 1 Token Setting Item o 2 Resync Type 3 Receiving Value D I Y m Y m Y m Y Serial Number m Y m Y 4 PGI “User Data” (see N1) o Y m Y 5 Enclosure Item c32 — c33 — 10240 Value 10240 F.8.23 Resynchronize Ack (RA) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 144~~
F.8.26 Exception Data (ED) SPDU ISO 8327, Version 2 for OSI/AS F.8.26 Exception Data (ED) SPDU (Ref. ISO 8327, Clause 8.3.26, Table 33) Sending Single Items D I 1 Reason Code m Y 2 PGI “User Data” (see N1) o Y 3 Enclosure Item c32 — Receiving Value 10240 D I m Y m Y c33 — Value 10240 F.8.27 Give Tokens Confirm (GTC) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 145~~
F.8.31 Activity Interrupt (AI) SPDU ISO 8327, Version 2 for OSI/AS Sending PGI “Linking Information” D I 4 Additional Reference Information o 5 Old Activity Identifier 6 Serial Number Receiving Value D I Y m Y m Y m Y m Y m Y Sending Single Items D I 7 New Activity Identified m Y 8 PGI “User Data” (see N1) o Y 9 Enclosure Item c32 — Value Receiving Value 10240 D I m Y m Y c33 — Value 10240 c32: If F.3/1 > 1 and F.6.2/7 then o else c33: If F.
~~PAGE 146~~
F.8.34 Activity Discard Ack (ADA) SPDU ISO 8327, Version 2 for OSI/AS Sending Single Items Receiving D I Value D I Value 10240 c36 Y 10240 c38 — 2 PGI “User Data” (see N1) c35 Y 3 Enclosure Item c37 — c35: c36: c37: c38: If F.3/1 > 1 then o else If F.3/1 > 1 then m else If F.3/1 > 1 and F.6.2/7 then o else If F.3/1 > 1 and F.6.2/8 then m else - Tandem Note. The proforma does not contain a note numbered c34. F.8.34 Activity Discard Ack (ADA) SPDU (Ref. ISO 8327, Clause 8.3.
~~PAGE 147~~
~~10 ISO 8823 for OSI/AS The following information describes this PICS.~~
~~PAGE 148~~
~~ISO 8823 for OSI/AS This page intentionally left blank.~~
~~PAGE 149~~
PICS for the OSI Presentation Protocol ISO 8823 for OSI/AS PICS for the OSI Presentation Protocol B.1 Introduction To evaluate the conformance of a particular implementation, it is necessary to have a description of the capabilities and options which have been implemented. Such a description is called a Protocol Implementation Conformance Statement (PICS). This Annex contains the PICS proforma for the Presentation protocol.
~~PAGE 150~~
B.2.4 Implementation Overview ISO 8823 for OSI/AS B.2.4 Implementation Overview Ref Question Response 1 Implementation name OSI/AS 2 Version C21 3 Machine name Tandem NonStop systems 4 Machine version 5 Operating system name NonStop Kernel 6 Operating system version C20 and C30 7 Special configuration requirements 8 Other information B.2.5 Claimed Compliance to Standards B.2.5.
~~PAGE 151~~
B.2.5.3 Amendments Implemented ISO 8823 for OSI/AS B.2.5.3 Amendments Implemented Ref Number Description 1 2 3 4 B.2.5.4 Conformance to Profiles Ref Question Response 1 Profile name NIST Protocol Agreements 2 Options implemented Yes 3 Are all supported features implemented? 4 Profile name 5 Options implemented 6 Are all supported features implemented? B.2.
~~PAGE 152~~
B.3 Supported Functional Units ISO 8823 for OSI/AS B.3 Supported Functional Units B.3.1 Guidance for Completion This section defines the functional units supported for which conformance is claimed. The D column reflects the definitions and specifications in ISO 8823.
~~PAGE 153~~
B.3.3 Protocol Mechanisms ISO 8823 for OSI/AS Ref Functional Unit Code D U I 12 Resynchronize (S) RESYN o I 13 Exceptions (S) EXCEP o I 14 Activity Management (S) ACT o I Mode Code D 1 X.410 (1984) 2 normal B.3.3 Protocol Mechanisms Ref U I o R 1 o R 2 Note. If the only protocol mechanism implemented is X.410, no further questions in the PICS proforma shall be answered. B.3.4 Functional Unit Negotiation In accordance with the functional units chosen in section 3.
~~PAGE 154~~
B.4.2 Kernel Functional Unit ISO 8823 for OSI/AS The U column is reserved for future use. The I column describes the actual capabilities of the implementation and shall be completed by the supplier using a symbol chosen from the following list: Symbol Meaning V Associated with FU and supported N Associated with FU and NOT supported I Not associated with FU and supported — Not associated with FU and NOT supported Note.
~~PAGE 155~~
B.4.5 Session Negotiated Release Functional Unit ISO 8823 for OSI/AS B.4.5 Session Negotiated Release Functional Unit Sending Ref PPDU or Session primitive D 1 S-REL-rsp(-)/cnf(-) 2 3 U Receiving I D U I o V m V S-GT-req/ind o I m I S-PT-req/ind o I m I B.4.6 Session Half Duplex Functional Unit Sending Ref PPDU or Session primitive D 1 S-GT-req/ind 2 S-PT-req/ind U Receiving I D U I o I m I o I m I B.4.
~~PAGE 156~~
B.4.11 Minor Synchronize Functional Unit ISO 8823 for OSI/AS B.4.11 Minor Synchronize Functional Unit Sending Ref PPDU or Session primitive D 1 S-SYNm-req/ind 2 U Receiving I D U I o V m V S-SYNm-req/ind o V m V 3 S-GT-req/ind o I m I 4 S-PT-req/ind o I m I B.4.
~~PAGE 157~~
B.4.15 Exceptions Functional Unit ISO 8823 for OSI/AS B.4.15 Exceptions Functional Unit Sending Ref PPDU or Session primitive D 1 S-UER-req/ind o 2 S-PER-ind — U — Receiving I D U I V m V — m V B.4.16 Initiator/Responder Capabilities This section is used to declare if the system is capable of initiating a presentation connection (by sending a CP PPDU) or responding to a CP PPDU (by sending a CPA PPDU or a CPR PPDU) or both.
~~PAGE 158~~
B.5.1 Guidance for Completion ISO 8823 for OSI/AS The I column describes the actual capabilities of the implementation and shall be completed by the supplier using a symbol chosen from the following list: Symbol Meaning X Not supported I Supported — Not applicable The supplier shall use the “Value” column to indicate restrictions by the imposed implementation on parameter value and length.
~~PAGE 159~~
~~B.5.2 CP PPDU ISO 8823 for OSI/AS B.5.2 CP PPDU B.5.2.~~
~~PAGE 160~~
~~B.5.~~
~~PAGE 161~~
~~B.5.3 CPA PPDU ISO 8823 for OSI/AS B.5.3 CPA PPDU B.5.3.~~
~~PAGE 162~~
~~B.5.4 CPR PPDU ISO 8823 for OSI/AS B.5.4.~~
~~PAGE 163~~
B.5.5 ARU PPDU ISO 8823 for OSI/AS B.5.5 ARU PPDU B.5.5.1 Sending Ref Parameter D 1 Presentation context identifier list 2 User data U I Value o I see “Other Information” o I session limit I Value B.5.5.2 Receiving Ref Parameter D U 1 Presentation context identifier list m I see “Other Information” 2 User data m I session limit I Value B.5.6 ARP PPDU B.5.6.1 Sending Ref Parameter D U 1 Provider reason o I 2 Event identifier o I B.5.6.
~~PAGE 164~~
B.5.8 ACA PPDU ISO 8823 for OSI/AS B.5.8 ACA PPDU B.5.8.1 Sending Ref Parameter D U I 1 Presentation context addition list o — 2 Presentation context deletion list o — 3 User data o — Value B.5.8.2 Receiving Ref Parameter D U I 1 Presentation context addition list m — 2 Presentation context deletion list m — 3 User data m — Value B.5.9 TD PPDU B.5.9.1 Sending Ref Parameter D 1 User data o U I Value I ~2 MB I Value I ~2 MB I Value I ~2 MB B.5.9.
~~PAGE 165~~
B.5.11 TE PPDU ISO 8823 for OSI/AS B.5.11 TE PPDU B.5.11.1 Sending Ref Parameter D 1 User data o U I Value — B.5.11.2 Receiving Ref Parameter D 1 User data m U I Value — B.5.12 TC PPDU B.5.12.1 Sending Ref Parameter D 1 User data m U I Value I session limit B.5.12.2 Receiving Ref Parameter D 1 User data m U I Value I session limit B.5.13 TCC PPDU B.5.13.1 Sending Ref Parameter D 1 User data o U I Value I session limit B.5.13.
~~PAGE 166~~
B.5.14 RS PPDU ISO 8823 for OSI/AS B.5.14 RS PPDU B.5.14.1 Sending Ref Parameter D U I Value 1 Resynchronize type o I 2 Synchronization point serial number o I 3 Tokens o I 4 Presentation context identifier list o — 5 User data o I session limit I Value B.5.14.2 Receiving Ref Parameter D U 1 Resynchronize type m I 2 Synchronization point serial number m I 3 Tokens m I 4 Presentation context identifier list m — 5 User data m I session limit B.5.
~~PAGE 167~~
B.5.16 Session Service Primitives Not Carrying PPDUs ISO 8823 for OSI/AS B.5.16 Session Service Primitives Not Carrying PPDUs B.5.16.1 Guidance for Completion The only Session parameter actively treated by the presentation provider is User Data. This is implied against each primitive listed below. B.5.16.
~~PAGE 168~~
B.5.17 Other Information ISO 8823 for OSI/AS B.5.17 Other Information Ref Response 1 Context identifiers may be integers from 0 to 32767. 2 Object identifiers for Abstract syntaxes and Transfer syntax may be up to 16 identifiers long. 3 Maximum number of presentation contexts is 16. B.6 Support of Syntaxes B.6.1 Transfer Syntaxes Supported This section shall be used to indicate which transfer syntaxes the implementation supports.
~~PAGE 169~~
~~B.6.3 PDU Encoding Restrictions ISO 8823 for OSI/AS B.6.3 PDU Encoding Restrictions This section is used to indicate whether any encoding restrictions exist for sending the Presentation PCI of PPDUs.~~
~~PAGE 170~~
~~B.6.~~
~~PAGE 171~~
~~11 ISO 8650 for OSI/AS The following information describes this PICS.~~
~~PAGE 172~~
~~ISO 8650 for OSI/AS This page intentionally left blank.~~
~~PAGE 173~~
PICS for the OSI ACSE Protocol ISO 8650 for OSI/AS PICS for the OSI ACSE Protocol B.1 Introduction To evaluate the conformance of a particular implementation, it is necessary to have a description of the capabilities and options which have been implemented. Such a description is called a Protocol Implementation Conformance Statement (PICS). This Annex contains the PICS proforma for the ACSE protocol. The proforma has been prepared in compliance with the guidelines given in ISO 9646-2.
~~PAGE 174~~
B.3 Implementation Details ISO 8650 for OSI/AS B.3 Implementation Details Specify the information necessary to uniquely identify the implementation and the systems in which it may reside. This may include details of: 1. Supplier, implementation name, operating system, suitable hardware; 2. System supplier and/or client of the test laboratory that is to test the implementation; 3. Information on whom to contact if there are queries concerning the content of the PICS; 4.
~~PAGE 175~~
B.5 ISO 8650 Addenda Implemented ISO 8650 for OSI/AS B.5 ISO 8650 Addenda Implemented 1 B.6 Defect Report Numbers and Amendments Implemented 1 Amendments: ISO 8650/AM1 B.7 Global Statement of Conformance 1 Are all mandatory features implemented? YES. Note. If a positive response is not given to this box then the implementation does not conform to ISO 8650. B.8 Supported Functions Protocol Mechanism D I 1 Normal mode o Y 2 X.
~~PAGE 176~~
B.9 Initiator/Responder Capability ISO 8650 for OSI/AS B.9 Initiator/Responder Capability This clause identifies the initiator/responder capabilities of an implementation. The supplier shall indicate the capabilities supported for which conformance is claimed. Capability D I 1 Association initiator o Y 2 Association responder o Y Note. One of these capabilities is mandatory for a system claiming conformance to this International Standard. B.
~~PAGE 177~~
~~B.11.1 A-Associated-Request APDU (AARQ) ISO 8650 for OSI/AS B.11.~~
~~PAGE 178~~
~~B.11.2 A-Associated-Response APDU (AARE) ISO 8650 for OSI/AS B.11.~~
~~PAGE 179~~
B.11.4 A-Release-Response APDU (RLRE) ISO 8650 for OSI/AS B.11.4 A-Release-Response APDU (RLRE) Sending Parameter D I 1 Reason o Y 2 User information o Y Receiving Parameter D I 3 Reason m Y 4 User information m Y Sending Parameter D I 1 Abort source o Y 2 User information o Y Receiving Parameter D I 3 Abort source m Y 4 User information m Y Value Value B.11.
~~PAGE 180~~
~~B.11.~~
~~PAGE 181~~
~~12 ISO 8571 for FTAM The following information describes this PICS.~~
~~PAGE 182~~
~~ISO 8571 for FTAM This page intentionally left blank.~~
~~PAGE 183~~
PICS for OSI/FTAM ISO 8571 for FTAM PICS for OSI/FTAM The following table contains a key to the notations used in this PICS as stated in ISO-8571-5. Symbol Meaning I Level of implementation of each feature in the role of initiator. Where this column is preprinted with dashes, representing a non-applicable entry, no entry shall be inserted in the “I” column. R Level of implementation of each feature in the role of responder.
~~PAGE 184~~
Section 2 General ISO 8571 Detail ISO 8571 for FTAM 5. Profiles to which conformance is claimed (see note 2) Note. 1. The System Conformance Statement is defined in ISO 9646. It relates to a PICS covering more than one layer of the reference model. 2. The list of profile names is not necessarily a fully inclusive set of those covered by this implementation.
~~PAGE 185~~
A.6 Global Statement of Conformance ISO 8571 for FTAM A.6 Global Statement of Conformance 1 Does the implementation referred to by this PICS conform to ISO 8571? Yes A.7 Initiator/Responder Capability State which combination of roles are, and which are not, implemented and specified in this PICS. Roles D I R 1 Sender o Yes Yes 2 Receiver o Yes Yes A.8 Application Context Name Details List the names of the Application Context Names recognized or provided by this implementation.
~~PAGE 186~~
~~Section 3 Syntax Detail ISO 8571 for FTAM Section 3 Syntax Detail A.~~
~~PAGE 187~~
A.10 Virtual Filestore ISO 8571 for FTAM A.10.2 Attributes A.10.2.1 Attribute Groups Implemented State which file attribute groups are implemented and which are not implemented. The level of support within each group shall be stated in 10.2.2. Attribute Group Name D I R 1 Kernel m Yes Yes 2 Storage o Yes Yes 3 Security o Yes Yes 4 Private o No No A.10.2.2 Attribute Values Complete the tables for all attribute groups, shown as supported in clause 10.2.
~~PAGE 188~~
A.
~~PAGE 189~~
A.10 Virtual Filestore ISO 8571 for FTAM 28 Private Group (Responder) D R full R partial Private use p No No Range of Values Not applicable Note. If the private use attribute is implemented, then the details of the values and their semantics should be stated in an appendix. A.10.2.3 Filename Detail Specify what restrictions, including filename conventions, if any, apply to the filename.
~~PAGE 190~~
A.10 Virtual Filestore ISO 8571 for FTAM A.10.3 File Structures A.10.3.1 Constraint Sets If the Contents type “Abstract Syntax/Constraint Set” is implemented, state which constraint sets are, and which are not, implemented. Where applicable, an integer figure shall be supplied to indicate the maximum depth of hierarchy that the implementation supports. Note.
~~PAGE 191~~
~~A.10 Virtual Filestore ISO 8571 for FTAM A.10.3.2.2 File Actions State whether the action is, or is not, supported within a file open regime, for the constraint sets implemented in the responder role.~~
~~PAGE 192~~
Section 5 File Protocol Detail ISO 8571 for FTAM State whether there are any circumstances under which modifications to the file contents or the values of the file attributes by FTAM protocol exchanges will not subsequently be available for use. State details here or in an appendix. Changes caused by local file store actions may modify the contents and attributes of a file such that the file is not accessible in the same way as before. A.10.5 Override State the implemented filestore capability.
~~PAGE 193~~
A.11 File Protocol ISO 8571 for FTAM Functional Units Kernel Read Writ e Access LFM EFM Grouping PDUs Clause F-CREATE A.11.8 m F-DELETE A.11.9 m F-READATTRIB A.11.10 m F-CHANGEATTRIB A.11.11 F-OPEN A.11.12 m m F-CLOSE A.11.13 m m F-BEGINGROUP A.11.14 m F-ENDGROUP A.11.15 m F-RECOVER A.11.16 F-LOCATE A.11.17 m F-ERASE A.11.18 m F-READ A.11.19 F-WRITE A.11.20 F-DATA-END A.11.21 m m FTRANSFEREND A.11.22 m m F-CANCEL A.11.23 m m F-RESTART A.11.
~~PAGE 194~~
A.11 File Protocol ISO 8571 for FTAM A.11.2 FTAM Regime Establishment F-INITIALIZE PDU Field Name D I D R Range of Values or Reference 1 F-INITIALIZE PDU m Yes m Yes 2 State result — — m Yes All values defined in ISO 8571 3 Action result — — m Yes All values defined in ISO 8571 4 Protocol version m Yes m Yes See Section 2 5 Implementation information o No o No See A.12.
~~PAGE 195~~
A.11 File Protocol ISO 8571 for FTAM A.11.4 FTAM Regime Termination (Abrupt) by Service User F-U-ABORT PDU Field Name D I R Range of Values or Reference 1 F-U-ABORT PDU m Yes Yes 2 Action Result m Yes Yes All values defined in ISO 8571 3 Diagnostic o Yes Yes See A.12.6 A.11.
~~PAGE 196~~
A.11 File Protocol ISO 8571 for FTAM A.11.8 File Creation F-CREATE PDU Field Name D I D R Range of Values or Reference 1 F-CREATE PDU c Yes c Yes See A.11 2 State result — — m Yes All values defined in ISO 8571 3 Action result — — m Yes All values defined in ISO 8571 4 Override m Yes — — See A.12.15 5 Initial attributes m Yes m Yes See A.10.2 6 Create password o Yes — — See A.12.11 7 Requested access m Yes — — See A.12.
~~PAGE 197~~
A.11 File Protocol ISO 8571 for FTAM F-CHANGE-ATTRIB PDU Field Name D I D R 2 Action Result — — m Yes All values defined in ISO 8571 3 Attributes m Yes o Yes See A.10.2 4 Diagnostic — — o Yes See A.12.
~~PAGE 198~~
A.11 File Protocol ISO 8571 for FTAM A.11.12 File Open F-OPEN PDU Field Name D I D R Range of Values or Reference 1 F-OPEN PDU c Yes c Yes See A.11 2 State result — — m Yes All values defined in ISO 8571 3 Action result — — m Yes All values defined in ISO 8571 4 Processing mode m Yes — — See A.12.17 5 Contents type m Yes m Yes See A.12.7.2 6 Concurrency control o No o No See A.12.13 7 Shared ASE information o No o No See A.12.
~~PAGE 199~~
A.11 File Protocol ISO 8571 for FTAM A.11.14 Beginning of Grouping F-BEGIN-GROUP PDU Field Name D I D R Range of Values or Reference 1 F-BEGIN-GROUP PDU c Yes c Yes See A.11 2 Threshold m Yes — — 1..4 Range of Values or Reference A.11.15 End of Grouping 1 F-END-GROUP PDU Field Name D I D R F-END-GROUP PDU c Yes c Yes See A.11 The F-END-GROUP PDU carries no fields.
~~PAGE 200~~
A.11 File Protocol ISO 8571 for FTAM A.11.16 Regime Recovery Tandem Implementation Note. The regime recovery feature is not implemented by Tandem FTAM. F-RECOVER PDU Field Name D I D R Range of Values or Reference 1 F-RECOVER PDU c No c No See A.
~~PAGE 201~~
A.11 File Protocol ISO 8571 for FTAM A.11.18 Erase File Access Data Unit F-ERASE PDU Field Name D I D R Range of Values or Reference 1 F-ERASE PDU c Yes c Yes See A.11 2 Action result — — m Yes All values defined in ISO 8571 3 FADU identity m Yes — — All values defined in ISO 8571 except “single name” and “name-list” values 4 Diagnostic — — o Yes See A.12.6 F-READ PDU Field Name D I 1 F-READ PDU c Yes See A.
~~PAGE 202~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.11.23 Cancel Data Transfer F-CANCEL PDU Field Name D I R Range of Values or Reference 1 F-CANCEL PDU c Yes Yes See A.11 2 Action result m Yes Yes All values defined in ISO 8571 3 Shared ASE information o No No See A.12.9 4 Diagnostic o Yes Yes See A.12.6 A.11.23.1 F-CANCEL Mapping If the following two conditions are met, ISO 8571 requires that F-CANCEL maps to P-RESYNC: 1.
~~PAGE 203~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.2 Access Control Detail This clause shall be completed if implementation of both the following is claimed: 1. the security attribute group 2. full support of the access control attribute Access Control Element Terms D I R Range of Values 1 Action list m Yes Yes See A.12.3.1 and A.12.3.2 2 Concurrency access o Yes No See A.12.3.3 3 Identity o Yes No See A.12.3.4 4 Passwords o Yes No See A.12.3.
~~PAGE 204~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM Note. 1. Further combinations, including reference numbers, should be detailed in an appendix. Instead of adding an appendix, the table has been extended. 2. Supports file types 1, 2, and 3. 3. Supports file types 1 and 3. 4. Supports file type 2. A.12.3.
~~PAGE 205~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.3.3 Concurrency Access Term If the concurrency access term is implemented in the access control element, complete details of the concurrency control available with each action. Tandem Implementation Note. The concurrency access term is not implemented by Tandem FTAM.
~~PAGE 206~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.3.6 Responder Access Passwords If the access passwords term of the access control element is implemented, the following table shall be completed for the responder role.
~~PAGE 207~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM Combinations 5 Identity 6 Password 7 Location D R o No o No o No Note. Implementation of access control without any of the above combinations is valid. A.12.4 Service Class Field Detail D I R 1 Transfer class o Yes Yes 2 Access class o Yes Yes 3 Management class o Yes Yes 4 Transfer and management class o Yes Yes 5 Unconstrained class o No No Note.
~~PAGE 208~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.6 Diagnostic Field Detail This clause shall be completed if any diagnostic field is indicated as implemented. The following tables assume that all diagnostic fields have the same implementation details. If this is not so, the tables of this clause shall be repeated as necessary in an appendix.
~~PAGE 209~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.8 FTAM Quality of Service Details A.12.8.1 Initiator State all possible combinations of FTAM quality of service and the recovery or restart functional units which the initiator is capable of generating. Initiator Functional Units (In request) FTAM Quality of service Neither Restart Recovery Both No recovery m Yes — — — — — — Class 1 o No o No o No o No Class 2 o No o No o No o No Class 3 o No o No o No o No A.
~~PAGE 210~~
A.
~~PAGE 211~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM Charging D R 1 Resource identifier term m No 2 Charging unit term m No 3 Charging value term m No 4 Further charging details including the number of charging elements supported None A.12.11 Filestore Password Detail State what restrictions apply to the range of filestore passwords supported.
~~PAGE 212~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.13 Concurrency Control If an implementation does not support access control but does claim support of concurrency control, this clause shall be completed to indicate which concurrency locks may be set from the initiator role and which set in the responder role. Further, state the default values applied by the responder if the concurrency control field is not implemented. Tandem Implementation Note.
~~PAGE 213~~
A.12 Expanded PDU Field Detail ISO 8571 for FTAM A.12.14 FADU Locking If FADU locking is implemented, complete the following table to indicate which FADU concurrency locks may be set from the implementation while FADU locking is enabled from the F-OPEN, assuming no additional access control restrictions. Tandem Implementation Note. FADU locking is not implemented by Tandem FTAM.
~~PAGE 214~~
Section 6 Document Type Detail ISO 8571 for FTAM A.12.17 Processing Mode State which processing modes are capable of being specified and which accepted. The validity and applicability of these for any instances of communications will be subject at least to the constraints of ISO 8571. Processing Mode D I R 1 Read o Yes Yes 2 Insert o Yes Yes 3 Replace o Yes Yes 4 Extend o Yes Yes 5 Erase o Yes Yes A.12.
~~PAGE 215~~
~~A. 13.~~
~~PAGE 216~~
~~A.13.2 FTAM-2 ISO 8571 for FTAM A. 13.1.2 Parameter Combinations State the valid string length parameter and string significance parameter combinations.~~
~~PAGE 217~~
~~A.13.2 FTAM-2 ISO 8571 for FTAM A. 13.2.2 Parameter Combinations State the valid string length parameter and string significance parameter combinations.~~
~~PAGE 218~~
~~A.13.3 FTAM-3 ISO 8571 for FTAM A.13.3 FTAM-3 A. 13.3.1 Parameter Combinations State the valid string length parameter and string significance parameter combinations.~~
~~PAGE 219~~
~~Appendix A GraphicString Support ISO 8571 for FTAM Appendix A GraphicString Support AppA.~~
~~PAGE 220~~
~~ISO 8571 for FTAM AppA.~~
~~PAGE 221~~
13 CCITT X.400: P1 1984 for MHS The following information describes this PICS. See PICS Version Information on page 1-2, for a description of each item in this list: • • • • • • • • Standard 1984 CCITT X.400: P1 (Message Handling System: P1) Standard Version 1984 X.411 “Red Book” Proforma 1984 CCITT X.400: P1 PICS Proforma Proforma Version CTS-WAN MHS P1 PICS MHS/PICS/P1/1.
~~PAGE 222~~
~~CCITT X.400: P1 1984 for MHS This page intentionally left blank.~~
~~PAGE 223~~
PICS for the OSI MHS 1984 P1 Protocol CCITT X.400: P1 1984 for MHS PICS for the OSI MHS 1984 P1 Protocol 1. PICS Cover Page Proforma Protocol Supplier (if not the system supplier) Name: Street: City: Country Reference Protocol Identification Date: 2. Supported Functions Proforma A function is supported for Origination if the correspondent service element is made available by the service provider to the end-user, which if required can invoke the service element itself.
~~PAGE 224~~
Mapping Between A/311 Keys and PICS Entries CCITT X.400: P1 1984 for MHS Mapping Between A/311 Keys and PICS Entries A/311 PICS S M N O NU O NA O Note. Every service element whole status is marked with ‘m’ should be supported by the IUT in order to fulfill the static conformance requirements. Service Element Originator = O Receipt/Relay = R Status A/311 Status Implemen. 1. Content Type Indication O R m m Y Y 2. Converted Indication O R o m X Y 3.
~~PAGE 225~~
3. Initiator/Responder Capability CCITT X.400: P1 1984 for MHS Service Element Originator = O Receipt/Relay = R Status A/311 Status Implemen. 18. Explicit Conversion O R o o X X 19. Implicit Conversion O R o o X X 20. Probe O R o o Y Y * Tandem Implementation Note: All deferrals are local. 3. Initiator/Responder Capability 1. Initiator only N 2. Responder only N 3. Both YMaximum is 20 concurrent associations per MTA/RTS group. Hundreds of MTA/RTS groups may be configured. 4.
~~PAGE 226~~
5. Supported Parameters Proforma CCITT X.400: P1 1984 for MHS 5. Supported Parameters Proforma A protocol element is supported for Origination if the IUT is able to generate it under some circumstances (either automatically or because an end-user explicitly required a related service). A protocol element is supported for reception if it is correctly interpreted and handled. When required, it will be made available to the end-user.
~~PAGE 227~~
5.1 MPDU Name: UserMPDU CCITT X.400: P1 1984 for MHS 5.1 MPDU Name: UserMPDU Status Parameter Range O/R A/311 Implemen. A/311 Implemen. Length Stand Implemen. Max 32K-1 1. UMPDU-ENVELOPE O R m m Y Y 1.1 MPDUIdentifier O R m m Y Y 1.2 OriginatorORName O R m m Y Y 1.3 Original EncodedInformation Types O R o m Y Y 1.4 ContentType O R m m Y Y Max 32K-1 1.5 UAContentID O R o m Y Y Max 16 Ch. 1.6 Priority O R m m Y Y 1.7 PerMessageFlag O R m m Y Y 1.
~~PAGE 228~~
5.1 MPDU Name: UserMPDU CCITT X.400: P1 1984 for MHS Status Range Parameter O/R A/311 Implemen. 1.1.2 IASString O R m m Y Y 1.7 PerMessageFlag 1.7.1 DisclosureRecipients O R m m Y Y 1.7.2 ConversionProhibited O R m m Y Y 1.7.3 AlternateRecipientAllowed O R m m Y Y 1.7.4 ContentReturnRequest O R o o Y Y 1.9 PerDomainBilateralInfo 1.9.1 CountryName O R m m Y Y 1.9.2 AdministrationDomainName O R m m Y Y 1.9.3 Private Domain Name O R m m Y Y 1.
~~PAGE 229~~
5.1 MPDU Name: UserMPDU CCITT X.400: P1 1984 for MHS Status Parameter Range O/R A/311 Implemen. 1.11.2.3 Action O R m m Y Y 1.11.2.3.1 Relayed O R m m Y Y 1.11.2.3.2 Rerouted O R o m Y Y 1.11.2.4 Converted O R m m Y* Y 1.11.2.5 Previous O R m m Y Y A/311 Implemen. Length Stand Implemen. *Tandem Implementation Note: No conversions performed. Status Parameter for ADMDs Range O/R A/311 Implemen. A/311 Implemen. Length Stand Implemen. Max 16 Ch. Max 16 Ch. 1.2.
~~PAGE 230~~
5.1 MPDU Name: UserMPDU CCITT X.400: P1 1984 for MHS Status Parameter for ADMDs Range O/R A/311 Implemen. A/311 Implemen. Length Stand Implemen. 1.7 PersonalName O R m m Y Y Max 64 Ch. Max 64 Ch. 1.7.1 Surname O R m m Y Y Max 40 Ch. Max 40 Ch. 1.7.2 GivenName O R m m Y Y Max 16 Ch. Max 16 Ch. 1.7.3 Initials O R m m Y Y Max 5 Ch. Max 5 Ch. 1.7.4 GenerationQualifier O R o o Y Y Max 3 Ch. Max 3 Ch. 1.8 OrganizationalUnit O R m m Y Y Max 32 Ch. Max 32 Ch. 1.
~~PAGE 231~~
5.1 MPDU Name: UserMPDU CCITT X.400: P1 1984 for MHS Status Range Parameter for PRDMs O/R A/311 Implemen. Stand Implemen. 1.5 PrivateDomainName O R m m Y Y Max 16 Ch. Max 16 Ch. 1.5.1 PrintableString O R m m Y Y 1.5.2 Numeric O R o m X Y 1.6 OrganizationName O R m m Y Y Max 64 Ch. Max 64 Ch. 1.7 PersonalName O R m m Y Y Max 64 Ch. Max 64 Ch. 1.7.1 Surname O R m m Y Y Max 40 Ch. Max 40 Ch. 1.7.2 GivenName O R m m Y Y Max 16 Ch. Max 16 Ch. 1.7.
~~PAGE 232~~
5.2 MPDU Name: Delivery Report MPDU CCITT X.400: P1 1984 for MHS 5.2 MPDU Name: Delivery Report MPDU Status Parameter Range O/R A/311 Implemen. 1 DELIVERY REPORT ENVELOPE O R m m Y Y 1.1 Report O R m m Y Y 1.2 Originator O R m m Y Y 1.3 TraceInformation O R m m Y Y 2 DELIVERY REPORT CONTENT O R m m Y Y 2.1 Original O R m m Y Y 2.2 Intermediate O R o o Y Y 2.3 UAContentId O R m m Y Y 2.4 ReportRecipientInfo O R m m Y Y 2.5 Returned O R o m X Y 2.
~~PAGE 233~~
5.3 MPDU Name: Probe MPDU CCITT X.400: P1 1984 for MHS Status Parameter Range O/R A/311 Implemen. A/311 2.4.4.3.1 DeliveredInfo O R m m Y Y 2.4.4.3.1.1 Delivery O R m m Y Y 2.4.4.3.1.2 TypeofUA O R o o Y Y 2.4.4.3.2 NonDeliveredInfo. O R m m Y Y 2.4.4.3.2.1 ReasonCode O R m m Y Y 132K-1 2.4.4.3.2.2 DiagnosticCode O R o m Y Y 132K-1 Implemen. Length Stand Implemen. 5.3 MPDU Name: Probe MPDU Status Parameter Range O/R A/311 Implemen.
~~PAGE 234~~
~~5.3 MPDU Name: Probe MPDU CCITT X.~~
~~PAGE 235~~
14 CCITT X.400: RTS for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard 1984 CCITT X.400: RTS (Message Handling System: RTS) Standard Version 1984 X.
~~PAGE 236~~
~~CCITT X.400: RTS for MHS This page intentionally left blank.~~
~~PAGE 237~~
PICS for the OSI MHS 1984 RTS Protocol CCITT X.400: RTS for MHS PICS for the OSI MHS 1984 RTS Protocol 1 PICS Cover Page Proforma Protocol Supplier (if not the system supplier) Reference Protocol Identification Name: CTS WAN RTS PICS for A/3211 and A/311 Functional Standards (ENV 41201 and ENV 41202) Reference Standards 2 Initiator/Responder Capability The IUT is capable of acting as: 1. Initiator only [N] 2. Responder only [N] 3.
~~PAGE 238~~
4 Supported RTS Elements Proforma CCITT X.400: RTS for MHS Abbreviation(s) Supp. : Supported Note. Every service element whose status is marked with “m” should be supported by the IUT in order to fulfill the static conformance requirements. Supported Functions Supported Functions Abbreviation Initiator Status Responder Supp Status Supp 1. Association Establishment m [ ] m [ ] 2. Association Release m [ ] m [ ] 3. Data Transfer m [ ] m [ ] 4. TWA Dialogue Mode o [X] o [X] 5.
~~PAGE 239~~
5 Supported Parameters Proforma CCITT X.400: RTS for MHS RTS Elements RTS Element Name Initiator Responder Status Supp Status Supp 1. PConnect m [ ] m [ ] 2. PAccept m [ ] m [ ] 3. PRefuse m [ ] m [ ] 4. AbortInformation m [ ] m [ ] 5 Supported Parameters Proforma A Parameter is supported for Origination if the IUT is able to generate it under some circumstances. A Parameter is supported for Reception if it is correctly interpreted and handled.
~~PAGE 240~~
5.1 PConnect Element CCITT X.400: RTS for MHS Abbreviation(s) Sts.: Status Supp.: Supported Std.: Standard Imp.: Implemented Orig.: Originator Rec.: Recipient Note. 1. Optional Parameters which are not supported for Reception should not be regarded as protocol violations. 2. In the following table every heading parameter marked “m” should be supported by the IUT in order to fulfill the static conformance review.
~~PAGE 241~~
5.2 PAccept Element CCITT X.400: RTS for MHS RTS Element : PConnect Originator Sts Supp Receiver Sts Supp Maxi-mum Octets Length Std Value Imp Parameters Std Imp Orig Rec Orig Rec 0 0 0 0 1. DataTransferSyntax m [ ] m [ ] 2. pUserData m [ ] m [ ] 2.1 checkpointSize o [ ] m [ ] 1:30 0:30 2.2windowSize o [ ] m [ ] 1:100 1:100 2.3dialogueMode o [ ] m [ ] 2.4 ConnectionData m [ ] m [ ] 2.4.1 open m [ ] m [ ] 2.4.1.1 null m [ ] m [ ] 2.4.1.
~~PAGE 242~~
5.3 PRefuse Element CCITT X.400: RTS for MHS RTS Element : PAccept Originator Sts Supp Receiver Sts Supp Maximum Octets Length Std Value Imp Parameters Std Imp Orig Rec Orig Rec 0 0 0 0 1. DataTransferSyntax m [ ] m [ ] 2. pUserData m [ ] m [ ] 2.1 checkpointSize o [ ] m [ ] 8 8 1:30 1:30 2.2 windowSize o [ ] m [ ] 8 8 1:100 1:100 2.3 ConnectionData m [ ] m [ ] 2.3.1 open m [ ] m [ ] 2.3.1.1 null m [ ] m [ ] 2.3.1.
~~PAGE 243~~
5.4 AbortInformation Element CCITT X.400: RTS for MHS RTS Element : PRefuse Parameters Originator Sts 1. RefuseReason Supp m [ ] Maximum Octets Length Receiver Sts Supp m Std Value Imp [ ] Std Imp Orig Rec Orig Rec 0:3 0:3 0:3 0:3 5.4 AbortInformation Element Instructions for Client Please fill in the IMP. (IMPlemented) VALUE Columns for the AbortReason field in this way: • ORIG.
~~PAGE 244~~
~~CCITT X.~~
~~PAGE 245~~
15 CCITT X.400: P1 1988 for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard 1988 CCITT X.400: P1 (Message Handling System: P1) Standard Version 1988 “Blue Book” Proforma 1988 CCITT X.400: P1 PICS Proforma Proforma Version CCITT-X.PICS-2, Geneva, Nov. 1990 PTT-NL/131-CTS2-5/SPE/9001 (P1/PICS/V2.
~~PAGE 246~~
~~CCITT X.400: P1 1988 for MHS This page intentionally left blank.~~
~~PAGE 247~~
PICS for the OSI MHS 1988 P1 Protocol CCITT X.400: P1 1988 for MHS PICS for the OSI MHS 1988 P1 Protocol 1 Introduction 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 (see Note 1). Such a statement is called a Protocol Implementation Conformance Statement (PICS).
~~PAGE 248~~
4.2 Conformance Testing Methodology and Framework Definitions CCITT X.400: P1 1988 for MHS • • • • • • • • • • • message transfer (MT) message transfer agent (MTA) message-transfer-service-element (MTSE) probe-transfer report transfer MTA-bind MTA-unbind initiator responder MTS-provider MTS-user 4.
~~PAGE 249~~
A.1 Identifications CCITT X.400: P1 1988 for MHS A.1 Identifications A.1.1 Identification of PICS Ref. No. Question Response 1 Date of Statement 2 PICS Serial Number 3 SCS Cross Reference A.1.2 Identification of the Implementation and/or System Ref. No. Question Response 1 Implementation Name Tandem OSI/MHS 2 Version Number 4 3 Machine Name 4 Machine Version Number 5 Operating System Name 6 Operating System Version 7 Special Configuration 8 Other Information Guardian A.1.
~~PAGE 250~~
A.2 Global Statement of Conformance CCITT X.400: P1 1988 for MHS A.2 Global Statement of Conformance Ref. No. 1 Question Response Are all mandatory capabilities implemented? Yes A.3 Instructions for Completing the PICS Proforma An item is said to be supported for origination if the IUT is able to generate it under some circumstances (either automatically or because the end-user explicitly requires a related service).
~~PAGE 251~~
A.3 Instructions for Completing the PICS Proforma CCITT X.400: P1 1988 for MHS p11 = A.5.4.20.O p12 = A.5.4.20.R p13 = p9 or p14 p14 = A.5.4.16.R p15 = A.5.4.16.O p16 = A.5.4.25.O p17 = A.5.4.25.R p18 = p1 or p17 or A.5.4.29.R p19 = A.5.7.3.1.1.5.O p20 = A.5.4.32.R p21 = A.5.4.32.O p22 = A.5.7.3.1.1.11.10.O p23 = “the MTA acts within a PRMD” p24 = A.5.4.2.
~~PAGE 252~~
A.4 Abbreviations CCITT X.400: P1 1988 for MHS A.4 Abbreviations The following abbreviations are used in this PICS proforma: Abbreviation Meaning c conditional D Defined I Implemented m mandatory N NO N/A Not Applicable o optional O/R O = Origination / R = Reception or Relay PHY Physical Delivery (not tested) SEC Security (not tested) Y YES A.5 Capabilities and Options A.5.
~~PAGE 253~~
A.5.2 Initiator/Responder Capability CCITT X.400: P1 1988 for MHS A.5.2 Initiator/Responder Capability A.5.2.1 Initiator Y. A.5.2.2 Responder Y. A.5.2.3 Both Y. A.5.3 Supported Application Contexts Application Context D I mts-transfer-protocol-1984 m Y mts-transfer-protocol m Y mts-transfer o Y Tandem Implementation Notes.
~~PAGE 254~~
A.5.4 Major Capabilities CCITT X.400: P1 1988 for MHS A.5.4 Major Capabilities Message Transfer services Ref. No. MHS Element of Service O/R D I Clause Ref. (X.400) 1 Access Management O R m m Y Y B.1 2 Alternate Recipient Allowed O R m c P1 Y B.3 3 Alternate Recipient Assignment O R N/A o N B.4 4 Content Type Indication O R m m Y Y B.12 5 Conversion Prohibition O R m c P9 Y Y B.13 6 Conversion Prohibition in Case of Loss of Information O R o c P9 N Y B.
~~PAGE 255~~
A.5.4 Major Capabilities CCITT X.400: P1 1988 for MHS Ref. No. MHS Element of Service O/R D I 23 Non Delivery Notification O R m m Y Y B.47 24 Original Encoded Information Types Information O R m m Y Y B.54 25 Originator Requested Alternate Recipient O R o o N N B.56 26 Prevention of Non Delivery Notification O R o o Y Y B.61 27 Probe O R m m Y Y B.63 28 Redirection Disallowed by Originator O R o c P2 N N B.
~~PAGE 256~~
A.5.4 Major Capabilities CCITT X.400: P1 1988 for MHS Ref. No. MHS Element of Service O/R D I Clause Ref. (X.400) 46 Physical Forwarding Prohibited O R o o N N B.60 47 Registered Mail O R o o N N B.70 48 Registered Mail to Addresses in Person O R o o N N B.71 49 Request for Forwarding Address O R o o N N B.75 50 * Special Delivery O R m m N N B.81 51 * Undeliverable Mail with Return of Physical Message O R m m N N B.
~~PAGE 257~~
A.5.4 Major Capabilities CCITT X.400: P1 1988 for MHS Ref. No. MHS Element of Service 64 65 Clause Ref. (X.400) O/R D I Report Origin Authentication O R o o N Y B.74 Secure Access Management O R o o N Y B.79 Note. Change in D21 to allow for all extension to be relayed. Please answer Y or N in the following table according to your implementation.
~~PAGE 258~~
A.5.5 Timers and Protocol Parameters CCITT X.400: P1 1988 for MHS A.5.5 Timers and Protocol Parameters “N/A” A.5.6 PDUs and Operations A.5.6.1 PDUs Ref. No. PDU 1 Clause Ref. (X.400) O/R D I MessageTransfer O R m m Y Y 13. 2 ReportTransfer O R m m Y Y 13. 3 Probe O R m m Y Y 13. O/R D I A.5.6.2 Operations Clause Ref. (X.400) Ref. No. PDU 1 MTABind O R c P3 c P4 Y Y 13. 2 MTAUnbind O R c P3 c P4 Y Y 13. “P3 = A.5.2.1 or A.5.2.3” “P4 = A.5.2.2 or A.5.3.3” A.5.
~~PAGE 259~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.1 MTA-bind Arguments Parameter Values Supported Clause Reference (X.411) O/R D I 1 BindArguments O R m m Y Y 1.1 NULL O R m m Y Y 1.2 SET O R m m Y Y 1.2.1initiator-name O R m m Y Y 12.1.1.1.1.1 1.2.2Initiator Credentials O R m m Y Y 12.1.1.1.1.2 1.2.2.1simple O R m m Y Y 1.2.2.2strong O R — — N N SEC 1.2.3SecurityContext O R — — N N SEC Parameter Note Permit Range of Values 12.1.1.
~~PAGE 260~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter Note Permit Range of Values Values Supported Clause Reference (X.411) O/R D I 3.2 authentication-error O R m m Y Y 12.1.2.1 3.3 unacceptable-dialoguemode O R m m Y Y 12.1.2.3 3.4 unacceptable-securitycontext O R — — Y Y SEC Tandem OSI PICS Manual–135046 15 -16 12.1.2.
~~PAGE 261~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.2 MTA-unbind Arguments “N/A” A.5.7.3 MessageTransfer PDU Parameters Parameters Note Permit Range of Values Values Supported Clause Reference (X.411) O/R D I 1 MessageTransferEnvelope O R m m Y Y 1.1 PerMessage TransferFields O R m m Y Y 1.1.1 MessageIdentifier O R m m Y Y 1.1 12.2.1.1.1.1 1.1.2 OriginatorName O R m m Y Y 3 8.2.1.1.1.1 1.1.3 OriginalEncoded InformationTypes O R m m Y Y 1.3 8.2.
~~PAGE 262~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameters Permit Range of Values Values Supported Clause Reference (X.411) O/R D I Note 1.1.11.7 Content Confidentiality AlgorithmId O R — — N N SEC X.50 0 8.2.1.1.1.27 1.1.11.8 MessageOrigin AuthenticationCheck O R — — N N SEC 2.1 8.2.1.1.1.29 1.1.11.9 Message SecurityLabel O R — — N N SEC 2.2 8.2.1.1.1.30 1.1.11.10 ContentCorrelator O R o m N Y 1.1.11.11 DLExpansionHistory O R c m Y Y 2.
~~PAGE 263~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameters O/R D I Note 1.2.5.11 ContentIntegrity Check O R — — N N 2.7 1.2.5.12 ProofOfDelivery Request O R — — N N 1.2.5.13 RedirectionHistory O R c m N Y 2 Content O R m m Y Y Permit Range of Values Values Supported Clause Reference (X.411) 8.2.1.1.1.28 8.2.1.1.1.32 2.8 P18 Tandem OSI PICS Manual–135046 15 -19 8.2.1.1.1.
~~PAGE 264~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.4 ReportTransfer PDU Parameters Parameters Note Permit Range of Values Values Supported Clause Reference (X.411) O/R D I 1 ReportTransferEnvelope O R m m Y Y 1.1 ReportIdentifier O R m m Y Y 1.1 12.2.1.3.1.1 1.2 ReportDestinationName O R m m Y Y 3 12.2.1.3.1.2 1.3 TraceInformation O R m m Y Y 1.6 12.2.1.1.1.3 1.4 Extensions O R m m Y Y 1.4.1 MessageSecurityLabel O R — — N N SEC 2.2 8.2.1.
~~PAGE 265~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameters O/R D I Note 2.2 PerRecipientReport TransferFields O R m m Y Y 2.2.1 ActualRecipientName O R m m Y Y 2.2.2 OriginallySpecified RecipientNumber O R m m Y Y 2.2.3 PerRecipientIndicators O R m m Y Y 1.7 2.2.4 LastTraceInformation O R m m Y Y 1.8 2.2.5 OriginallyIntended RecipientName O R m m Y Y 3 2.2.6 Supplementary Information O R o o N Y 2.2.7 Extensions O R m m Y Y 2.2.7.
~~PAGE 266~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.5 ProbeTransfer PDU Parameters Parameter Note Permit Range of Values Values Supporte d Clause Reference (X.411) O/R D I 1 ProbeTransferEnvelope O R m m Y Y 1.1PerProbeTransferFields O R m m Y Y 1.1.1 ProbeIdentifier O R m m Y Y 1.1 12.2.1.2.1.1 1.1.2 OriginatorName O R m m Y Y 3 8.2.1.1.1.1 1.1.3 OriginalEncoded InformationTypes O R m m Y Y 1.3 8.2.1.1.1.33 1.1.4 ContentType O R m m Y Y 1.
~~PAGE 267~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter Note Permit Range of Values Values Supporte d Clause Reference (X.411) O/R D I 1.2 PerRecipientTransferFields O R m m Y Y 1.2.1 RecipientName O R m m Y Y 1.2.2 OriginallySpecified RecipientNumber O R m m Y Y 1.2.3 PerRecipientIndicators O R m m Y Y 1.7 1.2.4 ExplicitConversion O R c c N N P15 P14 8.2.1.1.1.11 1.2.5 Extensions O R m m Y Y 1.2.5.1 OriginatorRequested AlternateRec.
~~PAGE 268~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.6 Supported Data Types and ORNames A.5.7.6.1 Common Data Types Parameter O/R D I Note 1.1 GlobalDomainIdentifier O R m m Y Y 1.2 1.2 LocalIdentifier O R m m Y Y 2.1 CountryName O R m m Y Y 2.1.1 x121-dcc-code O R m m Y Y 2.1.2 iso-3166-alpha2-code O R m m Y Y 2.2 AdministrationDomain Name O R m m Y Y 2.2.1 numeric O R m m Y Y 2.2.2 printable O R m m Y Y 2.
~~PAGE 269~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 3.1.8 voice O R o o Y Y 3.1.9 sfd O R o o Y Y 3.1.10 mixed-mode O R o o Y Y 3.2 NonBasicParameters O R o o Y Y 3.2.1 G3FacsimileNonBasic Parameters O R o o Y Y 3.2.1.1 two-dimensional O R o o Y Y 3.2.1.2 fine-resolution O R o o Y Y 3.2.1.3 unlimited-length O R o o Y Y 3.2.1.4 b4-length O R o o Y Y 3.2.1.5 a3-width O R o o Y Y 3.2.1.6 b4-width O R o o Y Y 3.2.1.
~~PAGE 270~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I Note 4.3 alternate-recipient-allowed O R m c Y N P24 4.4 content-return-request O R c c Y Y 5.1 CountryName O R m m Y Y 5.2 AdministrationDomain Name O R m m Y Y 5.3 PrivateDomainIdentifier O R c m Y Y 5.4 BilateralInformation O R m m Y Y 6.1 TraceInformationElement O R m m Y Y 6.1.1 GlobalDomainIdentifier O R m m Y Y 6.1.2 DomainSupplied Information O R m m Y Y 6.1.2.
~~PAGE 271~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter Note Permit Range of Values Values Supported Clause Reference (X.411) O/R D I 7.2 originating-MTA-report O R m m Y Y 7.3 originating-MTA-nondelivery-report O R m m Y Y 7.4 originator-report O R m m Y Y 7.5 originator-non-delivery-report O R m m Y Y 8.1 ArrivalTime O R m m Y Y 8.2 ConvertedEncoded InformationTypes O R m m Y Y 8.3 ReportType O R m m Y Y 8.3.
~~PAGE 272~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 8.3.2.1.4 physical-renditionnot-performed O R m m Y Y 8.3.2.1.5 physical-deliverynot-performed O R m m Y Y 8.3.2.1.6 restricted-delivery O R m m Y Y 8.3.2.1.7 directory-operation unsuccessful O R m m Y Y 8.3.2.2 NonDelivery Diagnostic Code O R o m Y Y 9.1 BuiltInContentType O R m m Y Y 9.1.1 unidentified O R o o Y Y 9.1.2 external O R o o Y Y 9.1.
~~PAGE 273~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS A.5.7.6.2 Extension Data Types Parameter Permit Range of Values Values Supported Clause Reference (X.411) O/R D I Note 1.1 algorithm-identifier O R — — N N SEC 8.5.10 1.2 Content O R — — N N SEC 8.3.1.1.1.37 1.3 ContentIdentifier O R — — N N SEC 8.2.1.1.1.35 1.4 MessageSecurityLabel O R — — N N SEC 2.2 8.2.1.1.1.30 2.1 SecurityPolicyIdentifier O R — — N N SEC 8.5.9 2.
~~PAGE 274~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter Note Permit Range of Values Values Supported Clause Reference (X.411) O/R D I 4.2 special-delivery O R — — N N 8.2.1.1.1.17 4.3 express-mail O R — — N N 8.2.1.1.1.17 4.4 counter-collection O R — — N N 8.2.1.1.1.17 4.5 counter-collection-withtelephone-advice O R — — N N 8.2.1.1.1.17 4.6 counter-collection-withtelex-advice O R — — N N 8.2.1.1.1.17 4.
~~PAGE 275~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I Note 8.2.2 originator-req. alternate-recipient O R m m Y Y 8.2.3 recipient-MDassignedalternate-rec O R m m Y Y 9.1 OrAddressAndOptional DirectoryName O R m m Y Y 9.2 origination-orexpansion- time R O m m Y Y 10.1 GlobalDomainIdentifier O R m m Y Y 10.2 MTAName O R m m Y Y 10.3 MTASupplied Information O R m m Y Y 10.3.1 ArrivalTime O R m m Y Y 10.3.
~~PAGE 276~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter Permit Range of Values Values Supported Clause Reference (X.411) O/R D I Note 11.1 Algorithm-Identifier O R — — N N SEC X.500 8.5.10 11.2 ContentIdentifier O R — — N N SEC 8.2.1.1.1.35 11.3 MessageSecurityLabel O R — — N N SEC 8.2.1.1.1.30 11 ProbeOrigin AuthenticationCheck A.5.7.6.3 ORNames ORNames consist of a mandatory address part and an optional directory-name part.
~~PAGE 277~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS NOTE 4: Extension-attributes are not required to be supported; when supplied they shall be used in addition to the StandardAttributes data type. When an Extension-attribute field is supported, it is assumed that the corresponding “extension-attribute-type” and “extension-attribute-values” are also supported. NOTE 5: Optional for UA in origination. NOTE 6: See ISO/IEC 9594-2 | X.501. Parameter O/R D I 1.1.
~~PAGE 278~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 1.2 Extensions Note Permit Range of Values NOTE3 NOTE4 1.2.1 CommonName O R m m Y Y 1.2.2 TeletexCommonName O R m m Y Y 1.2.3 TeletexOrganizational Name O R m m Y Y 1.2.4 TeletexPersonalName O R m m Y Y 1.2.4.1 surname O R m m N N 1.2.4.2 given-name O R m m N N 1.2.4.3 initials O R m m N N 1.2.4.4 generation-qualifier O R m m Y Y 1.2.
~~PAGE 279~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 2.1.4 NumericUserIdentifier O R m m Y Y 2.1.5 DomainDefinedAttributes O R m m Y Y 2.2 directory-name O R o o N N Note Permit Range of Values NOTE6 3 ORName with TerminalORAddress 3.1 address 3.1.1 CountryName O R m m Y Y 3.1.1.1 x121-dcc-code O R m m Y Y 3.1.1.2 iso-3166-alpha2-code O R m m Y Y 3.1.2 AdministrationDomainName O R m m Y Y 3.1.2.1 numeric O R m m Y Y 3.1.2.
~~PAGE 280~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I Note 3.2.2.1 telex O R m m Y Y 3.2.2.2 teletex O R m m Y Y 3.2.2.3 g3-facsimile O R m m Y Y 3.2.2.4 g4-facsimile O R m m Y Y 3.2.2.5 ia5-terminal O R m m Y Y 3.2.2.6 videotex O R m m Y Y 3.3 directory-name O R o o N N 4.1.1 CountryName O R — — N N 4.1.1.1 x121-dcc-code O R — — N N 4.1.1.2 iso-3166-alpha2-code O R — — N N 4.1.2 Administration DomainName O R — — N N 4.
~~PAGE 281~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 4.2.2.2 teletex-string O R — — N N 4.2.3 PhysicalDelivery OfficeNumber O R — — N N 4.2.3.1 printable-string O R — — N N 4.2.3.2 teletex-string O R — — N N 4.2.4 PhysicalDelivery OrganizationName O R — — N N 4.2.4.1 printable-string O R — — N N 4.2.4.2 teletex-string O R — — N N 4.2.5 PhysicalDelivery PersonalName O R — — N N 4.2.5.1 printable-string O R — — N N 4.2.5.
~~PAGE 282~~
A.5.7 Operation Arguments and PDU Parameters CCITT X.400: P1 1988 for MHS Parameter O/R D I 4.2.11 UniquePostalName O R — — N N 4.2.11.1 printable-string O R — — N N 4.2.11.2 teletex-string O R — — N N 4.2.12 ExtensionOR AddressComponents O R — — N N 4.2.12.1 printable-string O R — — N N 4.2.12.2 teletex-string O R — — N N 4.2.13 ExtensionPhysical DeliveryAddress Components O R — — N N 4.2.13.1 printable-string O R — — N N 4.2.13.2 teletex-string O R — — N N 4.2.
~~PAGE 283~~
A.5.8 Negotiation Capabilities CCITT X.400: P1 1988 for MHS Parameter 5.1.3.2 printable O/R D I Note O R — — N N NOTE1 5.2 Extensions Permit Range of Values NOTE4 5.2.1 Unformatted PostalAddress O R — — N N 5.2.1.1 printable-address O R — — N N 5.2.1.1.1 PrintableString O R — — N N 5.2.1.2 teletex-string O R — — N N 5.2.2 PhysicalDelivery CountryName O R — — N N 5.2.2.1 x121-dcc-code O R — — N N 5.2.2.2 iso-3166-alpha2-code O R — — N N 5.2.
~~PAGE 284~~
~~A.5.10 Multi-layer Dependencies CCITT X.~~
~~PAGE 285~~
16 CCITT X.400: P2 for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • Standard 1988 CCITT X.400: P2 (Message Handling System: P2) Standard Version 1988 “Blue Book” Proforma 1988 CCITT X.400: P2 PICS Proforma/ ISO/IEC 10021-15 Proforma Version CCITT: Draft Recommendation CCITT-X.
~~PAGE 286~~
~~CCITT X.400: P2 for MHS This page intentionally left blank.~~
~~PAGE 287~~
CCITT X.400: P2 for MHS PICS for the OSI MHS 1988 P2 Protocol PICS for the OSI MHS 1988 P2 Protocol 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 cooperative open systems. The purpose of an MHS is to enable users to exchange messages on a store-and-forward basis.
~~PAGE 288~~
2 Normative References CCITT X.400: P2 for MHS 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-1 1990, Information Technology—Open Systems Interconnection— Conformance Testing Methodology and Framework—Part I: General Concepts.
~~PAGE 289~~
Annex A CCITT X.400: P2 for MHS Annex A A.1 Identifications A.1.1 Identification of PICS Ref. No. Question Response 1 Date of Statement 2 PICS Serial Number 3 SCS Cross Reference A.1.2 Identification of the Implementation and/or System Ref. No.
~~PAGE 290~~
A.2 Identification of the Protocol CCITT X.400: P2 for MHS Ref. No. Question Response 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 CCITT 1988 X.400 series 2 Protocol version numbers IXth Plenary Assembly, Nov 1988 3 Addenda implemented n/a 4 Implemented defects reports (Ref. No.) n/a A.3 Global Statement of Conformance Ref. No.
~~PAGE 291~~
A.4 Instructions for Completing the PICS Proforma CCITT X.400: P2 for MHS A.4 Instructions for Completing the PICS Proforma A.4.1 Definition 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 parameter(s).
~~PAGE 292~~
A.4.4 Permitted Range of Value/Value Supported Columns CCITT X.400: P2 for MHS In the PICS proforma tables, every leading item 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.
~~PAGE 293~~
A.4.7 Additional Comments CCITT X.400: P2 for MHS 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. List of Predicates p1 = S.O.13 or S.O.17 p2 = S.O.3 p3 = S.O.14 p4 = S.O.5 p5 = S.O.6 p6 = S.O.18 p7 = S.O.19 p8 = S.O.2 p9 = P10 or p12 p10 = S.O.9 p11 = S.R.9 p12 = S.O.11 p13 = A.6.6.4.1.1.2.3.R p14 = A.6.6.4.1.1.2.3.O p15 = S.R.17 p16 = S.O.17 p17 = S.O.
~~PAGE 294~~
A.5 Abbreviations CCITT X.400: P2 for MHS 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 addressable without any restrictions. 4. Each line within the PICS proforma which requires implementation detail to be entered is numbered.
~~PAGE 295~~
A.6 Capabilities and Options CCITT X.400: P2 for MHS 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.
~~PAGE 296~~
A.6.3 Major Capabilities CCITT X.400: P2 for MHS Ref. No. MHS Element of Service 7 Clause Ref. (X.400) O/R D I Forwarded IP Message Indication O R o m Y Y B.31 8 Importance Indication O R o m Y Y B.35 9 Incomplete Copy Indication ** O R o o Y Y B.36 10 IP Message Identification O R m m Y Y B.37 11 Language Indication ** O R o m Y Y B.38 12 Multi-Part Body O R o m Y Y B.46 13 Non-Receipt Notification Request Indication *** O R o m N Y B.
~~PAGE 297~~
A.6.3 Major Capabilities CCITT X.400: P2 for MHS Ref. No. MHS Element of Service O/R D I 26 Content Type Indication O R m m Y Y B.12 27 Conversion Prohibition O R m m Y Y B.13 p9 Conversion Prohibition in Case of Loss of Information O R o o N Y B.14 p9 29 Converted Indication O R n/a m — Y B.15 30 Deferred Delivery O R m n/a Y — B.19 31 Deferred Delivery Cancellation O R o n/a Y — B.20 32 Delivery Notification O R m n/a Y — B.
~~PAGE 298~~
A.6.3 Major Capabilities CCITT X.400: P2 for MHS Ref. No. MHS Element of Service 49 Clause Ref. (X.400) O/R D I Probe O R o n/a Y — B.63 50 Redirection Disallowed by Originator O R o n/a N — B.68 51 Redirection of Incoming Messages O R n/a o — N B.69 52 Requested Delivery Method O R m n/a Y — B.76 53 Restricted Delivery O R n/a o — N B.77 54 Return of Content O R o n/a N — B.78 55 Submission Time Stamp Indication O R m m Y Y B.
~~PAGE 299~~
A.6.3 Major Capabilities CCITT X.400: P2 for MHS Ref. No. MHS Element of Service 70 Clause Ref. (X.400) O/R D I Registered Mail to Addresses in Person O R o o N N B.71 71 Request for Forwarding Address O R o o N N B.75 72 Special Delivery O R o m N N B.81 Note 2 O R o m N N B.91 Note 2 O/R D I 73 Undeliverable Mail with Return of Physical Message Note 2: Only for PDAU, else not applicable. Security services Ref. No.
~~PAGE 300~~
A.6.3 Major Capabilities CCITT X.400: P2 for MHS These elements of service only apply to IPMS-MS. Ref. No. MHS Element of Service O/R D I Clause Ref. (X.400) 87 MS Register O R n/a o — Y B.4n 88 Stored Message Alert O R n/a o — N B.82 89 Stored Message Auto-Forward O R n/a o — N B.83 90 Stored Message Deletion O R n/a m — Y B.84 91 Stored Message Fetching O R n/a m — Y B.85 92 Stored Message Listing O R n/a m — Y B.
~~PAGE 301~~
A.6.4 Timers and Protocol Parameters CCITT X.400: P2 for MHS A.6.4 Timers and Protocol Parameters N/A A.6.5 Supported PDUs Ref. No. MHS Element of Service IPM IPM Clause Ref. (X.420) O/R D I Interpersonal Message O R m m Y Y 7 Interpersonal Notification O R m c Y Y 8 p1 A.6.6 Supported PDU Parameters A.6.6.1. IPM Values Supported Clause Ref. (X.420) Parameter O/R D I 1 Heading O R m m Y Y 1.1 this-IPM O R m m Y Y #1.3 7.2.1 1.2 originator O R m m Y Y #1.2 7.2.2 1.
~~PAGE 302~~
A.6.6 Supported PDU Parameters CCITT X.400: P2 for MHS Parameter Permit Range of Values Values Supported Clause Ref. (X.420) O/R D I Note O c Y p6 #1.2 7.2.13 R m Y O c Y d p19 7.2.14 R m Y 1.14 low O R o m Y Y 1.14.2 normal O R o m Y Y 1.14.3 high O R o m Y Y 1.15 sensitivity O R c m Y Y p7 7.2.15 1.16 auto-forwarded O R c m Y Y p8 7.2.16 1.17 extensions * O R c m Y Y p9 7.2.17 1.17.1 incomplete-copy O R c c Y Y p10 p11 annex A.1 1.17.
~~PAGE 303~~
A.6.6 Supported PDU Parameters CCITT X.400: P2 for MHS Parameter Note Permit Range of Values Values Supported Clause Ref. (X.420) O/R D I 2.3.2 G3FacsimileData O R m m Y Y 2.4 g4-class1 O R o o Y Y 7.3.4 2.5 teletex O R o o Y Y 7.3.5 2.5.1 TeletexParameters O R m m Y Y 2.5.1.1 number-of-pages O R o o N Y 2.5.1.2 telex-compatible O R o m Y Y 2.5.1.3 TeletexNonBasic Parameters O R m m Y Y 2.5.1.3.1 graphic-character-sets O R o o Y Y 2.5.1.3.
~~PAGE 304~~
A.6.6 Supported PDU Parameters CCITT X.400: P2 for MHS Parameter O/R D I 2.8.1 MessageParameters O R m m Y Y 2.8.1.1 delivery-time O R o o Y Y 2.8.1.2 delivery-envelope O R o o Y Y 2.8.1.2.1 content-type O R o o Y Y 2.8.1.2.2 originator-name O R o o Y Y 2.8.1.2.3 original-encodedinformation-types O R o o Y Y 2.8.1.2.4 priority O R o o Y Y 2.8.1.2.5 delivery-flags O R o o Y Y 2.8.1.2.6 other-recipient-names O R o o Y Y 2.8.1.2.7 this-recipient-name O R o o Y Y 2.
~~PAGE 305~~
A.6.6 Supported PDU Parameters CCITT X.400: P2 for MHS Parameter Note Permit Range of Values Values Supported Clause Ref. (X.420) O/R D I 2.8.1.2.21 originator-returnaddress O R o o N N 2.8.1.2.22 physical-delivery report-request O R o o N N 2.8.1.2.23 originator-certificate O R o o N N 2.8.1.2.24 message-token O R o o N N 2.8.1.2.25 content-confidentialityalgorithm-identifier O R o o N N 2.8.1.2.26 content-integrity-check O R o o N N 2.8.1.2.
~~PAGE 306~~
A.6.6.2. IPN CCITT X.400: P2 for MHS A.6.6.2. IPN Parameter O/R D I Note Permit Range of Values Values Supported Clause Reference (X.420) 1 subject-ipm O R m m Y Y #1.3 8.1.1 2 ipn-originator O R o m Y Y #1.2 8.1.2 3 ipm-preferred-recipient O R m m Y Y #1.2 8.1.3 4 conversion-eits O R m m Y Y 5 NonReceiptFields O R m c Y Y 5.1 non-receipt-reason O R m m Y Y 5.1.1 ipm-discarded O R m m Y Y 5.1.2 ipm-auto-forwarded O R c m Y Y 5.
~~PAGE 307~~
A.6.6.2. IPN CCITT X.400: P2 for MHS comprises a type and, depending upon the type, one or more values. This section classifies the MS attributes specific to Interpersonal Messaging and applies to configurations 3 and 4 (see definitions in A.1.2 Identification of the Implementation and/or System on page 16-5). For each IPM or IPN it holds or handled, the implementation shall support the following attributes. Definition of support for these attributes is given in annex C and Table C1/X.420.
~~PAGE 308~~
~~A.6.6.2. IPN CCITT X.~~
~~PAGE 309~~
A.6.6.2. IPN CCITT X.400: P2 for MHS A.6.6.4 Common Data Types and ORNames A.6.6.4.1 Common Data Types Parameter O/R D I Note Permit Range of Values 1 RecipientSpecifier Values Supported Clause Reference (X.420) 7.1.2 1.1 Recipient O R m m Y Y #1.2 1.2 notification-requests O R c m Y Y p21 1.2.1 rn O R c c Y Y p16 p15 1.2.2 nrn O R c m Y Y p17 1.2.3 ipm-return O R o o Y Y 1.3 reply-requested O R c m Y Y p18 2 ORDescriptor 7.1.3 2.1 FormalName O R m m Y Y 2.1.
~~PAGE 310~~
A.6.6.2. IPN CCITT X.400: P2 for MHS ORNames. A proposed new ORName shall be rejected if it is already assigned to another MTS-user. Parameter Permit. Range of Values Values Supported Clause Reference (X.402) O/R D I Note 1 MnemonicORAddress O R m m Y Y A 18.5.1 2 NumericORAddress O R m m Y Y A 18.5.2 3 TerminalORAddress O R m m Y Y A 18.5.4 4 FormattedPostalORAddress O R — — N N PHY 18.5.3 5 Unformatted PostalORAddress O R — — N N PHY 18.5.
~~PAGE 311~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter Values Supported 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 64 64 64 64 O/R D I 1.1.2.1 numeric O R m m Y Y 1.1.2.2 printable O R m m Y Y Note1 1.1.3 PrivateDomainName O R m m Y Y Note2 1.1.3.1 numeric O R m m Y Y 1.1.3.2 printable O R m m Y Y 1.1.4 OrganizationName O R m m Y Y 1.1.5 PersonalName O R m m Y Y 1.1.5.1 surname O R m m Y Y 40 40 40 40 1.1.5.2 given-name O R m m Y Y 16 16 16 16 1.1.5.
~~PAGE 312~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter Note Permit Range of Values O/R D I 1.2.5 Teletex Organizational UnitNames O R m m N N 4 4 1.2.5.1Teletex Organizational UnitName O R m m N N 32 32 1.2.6 TeletexDomain DefinedAttributes O R o m N N 4 4 1.3 directory-name O R o o Y Y Values Supported Note5 2 ORName with NumericORAddress 2.1 address 2.1.1 CountryName O R m m Y Y 2.1.1.1 x121-dcc-code O R m m Y Y 2.1.2 Administration DomainName O R m m Y Y 2.1.2.
~~PAGE 313~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter Values Supported O/R D I 3.1.3 NetworkAddress O R m m Y Y 16 16 15 15 3.1.4 Terminal Identifier O R m m Y Y 24 24 24 24 3.1.5 PrivateDomain Name O R m m Y Y 3.1.5.1 numeric O R m m Y Y 16 16 16 16 3.1.5.2 printable O R m m Y Y 16 16 16 16 3.1.6 DomainDefinedAttributes O R o m Y Y 4 4 4 4 3.2 Extensions Note Permit Range of Values Note2 Note1 Note3 Note4 3.2.1 ExtendedNetworkAddress O R m m N N 3.2.1.
~~PAGE 314~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter O/R D I Note Permit Range of Values 4 ORName with FormattedPostalORAddress 4.1address 4.1.1 CountryName O R — — N N 4.1.1.1 x121-dcc-code O R — — N N 4.1.1.2 iso-3166-alpha2-code O R — — N N 4.1.2 Administration DomainName O R — — N N 4.1.2.1 numeric O R — — N N 4.1.2.2 printable O R — — N N Note1 4.1.3 PrivateDomainName O R — — N N Note2 4.1.3.1 numeric O R — — N N 4.1.3.
~~PAGE 315~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter O/R D I 4.2.5 PhysicalDelivery PersonalName O R — — N N 4.2.5.1 printable-string O R — — N N 4.2.5.2 teletex-string O R — — N N 4.2.6 PostalCode O R — — N N 4.2.6.1 numeric-code O R — — N N 4.2.6.2 printable-code O R — — N N 4.2.7 PosteRestante Address O R — — N N 4.2.7.1 printable-string O R — — N N 4.2.7.2 teletex-string O R — — N N 4.2.8 PostOfficeBox Address O R — — N N 4.2.8.
~~PAGE 316~~
A.6.6.2. IPN CCITT X.400: P2 for MHS Parameter O/R D I 4.2.13 ExtensionPhysical Delivery Address Components O R — — N N 4.2.13.1 printable-string O R — — N N 4.2.13.2 teletex-string O R — — N N 4.2.14 LocalPostal Attributes O R — — N N 4.2.14.1 printable-string O R — — N N 4.2.14.2 teletex-string O R — — N N 4.3 directory-name O R — — N N Note Permit Range of Values Note5 5 ORName with UnformattedPostalORAddress 5.1 address 5.1.1 CountryName O R — — N N 5.1.1.
~~PAGE 317~~
A.6.7 Negotiation Capabilities CCITT X.400: P2 for MHS Parameter O/R D I 5.2.2 PhysicalDelivery CountryName O R — — N N 5.2.2.1 x121-dcc-code O R — — N N 5.2.2.2 iso-3166-alpha2-code O R — — N N 5.2.3 PostalCode O R — — N N 5.2.3.1 numeric-code O R — — N N 5.2.3.2 printable-code O R — — N N 5.2.4 PDSName O R — — N N 5.3 directory-name O R — — N N Note Permit Range of Values Values Supported Note1 Note5 A.6.7 Negotiation Capabilities “N/A” A.6.
~~PAGE 318~~
~~A.7.2 Lower Layers CCITT X.~~
~~PAGE 319~~
17 CCITT X.400: P7 for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard 1988 CCITT X.400: P7 (Message Handling System: P7) Standard Version 1988 “Blue Book” Proforma 1988 CCITT X.400: P7 PICS Proforma Proforma Version CCITT-X.PICS 3.
~~PAGE 320~~
~~CCITT X.400: P7 for MHS This page intentionally left blank.~~
~~PAGE 321~~
PICS for the OSI MHS 1988 P7 Protocol CCITT X.400: P7 for MHS PICS for the OSI MHS 1988 P7 Protocol 1 Introduction 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). 2 Scope This document provides the PICS proforma for the P7 protocol as specified in CCITT X.
~~PAGE 322~~
4.2 Conformance Testing Methodology and Framework Definitions CCITT X.400: P7 for MHS • • • • • • • • • • Message Retrieval Service Element (MRSE); Message Submission Service Element (MSSE); message store (MS); message transfer system (MTS); MTS-provider; MTS-user; originator recipient; responder; user agent (UA). 4.
~~PAGE 323~~
A.1 Identifications CCITT X.400: P7 for MHS A.1 Identifications A.1.1 Identification of PICS Ref. No. Question Response 1 Date of Statement April 30, 1992 2 PICS Serial Number 3 SCS Cross Reference A.1.2 Identification of the Implementation and/or System Ref. No. Question Response 1 Implementation Name OSI/MHS 2 Version Number Rel.
~~PAGE 324~~
A.1.5 Identification of the Physical Configuration CCITT X.400: P7 for MHS A.1.5 Identification of the Physical Configuration Ref. No. 1 Question Response UA or MS N Y A.2 Global Statement of Conformance Ref. No. 1 Question Response Are all mandatory capabilities implemented? (Yes or No) Yes A.3 Instructions for Completing the PICS Proforma An item is said to be supported for origination (ORG.
~~PAGE 325~~
A.3 Instructions for Completing the PICS Proforma CCITT X.400: P7 for MHS For parameters, the supported Value shall be declared in the corresponding column when a “____” is present (see note 2). The Note column has to be read as follows: Symbol Meaning in Note Column nxx Refers to note nxx pxx Refers to predicate cxx #yy Refers to section A.5.6.yy PHY Physical Delivery element SEC Security element Tandem Implementation Note. OSI/MHS does not provide any kind of user agent.
~~PAGE 326~~
~~A.3 Instructions for Completing the PICS Proforma CCITT X.~~
~~PAGE 327~~
A.4 Abbreviations CCITT X.400: P7 for MHS A.4 Abbreviations The following abbreviations are used in this PICS proforma: O Origination R Reception D Defined in this document I Implemented A.5 Capabilities and Options A.5.
~~PAGE 328~~
A.5.2 Supported Application Contexts CCITT X.400: P7 for MHS A.5.2 Supported Application Contexts A.5.2 Application Context Name D UA D MS 1 ms-access M M Y 2 ms-reliable-access O O N Note I A.5.3 Major Capabilities A.5.3 Major Capabilities, Elements of Service D UA D MS Note I CLAUSE Reference (X.400) 1 Access Management O R M M M M Y Y B.1 2 Alternate Recipient Allowed O R O N/A M N/A Y B.3 3 Alternate Recipient Assignment O R N/A O N/A O N B.
~~PAGE 329~~
A.5.3 Major Capabilities CCITT X.400: P7 for MHS A.5.3 Major Capabilities, Elements of Service D UA D MS Note I CLAUSE Reference (X.400) 19 Latest Delivery Designation O R O N/A O N/A N B.39 20 Message Identification O R M M M M Y Y B.41 21 Multi-Destination Delivery O R O O O O Y Y B.45 22 Non-Delivery Notification O R M N/A M N/A Y B.47 23 Original Encoded Information Types O R M M M M Y Y B.54 24 Originator Requested Alternate Recipient O R O O O O N N B.
~~PAGE 330~~
A.5.3 Major Capabilities CCITT X.400: P7 for MHS D UA A.5.3 Major Capabilities, Elements of Service D MS Use of Directory I Note n1 Designation of Recipient by Directory Name O R Physical Delivery N N N N n1 CLAUSE Reference (X.400) B.24 N Additional Physical Rendition O R N B.2 Basic Physical Rendition O R N B.7 Counter Collection O R N B.16 Counter Collection with Advice O R N B.17 Delivery via Bureaufax Service O R N B.23 EMS (Express Mail Service) O R N B.
~~PAGE 331~~
A.5.4 Timers and Protocol Parameters CCITT X.400: P7 for MHS D UA A.5.3 Major Capabilities, Elements of Service D MS I CLAUSE Reference (X.400) Note Message Security Labelling O R N B.43 Message Sequence Integrity O R N B.44 Non-Repudiation of Delivery O R N B.49 Non-Repudiation of Origin O R N B.50 Non-Repudiation of Submission O R N B.51 Probe Origin Authentication O R N B.64 Proof of Delivery O R N B.65 Proof of Submission O R N B.
~~PAGE 332~~
A.5.5 Supported PDUs (Operations) CCITT X.400: P7 for MHS A.5.5.2 MSSE D UA D MS Note I 1 MessageSubmission M M 2 ProbeSubmission C M p19 Y 3 CancelDeferredDelivery C M p6 Y 4 SubmissionControl M O Tandem OSI PICS Manual–135046 17 -14 Y Y CLAUSE Reference (X.411, X.
~~PAGE 333~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.5.3 MRSE D UA D MS Note I CLAUSE Reference (X.411, X.413) 1 Summarize C M p34 Y MS 8.2 2 List C M p33 Y MS 8.3 3 Fetch C M p32 Y MS 8.4 4 Delete C M p31 Y MS 8.5 5 Register-MS M M Y MS 8.6 6 Alert C C N MS 8.7 D UA D MS I CLAUSE Reference (X.411, X.413) A.5.5.
~~PAGE 334~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.1.1 Abstract Binding Operations: MS-Bind D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.413) 2 RESULT Y 1 responder-credentials M M Y 1.1 simple M M Y 1.1.1 IA5String M O Y 1.1.2 OCTET STRING M O 1.2 strong — — 1.2.1 bind-token 1.2.1.1 token-type-identifier 1.2.1.2 token 2 available-auto-actions O O Y MS 7.1.
~~PAGE 335~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.2.1 MSSE Operations: MessageSubmission D UA D MS Note 2 RESULT 1 message-submissionidentifier M M 2 message-submission-time M M 3 content-identifier C M 4 extensions — — 4.1 type — — 4.1.1 originating-MS-certificate — — SEC 4.1.2 proof-of-submission — — SEC 4.2 criticality (depends on “type”) — — 4.
~~PAGE 336~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.1.1 MessageSubmission Envelope D UA D MS Note 1 originator-name M M #5.1 Y 2 original-encodedinformation-types M M #2.1.6 Y 3 content-type M M #2.1.7 Y 4 content-identifier O M 5 priority C M 6 per-message-indicators M M 6.1 disclosure-of-recipients C M p8 Y 6.2 implicit-conversion prohibited C M p7 Y 6.
~~PAGE 337~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.1.1 MessageSubmission Envelope D UA D MS 9 per-recipient-fields M M 9.1 recipient-name M M #5.2 Y 9.2 originator-reportrequest M M #2.1.8 Y 9.3 explicit-conversion C M p11 #2.1.10 Y 9.4 extensions O M Y 9.4.1 type M M Y 9.4.1.1 originator-requestedalternate-recipient C C p17 N 9.4.1.2 requested-deliverymethod C M p22 #2.1.9 Y 9.4.1.
~~PAGE 338~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.1.5 GlobalDomainIdentifier D UA D MS 1 country-name M M Y 1.1 x121-dcc-code O M Y 1.2 iso-3166-alpha2-code O M Y 2 administration-domainname M M Y 2.1 numeric O M Y 2.2 printable O M Y 3 private-domainidentifier C M 3.1 numeric O M Y 3.2 printable O M Y Note p28 I CLAUSE Reference (X.411) Value Supported CLAUSE Reference (X.
~~PAGE 339~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.1.6 EncodedInformationTypes D UA D MS 2.2.5 private-use O M Y 2.3 g4-class-1-and-mixedmode O M Y 3 external-encodedinformation-types O M Y Note Permit Range of Value UA MS I A.5.6.2.1.7 Content Type D UA D MS 1 built-in M M Y 1.1 unidentified O M Y 1.2 external O M Y 1.3 interpersonal-84 O M Y 1.4 interpersonal-88 O M Y 2 external O M Y A.
~~PAGE 340~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.2.1.10 Conversion D UA D MS Note Permit Range of Value UA MS I 1 From Telex to 1.2 ia5-text O O N 1.3 teletex O O N 1.4 g3-facsimile O O N 1.5 g4-class-1 O O N 1.7 videotex O O N 1.8 voice O O N 1.9 mixed-mode O O N 2 From ia5-text to 2.1 telex O O N 2.3 teletex O O N 2.4 g3-facsimile O O N 2.5 g4-class-1 O O N 2.7 videotex O O N 2.8 voice O O N 2.
~~PAGE 341~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.1.10 Conversion D UA D MS 6.2 ia5-text O O N 6.3 teletex O O N 6.4 g3-facsimile O O N 6.5 g4-class-1 O O N 6.7 videotex O O N 6.8 voice O O N 6.9 mixed-node O O N 7 From voice to 7.8 * voice O O N 8 From mixed mode to 8.1 telex O O N 8.2 ia5-text O O N 8.3 teletex O O N 8.4 g3-facsimile O O N 8.5 g4-class-1 O O N 8.
~~PAGE 342~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.2.2 MSSE Operations: ProbeSubmission D UA D MS Note Permit Range of Value UA MS I 3 ERRORS 1 SubmissionControl Violated M M Y 2 ElementOfServiceNotSubscribed M M Y 3 OriginatorInvalid M M Y 4 RecipientImproperlyspecified M M Y 5 InconsistentRequest M M Y 6 SecurityError — — 7 UnsupportedCritical Function M M 8 RemoteBindError C C Value Supported CLAUSE Reference (X.
~~PAGE 343~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.2.2.1.1 ProbeSubmissionEnvelope D UA D MS Note Permit Range of Value UA MS I 7.1.3 conversion-withlossprohibited C C p4 7.1.4 originator-certificate — — SEC 7.1.5 message-securitylabel — — SEC 7.1.6 content-correlator O O 7.1.7 probe-originauthentication-check — — 7.2 criticality (depends on “type”) M M Y 7.3 value (depends on “type”) M M Y Y Value Supported CLAUSE Reference (X.
~~PAGE 344~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.2.3 MSSE Operations: CancelDeferredDelivery D UA D MS 2 M M RESULT (EMPTY) A.5.6.2.3 MSSE Operations: CancelDeferredDelivery Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.
~~PAGE 345~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.2.4 MSSE Operations: SubmissionControl D UA D MS Note 1.2.3 other-security-labels — — SEC 1.3 waiting-content-types O M #2.1.7 Y 1.4 waiting-encodedinformation-types O M #2.1.6 Y A.5.6.2.
~~PAGE 346~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 4.2.1 type M M Y MS 8.2.2 4.2.2 value (depends on “type”) M M Y MS 8.2.2 4.2.3 count M M Y MS 8.2.2 A.5.6.3.1 MRSE Operations: Summarize D UA D MS Note Note Permit Range of Value UA MS Value Supported CLAUSE Reference (X.411) A.5.6.3.1 MRSE Operations: Summarize I Value Supported I CLAUSE Reference (X.411) 3 ERRORS MS 8.2 1 AttributeError M M Y MS 9.
~~PAGE 347~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.1 MRSE Operations: Summarize D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) 5 FILTER MS 8.1.2.1 1 item M M Y MS 8.1.2.2 1.1 equality M M Y MS 8.1.2.3 1.1.1 type M M Y MS 6.3.3.2 1.1.2 value (depends on “type”) M M Y MS 6.3.3.3 1.2 substrings O M Y MS 8.1.2.2 1.2.1 type M M Y MS 6.3.3.2 1.2.2 strings M M Y MS 8.1.2.2 1.2.2.
~~PAGE 348~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 3.1 type M M Y MS 8.1.4 3.2 from O M Y MS 8.1.4 3.3 count O M Y MS 8.1.4 D UA A.5.6.3.2 MRSE Operations: List Note D MS Note I Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) A.5.6.3.2 MRSE Operations: List Value Supported CLAUSE Reference (X.411) 2 RESULT 1 next M M Y MS 8.3.2 2 requested M M Y MS 8.1.5 2.
~~PAGE 349~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 2.1 search O M Y MS 8.1.3 2.2 precise M M Y MS 6.3.2 3 requested-attributes M M Y MS 8.1.4 3.1 type M M Y MS 8.1.4 3.2 from O M Y MS 8.1.4 3.3 count O M Y MS 8.1.4 A.5.6.3.3 MRSE Operations: Fetch D UA D MS Note Note Permit Range of Value UA MS I I Value Supported CLAUSE Reference (X.411) A.5.6.3.
~~PAGE 350~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.4 MRSE Operations: Delete D UA D MS Note Permit Range of Value UA MS Value Supported I CLAUSE Reference (X.411) 1 ARGUMENT MS 8.5 1 information-base-type O M Y MS 6.3.1 1.1 stored-messages O M Y MS 6.3.1 1.2 inlog O O N MS 6.3.1 1.3 outlog O O N MS 6.3.1 2 items M M Y MS 8.5.1 2.1 selector O M Y MS 8.1.3 2.2 sequence-numbers M M Y MS 6.3.2 A.5.6.3.
~~PAGE 351~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 2.1 type M M N MS 6.5.2 2.2 registration-identifier M M N MS 6.5.2 2.3 registration-parameter (depends on “type”) M M N MS 6.5.3 3 list-attribute-defaults M M Y MS 6.3.3.2 4 fetch-attribute-defaults M M Y MS 6.3.3.2 5 change-credentials M M Y MS 8.6.1 5.1 old-credentials M M Y MTS 12 5.1.1 simple M M Y MTS 5 5.1.1.
~~PAGE 352~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.5 MRSE Operations: Register-MS D UA D MS Note Permit Range of Value UA MS Value Supported I CLAUSE Reference (X.411) MS 8.6.2 2 RESULT (EMPTY) M A.5.6.3.5 MRSE Operations: Register-MS D UA M D MS Y Note Permit Range of Value UA MS Value Supported I CLAUSE Reference (X.413) 3 ERRORS MS 8.6 1 Attribute Error M M Y MS 9.2 2 AutoActionRequestError M M Y MS 9.
~~PAGE 353~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.6 MRSE Operations: Alert 3 ERRORS 1 Security Error D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.413) MS 8.7 — — SEC Y Permit Range of Value UA MS MS 9.8 D UA D MS 1 child-sequence-number M M Y MS 11.2.1 2 content M M Y MS 11.2.2 3 content-confidentialityalgorithm-identifier — — N MS 11.2.3 4 content-correlator O O N MS 11.2.
~~PAGE 354~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.7 MRSE Operations: MS Attributes D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.413) 22 message-originauthentication-check — — SEC MS 11.2.22 23 message-security-label — — SEC MS 11.2.23 24 message-submissiontime O O* 25 message-token — — SEC 26 original-eits O O #3.7.19.7 N MS 11.2.26 27 originator-certificate — — SEC N MS 11.2.
~~PAGE 355~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.7.19 MessageDeliveryEnvelope D UA D MS Note #3.7.19.4 Permit Range of Value UA MS I 1 message-deliveryidentifier M M 2 message-deliverytime M M Y 3 other-fields M M Y 3.1 content-type M M #3.7.19.7 Y 3.2 originator-name M M #5.2 Y 3.3 original-encodedinformation-types M M #3.7.19.6 Y 3.4 priority M M Y 3.5 delivery-flags identifier M M Y 3.6 other-recipient-names C C 3.
~~PAGE 356~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.7.19 MessageDeliveryEnvelope D UA D MS Note Permit Range of Value UA MS I 3.15.10 physical-deliveryreport-request — — PHY 3.15.11 originator-certificate — — SEC 3.15.13* message-token — — SEC 3.15.14 content-confidentialityalgorithm-identifier — — SEC 3.15.15 content-integritycheck — — SEC 3.15.16 message-originauthentication-check — — SEC 3.15.17 message-securitylabel — — SEC 3.
~~PAGE 357~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS Value Suppo rted CLAUSE Reference (X.411) Value Supported CLAUSE Reference (X.411) A.5.6.3.7.19.5 GlobalDomainIdentifier D UA D MS 2.1 numeric M M Y 2.2 printable M M Y 3 private-domain-identifier M M Y 3.1 numeric M M Y 3.2 printable M M Y A.5.6.3.7.19.6 EncodedInformationTypes D UA D MS 1 built-in-encodedinformation-types M M 1.1 undefined O M 1.
~~PAGE 358~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.7.19.7 ContentType D UA D MS 1 built-in M M 1.1 unidentified O M 1.2 external O M 1.3 interpersonal-84 O M 1.4 interpersonal-88 O M 2 external O M Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) Tandem Implementation Note. This page describes MTS Access Protocol (P3), which is not supported by OSI/MHS. A.5.6.3.2.7.
~~PAGE 359~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.2.7.35 ReportDeliveryEnvelope D UA D MS Note 3.2 non-delivery-diagnosticcode O M 4 delivered-encodedinformation-types C C p26 5 originally-intendedrecipient-name C C p26 6 supplementary-information O O 7 extensions O O 7.1 type M M 7.1.1 redirection-history O O intended-recipient-name M M redirection-reason M M 7.1.2 physical-forwarding-address — — PHY 7.1.
~~PAGE 360~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 1.3.1 type M M N MS8.1.4 1.3.2 from O M N MS8.1.4 1.3.3 count O M N MS8.1.4 A.5.6.3.9 MRSE Operations: Errors D UA Note D MS Note Permit Range of Value UA MS Value Supported CLAUSE Reference (X.411) A.5.6.3.8 MRSE Operations: Auto-Actions I I Value Supported CLAUSE Reference (X.411) 1 AttributeError MS 9.2 1 problems M M Y MS 9.2 1.
~~PAGE 361~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.3.9 MRSE Operations: Errors D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) 3 DeleteError MS 9.4 1 problems M M Y MS 9.4 1.1 problem M M Y MS 9.4 1.1.1 child-entry-specified M M Y MS 9.4 1.1.2 delete-restriction-problem M M Y MS 9.4 1.2 sequence-number M M Y MS 9.4 4 FetchRestrictionError 1 problems M M Y MS 9.5 1.
~~PAGE 362~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.4 Abstract MASE Operations A.5.6.4.1 MASE Operation: Register D UA D MS Note #5.1 Permit Range of Value UA MS I 1 ARGUMENT 1 user-name O O 2 user-address O O N 2.1 x121 O O N 2.1.1 x121-address O O N 2.1.2 tsap-id O O N 2.2 presentation O O N 3 deliverable-encodedinformation-types O O 4 deliverable-maximumcontent-length O O N 5 default-deliverycontrols O O N 5.
~~PAGE 363~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.6 Parameters Bounds A.5.6.4.1 MASE Operation: Register D UA D MS 2 M M RESULT (EMPTY) A.5.6.4.1 MASE Operation: Register D UA D MS 3 ERRORS 1 RegisterRejected M M 2 RemoteBindError C C Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) N Note Permit Range of Value UA MS Value Supported I CLAUSE Reference (X.411) Y p35 N Note.
~~PAGE 364~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.4.2 MASE Operation: ChangeCredentials UA to MS D UA D MS 3 ERRORS 1 NewCredentialsUnacceptable M M 2 OldCredentialsIncorrectlySpecified M M 3 RemoteBindError C C Note Permit Range of Value UA MS Value Supported I CLAUSE Reference (X.411) p35 Note. This section is relevant only if the Change Credentials MS to UA operation is supported. A.5.6.4.
~~PAGE 365~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS D UA D MS 1 Mnemonic OR Address O M Y X.402 clause 18 2 Numeric OR Address O M Y “ “ 3 Terminal OR Address O M Y “ “ 4 Formatted Postal OR Address — — PHY “ “ 5 Unformatted Postal OR Address — — PHY “ “ A.5.6.5.1.1.1 OR Name with Mnemonic OR Address D UA D MS Note Note Permit Range of Value UA MS I I OR Name 1 address M M Y 1.
~~PAGE 366~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.5.1.1.1 OR Name with Mnemonic OR Address D UA D MS 1.5.4 generational-qualifier O M Y 1.6 organizational-unit-names O M Y 1.6.1 OrganizationalUnitName O M Y 1.7 domain-defined-attributes O M Y 1.7.1 type M M Y 1.7.2 value M M Y 1.8 extension-attributes O O Y 1.8.1 extension-attribute-type M M Y 1.8.1.1 common-name O O Y 1.8.1.
~~PAGE 367~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.5.1.1.2 OR Name with Numeric OR Address D UA D MS Note Permit Range of Value UA MS I Value Supported CLAUSE Reference (X.411) Value Supported CLAUSE Reference (X.411) OR Name 1 address M M Y 1.1 country-name M M Y 1.1.1 x121-dcc-code O M Y 1.1.2 iso-3166-alpha2-code O M Y 1.2 administration-domainname M M Y 1.2.1 numeric O M Y 1.2.2 printable O M Y 1.
~~PAGE 368~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.5.1.1.3 OR Name with Terminal OR Address D UA D MS 1.6.1 type O M Y 1.6.2 value O M Y 1.7 extension-attributes O O Y 1.7.1 extension-attributes-type M M Y 1.7.1.1 extended-networkaddress O O N 1.7.1.2 terminal-type O O Y 1.7.2 extension-attributesvalues M M Y 2 directory-name O O N 3 Extension Data Types Note I Value Supported CLAUSE Reference (X.
~~PAGE 369~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.5.1.2.1 OR Name with Mnemonic OR Address D UA D MS 1.2.1 numeric M M Y 1.2.2 printable M M Y 1.3 private-domain-name M M Y 1.3.1 numeric M M Y 1.3.2 printable M M Y 1.4 organization-name M M Y 1.5 personal-name M M Y 1.5.1 surname M M Y 1.5.2 given-name M M Y 1.5.3 initials M M Y 1.5.4 generational-qualifier M M Y 1.
~~PAGE 370~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.5.1.2.1 OR Name with Mnemonic OR Address D UA D MS 3.3 given-name O O N 3.4 initials O O N 3.5 generational-qualifier O O N Note I Value Supported CLAUSE Reference (X.411) Value Supported CLAUSE Reference (X.411) TeletexDomainDefinedAttributes 3.6 type O O N 3.7 value O O N * Numbering conforms to proforma. A.5.6.5.1.2.
~~PAGE 371~~
A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS Permit Range of Value UA MS A.5.6.5.1.2.3 OR Name with Terminal OR Address D UA D MS 1.2.1 numeric M M Y 1.2.2 printable M M Y 1.3 network-address M M Y 1.4 terminal-identifier M M Y 1.5 private-domain-name C C 1.5.1 numeric M M Y 1.5.2 printable M M Y 1.6 domain-definedattributes M M Y 1.6.1 type O O Y 1.6.2 value M M Y 1.7 extension-atrributes O O Y 1.7.
~~PAGE 372~~
~~A.5.6 Supported PDU Parameters (Operations Arguments) CCITT X.400: P7 for MHS A.5.6.~~
~~PAGE 373~~
A.5.7 Negotiation Capabilities CCITT X.400: P7 for MHS A.5.6.6 Parameters Bounds Note Permit Range of Value UA MS Value Supported 42 ub-e163-4-sub-address-length 40 — 43 ub-built-in-encoded-informationtypes 32 — 44 ub-teletex-private-use-length 128 — 45 ub-encoded-information-types 1024 — 46 ub-labels-and-redirections 256 — 47 ub-transfer 512 — 48 ub-bilateral-info 1024 — 49 ub-additional-info 1024 — A.5.7 Negotiation Capabilities N/A A.5.
~~PAGE 374~~
~~A.5.9 Multi-Layer Dependencies CCITT X.~~
~~PAGE 375~~
18 CCITT X.400: RTSE for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard 1988 CCITT X.228: RTSE Protocol Standard Version 1988 “Blue Book” Proforma PICS Proforma for the RTSE protocol, CCITT X.228-1988 Proforma Version CTS2/XMHS/MH/RTSE/PICS/V2.
~~PAGE 376~~
~~CCITT X.400: RTSE for MHS This page intentionally left blank.~~
~~PAGE 377~~
PICS for the OSI MHS 1988 RTSE Protocol CCITT X.400: RTSE for MHS PICS for the OSI MHS 1988 RTSE Protocol 1 Introduction 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).
~~PAGE 378~~
4.2 Reliable Transfer Protocol Definitions CCITT X.400: RTSE for MHS 8. RTSE-user; 9. RTSE-provider; 10. ACSE-provider; 11. monologue interaction; 12. syntax-matching-services; 13. Reliable Transfer; 14. X.410-1984 mode; and 15. normal mode. 4.2 Reliable Transfer Protocol Definitions This document uses the following terms defined in CCITT X.228: 1. reliable-transfer-protocol-machine; 2. requesting-reliable-transfer-protocol-machine; 3. accepting-reliable-transfer-protocol-machine; 4.
~~PAGE 379~~
5 Conformance Clause CCITT X.400: RTSE for MHS 5 Conformance Clause The supplier of a protocol implementation which is claimed to conform to CCITT X.228 shall complete a copy of the PICS proforma in Annex A and shall provide the information necessary to identify both the supplier and the implementation. Annex A A.1 Identifications Ref. No. Question Response 1 Date of statement 2 n 3 SCS cross reference A.1.2 Identification of the Implementation Ref. No.
~~PAGE 380~~
A.1.4 Identification of Protocol CCITT X.400: RTSE for MHS A.1.4 Identification of Protocol Ref. No. Question Response 1 Title and Reference No. RTSE 1988 X.400 Series 2 Protocol version IXth Plenary Assembly Nov. 14–25 1988 3 Implemented Defects Reports (Ref. No.) A.2 Global Statement of Conformance Ref. No. 1 Question Response Are all mandatory capabilities implemented? Y Tandem Implementation Note. “Turn-Please” APDUs are only relevant for two-way alternate (TWA) dialogue mode.
~~PAGE 381~~
A.4 Abbreviations CCITT X.400: RTSE for MHS For parameters the supported Type/Length/Value shall be declared in the corresponding columns. Note. 1. In the following tables, every leading parameter marked “m” should be supported by the IUT. Sub-parameters marked “m” should be supported if the corresponding leading parameter is supported by the IUT. 2. In the columns marked “LENGTH” or “RANGE,” the maximum length and maximum number of occurrences have been stated according to the standard.
~~PAGE 382~~
A.5.2 Supported Application Contexts CCITT X.400: RTSE for MHS A.5.2 Supported Application Contexts This section is used to specify the Application Context in which the IUT operates. Item Ref. No. Application Context Clause Ref. (X.419) D I 1 mts-transfer-protocol-1984 (P1 1984, RTSE X.410 mode) 14.1 m Y 2 mts-transfer-protocol (P1 1988, RTSE X.410 mode) 14.1 m Y 3 mts-transfer (P1 1988, RTSE Normal mode) 14.1 m Y A.5.
~~PAGE 383~~
A.5.3 Major Capabilities CCITT X.400: RTSE for MHS Item Ref. No. Capability Clause Ref. (X.228) 15 Transfer-abort 7.9.1 16 Provider-abort 7.9.2 17 User-abort 7.9.3 Originate Note or Mode Receipt D I D I m Y m Y NM XM m x Y Y m — Y — NM XM m x Y Y m — Y — Note. N1: If Two Way Alternate Dialogue Mode is supported.
~~PAGE 384~~
A.5.4 Timers and Protocol Parameters CCITT X.400: RTSE for MHS A.5.4 Timers and Protocol Parameters This section is used to specify the support by the IUT of Timers and Protocol Parameters used by the Reliable Transfer Protocol. A.5.4.1 Timers Item Ref. No. Timer Name Clause Ref. (X.228) 1 Transfer Timer 2 3 Note or Mode D I A.4.4 m Y Recovery Timer A.4.5 m Y Time Recover Timer 7.8.3.3.3 m Y A.5.4.
~~PAGE 385~~
A.5.6 Supported PDU Parameters CCITT X.400: RTSE for MHS This section is used to declare support of the RTSE PDUs for the IUT. Item Ref. No. Capability Clause Reference (X.228) 1 RTORQapdu 2 Originate Note or Mode Receipt D I D I 7.1.2.1 m Y m Y RTOACapdu 7.1.2.2 m Y m Y 3 RTORJapdu 7.1.2.3 m Y m Y 4 RTTPapdu 7.4.2 NM XM m o N N m m N N See Note 5 RTTRapdu 7.3.2 NM m Y m Y 6 RTABapdu 7.7.3.2 m Y m Y Tandem Implementation Note.
~~PAGE 386~~
A.5.6 Supported PDU Parameters CCITT X.400: RTSE for MHS A.5.6.1 RTORQapdu RTSE PDU: RTORQapdu Item Ref. No. Parameter Name Clause Reference (X.228) 1 CheckpointSize 2 3 Note or Mode ORG or REC D 7.1.4.1 ORG REC o m Y Y WindowSize 7.1.4.2 ORG REC o m Y Y DialogueMode 7.1.4.3 ORG REC ORG REC m m o m Y Y Y Y ORG REC m m Y Y NM XM Maximum Octets Length I STD Connection DataRQ — 4.1 Open 7.1.4.4 N1 ORG REC m m Y Y 4.2 Recover 7.3.8.4.5 N2 ORG REC m m Y Y 4.2.
~~PAGE 387~~
A.5.6 Supported PDU Parameters CCITT X.400: RTSE for MHS A.5.6.2 RTOACapdu RTSE PDU: RTOACapdu Item Ref. No. Parameter Name Clause Reference (X.228) 1 CheckpointSize 2 Note or Mode Maximum Octets Length ORG or REC D 7.1.5.1 ORG REC o m Y Y WindowSize 7.1.5.2 ORG REC o m Y Y 3 Dialogue DataAC — ORG REC m m Y Y 3.1 Open 7.1.5.3 N1 ORG REC m m Y Y 3.2 Recover 7.8.3.5.4 N2 ORG REC m m Y Y 3.2.1 CalledSSuser- — ORG REC m m Y Y 64 64 3.2.
~~PAGE 388~~
A.5.6 Supported PDU Parameters CCITT X.400: RTSE for MHS Note. N1: In the Association Recover procedure, the “refuseReason” can only have the values “1” (rtsBusy) and “2” (cannotRecover). (Ref. 7.8.3.6.1) N2: Not used in Association Recover procedure. (Ref. 7.8.3.6.
~~PAGE 389~~
A.5.7 Negotiation Capabilities CCITT X.400: RTSE for MHS A.5.6.4 RTTPapdu RTSE PDU: RTTPapdu Item Ref. No. Parameter Name Clause Reference (X.228) 1 Priority 7.4.4.1 Note or Mode ORG or REC D ORG REC m m I Maximum Octets Length STD. Y Y IMP. Value STD. IMP. 0:3 0:3 A.5.6.5 RTTRapdu RTSE PDU: RTTRapdu Item Ref. No. Parameter Name Clause Reference (X.228) 1 User Data Part 7.3.2 Note or Mode Maximum Octets Length ORG or REC D I ORG REC o m Y Y STD. IMP. Value STD. IMP.
~~PAGE 390~~
A.5.8 Protocol Error Handling CCITT X.400: RTSE for MHS For negotiations of checkpointsize and windowsize, refer to the declarations of implemented values for corresponding parameters of the RTORQapdu (A.5.6.1) and the RTOACapdu (A.5.6.2) and for the corresponding Default value declarations (A.5.4.2.1 and A.5.4.2.2). A.5.8 Protocol Error Handling Item Ref. No. Error Type Clause Ref. (X.228) 1 Undefined PDU parameter 2 3 Note or Mode Action D I 7.
~~PAGE 391~~
19 CCITT X.435: EDI for MHS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard CCITT X.435 Standard Version CCITT Recommendation X.
~~PAGE 392~~
~~CCITT X.435: EDI for MHS This page intentionally left blank.~~
~~PAGE 393~~
~~Conformance to International Standard Profiles (ISPs) CCITT X.~~
~~PAGE 394~~
~~CCITT X.~~
~~PAGE 395~~
20 ISO 9594: 1993 DSP for NSDS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard ISO 9594 Directory Access System Protocol 1993 (DSP) Standard Version ISO 1993 X.500 DSP Proforma 1993 X.
~~PAGE 396~~
~~ISO 9594: 1993 DSP for NSDS This page intentionally left blank.~~
~~PAGE 397~~
Introduction ISO 9594: 1993 DSP for NSDS Introduction This document has been produced to facilitate the interconnection of information processing systems to provide directory services. The set of all such systems, together with the directory information which they hold, can be viewed as an integrated whole, called the Directory.
~~PAGE 398~~
3 Definitions ISO 9594: 1993 DSP for NSDS CCITT Rec. X.519 (1993) | ISO/IEC 9594-5:1993, Information Technology — Open Systems Interconnection — The Directory: Protocol Specifications. CCITT Rec. X.520 (1993) | ISO/IEC 9594-6:1993, Information Technology — Open Systems Interconnection — The Directory: Selected Attribute Types. CCITT Rec. X.521 (1993) | ISO/IEC 9594-7:1993, Information Technology — Open Systems Interconnection — The Directory: Selected Object Classes. CCITT Rec. X.
~~PAGE 399~~
4 Abbreviations ISO 9594: 1993 DSP for NSDS • full access (DSA); This document uses the following terms: centralized DSA: a DSA that is not capable of holding knowledge information about other DSAs. Such a DSA is not capable of returning referrals. cooperating DSA: a DSA that is capable of holding knowledge references. Such a DSA is capable of returning referrals, and may also be a chaining DSA. chaining DSA: a cooperating DSA that is capable of invoking chained operations, functioning as a DSP invoker.
~~PAGE 400~~
5 Conformance ISO 9594: 1993 DSP for NSDS 5 Conformance The supplier of a DSP implementation that is claimed to conform to ISO/IEC 9594 (1993) standard 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 Directory System Protocol— Protocol Implementation Conformance Statement (PICS) Proforma A.1 Identification of the implementation A.1.
~~PAGE 401~~
A.2 Identification of the Protocol ISO 9594: 1993 DSP for NSDS A.1.3 Identification of the System Supplier and/or Test Laboratory Client Item Question 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 Response A.2 Identification of the Protocol Item Question 1 Title, Reference, No.
~~PAGE 402~~
~~A.3.1 DSA Implementation and/or System ISO 9594: 1993 DSP for NSDS A.3.1 DSA Implementation and/or System Item No.~~
~~PAGE 403~~
A.3.1 DSA Implementation and/or System ISO 9594: 1993 DSP for NSDS A.3.1.1 DSA Supported Security Levels Item No. 1 Question DSA Supported Security Level(s) (authentication mode) PS Support — Y Predicate Name Simple-DSA SmpNoPwd, SmpUnPwd — Simple-DSA SmpPrPwd — Strong-DSA Strong-Or — Strong-DSA — Strong-DSA Strong-Pr — Strong-DSA Strong-Or — Strong-DSA Strong-Or Strong-Rs — Simple-DSA SimpleDN-Pr A.3.1.2 DSA Product Category Item No.
~~PAGE 404~~
A.4 Instruction for Completing the PICS Proforma ISO 9594: 1993 DSP for NSDS Item No. Question (Note 7) PS Support Predicate Name 6 Is security level “none” for peer entity authentication supported? o.2 Y 7 Is security level “simple with distinguished name” for peer entity authentication supported? o.2 Y SimpleDN-Pr 8 Is security level “strong” for peer entity authentication supported? o.2 N Strong-Pr 9 Is security level “none” for results authentication supported? o.
~~PAGE 405~~
A.4.1 Definition of Support ISO 9594: 1993 DSP for NSDS A.4.2 Status Columns (PS) This column indicates the level of support required for conformance to the ISO/IEC standard (PS column). The values are as follows: m mandatory support is required; o optional support is permitted for conformance to the standard. If implemented it must conform to the specifications and restrictions contained in the standard.
~~PAGE 406~~
A.6 Capabilities and Options ISO 9594: 1993 DSP for NSDS A.4.5 Predicate Column The item number contained in the predicate column, if any, means that the status in the “Status” column applies only when the PICS states that one or more features identified by the item is supported. A.4.6 Item Reference Numbers Each line within the PICS proforma which requires implementation details to be entered is number at the left hand edge of the line.
~~PAGE 407~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.2 Operations and Extensibility A.6.2.1 Operations Item No.~~
~~PAGE 408~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3 Protocol Elements A.6.3.1 DirectoryBind Elements A.6.3.1.1 Directory Bind Arguments Item No. Protocol Element PS Init PS Resp Predicate Note A.6.2.
~~PAGE 409~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp N N 10 certification-path o o Note 2 11 bind-token SIGNED m m N N 12 algorithm m m N N 13 name m m N N 14 time m m N N 15 random m m N N 16 externalProcedure i i N N 17 versions m m Y Y d(v1) c1: If SimpleDN-Pr or Strong-Pr then support is m else support is o. c2: If Mode4-DSA then m else o.
~~PAGE 410~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.3 ChainedRead Elements Item No. Protocol Element PS Init PS Resp c:m c:m Predicate Note A.6.2.~~
~~PAGE 411~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 14 CommonResults m m Y Y 15 ChainingResults m m Y Y c9:If IMode3-DSA or IMode6-DSA then m else o. c10:If IMode5-DSA or IMode6-DSA then m else o.
~~PAGE 412~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.5 ChainedAbandon Elements Item No. Protocol Element PS Init PS Resp c:m c:m Predicate Note A.6.2.1/5 Support Init Support Resp N N 1 abandon 2 AbandonArgument m m N N 3 invokeID m m N N 4 AbandonResult m m N N Support Init Support Resp Y Y A.6.3.6 ChainedList Elements Item No. Protocol Element PS Init PS Resp c:m c:m Predicate Note 1 chained list A.6.2.
~~PAGE 413~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.7 ChainedSearch Elements Item No. Protocol Element PS Init PS Resp c:m c:m Predicate Note A.6.2.~~
~~PAGE 414~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 4 SIGNED AddEntryArgument o o N N 5 object m m Y Y 6 entry m m Y Y 7 targetSystem c:m c:m Y Y 8 CommonArguments m m Y Y 9 AddEntryResults m m Y Y 10 ChainingResults m m Y Y A.6.2.2/9 c9:If IMode3-DSA or IMode6-DSA then m else o.
~~PAGE 415~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.9 ChainedRemove Entry Elements Item No. Protocol Element PS Init PS Resp Support Init Support Resp 1 chained remove entry c:m c:m Y Y 2 ChainingArguments m m Y Y 3 RemoveEntryArguments m m Y Y 4 SIGNED RemoveEntryArgument o o N N 5 object m m Y Y 6 CommonArguments m m Y Y 7 RemoveEntryResults m m Y Y 8 ChainingResults m m Y Y Support Init Support Resp Y Y Predicate Note A.6.2.
~~PAGE 416~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 5 object m m N N 6 newRDN m m N N 7 deleteOldRDN m m N N 8 newSuperior c:m c:m N N 9 CommonArguments m m N N 10 ModifyDNResult m m N N 11 ChainingResults m m N N d(false) A.6.2.2/11 = NULL c9: If IMode3-DSA or IMode6-DSA then m else o.
~~PAGE 417~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.12 Errors and Parameters Item No.~~
~~PAGE 418~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp 11 exclusions m m 12 nameResolveOnMaster m m Predicate Note d(false) Support Init Support Resp N N N N c9:If IMode3-DSA or IMode6-DSA then m else o. c12:If Strong-DSA then m else o. Note 4:This parameter may be ignored unless the request is signed. Note 5:This parameter is provided for compatibility with the 1988 edition of the Directory.
~~PAGE 419~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.14 Common Results Elements Item No. Protocol Element PS Init PS Resp c:m m 1 SecurityParameters 2 performer m m 3 aliasedDereferenced m m PS Init PS Resp Predicate Support Init Support Resp N N N N d(false) Y Y Note Support Init Support Resp Y Y Note Strong-Rs c12:If Strong-DSAthen m else o. A.6.3.15 Service Controls Item No.
~~PAGE 420~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.18 Filter Elements Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 1 item m m Y Y 2 and m m Y Y 3 or m m Y Y 4 not m m Y Y PS Init PS Resp Support Init Support Resp A.6.3.19 Filter Item Elements Item No.
~~PAGE 421~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No.~~
~~PAGE 422~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.22 Chaining Argument Elements Item No.~~
~~PAGE 423~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No.~~
~~PAGE 424~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.25 Trace Information Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 1 TraceItem m m Y Y 2 dsa m m Y Y 3 targetObject m m Y Y 4 operationProgress m m Y Y 5 nameResolutionPhase m m Y Y 6 nextRDNToBeResolved m m Y Y PS Init PS Resp Support Init Support Resp A.6.3.26 AccessPoint Item No.
~~PAGE 425~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 6 issuer m m N N 7 validity m m N N 8 subject m m N N 9 subjectPublicKey m m N N 10 issuerUniqueIdentifier o o Note 6 N N 11 subjectUniqueIdentifier o o Note 6 N N 12 CertificatePair o o N N 13 forward o o N N 14 reverse o o N N c26:If A.6.3.1.1/10 or A.6.3.1.2/10 or A.6.3.
~~PAGE 426~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.29 Access Control A.6.3.29.1 Access Control Information Item No.~~
~~PAGE 427~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.3.29.3 UserClasses Item No. Protocol Element PS Init PS Resp Predicate Note Support Init Support Resp 1 UserClasses m m Y Y 2 allUsers o o Y Y 3 thisEntry o o Y Y 4 name o o Y Y 5 UserGroup o o Y Y 6 subtree o o Y Y PS Init PS Resp Predicate Support Init Support Resp c:m c:m A.6.2.2/1 Y Y A.6.3.30 Subtrees Item No.
~~PAGE 428~~
~~A.6.~~
~~PAGE 429~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.4.2 Supported Attribute Types A.6.4.2.~~
~~PAGE 430~~
~~A.6.~~
~~PAGE 431~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS If the supplied implementation supports the collective attributes claimed in item A.3.1/10 then A.6.4.2.2 is required to be answered by the supplier.
~~PAGE 432~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.4.~~
~~PAGE 433~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.4.4 Information Framework The supplier of the implementation shall indicate, in the following table, the object class, attributes , and matching rules defined in ISO/IEC 9594-2, Information Framework for which support is claimed. A.6.4.4.1 Information Framework Object Classes Item No. Object class PS Support Predicate A.6.2.2/1 1 subentry c:m Y 2 accessControlSubentry c6 Y 3 collectiveAttributeSubentry c7 N Note c6:if A.
~~PAGE 434~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.4.5.2 Subschema Administration Attributes Item No. Attribute PS Support 1 dITStructureRules m — 2 dITContentRules m — 3 matchingRules m — 4 attributeTypes m — 5 objectClasses m — 6 nameForms m — 7 matchingRuleUse m — 8 structuralObjectClass m — 9 governingStructureRule m — Predicate Note A.6.4.5.3 Subschema Administration Matching Rules None. A.6.4.6 Access Control A.6.4.6.
~~PAGE 435~~
A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.4.7.2 DSAOperational Attributes Item No. Attribute Types PS Support Predicate 1 dsaType m N 2 myAccessPoint m N 3 superiorKnowledge c:m N A.3.1/3 4 specificKnowledge c:m N A.3.1/3 5 nonSpecificKnowledge c:m N A.3.1/4b 6 supplierKnowledge c:m N A.3.1/3 7 consumerKnowledge c:m N A.3.1/3 8 secondaryShadows o N Note A.6.4.7.3 DSA Operational Matching Rules Item No.
~~PAGE 436~~
~~A.6.1 Supported Application Context ISO 9594: 1993 DSP for NSDS A.6.~~
~~PAGE 437~~
21 ISO 9594: X.500 DAP for NSDS The following information describes this PICS. See PICS Version Information on page 1-2 for a description of each item in this list: • • • • • • • • Standard ISO 9594 Directory Access System Protocol 1993 (DAP) Standard Version ISO 1993 X.500 DAP Proforma 1993 X.
~~PAGE 438~~
~~ISO 9594: X.500 DAP for NSDS This page intentionally left blank.~~
~~PAGE 439~~
Introduction ISO 9594: X.500 DAP for NSDS Introduction This document has been produced to facilitate the interconnection of information processing systems to provide directory services. The set of all such systems, together with the directory information which they hold, can be viewed as an integrated whole, called the Directory.
~~PAGE 440~~
3 Definitions ISO 9594: X.500 DAP for NSDS CCITT Rec. X.519 (1993) | ISO/IEC 9594-5:1993, Information Technology — Open Systems Interconnection — The Directory: Protocol Specifications. CCITT Rec. X.520 (1993) | ISO/IEC 9594-6:1993, Information Technology — Open Systems Interconnection — The Directory: Selected Attribute Types. CCITT Rec. X.521 (1993) | ISO/IEC 9594-7:1993, Information Technology — Open Systems Interconnection — The Directory: Selected Object Classes. CCITT Rec. X.
~~PAGE 441~~
4 Abbreviations ISO 9594: X.500 DAP for NSDS • • • • • • full access (DSA); lookup DUA; browse DUA; administrative DUA; reference resolution mode(0 and 1); enhanced authentication modes (0–7) This Document uses the following terms: centralized DSA: a DSA that is not capable of holding knowledge information about other DSAs. Such a DSA is not capable of returning referrals. cooperating DSA: a DSA that is capable of holding knowledge references.
~~PAGE 442~~
5 Conformance ISO 9594: X.500 DAP for NSDS 5 Conformance The supplier of a DSP implementation that is claimed to conform to ISO/IEC 9594 (1993) standard 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.
~~PAGE 443~~
ANNEX A ISO 9594: X.500 DAP for NSDS ANNEX A Directory System Protocol— Protocol Implementation Conformance Statement (PICS) Proforma A.1 Identification of the implementation A.1.1 Identification of PICS Item Questions 1 Date of Statement (DD/MM/YY) 2 PICS Serial Number 3 System Conformance Statement Cross Reference Response DRAFT A.1.
~~PAGE 444~~
A.2 Identification of the protocol ISO 9594: X.500 DAP for NSDS Item Question 6 Fax Number 7 E-Mail Address 8 Other information Response A.2 Identification of the protocol Item Question 1 Title, Reference, No., publication date of the protocol standard 2 Protocol Version Number 3 Implemented Addenda 4 Implemented Defect Reports (Reference No.) Response A.3 Global statement of conformance If the supplied implementation is a DSA implementation, A.3.
~~PAGE 445~~
~~A.3.1 DSA Implementation and/or System ISO 9594: X.500 DAP for NSDS A.3.1 DSA Implementation and/or System Item No.~~
~~PAGE 446~~
~~A.3.1 DSA Implementation and/or System ISO 9594: X.500 DAP for NSDS Item No.~~
~~PAGE 447~~
A.3.2 DUA Implementation and/or System ISO 9594: X.500 DAP for NSDS A.3.1.2 DSA Product Category Item No. 1 PS Support Predicate Name solitary — Y ISolitary chainer—indirect access — Y TBS chainer—full access — Y IChainFull nonchainer—direct access — Y TBS nonchainer—indirect access — Y TBS nonchainer—full access — Y TBS PS Support Predicate Name Question DSA Category A.3.2 DUA Implementation and/or System Item No.
~~PAGE 448~~
A.4 Instruction for completing the PICS Proforma ISO 9594: X.500 DAP for NSDS Item No. Question PS Support lookup — Y browse — N administrative — N PS Support 1 — Y 2 — Y Y Predicate Name A.3.2.3 DUA Miscellaneous Capabilities Item No. Question 3 Is normalization of protocol elements with UTC (part 11, clause A.4.1 of SIA) supported? — 4 Are all other miscellaneous capabilities supported? — Predicate Name A.4 Instruction for completing the PICS Proforma A.4.
~~PAGE 449~~
A.4.1 Definition of Support ISO 9594: X.500 DAP for NSDS A.4.2 Status Columns (PS) This column indicates the level of support required for conformance to the ISO/IEC standard (PS column). The values are as follows: m mandatory support is required; o optional support is permitted for conformance to the standard. If implemented it must conform to the specifications and restrictions contained in the standard.
~~PAGE 450~~
A.6 Capabilities and Options ISO 9594: X.500 DAP for NSDS A.4.5 Predicate Column The item number contained in the predicate column, if any, means that the status in the “Status” column applies only when the PICS states that one or more features identified by the item is supported. A.4.6 Item Reference Numbers Each line within the PICS proforma which requires implementation details to be entered is number at the left hand edge of the line.
~~PAGE 451~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.2 Operations and Extensibility A.6.2.1 Operations Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) 1 DirectoryBind m m Y Y 2 DirectoryUnbind m m Y Y 3 Read o m Y Y 4 Compare o m Y Y 5 Abandon o m N Y 6 List o m Y Y 7 Search o m Y Y 8 AddEntry o m Y Y 9 RemoveEntry o m Y Y 10 ModifyEntry o m Y Y 11 ModifyDN o m Y Y A.3.1/6, A.3.
~~PAGE 452~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.1.1 Directory Bind Arguments Item No. Protocol Element PS DUA PS DSA Predicate Note A.6.2.1/1 Support (DUA) Support (DSA) Y Y Y Y Y Y Y Y N N 1 DirectoryBindArg c:m c:m 2 credentials c1 c1 3 simple c:m c:m 4 name m m 5 validity c:m c:m 6 password o o Y Y 7 unprotected o.3 o.3 Y Y 8 protected o.3 o.
~~PAGE 453~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) N N 10 certification-path o o Note 3 11 bind-token SIGNED m m N N 12 algorithm m m N N 13 name m m N N 14 time m m N N 15 random m m N N 16 externalProcedure i i N N 17 versions m m Y Y d(v1) c1: If SimpleDUA or Simple-DSA or Strong-DUA or Strong-DSA then m else o. c14: If IMode4-DUA then m else o.
~~PAGE 454~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.3 Read Elements Item No. Protocol Element PS DUA PS DSA c:m c:m Predicate Support (DUA) Support (DSA) Y Y Y Y N N Y Y d({}) Y Y d(false) N N Note 1 read A.6.2.
~~PAGE 455~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.5 Abandon Elements Item No. Protocol Element PS DUA PS DSA c:m c:m Predicate Note A.6.2.1/5 Support (DUA) Support (DSA) N Y 1 abandon 2 AbandonArgument m m N Y 3 invokeID m m N Y 4 AbandonResult m m N N Support (DUA) Support (DSA) Y Y Y Y N N N N N N A.6.3.6 List Elements Item No. Protocol Element PS DUA PS DSA c:m c:m Predicate Note 1 list A.6.2.
~~PAGE 456~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.7 Search Elements Item No. Protocol Element PS DUA PS DSA c:m c:m Predicate Note A.6.2/7 Support (DUA) Support (DSA) Y Y Y Y N N Y Y 1 search 2 SearchArgument m m 3 SIGNED SearchArgument o o 4 baseObject m m 5 subset m m d(0) Y Y 6 filter o m d(and{}) Y Y 7 searchAlias m m d(true) Y Y 8 selection o m d({}) Y Y 9 pagedResults c:m c:m A.6.2.
~~PAGE 457~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) 4 object m m Y Y 5 entry m m Y Y 6 targetSystem c:m c:m N N 7 CommonArguments m m Y Y 8 AddEntryResults m m Y Y A.6.2.
~~PAGE 458~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.9 Remove Entry Elements Item No. Protocol Element PS DUA PS DSA c:m c:m Predicate Note A.6.2.1/9 Support (DUA) Support (DSA) Y Y Y Y N N 1 remove entry 2 RemoveEntryArguments m m 3 SIGNED RemoveEntryArgument o o 4 object m m Y Y 5 CommonArguments m m Y Y 6 RemoveEntryResults m m = NULL Y Y Note Support (DUA) Support (DSA) Y Y Y Y N N IMode3-DUA, IMode3-DSA A.6.3.
~~PAGE 459~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.12 Errors and Parameters Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) 1 Abandoned c:m m A.6.2.1/5 N N 2 AbandonFailed c:m m A.6.2.
~~PAGE 460~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) N N 9 referenceType o m IRefRes-DUA 10 entryOnly o m IRefRes-DUA d(true) N N 11 exclusions o m IRefRes-DUA d(false) N N 12 nameResolveOnMaster o m IRefRes-DUA d(false) N N Note 5: This parameter may be ignored unless the request is signed.
~~PAGE 461~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.14 Common Results Elements Item No. Protocol Element PS DUA PS DSA 1 SecurityParameters c2 c3 2 performer m m 3 aliasedDereferenced m m Predicate Support (DUA) Support (DSA) N N N N d(false) Y Y Note Support (DUA) Support (DSA) Y Y Note Strong-Rs c2: If Strong-DUA then m else o. c3: If Strong-DSA then m else o. A.6.3.15 Service Controls Item No.
~~PAGE 462~~
~~A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No.~~
~~PAGE 463~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.18 Filter Elements Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) 1 item o m Y Y 2 and o m Y Y 3 or o m Y Y 4 not o m Y Y PS DUA PS DSA Support (DUA) Support (DSA) c27: If not ILookup-DUA then m else o. A.6.3.19 Filter Item Elements Item No.
~~PAGE 464~~
~~A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.21 Continuation Reference Item No.~~
~~PAGE 465~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No. Protocol Element PS DUA PS DSA 4 random c20 m 5 target c22 c22 c20: c21: c22: c23: c24: c25: Predicate Note Support (DUA) Support (DSA) — — — — IMode4-DUA If the argument or result is to be signed then support of this parameter is m else o. If the argument is to be signed then support is m else o. If the implementation supports signed results then support of this parameter is m else o.
~~PAGE 466~~
~~A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.23 Certification Path Item No.~~
~~PAGE 467~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item No. Protocol Element PS DUA PS DSA Predicate Note Support (DUA) Support (DSA) 16 userFirst m m Y Y 17 userClasses m m Y Y 18 userPermissions m m Y Y 19 precedence o o Y Y 20 protectItems m m Y Y 21 grantsAndDenials m m Y Y c7: If SimpleAC-DUA or BasicAC-DUA then m else n/a. c8: If SimpleAC-DSA or BasicAC-DSA then m else n/a.
~~PAGE 468~~
~~A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.3.24.2 Protected Items Item No.~~
~~PAGE 469~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.4.1 Supported Object Classes A.6.4.1.1 Standard Object Classes The supplier of the DSA implementation shall indicate, in the table below, the selected object classes defined in ISO/IEC 9594-7 for which conformance is claimed.
~~PAGE 470~~
~~A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Index Supported object classes A.6.4.2 Supported Attribute Types A.6.4.2.~~
~~PAGE 471~~
~~A.6.1 Supported Application Context ISO 9594: X.~~
~~PAGE 472~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS Item Attribute Type Upperbound PS Support 42 owner o Y 43 roleOccupant o Y 44 seeAlso o Y 45 userPassword c12 Y 46 userCertificate c3 N 47 cACertificate c3 N 48 authorityRevocationList ?o N 49 certificateRevocationList ?o N 50 crossCertificatePair ?o N 128 Note c3:If Strong-DSA then m else o. c11:If A.6.2.2/1 (support for subentries) then m else o. c12:If A.6.3.1.1/6 or A.6.3.1.1.
~~PAGE 473~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.4.2.3 Other Supported Attribute Types The supplier of the DSA implementation is required to list any other object classes provided for which conformance is claimed in the following table: Index Attribute types Masterknowledge Time-Stamp StructureRuleTable ObjectClassTable AttributeTable A.6.4.
~~PAGE 474~~
~~A.6.1 Supported Application Context ISO 9594: X.~~
~~PAGE 475~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.4.4.2 Information Framework Attributes Item No. Attribute PS Support Predicate 1 createTimestamp m Y 2 modifyTimestamp m Y 3 creatorsName o Y 4 modifiersName o Y 5 administrativeRole m Y 6 subtreeSpecification c:m Y A.6.2.2/1 7 collectiveExclusions c:m N A.3.1/11 Note A.6.4.4.3 Information Framework Matching Rules Item No.
~~PAGE 476~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.4.6 Access Control A.6.4.6.1 Access Control Object Classes None. A.6.4.1.2 Access Control Attributes Item No. Attribute PS Support m Y Predicate 1 accessControlScheme 2 prescriptiveACI c:m Y SimpleAC-DSA or BasicAC-DSA 3 entryACI c:m N BasicAC-DSA 4 subentryACI c:m Y SimpleAC-DSA or BasicAC-DSA Note A.6.4.6.3 Access Control Matching Rules None. A.6.4.7. DSA Operational Attributes A.6.4.7.
~~PAGE 477~~
A.6.1 Supported Application Context ISO 9594: X.500 DAP for NSDS A.6.4.7.3 DSA Operational Matching Rules Item No. Attribute Types PS Support Predicate 1 accessPointMatch m N 2 masterAndShadowAccess PointsMatch o N 3 supplierOrConsumerInformation Match o N 4 supplierAndConsumerMatch c:m N A.3.1/3 PS Support Predicate Note c18: If not ISolitary then m else o. A.6.4.8 MHS Attribute Types Item No.
~~PAGE 478~~
~~A.6.1 Supported Application Context ISO 9594: X.~~
~~PAGE 479~~
A Tandem Manuals for OSI-Related Products This appendix lists and briefly describes the manuals available for the following Tandem OSI-related products: • • • • • • Tandem LAN Access Method (TLAM) Tandem X.
~~PAGE 480~~
Manuals for TLAM (Tandem LAN Access Method) Tandem Manuals for OSI-Related Products • TLAM Management Programming Manual. This manual describes the programmatic interface provided by the Tandem LAN Access Method (TLAM) for the management applications programs that run on a Tandem host and manage the TLAM subsystem. It includes a list and description of command, response, and EMS tokens. Figure A-1 shows the manual set for TLAM and the type of information contained in each manual. Figure A-1.
~~PAGE 481~~
Tandem Manuals for OSI-Related Products Manuals for X25AM (Tandem X.25 Access Method) Manuals for X25AM (Tandem X.25 Access Method) X.25 Access Method enables a NonStop system to connect to public or private data networks conforming to the CCITT X.25 recommendation. It is used by applications and terminals on a NonStop system to communicate with host computers or terminals in an X.25 network. There are six manuals in the X25AM manual set, as follows: • • Introduction to Tandem X.25 Capabilities.
~~PAGE 482~~
~~Manuals for X25AM (Tandem X.25 Access Method) Tandem Manuals for OSI-Related Products Figure A-2. X25AM Manual Set Concepts and Programming Introduction to Tandem X.~~
~~PAGE 483~~
Tandem Manuals for OSI-Related Products Manuals for OSI/TS (Tandem OSI/Transport Services) Manuals for OSI/TS (Tandem OSI/Transport Services) Tandem OSI/TS provides OSI Transport Layer services to OSI/AS applications or to user applications needing direct access to OSI transport services. It implements the connectionless network layer protocol (CLNP) for use over local area networks or (optionally) X.25 public data networks.
~~PAGE 484~~
~~Manuals for OSI/TS (Tandem OSI/Transport Services) Tandem Manuals for OSI-Related Products Figure A-3. Tandem OSI/TS Manual Set Concepts and Programming Tandem OSI/AS and OSI/TS Supp.~~
~~PAGE 485~~
Tandem Manuals for OSI-Related Products Manuals for OSI/AS (Tandem OSI/Application Services) Manuals for OSI/AS (Tandem OSI/Application Services) Tandem OSI/AS provides the services of the OSI Session Layer, Presentation Layer, and the ACSE component of the Application Layer, allowing Tandem applications to communicate with other applications in a multivendor environment. There are five manuals in the OSI/AS manual set, as follows: • • Tandem OSI/AS Programming Manual.
~~PAGE 486~~
Manuals for OSI/AS (Tandem OSI/Application Services) Tandem Manuals for OSI-Related Products Figure A-4. Tandem OSI/AS Manual Set Tandem OSI/AS Programming Manual Concepts and Programming Management Methods Tandem OSI/AS Configuration and Management Manual Tandem OSI/AS and OSI/TS Supp.
~~PAGE 487~~
Tandem Manuals for OSI-Related Products Manuals for Tandem FTAM (Tandem File Transfer, Access and Management) Manuals for Tandem FTAM (Tandem File Transfer, Access and Management) Tandem FTAM provides file transfer, access, and management functions across a heterogeneous network, in conformance with the ISO File Transfer, Access and Management (FTAM) standard.
~~PAGE 488~~
Manuals for Tandem FTAM (Tandem File Transfer, Access and Management) Tandem Manuals for OSI-Related Products Figure A-5. Tandem OSI/FTAM Manual Set Tandem OSI/FTAM Programming Guide Concepts and Programming Tandem OSI/FTAM Programming Reference Manual Tandem OSI/FTAM Configuration and Management Manual Management Methods Management Reference for Operators Tandem OSI/FTAM Responder Manual SCF Ref.
~~PAGE 489~~
Tandem Manuals for OSI-Related Products Manuals for OSI/MHS (Tandem OSI/Message Handling System) Manuals for OSI/MHS (Tandem OSI/Message Handling System) Tandem OSI/MHS is a message handling system in conformance with the CCITT X.400 recommendation. It supports the exchange of messages among diverse applications, such as electronic mail and electronic data interchange (EDI), across OSI networks.
~~PAGE 490~~
Manuals for OSI/MHS (Tandem OSI/Message Handling System) Tandem Manuals for OSI-Related Products messages) provided by OSI/MHS for the management application programs that run on a Tandem host and manage the OSI/MHS subsystem. It includes a list and description of command, response, and EMS tokens. Figure A-6 shows the manual set for OSI/MHS and the type of information contained in each manual. Figure A-6.
~~PAGE 491~~
Tandem Manuals for OSI-Related Products Manuals for NonStop Directory Services (NSDS) Manuals for NonStop Directory Services (NSDS) NSDS is the Tandem implementation of the CCITT X.500 Recommendations, equivalent to the OSI standard for directory services. NSDS complies with the 1988 version of the standard and includes some features of the 1993 recommendation. There are eight manuals in the NSDS manual set, as follows: ² Introduction to NonStop Directory Services (NSDS).
~~PAGE 492~~
~~Manuals for NonStop Directory Services (NSDS) Tandem Manuals for OSI-Related Products Figure A-7.~~