Stable Implementation Agreements for Open Systems Interconnection Protocols: Part 10 - FTAM Phase 3 Output from the December 1993 Open Systems Environment Implementors' Workshop (OIW) SIG Chair: Joe Mohen, Proginet SIG Editor: Larry Friedman, Digital Equipment Corporation PART 10 - FTAM Phase 3 December 1993 (Stable) Foreword This part of the Stable Implementation Agreements was prepared by the File Transfer, Access and Management Special Interest Group (FTAM SIG) of the Open Systems Environment Implementors' Workshop (OIW). See Part 1 - Workshop Policies and Procedures of the "Draft Working Implementation Agreements Document" for the charter. Text in this part has been approved by the Plenary of the above- mentioned Workshop. This part replaces the previously existing chapter on this subject. There is no significant technical change from this text as previously given. References to Part 9 are made in this part. Future changes and additions to this version of these Implementor Agreements will be published as change pages. Deleted and replaced text will be shown as struck. New and replacement text will be shown as shaded. ii PART 10 - FTAM Phase 3 December 1993 (Stable) Table of Contents Part 10 - File Transfer, Access and Management Phase 3 . . . 1 0 Introduction . . . . . . . . . . . . . . . . . . . . . . 1 1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Normative References . . . . . . . . . . . . . . . . . . 2 3 Status . . . . . . . . . . . . . . . . . . . . . . . . . 3 4 Errata . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 Conformance . . . . . . . . . . . . . . . . . . . . . . . 8 6 Assumptions . . . . . . . . . . . . . . . . . . . . . . . 8 7 Filestore Agreements . . . . . . . . . . . . . . . . . . 8 7.1 Document Types . . . . . . . . . . . . . . . . . . . 8 7.2 FADU Identities . . . . . . . . . . . . . . . . . . 12 7.3 Access Control Attribute . . . . . . . . . . . . . . 12 8 Protocol Agreements . . . . . . . . . . . . . . . . . . . 13 8.1 Implementation Profile M1.3 . . . . . . . . . . . . 13 8.2 Functional Units . . . . . . . . . . . . . . . . . . 13 8.3 Implementation Information Parameter . . . . . . . . 13 8.4 F-Check . . . . . . . . . . . . . . . . . . . . . . 13 8.5 Error Recovery . . . . . . . . . . . . . . . . . . . 14 8.5.1 Docket Handling . . . . . . . . . . . . . . 14 8.5.2 Parameters for Error Recovery . . . . . . . 14 8.6 Concurrency Control . . . . . . . . . . . . . . . . 15 8.6.1 Concurrency Control to whole file . . . . . 15 8.6.2 FADU Locking . . . . . . . . . . . . . . . 15 8.7 Create Password . . . . . . . . . . . . . . . . . . 15 8.8 Initiator Identity, Passwords and Account . . . . . 16 9 Range of Values for Integer-Type Parameter . . . . . . . 16 Annex A (normative) Profile Requirements List for NIST OIW FTAM Phase 3 . . . . . 18 0 Introduction . . . . . . . . . . . . . . . . . . . . . . 18 A.0.1 Conformance requirement of Base Standards . 18 A.0.2 Conformance requirement of Profiles . . . . 19 A.1 (void) . . . . . . . . . . . . . . . . . . . . . . . 21 A.2 (void) . . . . . . . . . . . . . . . . . . . . . . 21 iii PART 10 - FTAM Phase 3 December 1993 (Stable) A.3 ISO 8571 Protocol versions . . . . . . . . . . . . . 21 A.4 ISO 8571 Addenda . . . . . . . . . . . . . . . . . . 21 A.5 Defect report numbers and amendments . . . . . . . . 21 A.6 Global statement of conformance . . . . . . . . . . 22 A.7 Initiator/Responder capability . . . . . . . . . . . 22 A.8 Application Context Name details . . . . . . . . . . 22 A.9 Abstract syntaxes . . . . . . . . . . . . . . . . . 23 A.10 Virtual filestore . . . . . . . . . . . . . . . . . 24 A.10.1 File model . . . . . . . . . . . . . . . . 24 A.10.2 Attributes . . . . . . . . . . . . . . . . 25 A.10.2.1 Attribute groups . . . . . . . . . . . . . 25 A.10.2.2 Attribute values . . . . . . . . . . . . . 25 A.10.2.3 Filename detail . . . . . . . . . . . . . 27 A.10.3 File structures . . . . . . . . . . . . . . 27 A.10.3.1 Constraint sets . . . . . . . . . . . . . . 27 A.10.3.2 File and filestore actions . . . . . . . . 28 A.10.3.2.1 Filestore Actions . . . . . . . . . . . . . 28 A.10.3.2.2 File Actions . . . . . . . . . . . . . . . 29 A.10.3.2.3 Access contexts supported . . . . . . . . . 31 A.10.4 Additional Information . . . . . . . . . . 34 A.10.5 Override . . . . . . . . . . . . . . . . . 34 A.11 File protocol . . . . . . . . . . . . . . . . . . . 35 A.11.1 GraphicString support . . . . . . . . . . . 36 A.11.2 FTAM regime establishment . . . . . . . . . 36 A.11.3 FTAM regime termination (orderly) . . . . . 38 A.11.4 FTAM regime termination (abrupt) by service user . . . . . . . . . . . . . . . . . . . 38 A.11.5 FTAM regime termination (abrupt) by service provider . . . . . . . . . . . . . . . . . 38 A.11.6 File selection . . . . . . . . . . . . . . 40 A.11.7 File deselection . . . . . . . . . . . . . 40 A.11.8 File creation . . . . . . . . . . . . . . . 41 A.11.9 File deletion . . . . . . . . . . . . . . . 42 A.11.10 Read attributes . . . . . . . . . . . . . . 42 A.11.11 Change attributes . . . . . . . . . . . . . 43 A.11.12 File close . . . . . . . . . . . . . . . . 45 A.11.13 Beginning of grouping . . . . . . . . . . . 45 A.11.14 End of grouping . . . . . . . . . . . . . . 45 A.11.15 Regime recovery . . . . . . . . . . . . . . 47 A.11.16 Locate file access data unit . . . . . . . 48 A.11.17 Erase file access data unit . . . . . . . . 48 A.11.18 Read bulk data . . . . . . . . . . . . . . 49 iv PART 10 - FTAM Phase 3 December 1993 (Stable) A.11.19 Write bulk data . . . . . . . . . . . . . . 49 A.11.20 End of data transfer . . . . . . . . . . . 50 A.11.21 End of transfer . . . . . . . . . . . . . . 50 A.11.22 Cancel data transfer . . . . . . . . . . . 51 A.11.23 F-CANCEL mapping . . . . . . . . . . . . . 51 A.11.24 Restart data transfer . . . . . . . . . . . 51 A.12 Expanded PDU field andfilestore detail . . . . . . . 52 A.12.1 Implementation information detail . . . . . 52 A.12.2 Access control detail . . . . . . . . . . . 52 A.12.3 Access control element detail . . . . . . . 52 A.12.3.1 Action list detail (initiator) . . . . . . 52 A.12.3.2 Action list detail (responder) . . . . . . 52 A.12.3.3 Concurrency access term . . . . . . . . . . 53 A.12.3.4 Identity term . . . . . . . . . . . . . . . 55 A.12.3.5 Initiator access passwords . . . . . . . . 55 A.12.3.6 Responder access passwords . . . . . . . . 55 A.12.3.7 Location Term . . . . . . . . . . . . . . . 56 A.12.3.7.1 Application Entity Titles detail . . . . . 56 A.12.3.8 Access control element combinations . . . . 57 A.12.4 Service class field detail . . . . . . . . 58 A.12.5 Functional unit field detail . . . . . . . 59 A.12.6 Diagnostic field detail . . . . . . . . . . 62 A.12.7 Contents type detail . . . . . . . . . . . 64 A.12.7.1 Contents list parameter . . . . . . . . . . 64 A.12.7.2 Contents type parameter . . . . . . . . . . 64 A.12.8 FTAM Quality of service details . . . . . . 64 A.12.9 Details of shared ASE information . . . . . 64 A.12.10 Details of charging . . . . . . . . . . . . 65 A.12.11 Filestore password detail . . . . . . . . . 65 A.12.12 Create password detail . . . . . . . . . . 65 A.12.13 Concurrency control . . . . . . . . . . . . 65 A.12.13.1 Supported values . . . . . . . . . . . . . 65 A.12.13.2 Responder Default values . . . . . . . . . 68 A.12.14 FADU Locking . . . . . . . . . . . . . . . 69 A.12.15 Initiator Override . . . . . . . . . . . . 69 A.12.16 Requested Access . . . . . . . . . . . . . 69 A.12.17 Processing mode . . . . . . . . . . . . . . 70 v PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.18 Recovery mode . . . . . . . . . . . . . . . 71 A.13 Document types . . . . . . . . . . . . . . . . . . . 71 A.13.1 FTAM-1 (See 7.1) . . . . . . . . . . . . . 79 A.13.1.1 Universal class number parameter (See part 9 10.1) . . . . . . . . . . . . . . . . . . 79 A.13.1.2 String length parameter and string significance parameter combinations . . . . 79 A.13.1.3 G sets supported . . . . . . . . . . . . . 80 A.13.1.4 G and C sets supported . . . . . . . . . . 80 A.13.2 FTAM-2 (see 7.1) . . . . . . . . . . . . 81 A.13.2.1 Universal class number parameter (see part 9 10.1) . . . . . . . . . . . . . . . . . . 81 A.13.2.2 String length parameter and string significance parameter combinations . . . . 82 A.13.2.3 G sets supported . . . . . . . . . . . . . 82 A.13.2.4 G and C sets supported . . . . . . . . . . 82 A.13.3 FTAM-3 . . . . . . . . . . . . . . . . . . 83 A.13.3.1 String length parameter and string significance parameter combinations (see 7.1) . . . . . . . . . . . . . . . 84 A.13.4 FTAM-4 (see 7.1) . . . . . . . . . . . . . 84 A.13.4.1 String length parameter and string significance parameter combinations . . . . 84 A.13.5 NBS-6 . . . . . . . . . . . . . . . . . . . 86 A.13.5.1 Parameter0 . . . . . . . . . . . . . . . . 86 A.13.5.2 Parameter1 (see part 9 10.1) . . . . . . 86 A.13.5.3 Parameter2 . . . . . . . . . . . . . . . . 87 A.13.6 NBS-7 . . . . . . . . . . . . . . . . . . . 88 A.13.6.1 Parameter0 . . . . . . . . . . . . . . . . 88 A.13.6.2 Parameter1 (see part 9 10.1) . . . . . . 88 A.13.6.3 Parameter2 . . . . . . . . . . . . . . . . 89 A.13.7 NBS-8 . . . . . . . . . . . . . . . . . . . 89 A.13.7.1 Parameter0 . . . . . . . . . . . . . . . . 89 vi PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.7.2 Parameter1 (see part 9 10.1) . . . . . . 89 A.13.7.3 Parameter2 . . . . . . . . . . . . . . . . 90 A.13.8 NBS-11 . . . . . . . . . . . . . . . . . . 91 A.13.8.1 Parameter0 . . . . . . . . . . . . . . . . 91 A.13.8.2 Parameter1 (see part 9 10.1) . . . . . . 91 A.13.8.3 Parameter2 . . . . . . . . . . . . . . . . 91 A.13.9 NBS-12 (see 7.1) . . . . . . . . . . . . . 92 A.13.9.1 Universal class number parameter (see part 9 10.1) . . . . . . . . . . . . . . . . . . 92 A.13.9.2 String length parameter . . . . . . . . . . 92 A.13.9.3 String significance parameter . . . . . . . 92 A.13.9.4 Character set parameter . . . . . . . . . . 93 A.13.9.5 G sets supported . . . . . . . . . . . . . 94 A.13.9.6 G and C sets supported . . . . . . . . . . 94 Annex B (normative) Register of FTAM Objects . . . . . . . . . . . . . . . . . . 96 B.1 Introduction . . . . . . . . . . . . . . . . . . . . 96 B.2 Index of OIW FTAM Objects . . . . . . . . . . . . . 96 B.2.1 FTAM Phase 2 Defined Objects . . . . . . . 96 Annex C (normative) Document Types . . . . . . . . . . . . . . . . . . . . . . . 103 C.1 NBS-10 Random Binary Access File . . . . . . . . . . 103 C.1.1 Entry Number: NBS-10 . . . . . . . . . . . 103 C.1.2 Information objects . . . . . . . . . . . . 103 C.1.3 Scope and field of application . . . . . . 105 C.1.4 References . . . . . . . . . . . . . . . . 106 C.1.5 Definitions . . . . . . . . . . . . . . . . 106 C.1.6 Abbreviations . . . . . . . . . . . . . . . 106 C.1.7 Document semantics . . . . . . . . . . . . 106 C.1.8 Abstract syntactic structure . . . . . . . 106 C.1.9 Definition of transfer . . . . . . . . . . 106 C.1.9.1 Datatype definition . . . . . . . . . . . . 107 C.1.9.2 Presentation data values . . . . . . . . . 108 C.1.9.3 Sequence of presentation data values . . . 108 C.1.10 Transfer syntax . . . . . . . . . . . . . . 108 vii PART 10 - FTAM Phase 3 December 1993 (Stable) C.1.11 ASE Specific Specifications . . . . . . . . 109 C.1.11.1 Simplification . . . . . . . . . . . . . . 109 C.1.11.2 The READ operation . . . . . . . . . . . . 109 C.1.11.3 The REPLACE operation . . . . . . . . . . . 109 C.1.11.4 The INSERT operation . . . . . . . . . . . 109 C.2 NBS-11 Indexed File With Unique Keys . . . . . . . . 110 C.2.1 Entry Number: NBS-11 . . . . . . . . . . 110 C.2.2 Information objects . . . . . . . . . . . . 110 C.2.3 Scope and field of application . . . . . . 112 C.2.4 References . . . . . . . . . . . . . . . . 112 C.2.5 Definitions . . . . . . . . . . . . . . . . 112 C.2.6 Abbreviations . . . . . . . . . . . . . . . 112 C.2.7 Document semantics . . . . . . . . . . . . 112 C.2.8 Abstract syntactic structure . . . . . . . 115 C.2.9 Definition of transfer . . . . . . . . . . 115 C.2.9.1 Datatype definitions . . . . . . . . . . . 115 C.2.9.2 Presentation data values . . . . . . . . . 115 C.2.9.3 Sequence of presentation data values . . . 116 C.2.10 Transfer syntax . . . . . . . . . . . . . . 116 C.2.11 ASE Specific Specifications . . . . . . . . 116 C.2.11.1 Simplification . . . . . . . . . . . . . . 116 C.2.11.2 Access context selection . . . . . . . . . 117 C.2.11.3 The INSERT operation . . . . . . . . . . . 117 C.2.11.4 The EXTEND operation . . . . . . . . . . . 117 C.2.11.5 The REPLACE operation . . . . . . . . . . . 117 C.3 NBS-12 Simple Text File Document Type . . . . . . . 119 C.3.1 Entry Number: NBS-12 . . . . . . . . . . 119 C.3.2 Information objects . . . . . . . . . . . . 119 C.3.3 Scope and field of application . . . . . . 120 C.3.4 References . . . . . . . . . . . . . . . . 120 C.3.5 Definitions . . . . . . . . . . . . . . . . 120 C.3.6 Abbreviations . . . . . . . . . . . . . . . 121 C.3.7 Document semantics . . . . . . . . . . . . 121 C.3.8 Abstract syntactic structure . . . . . . . 122 C.3.9 Definition of transfer . . . . . . . . . . 123 C.3.9.1 Datatype definitions . . . . . . . . . . . 123 C.3.9.2 Presentation data values . . . . . . . . . 123 C.3.9.3 Sequence of presentation data values . . . 125 C.3.10 Transfer syntax . . . . . . . . . . . . . . 125 C.3.11 ASE Specific Specifications . . . . . . . . 125 C.3.11.1 viii PART 10 - FTAM Phase 3 December 1993 (Stable) Simplification and relaxation . . . . . . . 125 C.3.11.1.1 Simplification to FTAM-1 . . . . . . . . . 125 C.3.11.1.2 Relaxation to FTAM-2 . . . . . . . . . . . 125 C.3.11.1.3 Character set relaxation . . . . . . . . . 126 C.3.11.1.4 String length relaxation . . . . . . . . . 126 C.3.11.2 Access context selection . . . . . . . . . 126 C.3.11.3 The INSERT operation . . . . . . . . . . . 127 Annex D (normative) Constraint Sets . . . . . . . . . . . . . . . . . . . . . . . 128 D.1 NBS random access constraint set . . . . . . . . . . 128 D.1.1 Field of application . . . . . . . . . . . 129 D.1.2 Basic constraints . . . . . . . . . . . . . 129 D.1.3 Structural constraints . . . . . . . . . . 130 D.1.4 Action constraints . . . . . . . . . . . . 130 D.1.5 Identity constraints . . . . . . . . . . . 130 Annex E (normative) Abstract Syntaxes . . . . . . . . . . . . . . . . . . . . . . 131 E.1 NBS Node Name Abstract Syntax . . . . . . . . . . . 131 E.2 NBS Random Binary Access File Abstract Syntax . . . 132 E.3 NBS Simple Text Abstract Syntax . . . . . . . . . . 133 Annex F (normative) Delta Protocol Implementation Conformance Statement (PICS) Pro forma . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Annex G (normative) Amendments and Corrigenda . . . . . . . . . . . . . . . . . . 137 ix PART 10 - FTAM Phase 3 December 1993 (Stable) List of Tables Table 1 - Phase 2/Phase 3 Interworking . . . . . . . . . . . 3 Table 2 - List of Errata . . . . . . . . . . . . . . . . . . 5 Table 3 - Implementation Profiles and Document Types - FTAM- 1 Through FTAM-4 . . . . . . . . . . . . . . . . . . . . 9 Table 4 - Information objects in NBS-10 . . . . . . . . . . . 104 Table 5 - Information objects in NBS-11 . . . . . . . . . . . 111 Table 6 - Datatypes for keys . . . . . . . . . . . . . . . . 114 Table 7 - Information objects in NBS-12 . . . . . . . . . . . 119 Table 8 - Basic constraints in the NBS Random Access Constraint Set . . . . . . . . . . . . . . . . . . . . 128 Table 9 - Identity constraints in the NBS Random Access Constraint Set . . . . . . . . . . . . . . . . . . . . . 129 x Part 10 - File Transfer, Access and Management Phase 3 Editor's Note - The "NBS" designation remains in effect for document types, abstract syntaxes, and constraint sets defined in all FTAM agreements up to 1/1/89. After 1/1/89, any new functionality references the "NIST" designation. This is to reflect the change in identifying organization from "NBS" to "NIST." 0 Introduction This clause contains Implementors Agreements based on ISO 8571 File Transfer, Access and Management. These Agreements define enhancements to the Stable FTAM Implementation Agreements for OSI Protocols, Version 1, Edition 1, December 1987 (FTAM Phase 2 Agreements, NBS 500-150), including all their subsequent Errata changes through Version 4, Edition 1 (NIST Special Publication 500-183, this document part 9). Therefore it is assumed that the reader is familiar both with the contents of the base standard ISO 8571 and its underlying layers, and also with the above-mentioned NIST FTAM Phase 2 specifications. Phase 2 Agreements define six Implementation Profiles which are T1, T2, T3, A1, A2, and M1. In order to avoid ambiguity when referring to these Implementation Profiles the above designations will apply only to Phase 2 functionality, references to Phase 3 enhanced Implementation Profiles will be by the addition of a ".3," i.e., T1.3, T2.3, T3.3, A1.3, A2.3, and M1.3. The following clauses specify the functionality of OIW FTAM Phase 3: a) Clauses 1 and 8 specify the technical details of FTAM Phase 3 which are defined in addition to the functionality of FTAM Phase 2. Included is also a status overview regarding statements on Phase 2/Phase 3 compatibility and interworking; b) Annex A is a Profile Requirements List for the Implementation Profiles T1.3, T2.3, A1.3 and M1.3, summarizing all features of FTAM Phase 3, including those of FTAM Phase 2. This Profile Requirements List is fully based on the FTAM PICS Proforma ISO 8571-5; c) Annex B is an index of Object Identifiers. It is the official NIST OIW Register of NIST OIW defined FTAM objects. It contains the Object Descriptors and Object Identifiers for these objects, including a reference to the clause in the NIST OIW Stable Agreements where the respective object 1 PART 10 - FTAM Phase 3 December 1993 (Stable) is being defined; d) Annexes C, D, and E provide definitions for additional document types, constraint sets and abstract syntaxes; 1 Scope These Phase 3 Agreements specify additional functionality to the FTAM Phase 2 Agreements. These additional functions include: Further specifications of document types; Specification for Restart Data Transfer and Recovery functional units; Specification of FADU Locking functional unit; More details on Access Control and Concurrency Control. All Phase 2 systems are upward compatible to a Phase 3 system and can therefore interwork with it, if the additional functions are negotiated out (e.g., use of Recovery) or not used for the interconnection (e.g., additional features for document types). 2 Normative References Amendments and corrigenda to the base standards referenced: See annex G for a complete list of these documents. ISO 8571-1: 1988(E), Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management Part 1: General Introduction ISO 8571-2: 1988(E), Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management Part 2: Virtual Filestore Definition ISO 8571-3: 1988(E), Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management Part 3: The File Service Definition ISO 8571-4: 1988(E), Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management Part 4: File Protocol Specification 2 PART 10 - FTAM Phase 3 December 1993 (Stable) 3 Status These FTAM Phase 3 Agreements were completed December 15, 1989. No further enhancements will be made to this version (see also next clause ERRATA). The following tables summarize the functions and features which are defined for FTAM Phase 3 in addition to the FTAM Phase 2 specifications. They also state the degree of possible interworking and the backward compatibility. Table 1 - Phase 2/Phase 3 Interworking Additional requirements in FTAM phase 3 Backward compatibility to FTAM phase 2 FTAM-1: GraphicString,VisibleString full backward compatibility if FTAM-2: VisibleString the additional features of Phase 3 are not being used (character create-password parameter for Initiator sets in FTAM-1, - 2), or not requested by an Initiator (functional units) or not required by a Responder (parameters) not requested by an Initiator (functional units) Profile M1.3: Requires support of (1)-T service class including Limited File Management FU, Enhanced FM FU; TM service class including Enhanced FM FU or (2)-A service class including Limited File Management FU, Enhanced FM FU 3 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 1 - Phase 2/Phase 3 Interworking (continued) Additional optional features in FTAM phase 3 Backward compatibility to FTAM phase 2 FTAM-2: GeneralString, IA5String FTAM-4 NBS-8 in T2.3, A1.3 NBS-9 in A1.3, A2.3 NBS-10 NBS-11 NBS-12 Recovery functional unit Restart-data-transfer functional unit full backward compatibility if the FADU-locking functional unit and FADU-lock additional features of parameters in A1.3, A2.3 Phase 3 are not requested, negotiated Concurrency-control parameter for Initiator out or not being used Concurrency-control parameters for Responder create-password parameter for Responder location-field of access-control element suggested-delay term of diagnostic parameter supported conditionally on Recovery functional units 4 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 1 - Phase 2/Phase 3 Interworking (concluded) Relaxation for FTAM phase 3 Backward compatibility to FTAM phase 2 Profiles A1.3, A2.3 do not require transfer if T service class not service class being used no minimum requirements for maximum-string- if a Phase 3 system length parameters for document types stays below this minimum requirement 4 Errata Table 2 - List of Errata No. of Type Referenced Clause Description errata document CP Editorial NIST-SP All Update to ISO style. 3/91-1 500-183 General formatting and error corrections. Alignment with the wording of the ISP. Consistent naming conventions. CP Editorial NIST-SP 8.6.1 Previous errata 6/91-1 500-183 changed the Profile Requirements List (PRL) support of Concurrency Control A.13.9.1.2 from "m" to "o". This A.13.9.1.3 change was not A.13.9.1.4 reflected. Alignment with the ISP. 5 PART 10 - FTAM Phase 3 December 1993 (Stable) No. of Type Referenced Clause Description errata document CP Editorial NIST SP Table 4 Include "FTAM" in 9/91-1 500-183 object descriptor for consistency with Table 5 other OIW FTAM CP objects. 9/91-2 Table 8 Add definition for CP Datatype3 9/91-2 Clause 2 Delete last line of A.12.16.1 Write Whole File CP A.12.16.5 [previous change 9/91-3 A.12.17.1 incomplete]. A.12.17.5 CP Add reference to 9/91-4 corrigenda. A.13.6.1 A.13.6.2 Support level from "o" to "m". Add note C.2.7 that must support at CP C.2.9.1 least one action. Add 9/91-5 C.2.9.2 note about supporting at least one optional C.1.11.1 FU. C.2.11.1 CP C.3.11.1 Change to spelling of 9/91-6 ASN.1 text types. E.1 E.2 Changes to add E.3 Datatype3 to text CP descriptions 9/91-7 Annex B "Structural Simplification" to CP Added "Simplification" 9/91-8 Annex G Changed "will" to "can" CP 9/91-9 Added Editors note of intention to remove CP object definitions 6 PART 10 - FTAM Phase 3 December 1993 (Stable) 7 PART 10 - FTAM Phase 3 December 1993 (Stable) 5 Conformance In addition to the specific requirements specified in the following subclauses, conformance to this Phase 3 specification requires conformance to ISO 8571: 1988 conformance to Phase 2 FTAM, unless specified otherwise in this part 10. The access Profiles A1.3 and A2.3 do not include the requirement for transferring files using the File Transfer service class. 6 Assumptions FTAM Phase 3 Agreements specify additional functionality to the Implementation Profiles T1, T2, T3, A1, A2, and M1 as defined in the FTAM Phase 2 Agreements. So all definitions and requirements for these Implementation Profiles apply also to the Phase 3 Agreements. 7 Filestore Agreements 7.1 Document Types In addition to the Phase 2 Document Type Agreements the document types FTAM-4 (see ISO 8571-2, Annex B) and NBS-10, NBS-11, NBS-12 (see Annex C) are defined for optional support. Table 2 gives the support levels for all document types with respect to the Implementation Profiles. For FTAM-1, FTAM-2, FTAM-3 and FTAM-4 the supported parameter values for and , respectively are listed. Other values are outside the scope of these Agreements. No restriction or minimum requirement is defined for the parameter of these document types. 8 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 3 - Implementation Profiles and Document Types - FTAM-1 Through FTAM-4 Implementation Document Universal Class String Significance Profile Type Number (Note 1) (Notes 1,3,4,5) T1.3, T2.3, FTAM-1 GraphicString (25) `variable' 'fixed' T3.3, A1.3, VisibleString (26) `variable' 'fixed' A2.3 GeneralString (27) `not-significant' IA5String (22) `not-significant' T2.3, T3.3, FTAM-2 GraphicString (25) `not-significant' A1.3, A2.3 VisibleString (26) `not-significant' [GeneralString `not-significant' (27)] [IA5String (22)] `not-significant' T1.3, T2.3, FTAM-3 - `not-significant' T3.3, A1.3, A2.3 [T2.3], [T3.3], FTAM-4 - `not-significant' [A1.3], [A2.3] 9 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 3 - Implementation Profiles and Document Types - NBS-6 Through NBS-11 (continued) Implementation Profile Document (Note 1) Type [T2.3], T3.3, [A1.3], NBS-6 A2.3 [T2.3], T3.3, [A1.3], NBS-7 A2.3 [T2.3], T3.3, [A1.3], NBS-8 A2.3 [T1.3], [T2.3], NBS-9 [T3.3], [A1.3], [A2.3] [T2.3], [T3.3], NBS-10 [A1.3], [A2.3] [T2.3], [T3.3], NBS-11 [A1.3], [A2.3] 10 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 3 - Implementation Profiles and Document Types - NBS-12 (concluded) Implementation Document Universal Character-set String- profile (Note type class number escape significance 1) sequences as defined for reg. numbers C0 G0 G1 [T2.3], NBS-12 IA5String (parameter `variable' [T3.3], [22] absent) `fixed' [A1.3], GraphicString (parameter `variable' [A2.3] See Note 6 [25] absent) `fixed' GraphicString - 6 100 `variable' [25] `fixed' VisibleString (parameter `variable' [26] absent) `fixed' GeneralString (parameter `variable' [27] absent) `fixed' GeneralString 1 6 100 `variable' [27] `fixed' NOTES 1 Brackets around a Profile designator or a parameter value indicate that the respective document type or parameter value is optionally supported in this Implementation Profile. 2 The support level for document types in Implementation Profile M1.3 depends on the T- or A-Implementation Profile, in conjunction with which M1.3 is implemented. 3 The support for IA5 String is the ISO 646, IRV GO character set and the ISO 646, IRV CO set. 4 The minimum level of support for Graphic String is the ISO 646, IRV GO character set and the 8859-1 GO and G1 sets. 5 The minimum level of support for General String is the ISO 646, IRV GO character set and the 8859-1 GO and G1 sets, and ISO 646, IRV CO set. 6 If the Character-Set parameter is absent, the following defaults apply: 11 PART 10 - FTAM Phase 3 December 1993 (Stable) Universal-class-number Default registration numbers CO GO G1 IA5String [22] 1 2 - GraphicString [25] - 2 - VisibleString [26] - 2 - GeneralString [27] 1 2 - Registration Content Escape number Sequence 1 CO set of ISO 646 ESC 2/1 2 ISO 646, IRV 4/0 6 ISO 646, USA Version-X 3.4 - 1968 - (Left-hand part of ISO 8859-1) ESC 2/8 100 Right-hand part of Latin Alphabet 4/2 No 1 ISO 8859-1, ECMA-94 ESC 2/13 4/1 7.2 FADU Identities In addition to the Phase 2 FADU Identity Agreements the following is specified: For the document type NBS-11 used in conjunction with the Transfer service class or the Transfer and Management service class, the support of the FADU identities of "current," "next," "previous" and "end" is outside the scope of these Agreements. 7.3 Access Control Attribute The location field of access control element is optionally supported. It is the implementor's choice which combinations of fields in an access control element are supported. The ACE combination should be stated in the PICS. 12 PART 10 - FTAM Phase 3 December 1993 (Stable) 8 Protocol Agreements 8.1 Implementation Profile M1.3 The functions defined for the Implementation Profile M1.3 shall always be implemented in conjunction with one or more of the Implementation Profiles T1.3, T2.3, A1.3, or A2.3. The service classes and functional units that shall be implemented are specified in Annex A, A.12.4 and A.12.5. For an implementation supporting the Profile M1.3 in conjunction with T1.3 or T2.3, any of the service classes Transfer, Management or (Transfer, Management, Transfer-and-Management) may be requested and any of the classes Transfer, Management, Transfer-and-Management may be responded on F-INITIALIZE. For an implementation supporting the Profile M1.3 in conjunction with A1.3 or A2.3, any of the service classes Access or Management may be requested and responded on F-INITIALIZE. 8.2 Functional Units For FTAM Phase 3 implementations Recovery and Restart Data Transfer are optionally supported. FADU locking is optionally supported for Implementation Profiles A1.3 and A2.3. 8.3 Implementation Information Parameter In addition to the Agreements as specified for FTAM Phase 2, part 9 clause 12 , the following value is defined NBS-Phase3. 8.4 F-Check In order to maximize interoperability, implementations of FTAM service providers should not restrict the amount of data transmitted between successive F-CHECK requests to a single quantity. Variations in the amount of data transmitted between checkpoints may be required to accommodate differences in real end systems supporting FTAM Virtual Filestores and/or in the communications media underlying FTAM associations. It is required that all FTAM implementations are able to receive at least one PSDU between checkpoints. 13 PART 10 - FTAM Phase 3 December 1993 (Stable) 8.5 Error Recovery Procedures for Class I, II and III errors are defined and supported for FTAM Phase 3 implementations. It is the implementor's choice whether to handle class I errors using F- RESTART PDUs or whether to use the class II error procedure. 8.5.1 Docket Handling When a class III error occurs, the length of time a docket is maintained is determined by the local system. Recovery from a class III error is only possible as long as both end systems maintain the docket. It is also a local decision how many dockets can be maintained simultaneously. 8.5.2 Parameters for Error Recovery The following information is given: The semantics of the parameter is as defined in ISO 8571; including the local knowledge of FERPM; No minimum requirement for the parameter or the checkpoint size is defined; For the parameter of F-OPEN, the values "none" and "at-start-of-transfer" are supported. The value "at-any-active-checkpoint" is optionally supported. If recovery mode "at-start-of-transfer" is negotiated, no F- CHECK shall be issued. When recovering at the start of the transfer, the value of 0 shall be used; It is required that Responders implementing the Restart- data-transfer or the Recovery functional unit must be able to negotiate parameter to a value other than "none"; For the parameter of F-INITIALIZE, F-P-ABORT and F-RECOVER PDUs, the term shall be supported if the Recovery functional unit is implemented. The Basic FERPM should wait at least the amount of time as given by the term before attempting to recover. 14 PART 10 - FTAM Phase 3 December 1993 (Stable) 8.6 Concurrency Control 8.6.1 Concurrency Control to whole file If parameters are supported, details of their possible usage is a local matter and shall be specified in the PICS. Default values for concurrency control are as specified for FTAM Phase 2 Agreements. No minimum requirement is defined for parameter values. For a first accessor either the specified concurrency locks or the default values are assigned. For a subsequent accessor the access to a file is granted only if this concurrency control requirement, as specified in this concurrency control parameter or given by the default values, can be met. Otherwise the subsequent request shall be rejected. 8.6.2 FADU Locking FADU locking functional unit and the respective parameters are optionally supported for the Implementation Profiles A1.3 and A2.3. It is understood that ISO 8571-4 Clause 18.4 also applies to FADU locks; that means that as long as a docket is maintained, FADU locks locking any FADUs recorded in that docket should be maintained. 8.7 Create Password The parameter for an implementation acting as an Initiator is supported. This parameter is optionally supported for an implementation acting as a Responder. 15 PART 10 - FTAM Phase 3 December 1993 (Stable) 8.8 Initiator Identity, Passwords and Account An Initiator must be capable of sending and not sending the parameters , , and to satisfy the requirements of the Responder. The contents of the , , , and parameters shall be in the convention of the responding implementation. 9 Range of Values for Integer-Type Parameter In addition to the parameters specified for FTAM Phase 2 under the same heading, the parameters F-RECOVER request bulk-transfer-number NBS-AS3 NBS-Node-Name starting-fadu fadu-count may be encoded so that the length of its contents octets is no more than eight octets. The following Editor's notes refer to Annex A: Editor's Note - The page numbering of the PICs tables may not be aligned with the text of this document. The reason for this problem is that the PICs tables are coded using a different wordprocessor. The tables are being converted, but until this is completed the page numbering, and format of the tables may be aligned with the text of this document. In the event of a discrepancy becomming apparent in the body of these agreements and the tables in this annex, this annex is to take precedence. Editor's Note - Delete lines A.13.9.1.2, A.13.9.1.3, A.13.9.1.4, when the PICS tables are converted to WordPerfect Version 5.1 format. Editor's Note - Change table A.5 to reference Annex G. See ISO/IEC ISP 10607-4:1990 A.5. When Annex A is converted to Wordperfect V5.1. Editor's Note - A.12.16.1, A.12.16.5, A.12.17.1, and 16 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.17.5 replace the "o" with "m" in the A1.3 column. Add a note to tables A.12.16 and A.12.17 "For the profile A1.3, the support of at least one of insert, replace, or extend is required." Also add a note to tables A.12.16 and A.12.17 " For profiles T1.3 and T2.3, the support of at least one of read, insert, replace or extend is required." When Annex A is converted to WordPerfect V5.1. Editor's Note - A.13.6.1, and A.13.6.2 change parameter names to "Universal time," "Generalized time," "IA5String," "Boolean," "Bit," "Integer." When Annex A is converted to WordPerfect V5.1. 17 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex A (normative) Profile Requirements List for NIST OIW FTAM Phase 3 0 Introduction This annex to NIST FTAM Phase 3 Agreements defines a Profile Requirements List (PRL) for the Implementation profiles: T1.3 - Simple File Transfer T2.3 - Positional File Transfer A1.3 - Simple File Access M1.3 - Management This annex specifies the constraints and characteristics of NIST OIW FTAM Phase 3 on what shall or may appear in the supplier columns of an FTAM Phase 3 PICS. This annex is completely based on ISO 8571-5. It uses only a selection of the tables from ISO 8571-5 which are necessary for the specification of the FTAM Phase 3 status, and retains their numbering, in order to facilitate for a supplier to fill in the respective PICS Proforma. This annex is a summary of all definitions of FTAM Phase 3 as they appear in the Stable Implementation Agreements for OSI Protocols, Version 5 Edition 1, December 1991, parts 9 and 10. A.0.1 Conformance requirement of Base Standards The D-column of clauses A.1 to A.13 specifies the conformance requirement of the base standards ISO 8571, as written in ISO 8571-5. The definitions apply as defined in ISO 8571-5, clause 8.1: m - mandatory support o - optional support f - full support of attributes p - partial support of attributes - - not applicable A single value in the D-column applies to the Initiator role of a system as well as to the Responder role. If two values are specified in the D-column separated by a space, they apply to the Initiator (I) role and to the Responder (R) role, respectively. 18 PART 10 - FTAM Phase 3 December 1993 (Stable) A.0.2 Conformance requirement of Profiles The Conformance requirement of the Implementation Profiles is specified in the "Profiles" column/columns in clauses A.1 to A.13. The following convention is applied for this purpose: a "PROFILES" column is valid for all Profiles T1.3, T2.3 and M1.3 if different conformance requirements apply to different Profiles, separate columns are included in the tables, each bearing the corresponding Profile name as its heading, or separate tables for these Profiles are used a single value in these columns applies to the Initiator as well as to the Responder role of an implementation if two values are specified in a column separated by a space, they apply to the Initiator (I) role and to the Responder (R) role, respecitvely. For the conformance requirements of the NIST FTAM Phase 3 Profiles the following abbreviations are used. mandatory; m: This is a mandatory or optional feature in the base standard. It shall be supported, i.e., its syntax and procedures shall be implemented as specified in the base standard or in FTAM Phase 3 by all implementations claiming conformance to the Profile. However, it is not a requirement that the feature shall be used in all instances of communication, unless mandated by the base standard or stated otherwise in FTAM Phase 3. Also for features which are optional in the base standard, conformant implementations shall be able to interwork with other implementations not supporting this feature. The support of a feature can be conditional, depending on the support of a class of features to which it belongs, e.g., an attribute in an attribute group, a parameter in a PDU, a PDU in a functional unit. optional; o: It is left to the implementation as to whether this feature is implemented or not. 19 PART 10 - FTAM Phase 3 December 1993 (Stable) If an attribute group with a support level of "o" is chosen to be supported, then all the attributes in this group that are classified as "m" shall be suppported. The support for PDUs is determined by the negotiation of functional units when the connection is established. If a parameter is optionally supported, then its syntax shall be implemented, but it is left to each implementation whether its procedures are implemented or not. When receiving an optional parameter which is not subject of negotiation and is not supported by the Receiver, the Receiver shall at least inform the Sender by informative diagnostic land interworking shall not be disrupted. conditional;c: This feature shall be supported under the conditions specified in FTAM Phase 3. If these conditions are not met, the feature is outside the scope of the Profile. excluded; x: This feature is excluded from the Profile. The implementor's answer in the PICS shall always be "no." outside the scope; i: This feature is outside the scope of the Profile, i.e., it many be ignored, and will therefore not be subject of a Profile conformance test. However, the syntax of all parameters of supported PDUs shall be implemented, even if their procedures are not (i.e., the Receiver shall be able to decode the PDU). not applicable; -: This feature is not defined in the context where it is mentioned, e.g., a parameter which is not part of the respective PDU. The occurrence of "not applicable" features is mainly due to the format of the tables in the Phase 3 Profiles Requirements List. 20 PART 10 - FTAM Phase 3 December 1993 (Stable) Section 1 A.1 (void) A.2 (void) Section 2: General ISO 8571 Detail A.3 ISO 8571 Protocol versions 1 FTAM protocol version-1 version number(s) A.4 ISO 8571 Addenda 1 ISO 8571-1 - 2 ISO 8571-2 - 3 ISO 8571-3 - 4 ISO 8571-4 - 5 ISO 8571-5 - A.5 Defect report numbers and amendments 1 ISO 8571-1 - 2 ISO 8571-2 - 3 ISO 8571-3 - 4 ISO 8571-4 - 21 PART 10 - FTAM Phase 3 December 1993 (Stable) 5 ISO 8571-5 - A.6 Global statement of conformance 1 Does FTAM Phase 3 yes conform to ISO 8571? A.7 Initiator/Responder capability ROLES D PROFILES I R 1 Sender o o o 2 Receiver o o o NOTE - See part 9, 18.1. A.8 Application Context Name details 1 ISO 8571-4 defines a value for a simple transfer mechanism. Other values are not defined for FTAM Phase 3 (see part 9 5.9). 22 PART 10 - FTAM Phase 3 December 1993 (Stable) Section 3: Syntax Detail A.9 Abstract syntaxes Object Object Identifier D T1. T2. A1 M1 Descriptor 3 3 .3 .3 1 FTAM PCI {iso standard 8571 m m m m m abstract-syntax(2) ftam-pci(1) } 2 FTAM FADU {iso standard 8571 o i m m i abstract-syntax(2) ftam-fadu(2) } 3 {joint iso ccitt m m m m m association-control(2) abstract-syntax(1) apdus(0) version1(1) } 4 FTAM {iso standard 8571 o m m m - unstructure abstract-syntax(2) d unstructured-text(3) } text abstract syntax 5 FTAM {iso standard 8571 o m m m - unstructure abstract-syntax(2) d unstructured-binary(4) binary } abstract syntax 6 NBS file {iso identified- - c c c - directory organization oiw(14) entry ftamsig(5) abstract- abstract syntax(2) nbs-as2(2) } syntax 7 NBS {iso identified- - i c c - abstract organization oiw(14) syntax AS1 ftamsig(5) abstract- syntax(2) nbs-as1(1) } 8 NBS random {iso identified- - i c c - access organization oiw(14) node name ftamsig(5) abstract- abstract syntax(2) nbs-node- See Clause 9 syntax name(3) } 23 PART 10 - FTAM Phase 3 December 1993 (Stable) 9 NBS random {iso identified- - i c c - binary organization oiw(14) access file ftamsig(5) abstract- abstract syntax(2) nbs-random- syntax binary(4) } 10 NBS simple {iso identified- - i c c - text organization oiw(14) abstract ftamsig(5) abstract- syntax syntax(2) nbs-simple- text(5) } NOTES 1 The abstract syntaxes which are supported in the Implementation Profile M1.3 depend on the T-or A-Profile in conjunction with which M1.3 is implemented. 2 The support requirements for the conditional abstract syntaxes depend on the constraint sets and document types which are implemented (see clause A.13). 3 ISO 8571 requires the presence of the transfer syntax derived fromthe "Basic Encoding of a single ASN.1 type" "{joint-iso-ccitt asn1 (1) basic-encoding (1)} encoding rules fortransfer of the "FTAM-FADU" abstract syntaxes. Implementation detail of this transfer syntax, and other transfer syntaxes supported, is specified in the PICS of ISO 8823. Section 4: Virtual Filestore Detail A.10 Virtual filestore This clause details the conformance to the file model, file attribute support and to file structure support. A.10.1 File model 24 PART 10 - FTAM Phase 3 December 1993 (Stable) FILE MODEL D PROFILES R 1 Hierarchical o m Other models i A.10.2 Attributes A.10.2.1 Attribute groups ATTRIBUTE GROUP D PROFILE NAME S 1 Kernel m m 2 Storage o o 3 Security o o 4 Private o i A.10.2.2 Attribute values KERNEL D PROFILES GROUP(INITIATOR) I full RANGE OF VALUES 1 Filename f m see A.10.2.3 2 Permitted Actions f m 3 Contents Type f m see A.12.7 KERNEL GROUP D (RESPONDER) PROFILES RANGE OF R full VALUES 4 Filename f m see A.10.2.3 5 Permitted Actions f m 6 Contents Type f m see A.12.7 25 PART 10 - FTAM Phase 3 December 1993 (Stable) STORAGE GROUP D PROFILES (INITIATOR) I full RANGE OF VALUES 7 Storage account f m 8 File availability f m 9 Future filesize f m see part 9, 17.9 NOTE - An initiator shall not partially support attributes STORAGE GROUP D PROFILES (RESPONDER) R full RANGE OF R partial VALUES 10 Storage account p o o 11 Date and time of p o o creation 12 Date and time of p o o last modification 13 Date and time of p o o last read access 14 Date and time of p o o last attribute modification 15 Identity of p o o creator 16 Identity of last p o o modifier 17 Identity of last p o o reader 18 Identity of last p o o attribute modifier 19 File availability p m x 20 Filesize p m x see part 9 17.9 21 Future filesize p o o see part 9 17.9 26 PART 10 - FTAM Phase 3 December 1993 (Stable) SECURITY GROUP D PROFILES (INITIATOR) I full RANGE OF VALUES 22 Access control f m see A.12.2 23 Legal f m qualifications NOTE - An initiator shall not partially support attributes SECURITY GROUP D PROFILES (RESPONDER) R full RANGE OF R partial VALUES 24 Access control p m x see A.12.2, part 9, 9.2 25 Legal p o o qualifications A.10.2.3 Filename detail See part 9 9.1 A.10.3 File structures A.10.3.1 Constraint sets 27 PART 10 - FTAM Phase 3 December 1993 (Stable) CONSTRAINT SET NAME D T1.3 T2.3 A1.3 M1. 3 1 Unstructured o m m m - 2 Sequential Flat o i m m - 3 Ordered flat o i o o - 4 Ordered flat with unique o i o o - names 5 Ordered hierarchical o i i i - 6 General hierarchical o i i i - 7 General hierarchical o i i i - with unique names 8 NBS ordered flat - i o o - 9 NBS random access - i o o - access A.10.3.2 File and filestore actions A.10.3.2.1 Filestore Actions Support for filestore actions is dependent upon the functional units implemented (see A.12.4 and A.12.5) 28 PART 10 - FTAM Phase 3 December 1993 (Stable) A.10.3.2.2 File Actions CONSTRAINT SET RESPONDER unstructured ACTION D T1.3 1 Locate --- --- 2 Read o o 3 Insert --- --- 4 Replace o o 5 Extend o o 6 Erase o i CONSTRAINT SET Respon unstruct sequent ordered ordered NBS NBS der ured ial flat flat ordere random flat with d access unique flat names Action D D T2. D T2. D T2. D T2. D T2. T2. 3 3 3 3 3 3 7 Locate -- -- o i o i o i - i -- i - 8 Read o o o o o o o o - o -- o - 9 Insert -- -- o o o o o o - o -- o - 1 Replace o o -- -- o o o o - o -- o 0 - 1 Extend o o -- -- o o o o - -- -- -- 1 - 29 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 Erase o i o i o i o i - i -- i 2 - 30 PART 10 - FTAM Phase 3 December 1993 (Stable) CONSTRAINT SET Respon unstruct sequent ordered ordered NBS NBS der ured ial flat flat ordere random flat with d access unique flat names Action D D A1. D A1. D A1. D A1. D A1. A1. 3 3 3 3 3 3 1 Locate -- -- o o o o o o - o -- o 3 - 1 Read o o o o o o o o - o -- o 4 - 1 Insert -- -- o o o o o o - o -- o 5 - 1 Replace o o -- -- o o o o - o -- o 6 - 1 Extend o o -- -- o o o o - -- -- -- 7 - 1 Erase o o o o o o o o - o -- o 8 - NOTE - File actions are not defined in implementation Profile M1.3 A.10.3.2.3 Access contexts supported CONSTRAINT SET RESPONDER unstructured ACCESS CONTEXT D T1.3 1 US -- -- 2 UA o m 3 FS -- -- 4 FL -- -- 31 PART 10 - FTAM Phase 3 December 1993 (Stable) 5 FA -- -- 6 HN -- -- 7 HA -- -- 32 PART 10 - FTAM Phase 3 December 1993 (Stable) CONSTRAINT SET Respon unstruct sequent ordered ordered NBS NBS der ured ial flat flat ordere random flat with d access unique flat names Access D D T2. D T2. D T2. D T2. D T2. Contex T2. 3 3 3 3 3 t 3 8 US -- -- -- -- -- -- -- -- - -- -- -- - 9 UA o m o m o m o m - m -- m - 1 FS -- -- -- -- -- -- -- -- - -- -- -- 0 - 1 FL -- -- -- -- -- -- -- -- - -- -- -- 1 - 1 FA -- -- o m o m o m - m -- -- 2 - 1 HN -- -- -- -- -- -- -- -- - -- -- -- 3 - 1 HA -- -- -- -- o o o o - o -- -- 4 - CONSTRAINT SET Respon unstruct sequent ordered ordered NBS NBS der ured ial flat flat ordere random flat with d access unique flat names Access D D A1. D A1. D A1. D A1. D A1. Contex A1. 3 3 3 3 3 t 3 1 US -- -- -- -- -- -- -- -- - -- -- -- 5 - 33 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 UA o m o m o m o m - m -- m 6 - 1 FS -- -- -- -- -- -- -- -- - -- -- -- 7 - 1 FL -- -- -- -- -- -- -- -- - -- -- -- 8 - 1 FA -- -- o m o m o m - m -- -- 9 - 2 HN -- -- -- -- -- -- -- -- - -- -- -- 0 - 2 HA -- -- -- -- o o o o - o -- -- 1 - NOTE - The supported access contexts for implementation Profile M1.3 are defined in the T- or A-Profile in conjunction with which M1.3 is implemented. A.10.4 Additional Information (Void) A.10.5 Override RESPONDER OVERRIDE D PROFILES R 1 Create failure o m 2 Select old file o m 3 Delete and recreate with o old attributes o 4 Delete and create with o new attributes m NOTE - The specification of the role of initiator is given in A.12.15. 34 PART 10 - FTAM Phase 3 December 1993 (Stable) Section 5: File Protocol Detail A.11 File protocol See part 9, 5.1 - 5.3 and 17 Subclauses A.11.2 to A.11.24 specify an indication of which PDUs are supported. The conformance requiremnts for PDUs are dependent on the particular functional units implemented. PDUs indicated in A.11.8 to A.11.24 as conditional shall be considered as mandatory when a particular functional unit is implemented, according to the following table: Functional Units PDUs Clau Ker Rea Wri Acce LF EFM Gro Rec Rest se nel d te ss M u- o- art pin ver g y F-CREATE A.11 m .8 F-DELETE A.11 m .9 F-READ- A.11 m ATTRIB .10 F-CHANGE- A.11 m ATTRIB .11 F-OPEN A.11 m m .12 F-CLOSE A.11 m m .13 F-BEGIN- A.11 m GROUP .14 F-END- A.11 m GROUP .15 F-RECOVER A.11 m .16 F-LOCATE A.11 m .17 F-ERASE A.11 m .18 35 PART 10 - FTAM Phase 3 December 1993 (Stable) F-READ A.11 m .19 F-WRITE A.11 m .20 F-DATA-END A.11 m m .21 F- A.11 m m TRANSFER- .22 END F-CANCEL A.11 m m .23 F-RESTART A.11 m .24 NOTES 1 In order to keep the protocol tables compact, some forward references have been introduced to clauses which expand upon the detail of field support. 2 The FTAM protocol will require a number of optional lower layer services to be available (e.g., Application Entity Titles in ACSE). This requirement is outside the scope of this Profiles Requirements List. A.11.1 GraphicString support (Void) A.11.2 FTAM regime establishment D PROFILE S I R I R 1 F-INITIALIZE PDU m m m m FIELD NAME RANGE OF VALUES OR REFERENCES 2 State result - m - m all values defined in ISO 8571 36 PART 10 - FTAM Phase 3 December 1993 (Stable) D PROFILE S I R I R 3 Action result - m - m all values defined in ISO 8571 4 Protocol version m m m m see section 2 5 Implementation o o o o see A.12.1 information 6 Presentation m m m m see note 1, part context management 9, 17.10 7 Service class m m m m see A.12.4 8 Functional units m m m m see A.12.5 9 Attribute groups m m m m see A.10.2 10 Shared ASE o o i i see part 9, 5.8 information 11 FTAM Quality of m m m m see A.12.8 Service 12 Contents type list o o m m see A.12.7.1, part 9 18.4 13 Initiator identity o - m - see 8.8, part 9, 16.1 and 18.4 14 Account o - o - see 8.8, part 9, 18.4 15 Filestore password o - m - see A.12.11, 8.8, part 9 16.1 16 Diagnostic - o - m see A.12.6, 8.5.2, part 9 13 17 Checkpoint window m m m m see note 2, 8.5.2 NOTES 1 The values available for the presentation context management field depend upon the functional units implemented in ISO 8823. 2 Checkpoint window field is indicated as mandatory in 37 PART 10 - FTAM Phase 3 December 1993 (Stable) accordance with ISO 8571-4. The field is defaulted to the value 1. A.11.3 FTAM regime termination (orderly) D PROFILE S I R I R 1 F-TERMINATE PDU m m m m FIELD NAME RANGE OF VALUES OR REFERENCES 2 Shared ASE o o i i see part 9 5.8 information 3 Charging - o - o see A.12.10 A.11.4 FTAM regime termination (abrupt) by service user D PROFILE S 1 F-U-ABORT PDU m m FIELD NAME RANGE OF VALUES OR REFERENCES 2 Action result all values m m defined in ISO 8571 3 Diagnostic see A.12.6, part o m 9 13 A.11.5 FTAM regime termination (abrupt) by service provider D PROFILE S 1 F-P-ABORT PDU m m FIELD NAME RANGE OF VALUES OR REFERENCES 38 PART 10 - FTAM Phase 3 December 1993 (Stable) 2 Action result all values m m defined in ISO 8571 3 Diagnostic see A.12.6, o m 8.5.2, part 9 13 39 PART 10 - FTAM Phase 3 December 1993 (Stable) A.11.6 File selection D PROFILE S I R I R 1 F-SELECT PDU m m m m FIELD NAME RANGE OF VALUES OR REFERENCES 2 State result - m - m all values defined in ISO 8571 3 Action result - m - m all values defined in ISO 8571 4 Attributes m m m m see A.10.2, part 9 17.9 5 Requested access m - m - see A.12.16 6 Access passwords o - m - see 8.8, part 9 16.2 7 Concurrency control o - o - see A.12.13, 8.6.1 8 Shared ASE o o i i see part 9, 5.8 information 9 Account o - o - see 8.8, part 9 18.4 10 Diagnostic - o - m see A.12.6, part 9 13 A.11.7 File deselection D PROFILE S I R I R 1 F-DESELECT PDU m m m m 40 PART 10 - FTAM Phase 3 December 1993 (Stable) FIELD NAME RANGE OF VALUES OR REFERENCES 2 Action result - m - m all values defined in ISO 8571 3 Charging - o - o see A.12.10 4 Shared ASE o o i i see part 9 5.8 information 5 Diagnostic - o - m see A.12.6, part 9 13 A.11.8 File creation D PROFILE S I R I R 1 F-CREATE PDU c c c c see A.11, A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 State result - m - m all values defined in ISO 8571 3 Action result - m - m all values defined in ISO 8571 4 Override m - m - see A.12.15 5 Initial attributes m m m m see A.10.2, part 9 10.2.2, 17.9 6 Create password o - m - see A.12.12, 8.7, 8.8, part 9 16.2 7 Requested access m - m - see A.12.16 8 Access passwords o - m - see 8.8, part 9 16.2 9 Concurrency control o - o - see A.12.13, 8.6.1 41 PART 10 - FTAM Phase 3 December 1993 (Stable) 10 Shared ASE o o i i see part 9 5.8 information 11 Account o - o - see 8.8, part 9 18.4 12 Diagnostic - o - m see A.12.6, part 9 13 A.11.9 File deletion D PROFILE S I R I R 1 F-DELETE PDU c c c c see A.11, A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 Action result - m - m all values defined in ISO 8571 3 Shared ASE o o i i information 4 Charging - o - o see A.12.10 5 Diagnostic - o - m see A.12.6, part 9 13 A.11.10 Read attributes D PROFILE S I R I R 1 F-DELETE PDU c c c c see A.11, A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 Action result - m - m all values defined in ISO 8571 42 PART 10 - FTAM Phase 3 December 1993 (Stable) 3 Attribute names m - m - 4 Attributes - o - m see A.10.2, part 9 17.9 5 Diagnostic - o - m see A.12.6, part 9 13 A.11.11 Change attributes D T1.3, T2.2, M1.3 A1.3 I R I R 1 F-CHANGE- c c i m m see A.11, A.12.5 ATTRIB PDU FIELD i RANGE OF VALUES OR NAME REFERENCES 2 Action - m i - m all values defined result in ISO 8571 3 Attribute m o i m m see A.10.2, part 9 s 17.9 4 Diagnosti - o i - m see A.12.6, part 9 c 13 43 PART 10 - FTAM Phase 3 December 1993 (Stable) File open T1.3, M1. D T2.3, A1.3 3 IR I R 1 F-OPEN-PDU cc m m i see A.11, A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 State result - m - m i all values defined in ISO 8571 3 Action result - m - m i all values defined in ISO 8751 4 Processing m - m - i see A.12.17 mode 5 Contents type m m m m i see A.12.7.2 6 Concurrency o o o o i see A.12.13, control 8.6.1 7 Shared ASE o o i i i see part 9 5.8 information 8 Enable FADU m - m - i `false' for locking T1.3 and T2.3 9 Activity o - o - i identifier 10 Diagnostic - m - m i see A.12.6, part 9, 13 11 Recovery mode m m m m i see A.12.18 12 Remove o - i - i contexts 13 Define o - i - i contexts 14 Presentation - m - m i see note action 44 PART 10 - FTAM Phase 3 December 1993 (Stable) NOTE - The values depend upon the functional units implemented in ISO 8823. A.11.12 File close T1.3, M1. D T2.3, A1.3 3 1 F-CLOSE-PDU c m i see A.11, A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 Action m m i all values result defined in ISO 8571 3 Shared ASE o i i see part 9 5.8 information 4 Diagnostic o m i see A.12.6, part 9 13 A.11.13 Beginning of grouping T1.3, A1. D T2.3 3 IR I I R R 1 F-BEGIN-GROUP cc m m o see A.11, PDU o A.12.5 FIELD NAME RANGE OF VALUES OR REFERENCES 2 Threshold m - m - m - A.11.14 End of grouping T1.3, T2.3 A1. D 3 1 F-END-GROUP c m o see A.11, A.12.5 PDU 45 PART 10 - FTAM Phase 3 December 1993 (Stable) The F-END-GROUP PDU carries no fields. 46 PART 10 - FTAM Phase 3 December 1993 (Stable) A.11.15 Regime recovery See 8.5 D T1.3, T2.2, M1.3 A1.3 I R I R 1 F-RECOVER c c c c i see A.11, A12.5 PDU FIELD RANGE OF VALUES OR NAME REFERENCE 2 State - m - m i all values defined result in ISO 8571 3 Action - m - m i all values defined result in ISO 8571 4 Activity m - m - i identifie r 5 Bult m - m - i see clause 9 transfer number 6 Requested m - m - i see A.12.16 access 7 Access o - m - i see 8.8 part 9 16.2 passwords 8 Contents - m - m i see A.12.7.2 type 9 Recovery m m m m i point 10 Diagnosti - o - m i see A.12.6, 8.5.2, c part 9 13 11 Remove o - i - i see notes contexts 12 Define o - i - i see notes contexts 13 Presentat - m - m i see notes ion action 47 PART 10 - FTAM Phase 3 December 1993 (Stable) NOTES 1 The values available for the presentation action field depend upon the functional units implemented in ISO 8823. 2 Presentation action field is indicated as mandoratory is accordance with ISO 8571-4. The field is defaulted to no action. A.11.16 Locate file access data unit D T1.3, A1. M1. I R T2.3 3 3 I R 1 F-LOCATE c c i m i see A.11, A.12.5 PDU m RANGE OF VALUES FIELD OR PREFERENCE NAME 2 Action - m i - i all values defined result m in ISO 8571 3 FADU m o i m i see part 9 17.9 identity o 4 FADU lock o - i o i see A.12.14 - 5 Diagnosti - o i - i see A.12.6, part 9 c m 13 A.11.17 Erase file access data unit D T1.3, A1.3 M1. I R T2.3 I R 3 1 F-ERASE c c i m m i see A.11, A.12.5 PDU FIELD RANGE OF VALUES NAME OR REFERENCE 48 PART 10 - FTAM Phase 3 December 1993 (Stable) 2 Action - m i - m i all values defined result in ISO 8571 3 FADU m - i m - i see part 9 17.9 identit y 4 Diagnos - o i - m i see A.12.6, part 9 tic 13 A.11.18 Read bulk data D T1.3, A1. M1. I R T2.3 3 3 I R I R 1 F-READ c c c c m i see A.11, A.12.5 PDU m FIELD RANGE OF VALUES NAME OR REFERENCE 2 FADU m - m - m i see part 9 17.9 identity - 3 Access m - m - m i see A10.3.2.3 context - 4 FADU lock o - i - o i - A.11.19 Write bulk data D T1.3, A1.3 M1.3 I R T2.3 I R I R 1 F-WRITE c c c c m m i see A.11, PDU A. 12.5 FIELD RANGE OF NAME VALUES OR REFERENCE 2 FADU m - m - m - i operation 49 PART 10 - FTAM Phase 3 December 1993 (Stable) 3 FADU m - m - m - i see part 9 identity 17.9 4 FADU Lock o - i - o - i A.11.20 End of data transfer D T1.3, M1.3 T2.3, A1.3 1 F-DATA-END c m i see A.11, A.12.5 PDU RANGE OF VALUES FIELD NAME OR REFERENCE 2 Action m m i all values result defined in ISO 8571 3 Diagnostic o m i see A.12.6, part 9 13 A.11.21 End of transfer D T1.3, M1. I R T2.3, A1.3 3 I R 1 F-TRANSFER- c c m m i see A.11, A.12.5 END PDU RANGE OF VALUES FIELD NAME OR REFERENCE 2 Action result - m - m i all values defined in ISO 8571 3 Shared ASE o o i i i see part 9 5.8 information 4 Diagnostic - o - m i see A.12.6, part 9 13 50 PART 10 - FTAM Phase 3 December 1993 (Stable) A.11.22 Cancel data transfer See part 9 clause 11 D T1.3, M1.3 T2.3, A1.3 1 F-CANCEL PDU c m i see A.11, A.12.5 RANGE OF VALUES FIELD NAME OR REFERENCE 2 Action result m m i all values defined in ISO 8571 3 Shared ASE o i i see part 9 5.8 information 4 Diagnostic o m i see A.12.6, part 9 13 A.11.23 F-CANCEL mapping See part 9 clauses 11 and 17.10 A.11.24 Restart data transfer D T1.3, M1.3 T2.3, A1.3 1 F-RESTART PDU c c i see A.11, A.12.5 RANGE OF VALUES FIELD NAME OR REFERENCE 2 Checkpoint m m i identifier 51 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12 Expanded PDU field andfilestore detail This clause identifies further PDU filed and filestore detail to expand on that given in A.10 and A.11. A.12.1 Implementation information detail See 8.3, part 9 5.6 and 12 A.12.2 Access control detail See 7.3, part 9 9.2 Access control RANGE OF VALUES element terms D PROFILE S 1 Action list m m 2 Concurrency o o see A.12.3.3 access 3 Identity o o 4 Passwords o o see A.12.3.5, A.12.3.6, 8.8 5 Location o o A.12.3 Access control element detail A.12.3.1 Action list detail (initiator) (Void) A.12.3.2 Action list detail (responder) 52 PART 10 - FTAM Phase 3 December 1993 (Stable) (Void) A.12.3.3 Concurrency access term If the concurrency access term is supported in the access control element the following details of the concurrency control shall be available with each action. T1.3 not shared exclusive no Action required D T1.3 D T1.3 access D D T1.3 T1.3 1 Read o o o o o o o o 2 Insert o o i o i o i i 3 Replace o o o o o o o o 4 Extend o o o o o o o o 5 Erase o o i o i o i i 6 Read o o o o o o o attributes o 7 Change o o i o i o i attributes i 8 Delete o o o o o o o file o T2.3 not shared exclusive no Action required D T2.3 D T2.3 access D D T2.3 T2.3 9 Read o o o o o o o o 10 Insert o o o o o o o o 11 Replace o o o o o o o o 53 PART 10 - FTAM Phase 3 December 1993 (Stable) 12 Extend o o o o o o o o 13 Erase o o i o i o i i 14 Read o o o o o o o attributes o 15 Change o o i o i o i attributes i 16 Delete o o o o o o o file o A1.3 not shared exclusive no Action required D A1.3 D A1.3 access D D A1.3 A1.3 17 Read o o o o o o o o 18 Insert o o o o o o o o 19 Replace o o o o o o o o 20 Extend o o o o o o o o 21 Erase o o o o o o o o 22 Read o o o o o o o attributes o 23 Change o o i o i o i attributes i 24 Delete o o o o o o o file o M1.3 not shar exclus no Action requi M1. ed M1. ive acces M1. red 3 D 3 D s 3 D M1.3D 25 Read o i o i o i o i 54 PART 10 - FTAM Phase 3 December 1993 (Stable) 26 Insert o i o i o i o i 27 Replace o i o i o i o i 28 Extend o i o i o i o i 29 Erase o i o i o i o i 30 Read o o o o o o o o attribute s 31 Change o o o o o o o o attribute s 32 Delete o o o o o o o o file A.12.3.4 Identity term (void) A.12.3.5 Initiator access passwords If the passwords term of the access control element is implemented the following values shall be supported for the initiator role. See part 9 16.3 Initiator Access D PROFILES Passwords I 1 OctetString o o 2 Graphic String o o A.12.3.6 Responder access passwords If the passwords term of the access control element is implemented the following values shall be supported for the responder role. See part 9 16.3 55 PART 10 - FTAM Phase 3 December 1993 (Stable) Responder D T1.3 T2.3 A1.3 M1.3 Access OctetStri OctetStri OctetStri OctetStri Passwords ng ng ng ng GraphicSt GraphicSt GraphicSt GraphicSt ring ring ring ring 1 Read- o o o o i password 2 Insert- o i o o i password 3 Replace- o o o o i password 4 Extend- o o o o i password 5 Erase- o i i o i password 6 Read- o o o o o attribute- password 7 Change- o i i i o attribute- password 8 Delete- o o o o o password A.12.3.7 Location Term (Void) A.12.3.7.1 Application Entity Titles detail See part 9 5.7 56 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.3.8 Access control element combinations Combinat D PROFILES ions R 1 Identity Password Location o o 2 Identity Password o o 3 Identity Location o o 4 Password Location o o 5 Identity o o 6 Password o o 7 Location o o NOTE - Implementation of access control without any of the above combinations is valid. 57 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.4 Service class field detail See 5.1, 8.1, part 9 table 7 D T1.3, A1.3 M1.3 M1.3 T2.3 (T) (A) 1 Transfer class o m i m i 2 Access class o i m i m 3 Management class o i i m m 4 Transfer and o o i m i management class 5 Unconstrained class o i i i i NOTES 1 The initiator is only permitted to specify those combinations defined in ISO 8571-3 2 The notation M1.3(T) indicates M1.3 combined with a Transfer Profile T1.3 or T2.3. M1.3(A) means 1.3 combined with the Access Profile A1.3. 58 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.5 Functional unit field detail See 8.1, 8.2, part 9 table 7 T1.3, T2.3 SERVICE CLASSES Transfer Transfer and FUNCTIONAL D T1.2, T2.3 Management UNITS D T1.3, T2.3 1 Kernel m m m m 2 Read (see note c o c o 2) 3 Write (see note c o c o 2) 4 File Access 5 Limited File o o m m Management 6 Enhanced File Management o i o i 7 Grouping m m m m 8 FADU Locking 9 Recovery o o o o 1 Restart o o o o 0 NOTES 1 The recovery and the restart functional units are only available at the internal file service interface and should only be explicity referenced in the protocol. 2 The c indicates that either or both of the read and write functional units shall be implemented in the particular service class. 59 PART 10 - FTAM Phase 3 December 1993 (Stable) A1.3 SERVICE CLASSES Access FUNCTIONAL UNITS D A1.3 1 Kernel m m 1 1 Read m m 2 1 Write m m 3 1 File Access m m 4 1 Limited File o o 5 Management 1 Enhanced File o i 6 Management 1 Grouping o o 7 1 FADU Locking o o see 8.6.2 8 1 Recovery o o 9 2 Restart o o 0 See 8.1 M1.3(T) SERVICE Transfer CLASSES Transfer and FUNCTIONAL D Management Management UNITS M1.3(T) D D M1.3(T) M1.3(T) 21 Kernel m m m m 22 Read c o 23 Write c o 24 File Access 60 PART 10 - FTAM Phase 3 December 1993 (Stable) 25 Limited o m m m m m File Management 26 Enhanced o m o m o m File Management 27 Grouping m m m m 28 FADU Locking 29 Recovery o o 30 Restart o o NOTE - M1.3(T) indicates M1.3 in conjuction with a Transfer Profile T1.3 or T2.3. This table lists only the additional functionality as defined by M1.3. 61 PART 10 - FTAM Phase 3 December 1993 (Stable) See 8.1 M1.3(A) SERVICE Access CLASSES Management FUNCTIONAL D M1.3(A) D M1.3(A) UNITS 31 Kernel m m 32 Read 33 Write 34 File Access 35 Limited File o m m m Management 36 Enhanced File o m o m Management 37 Grouping m m 38 FADU Locking 39 Recovery 40 Restart NOTE - M1.3(A) indicates M1.3 in conjuction with the Access Profile A1.3. This table lists only the additional functionality as defined by M1.3. A.12.6 Diagnostic field detail D T1.3, M1.3 T2.3, A1.3 1 Diagnosti m m m c type 2 Error m m m identifie r 3 Error m m m observer 62 PART 10 - FTAM Phase 3 December 1993 (Stable) 4 Error m m m source 5 Suggested o c i see 8.5.2 delay 6 Further o m m details For values of the 'further details' term only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets is required (see part 9 clause 13). 63 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.7 Contents type detail A.12.7.1 Contents list parameter See part 9 10.2.1 D PROFILES Maximum number of I R elements 1 document type o o m specifications 2 abstract syntax o o m specifications A.12.7.2 Contents type parameter See part 9 10.2.3 D PROFILES REFERENCE 1 document type o m see part 9 9.1 specifications 2 abstract syntax / o i constraint set pair specificaitons NOTE - The detail of document types supported is contained in clause A.13. A.12.8 FTAM Quality of service details See 8.5.2 A.12.9 Details of shared ASE information (Void) 64 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.10 Details of charging See part 9 5.8 and 18.4 Charging D PROFILES R 1 Resource indentifier m m term 2 Charging unit term m m 3 Charging value term m m A.12.11 Filestore password detail Filestore password D PROFILE detail S 1 OctetString o o 2 GraphicString o o A.12.12 Create password detail See part 9 16.3 Create password D PROFILE detail S 1 OctetString o o 2 GraphicString o o A.12.13 Concurrency control A.12.13.1 Supported values See 8.6.1 T1.3 not shared exclusive no access required Action D T1.3 D T1.3 D T1.3 D T1.3 65 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 Read o o o o oo o o 2 Insert o i o i oi o i 3 Replace o o o o oo o o 4 Extend o o o o oo o o 5 Erase o i o i oi o i 6 Read o o o o oo o o attrib 7 Change o i o i oi o i attrib 8 Delete o o o o oo o o file 66 PART 10 - FTAM Phase 3 December 1993 (Stable) T2.3 not shared exclusive no access required Action D T2.3 D T2.3 D T2.3 D T2.3 9 Read o o o o oo o o 1 Insert o o o o oo o o 0 1 Replace o o o o oo o o 1 1 Extend o o o o oo o o 2 1 Erase o i o i oi o i 3 1 Read o o o o oo o o 4 attrib 1 Change o i o i oi o i 5 attrib 1 Delete o o o o oo o o 6 file A1.3 not shared exclusive no access required Action D A1.3 D A1.3 D A1.3 D A1.3 1 Read o o o o oo o o 7 1 Insert o o o o oo o o 8 1 Replace o o o o oo o o 9 2 Extend o o o o oo o o 0 2 Erase o o o o oo o o 1 67 PART 10 - FTAM Phase 3 December 1993 (Stable) 2 Read o o o o oo o o 2 attrib 2 Change o i o i oi o i 3 attrib 2 Delete o o o o oo o o 4 file M1.3 not shared exclusive no access required Action D M1.3 D M1.3 D M1.3 D M1.3 2 Read o i o i oi o i 5 2 Insert o i o i oi o i 6 2 Replace o i o i oi o i 7 2 Extend o i o i oi o i 8 2 Erase o i o i oi o i 9 3 Read o o o o oo o o 0 attrib 3 Change o o o o oo o o 1 attrib 3 Delete o o o o oo o o 2 file A.12.13.2 Responder Default values See 8.6.1, part 9 clause 14 68 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.14 FADU Locking A1.3 FADU Locking Support Values not shared exclusive no access required Action D A1.3 D A1.3 D A1.3 D A1.3 Read o o o o oo o o 1 Insert o o o o oo o o 2 Replace o o o o oo o o 3 Extend o o o o oo o o 4 Erase o o o o oo o o 5 A.12.15 Initiator Override Initiator override D PROFILE S I 1 Create failure o o 2 Select old file o o 3 Delete and recreate o o with old attributes 4 Delete and create o o with new attributes NOTE - The specification of the role of responder is given in A.10.5 A.12.16 Requested Access See part 9 clause 15 69 PART 10 - FTAM Phase 3 December 1993 (Stable) Action D T1.3 T2.3 A1.3 M1.3 Read o o o o i 1 Insert o i o o i 2 Replace o o o o i 3 Extend o o o o i 4 Erase o i i o i 5 Read attrib o o o o m 6 Change attrib o i i i m 7 Delete file o o o o m 8 A.12.17 Processing mode Processing mode D T1.3 T2.3 A1.3 M1.3 Read o o o o i 1 Insert o i o o i 2 Replace o o o o i 3 Extend o o o o i 4 Erase o i i o i 5 70 PART 10 - FTAM Phase 3 December 1993 (Stable) A.12.18 Recovery mode See 8.5.2 Recovery mode D T1.3, M1.3 T2.3, A1.3 1 None o o i 2 At start of transfer o o i 3 Any active checkpoint o o i Section 6: Document Type Detail A.13 Document types See 7.1 Conformance to document types is given a two levels. The following table indicates which document types have some level of support. The detail of that level of support is stated in the following tables. Entry FTAM-1 D T1.3 T2.3 number A1.3 M1.3 Object ISO FTAM unstructured text o m m 1 descripto {iso standard 8571 document- m i r type(5)unstructered-text(1)} see A.13.1 Object identifie r Entry FTAM-2 D T1.3 T2.3 number A1.3 M1.3 Object ISO FTAM sequential text o i m 2 descripto {iso standard 8571 document- m i r type(5)sequential-text(2)} see A.13.2 Object identifie r Entry FTAM-3 D T1.3 T2.3 number A1.3 M1.3 71 PART 10 - FTAM Phase 3 December 1993 (Stable) Object ISO FTAM unstructured binary o m 3 descripto m r m i Object {iso standard 8571 document-type(5)sequential- identifie binary(3)} r see A.13.3 Entry FTAM-4 D T1.3 T2.3 number A1.3 M1.3 Object ISO FTAM sequential binary 4 descripto o i r o o Object i identifie {iso standard 8571 document-type(5)sequential- r bindary(4)} see A.13.4 72 PART 10 - FTAM Phase 3 December 1993 (Stable) Entry NBS-6 D T1.3 T2.3 number A1.3 M1.3 Object NBS-6 FTAM sequential file - i m 5 descripto {iso identified-organization m i r oiw(14) ftamsig(5) see A.13.5 Object document-type(5) identifie sequential(6)} r Entry NBS-7 D T1.3 T2.3 number A1.3 M1.3 Object NBS-7 FTAM random access - i m 6 descripto file m i r {iso identified-organization see A.13.6 Object oiw(14) ftamsig(5) identifie document-type(5) random r file(7)} Entry NBS-8 D T1.3 T2.3 number A1.3 M1.3 Object NBS-8 FTAM indexed file - i o 7 descripto {iso identified-organization o i r oiw(14) ftamsig(5) see A.13.7 Object document-type(5) indexed- identifie file(8)} r Entry NBS-9 D T1.3 T2.3 number A1.3 M1.3 Object NBS-9 FTAM file directory - o o 8 descripto file o i r {iso identified-organization see 7.1 Object oiw(14) ftamsig(5) identifie document-type(5) random- r binary(10)} Entry NBS-10 D T1.3 T2.3 number A1.3 M1.3 73 PART 10 - FTAM Phase 3 December 1993 (Stable) Object NBS-10 FTAM random binary - i o 9 descripto access file o i r {iso identified-organization see 7.1 Object oiw(14) ftamsig(5) identifie document-type(5) random r bindary(10)} Entry NBS-11 D T1.3 T2.3 number A1.3 M1.3 1 Object NBS-11 FTAM indexed file - i o 0 descripto with unique keys o i r {iso identified-organization see A.13.8 Object oiw(14) ftamsig(5) identifie document-type(5) indexed- r file-with-unique-keys(11)} Entry NBS-12 D T1.3 T2.3 number A1.3 M1.3 1 Object NBS-12 FTAM simple text - i o 1 descripto file o i r {iso identified- see A.13.9 Object organization oiw(14) identifie ftamsig(5) r document-type(5) simple- text-file(12)} 74 PART 10 - FTAM Phase 3 December 1993 (Stable) Constraint sets and FADU identities for document types For the constraint set/FADU identity tables the following notation is used: m mandatory in the constraint set definition, or optional in the constraint set definition but shall b implemented by implementations claiming conformance to the Profile. The support of the FADU identity will be dependent on the actions which have been implemented. o optional in the constaint set definition i not supported (outside the scope of this ISP, may be ignored) - not applicable (not defined in the constraint set definition) x excluded (disallowed in the document type definition or in FTAM Phase 3) Implementation Profile T1.3. FADU Beg End Fir Las Curr Nex Previ Node Node Identity in st t ent t ous Seq Numbe Constraint r set FTAM - - m - - - - - - unstuctured constraint set FTAM-1 - - m - - - - - - FTAM-3 - - m - - - - - - NBS-9 - - m - - - - - - 75 PART 10 - FTAM Phase 3 December 1993 (Stable) Implementation Profile T2.3 (see 7.2, part 9 clause 10) FADU Beg End Fir Las Curr Nex Previ Node Node Identity in st t ent t ous Seq Numbe Constraint r set FTAM - - m - - - - - - unstuctured constraint set FTAM-1 - - m - - - - - - FTAM-3 - - m - - - - - - NBS-9 - - m - - - - - - FTAM o o o o o o o - o sequential flat Constraint set FTAM-2 m m i i i i i - i FTAM-4 m m i i i i i - i NBS-6 m m i x x i x - x NBS-12 m m x x x x x - x FTAM ordered o o o o o o o o o flat Constraint set NBS-8 m i i i i i i m i FTAM ordered o o - - o o o o o flat constr set with unique names NBS-11 m i - - i i i m i 76 PART 10 - FTAM Phase 3 December 1993 (Stable) FTAM ordered o o o o o o o - o flat Constraint set NBS-7 m m m m i i i - m FTAM random o o - - - - - o o access Constraint set NBS-10 m m - - - - - m m 77 PART 10 - FTAM Phase 3 December 1993 (Stable) Implementation Profile A1.3 (see part 9 clause 10) FADU Identity Beg End Fir Las Curr Ne Prev Node Node Constraint in st t ent xt ious Seq Numb Set er FTAM _ _ m _ _ _ _ _ _ unstructured constraint set FTAM-1 - - m - - - - - - FTAM-3 - - m - - - - - - NBS-9 - - m - - - - - - FTAM o o o o o o o _ o sequential flat constraint set FTAM-2 m m m i i m i - i FTAM-4 m m m i i m i - i NBS-6 m m m x x m x - x NBS-12 m m m x x m x - x FTAM ordered o o o o o o o o o flat constraint set NBS-8 m m i i m m m m i FTAM ordered o o - - o o o o o flat constr set with unique names NBS-11 m m - - m m m m i 78 PART 10 - FTAM Phase 3 December 1993 (Stable) NBS ordered o o o o o o o - o flat constraint set NBS-7 m m m m m m m - m NBS random o o - - - - - o o access constraint set NBS-10 m m - - - - - m m A.13.1 FTAM-1 (See 7.1) A.13.1.1 Universal class number parameter (See part 9 10.1) D T1.3, T2.3, A1.3 1 Universal class number o m parameter supported 2 PrintableString - Universal class 19 o i 3 TeletexString - Universal class 20 o i 4 VideotexString - Universal class 21 o i 5 IA5String - Universal class 22 o m see part 9 10.1.1-2 6 GraphicString - Universal class 25 o m see A.13.1.3 7 VisibleString - Universal class 26 o m 8 GeneralString - Universal class 27 o m see A.13.1.4 A.13.1.2 String length parameter and string significance parameter combinations D T1.3, T2.3, A1.3 79 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 Maximum string length o m parameter and variable length strings 2 Maximum string length o m parameter and fixed length strings 3 Maximum string length o m parameter and not significant strings 4 Unbounded strings and o m variable length strings 5 Unbounded strings and o m not significant strings A.13.1.3 G sets supported G sets which are supported in FTAM-1 GraphicString. 1 For values of GraphicString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets is required. (see part 9 10.1.1 and 10-1-3) A.13.1.4 G and C sets supported G and C sets which are supported in FTAM-1 GeneralString 1 For values of GeneralString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets and ISO 646 IRV (C0) control set is required (see part 9 10.1-3) 80 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.2 FTAM-2 (see 7.1) A.13.2.1 Universal class number parameter (see part 9 10.1) D T2.3, A1.3 1 Universal class number o m parameter supported 2 PrintableString - Universal class 19 o i 3 TeletexString - Universal class 20 o i 4 VideoexString - Universal class 21 o i 5 IA5String - Universal class 22 o o see part 9 10.1.1-2 6 GraphicString - Universal class 25 o m see A.13.2.3 7 VisibleString - Universal class 26 o m 8 GeneralString - Universal class 27 o o see A.13.2.4 81 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.2.2 String length parameter and string significance parameter combinations D T2.3, A1.3 1 Maximum string length o i parameter and variable length strings 2 Maximum string length o i parameter and fixed length strings 3 Maximum string length o m parameter and not significant strings 4 Unbounded strings and o i variable length strings 5 Unbounded strings and o m not significant strings A.13.2.3 G sets supported G sets which are supported in FTAM-2 GraphicString. 1 For values of GraphicString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets is required. (see part 9 10.1.1 and 10.1.3) A.13.2.4 G and C sets supported G and C sets which are supported in FTAM-2 GeneralString 82 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 For values of GraphicString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets and ISO 646 IRV (C0) control character set is required. (see part 9 10.1.1-3) A.13.3 FTAM-3 83 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.3.1 String length parameter and string significance parameter combinations (see 7.1) D T1.3, T2.3, A1.3 1 Maximum string o i length parameter and variable length strings 2 Maximum string o i length parameter and fixed length strings 3 Maximum string o m length and not significant strings 4 Unbounded strings o i and variable length strings 5 Unbounded strings o m and not significant strings A.13.4 FTAM-4 (see 7.1) A.13.4.1 String length parameter and string significance parameter combinations D T2.3, A1.3 1 Maximum string o i length parameter and variable length strings 2 Maximum string o i length parameter and fixed length strings 84 PART 10 - FTAM Phase 3 December 1993 (Stable) 3 Maximum string o m length parameter and not significant strings 4 Unbounded strings o i and variable length strings 5 Unbounded strings o m and not significant strings 85 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.5 NBS-6 See part 9 tables 2, 3 A.13.5.1 Parameter0 D T2.3, A1.3 1 Parameter0 - m supported 2 Universal-time- Universal - m class 23 3 Generalized- Universal - m time - class 24 4 boolean - Universal - m class 1 5 null - Universal - m class 5 A.13.5.2 Parameter1 (see part 9 10.1) D T2.3, A1.3 1 Parameter1 - m supported 2 integer - Universal - m class 2 3 bit - Universal - m class 3 4 IA5 - Universal - m class 22 5 GraphicString - Universal - m class 25 6 GeneralString - Universal - m class 27 7 OctetString - Universal - m class 4 86 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.5.3 Parameter2 D T2.3, A1.3 1 Parameter2 - o supported 87 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.6 NBS-7 See part 9 tables 2, 3 A.13.6.1 Parameter0 D T2.3, A1.3 1 Parameter0 - m supported 2 Universal-time- Universal - m class 23 3 Generalized- Universal - m time - class 24 4 boolean - Universal - m class 1 5 null - Universal - m class 5 A.13.6.2 Parameter1 (see part 9 10.1) D T2.3, A1.3 1 Parameter1 - m supported 2 integer - Universal - m class 2 3 bit - Universal - m class 3 4 IA5 - Universal - m class 22 5 GraphicString - Universal - m class 25 6 GeneralString - Universal - m class 27 7 OctetString - Universal - m class 4 88 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.6.3 Parameter2 D T2.3, A1.3 1 Parameter2 - o supported A.13.7 NBS-8 See part 9 tables 2,3 A.13.7.1 Parameter0 Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter0 supported - m - m 2 Universal-time - Universal class 23 - m - m 3 Generalized-time - Universal class 24 - m - m 4 boolean - Universal class 1 - m - - 5 null - Universal class 5 - m - - A.13.7.2 Parameter1 (see part 9 10.1) Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter1 supported - m - m 2 integer - Universal class 2 - m - m 3 bit - Universal class 3 - m - - 4 IA5 - Universal class 22 - m - m 5 GraphicString - Universal class 25 - m - m 6 GeneralString - Universal class 27 - m - m 89 PART 10 - FTAM Phase 3 December 1993 (Stable) 7 OctetString - Universal class 4 - m - m A.13.7.3 Parameter2 Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter2 supported - o - o 90 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.8 NBS-11 See part 9 tables 2,3 A.13.8.1 Parameter0 Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter0 supported - m - m 2 Universal-time - Universal class 23 - m - m 3 Generalized-time - Universal class 24 - m - m 4 boolean - Universal class 1 - m - - 5 null - Universal class 5 - m - - A.13.8.2 Parameter1 (see part 9 10.1) Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter1 supported - m - m 2 integer - Universal class 2 - m - m 3 bit - Universal class 3 - m - - 4 IA5 - Universal class 22 - m - m 5 GraphicString - Universal class 25 - m - m 6 GeneralString - Universal class 27 - m - m 7 OctetString - Universal class 4 - m - m A.13.8.3 Parameter2 91 PART 10 - FTAM Phase 3 December 1993 (Stable) Data Key Type Types D T2.3, D T2.3, A1.3 A1.3 1 Parameter2 supported - o - o A.13.9 NBS-12 (see 7.1) A.13.9.1 Universal class number parameter (see part 9 10.1) D T2.3, A1.3 1 Universal class number - m parameter supported 2 PrintableString - Universal class 19 - i 3 TeletexString - Universal class 20 - i 4 VideotexString- Universal class 21 - i 5 IA5String - Universal class 22 - m 6 GraphicString - Universal class 25 - m see A.13.9.5 7 VisibleString - Universal class 26 - m 8 GeneralString - Universal class 27 - m see A.13.9.6 A.13.9.2 String length parameter D T2.3, A1.3 1 Maximum string length - parameter supported m A.13.9.3 String significance parameter D T2.3, A1.3 92 PART 10 - FTAM Phase 3 December 1993 (Stable) 1 String significance - m see 7.1 parameter suported table 3(c) 2 Variable length - m strings supported 3 Fixed length - m strings supported A.13.9.4 Character set parameter D T2.3, A1.3 1 Character set - m see 7.1 parameter table 3(c) supported 93 PART 10 - FTAM Phase 3 December 1993 (Stable) A.13.9.5 G sets supported G sets which are supported in NBS-12 GraphicString. 1 For values of GraphicString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character sets is required. (see part 9 10.1.1 and 10.1.3) A.13.9.6 G and C sets supported G and C sets which are supported in NBS-12 GeneralString. 1 For values of GeneralString only the support of character strings of the ISO 646 IRV (G0) and ISO 8859-1 (G0 and G1) character set and ISO (C0) control character sets is required. (see part 9 10.1.1-3) - END OF FTAM PHASE 3 PROFILES REQUIREMENT LIST 94 PART 10 - FTAM Phase 3 December 1993 (Stable) 95 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex B (normative) Register of FTAM Objects B.1 Introduction The objects defined in B.2.1 and B.2.2 will be removed from this document after ISO/IEC ISP 10607-2 and ISO/IEC ISP 10607-2/Amd.1 are published. During the period between publishing the ISP and the removal of the definitions from this document, the definitions in the ISP will take precedence over this document. When the object definitions are removed, clauses B.2.1 and B.2.2 will be changed to point to the ISP. B.2 Index of OIW FTAM Objects B.2.1 FTAM Phase 2 Defined Objects 96 PART 10 - FTAM Phase 3 December 1993 (Stable) Object Identifier Prefix: nist-adhoc::= {iso(1) identified- organization(3) icd(9999) organization-code(1)} Object Object Object Date of Reference to descriptor identifier registr definition ation NBS-6 NBS-6 FTAM {nist-adhoc Dec 15, Stable sequential document- '89 Agreements file type(5) Withdra Vers. 4, Ed. sequential(6 wn 1, Dec '90 ) } March NIST SP 500- 16, '90 183 part 9, annex A clause A.1 NBS-7 NBS-7 FTAM {nist-adhoc Dec 15, Stable random access document- '89 Agreements file type(5) Withdra Vers. 4, Ed. random wn 1, Dec '90 file(7) } March NIST SP 500- 16, '90 183 part 9, annex A clause A.2 NBS-8 NBS-8 FTAM {nist-adhoc Dec 15, Stable indexed file document- '89 Agreements type(5) Withdra Vers. 4, Ed. indexed- wn 1, Dec '90 file(8) } March NIST SP 500- 16, '90 183 part 9, annex A clause A.3 NBS-9 NBS-9 FTAM {nist-adhoc Dec 15, Stable file document- '89 Agreements directory type(5) Withdra Vers. 4, Ed. file file- wn 1, Dec '90 directory(9) March NIST SP 500- } 16, '90 183 part 9, annex A clause A.4 97 PART 10 - FTAM Phase 3 December 1993 (Stable) NHS ordered {nist-adhoc Dec 15, Stable flat constraint- '89 Agreements constraint set(4) Withdra Vers. 4, Ed. set nbs-ordered- wn 1, Dec '90 flat(1) } March NIST SP 500- 16, '90 183 part 9, annex B clause B.1 NBS-AS1 NBS abstract {nist-adhoc Dec 15, Stable syntax AS1 abstract- '89 Agreements styntax(2) Withdra Vers. 4, Ed. nbs-as1(1) } wn 1, Dec '90 March NIST SP 500- 16, '90 183 part 9, annex C clause C.1 NBS-AS2 NBS file {nist-adhoc Dec 15, Stable directory abstract- '89 Agreements entry styntax(2) Withdra Vers. 4, Ed. abstract nbs-as2(2) } wn 1, Dec '90 syntax March NIST SP 500- 16, '90 183 part 9, annex C clause C.2 AP-Title {nist-adhoc Dec 15, Stable ftam-nil-ap- '89 Agreements title(7) } Vers. 4, Ed. 1, Dec '90 NIST SP 500- 183 part 5, 12.1.1.1 98 PART 10 - FTAM Phase 3 December 1993 (Stable) Object Identifier Prefix: nist-oiw-ftam::= {iso(1) identified- organization(3) oiw(14)ftamsig(5)} Object Object Object Date of Reference to descriptor identifier registr definition ation NBS-6 NBS-6 FTAM {nist-adhoc March Stable sequential document- 16, '90 Agreements file type(5) Vers. 4, Ed. sequential(6 1, Dec '90 ) } NIST SP 500- 183 part 9, annex A clause A.5 NBS-7 NBS-7 FTAM {nist-adhoc March Stable random access document- 16, '90 Agreements file type(5) Vers. 4, Ed. random 1, Dec '90 file(7) } NIST SP 500- 183 part 9, annex A clause A.6 NBS-8 NBS-8 FTAM {nist-adhoc March Stable indexed file document- 16, '90 Agreements type(5) Vers. 4, Ed. indexed- 1, Dec '90 file(8) } NIST SP 500- 183 part 9, annex A clause A.7 NBS-9 NBS-9 FTAM {nist-adhoc March Stable file document- 16, '90 Agreements directory type(5) Vers. 4, Ed. file file- 1, Dec'90 directory(9) NIST SP 500- } 183 part 9, annex A clause A.8 99 PART 10 - FTAM Phase 3 December 1993 (Stable) NHS ordered {nist-adhoc March Stable flat constraint- 16, '90 Agreements constraint set(4) Vers. 4, Ed. set nbs-ordered- 1, Dec '90 flat(1) } NIST SP 500- 183 part 9, annex B clause B.2 NBS-AS1 NBS abstract {nist-adhoc March Stable syntax AS1 abstract- 16, '90 Agreements styntax(2) Vers. 4, Ed. nbs-as1(1) } 1, Dec '90 NIST SP 500- 183 part 9, annex C clause C.3 NBS-AS2 NBS file {nist-adhoc March Stable directory abstract- 16, '90 Agreements entry styntax(2) Vers. 4, Ed. abstract nbs-as2(2) } 1, Dec '90 syntax NIST SP 500- 183 part 9, annex C clause C.4 100 PART 10 - FTAM Phase 3 December 1993 (Stable) Object Identifier Prefix: nist-oiw-ftam:= {iso(1) identified- organization(3) oiw(14)ftamsig(5)} Object Object Object Date of Reference descriptor identifier registr to ation definition NBS-10 NBS-10 random {nist-oiw-ftam March Stable binary access document- 15, '89 Agreements file type(5) Vers. 4, random- Ed. 1, binary(10) } December '90 NIST SP 500-183 part 10, annex C clause C.1 NBS-11 NBS-11 FTAM {nist-oiw-ftam March Stable indexed document- 15, '89 Agreements file with type(5) Vers. 4, unique keys indexed-file- Ed. 1, with-unique- December keys(11) } '90 NIST SP 500-183 part 10, annex C clause C.2 NBS-12 NBS-12 FTAM {nist-oiw-ftam March Stable simple text document- 15, '89 Agreements file type(5) Vers. 4, simple-text- Ed. 1, file (12) } December '90 NIST SP 500-183 part 10, annex C clause C.3 101 PART 10 - FTAM Phase 3 December 1993 (Stable) NBS Random {nist-oiw-ftam March Stable Access constraint- 15, '89 Agreements set(4) Vers. 4, nbs-random- Ed. 1, access(2) } December '90 NIST SP 500-183 part 10, annex D clause D.1 NBS-AS3 NBS random {nist-oiw-ftam March Stable access abstract- 15, '89 Agreements node name syntax(2) Vers. 4, abstract nbs-node- Ed. 1, syntax name(3) } December '90 NIST SP 500-183 part 10, annex E clause E.1 NBS-AS4 NBS random {nist-oiw-ftam March Stable binary abstract- 15, '89 Agreements access file styntax(2) Vers. 4, abstract nbs-random- Ed. 1, syntax binary(4) } December '90 NIST SP 500-183 part 10, annex E clause E.2 NBS-AS5 NBS simple {nist-oiw-ftam March Stable text abstract- 15, '89 Agreements abstract styntax(2) Vers. 4, syntax nbs-simple- Ed. 1, text(5) } December '90 NIST SP 500-183 part 10, annex E clause E.3 102 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex C (normative) Document Types C.1 NBS-10 Random Binary Access File C.1.1 Entry Number: NBS-10 C.1.2 Information objects 103 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 4 - Information objects in NBS-10 document type name {iso identified-organization oiw(14) ftamsig(5) document-type(5) random- binary(10)} "NBS-10 FTAM random binary access file" abstract syntax names: a) name of asname1 {iso identified-organization oiw(14) ftamsig(5) abstract-syntax(2) nbs- random-binary(4)} b) name of asname2 "NBS random binary access file abstract syntax" {iso standard 8571 c) name of asname3 abstract-syntax(2) ftam-fadu(2)} "FTAM FADU" {iso identified-organization oiw(14) ftamsig(5) abstract-syntax(2) nbs-node-name(3)} "NBS random access node name abstract syntax" transfer syntax names: {joint-iso-ccitt asn1(1) basic- encoding(1)} "Basic encoding of a single ASN.1 type" file model {iso standard 8571 file-model(3) hierarchical(1)} "FTAM hierarchical file model" constraint set {iso identified-organization oiw(14) ftamsig(5) constraint-set(4) nbs-random- access(2)} "NBS random access constraint set" File contents: Datatype1 ::= OCTET STRING Datatype2 ::= Node-Name --The type to be used for Node-Name is defined in ISO 8571-FADU --The only Choice for Node-Name is user-coded Datatype3 ::= NBS-Node-Name --As defined by the NBS Random Access Node-Name Abstract Syntax 104 PART 10 - FTAM Phase 3 December 1993 (Stable) C.1.3 Scope and field of application This document type defines the contents of a file for storage, for transfer and access by FTAM. 105 PART 10 - FTAM Phase 3 December 1993 (Stable) C.1.4 References ISO 8571, Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management C.1.5 Definitions This definition makes use of the terms data element, data unit and file access data unit as defined in ISO 8571-1. C.1.6 Abbreviations FTAM File Transfer, Access and Management C.1.7 Document semantics The document consists of zero, one, or more File Access Data Units. Each FADU contains precisely one data unit which consists of precisely one data element. The data element is made up of one octet. The order of each of these elements is significant. The semantics of the data elements is not specified by this document type. The document structure takes any of the forms allowed by the FTAM hierarchical file model as constrained by the NBS random access constraint set. The definition for FTAM hierarchical file model appears in 8571-2. There are no size or length limitations imposed by this definition. C.1.8 Abstract syntactic structure The abstract syntactic structure of the document is a series of octets. C.1.9 Definition of transfer 106 PART 10 - FTAM Phase 3 December 1993 (Stable) C.1.9.1 Datatype definition The presentation data value used for transfer is an ASN.1 OCTET STRING. Datatype2 is used to specify the FADU-Identity of "name-list" in the FTAM PDUs specifying FADU-Identity, where "name-list" is defined as a SEQUENCE of EXTERNAL. The EXTERNAL is defined as Node-Name in the FTAM FADU abstract syntax. The use of Datatype2 is defined in "NBS random access constraint set." 107 PART 10 - FTAM Phase 3 December 1993 (Stable) Datatype3 specifies the "user-coded" form of the Node-Name in the FTAM FADU abstract syntax, where "user-coded" is defined as an EXTERNAL. That EXTERNAL is defined by Datatype3. The use of Datatype3 is defined in "NBS random access constraint set." C.1.9.2 Presentation data values The document is transmitted as a series of presentation data values. Each presentation data value shall consist of the "data" from one or more FADUs concatenated together. The result is one value of the ASN.1 data type OCTET STRING. The "fadu-count" field supplied in the Node-Name specifies the number of FADUs to transfer during a Read operation. The requested FADUs may be transferred as one or more presentation data values. All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname1" declared in table 4. NOTE - Specific carrier standards may impose additional constraints on the presentation context to be used, when the above permits a choice. Boundaries between P-DATA primitives and between presentation data values are chosen locally by the sending entity at the time of transmission. The boundaries are not preserved when the file is stored and they carry no semantics of the document type. Receivers which support this document type shall accept a document with any of the permitted transfer options. C.1.9.3 Sequence of presentation data values The sequence of presentation data values is the same as the sequence of Data Units within the file. C.1.10 Transfer syntax An implementation supporting these document types shall support the transfer syntax generation rules named in table 4 for all presentation data values transferred. Implementations may optionally support other transfer syntaxes. 108 PART 10 - FTAM Phase 3 December 1993 (Stable) C.1.11 ASE Specific Specifications C.1.11.1 Simplification The document type NBS-10 may be simplified to the document type FTAM-3. The resultant document contains the same sequence of data values as would result from accessing the file as an NBS-10 file. C.1.11.2 The READ operation A READ operation may be applied to a range of FADUs via the FADU- Identity of "NodeSeq." The "starting-fadu" part of the node name specifies the node number of the first FADU; the "fadu-count" specifies the number of consecutive FADUs to be transferred. A READ operation applied to a range of FADUs that spans beyond the end of file is valid. All available data in the range is transferred. An informative diagnostic (5005) is returned on the F-Data-End request indicating that the end of file was reached and a portion of the request was satisfied. C.1.11.3 The REPLACE operation When the REPLACE operation is applied to the root FADU of an NBS- 10 document, the transferred data shall be any NBS-10 document. The REPLACE operation applied to a FADU-Identity of "node number" is used to replace a series of FADUs, starting at the specified position in the file, by the new FADUs being transferred. The number of replaced FADUs is determined by the number of transferred FADUs. If the replacement spans beyond the end of the existing file, then the additional FADUs are inserted at the end of the file. C.1.11.4 The INSERT operation When the INSERT operation is applied at the end of file, the transferred data shall be a series of FADUs which would be generated by reading any NBS-10 document type in access context UA. 109 PART 10 - FTAM Phase 3 December 1993 (Stable) C.2 NBS-11 Indexed File With Unique Keys C.2.1 Entry Number: NBS-11 C.2.2 Information objects 110 PART 10 - FTAM Phase 3 December 1993 (Stable) Table 5 - Information objects in NBS-11 document name {iso identified-organization oiw(14) ftamsig(5) document-type(5) indexed- file-with-unique-keys(11)} "NBS-11 FTAM indexed file with unique keys" abstract syntax names: a) name for asname1 {iso identified-organization oiw(14) ftamsig(5) abstract syntax(2) nbs- as1(1)} b) name for asname2 "NBS abstract syntax AS1" {iso standard 8571 abstract-syntax(2) ftam-fadu(2)} "FTAM FADU" transfer syntax names: {joint-iso-ccitt asn1(1) basic- encoding(1)} "Basic Encoding of a single ASN.1 type" parameter syntax: PARAMETERS ::= SEQUENCE { DataTypes, KeyType, KeyPosition } DataTypes ::= SEQUENCE OF CHOICE { Parameter0, Parameter1, Parameter2 } KeyType ::= CHOICE { Parameter0, Parameter1, Parameter2 } -- Parameter0, Parameter1, Parameter2, as -- defined for the document types NBS-6, -- NBS-7, NBS-8 KeyPosition::= INTEGER file model {iso standard 8571 file-model(3) hierarchical(1)} "FTAM hierarchical file model" constraint set {iso standard 8571 constraint-set(4) ordered-flat-unique-names(4)} "FTAM ordered flat constraint set with unique names" 111 PART 10 - FTAM Phase 3 December 1993 (Stable) file contents: Datatype1 ::= PrimType -- as defined in NBS-AS1 Datatype2 ::= CHOICE { Node-Descriptor-Data-Element, Enter-Subtree-Data-Element, Exit-Subtree-Data-Element } Datatype3 ::= Prim Type -- as defined by the NBS abstract syntax AS1 C.2.3 Scope and field of application The document type defines the contents of a file for storage, for transfer and access using FTAM. NOTE - Storage refers to apparent storage within the Virtual Filestore. C.2.4 References ISO 8571, Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management C.2.5 Definitions This definition makes use of the terms data element, data unit and file access data unit as defined in ISO 8571-1. C.2.6 Abbreviations FTAM File Transfer, Access and Management C.2.7 Document semantics The document consists of zero, one, or more File Access Data Units. Each FADU consists of precisely one data unit which consists of zero, one, or more data elements. The order of each of these elements is significant. The document structure takes any of the forms allowed by the FTAM hierarchical file model as constrained by the FTAM ordered flat constraint set with unique names (see table 5). These definitions appear in ISO 8571-2. 112 PART 10 - FTAM Phase 3 December 1993 (Stable) The following additional requirements are specified for the use of the ordered flat constraint set with unique names: The FADU identity "node number" is not required for conformant implementations; The identities "next" and "previous" are allowed for all FADUs. Each data element is a data type from the set of primitive data types defined in part 9 Annex C, NBS abstract syntax AS1. Each data unit contains the same data element types in the same order as all other data units. These types and their respective maximum lengths are defined by the parameter. 113 PART 10 - FTAM Phase 3 December 1993 (Stable) For Datatype1 and Datatype3, the string-length field of Parameter1 specifies the length of the value in octets for the INTEGER, BIT STRING and OCTET STRING types. For character-type data elements, the string-length indicates the actual number of characters from the specified character set, not including any escape sequences or overhead from the character encoding. For floating point numbers, finite form, length-1 and length-2 specify the length in bits of mantissa and exponent, respectively. The length-1 and length-2 values are irrelevant for the other choices of floating point numbers. Each data unit in the file has a key associated with it, which is the user-coded form of Node-Name. The key of each data unit is of the same data type as the key of all other data units in the file and is a single data element from the set of primitive data types defined in part 9 Annex C, C.3 of NIST SP 500-183. The type and length of the key are defined by the parameter. The primitive data types and minimum size ranges of each unit which an implementation must accept as a key value are given in the following table 6. Table 6 - Datatypes for keys Key Type Minimum Order Range (octets ) ASN.1 INTEGER (1-2) increasing numeric ASN.1 IA5String (1-16) value ASN.1 GraphicString ASN.1 (1-16) lexical order GeneralString (1-16) lexical order ASN.1 OCTET STRING (1-16) lexical order ASN.1 GeneralizedTime increasing value ASN.1 UniversalTime increasing time value NBS-AS1 FloatingPointNumber increasing time value increasing numeric value The position of the key in the data unit is specified by the parameter. KeyPosition = 0 implies the key is not part of the data 114 PART 10 - FTAM Phase 3 December 1993 (Stable) KeyPosition > 0 specifies the actual data element in the data unit. C.2.8 Abstract syntactic structure The abstract syntactic structure of the document is a hierarchically structured file as defined in the ASN.1 module ISO8571-FADU in ISO 8571, in which each of the file access data units has the abstract syntactic structure of NBS-AS1 as defined by the parameters. C.2.9 Definition of transfer C.2.9.1 Datatype definitions The file consists of data values which are of a) Datatype1 defined in table 5, where the PrimType in the datatype is given by the NBS-AS1 definition; or b) Datatype2 defined in table 5, which is the ASN.1 datatype declared as "Data-Element" in the ASN.1 module ISO8571-FADU; or c) Datatype3, defined in Table 5, which specifies the user- coded form of the Node-Name in the FTAM FADU abstract syntax, where user-coded is defined as EXTERNAL. C.2.9.2 Presentation data values The document is transferred as a series of presentation data values, each of which is a) one value of the ASN.1 datatype "Datatype1," carrying one of the data elements from the document. All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname1" or b) a value of "Datatype2." All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname2."; or c) a value of "Datatype3" carrying a Key. All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname1". 115 PART 10 - FTAM Phase 3 December 1993 (Stable) NOTES 1 Specific carrier standards may impose additional constraints on the presentation context to be used, where the above permits a choice. 2 Any document type defined in this entry either makes no use of Datatype2, or starts with a Datatype2 transmission. Boundaries between presentation data values in the same presentation context, and boundaries between P-DATA primitives, are chosen locally by the sending entity at the time of transmission, and carry no semantics of the document type. Receivers which support this document type shall accept a document with any of the permitted transfer options (e.g., document type parameters and transfer syntaxes). C.2.9.3 Sequence of presentation data values The sequence of presentation data values of type a) and the sequence of presentation data values of types a) and b) is the same as the sequence of data elements within a Data Unit, and Data Units in the hierarchical structure, when flattened according to the definition of the hierarchical file model in ISO 8571-2. C.2.10 Transfer syntax An implementation supporting this document type shall support the transfer syntax generation rules named in table 5 for all presentation data values transferred. Implementation may optionally support other named transfer syntaxes. C.2.11 ASE Specific Specifications C.2.11.1 Simplification This simplification loses information. The document type NBS-11 may be accessed as a document type FTAM- 3 (allowed only when reading the file) by specifying document type FTAM-3 in the parameter in , and limiting access context to UA on F-READ. The octet representation of the transferred data is unpredictable. It will usually correspond to the data values as 116 PART 10 - FTAM Phase 3 December 1993 (Stable) stored in the local Real Filestore of the Responder. A document of type NBS-11 can be accessed as a document of type NBS-6 (allowed only when reading the file) by specifying document type NBS-6 with appropriate data type parameters in the parameter on the . The traversal order of the FADUs must be maintained. NOTE - The traversal order is as reading the file as NBS-11 in key order. A document of type NBS-11 may be accessed as a document of type NBS-8 (allowed only when reading the file) by specifying document type NBS-8 in the parameter in the . C.2.11.2 Access context selection A document of type NBS-11 may be accessed in any one of the access contexts defined in the FTAM ordered flat constraint set with unique names. The presentation data units transferred in each case are those derived from the structuring elements defined for that access context in ISO 8571-2. C.2.11.3 The INSERT operation When the operation is applied, the transferred material shall be the series of FADUs which would be generated by reading any NBS-11 document with the same parameter values in access context FA. A transferred FADU whose name duplicates that of an already existing FADU will cause the operation to fail. The failure shall be signalled by issuing an F-CANCEL Request with a corresponding diagnostic. C.2.11.4 The EXTEND operation This operation is excluded for use with this document type. C.2.11.5 The REPLACE operation When the operation is applied with FADU Identity "begin," a transferred FADU whose name duplicates that of a previously transferred FADU will cause the operation to fail. The failure shall be signalled by issuing an F-CANCEL 117 PART 10 - FTAM Phase 3 December 1993 (Stable) Request with a corresponding diagnostic. 118 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3 NBS-12 Simple Text File Document Type C.3.1 Entry Number: NBS-12 C.3.2 Information objects Table 7 - Information objects in NBS-12 document type names {iso identified-organization oiw(14) ftamsig(5) document-type(5) simple-text-file(12)} "NBS-12 FTAM simple text file" abstract syntax names: a) name for asname1 {iso identified-organization oiw(14) ftamsig(5) abstract-syntax(2) nbs-simple-text(5)} b) name for asname2 "NBS simple text abstract syntax" {iso standard 8571 abstract-syntax(2) ftam-fadu(2)} "FTAM FADU" transfer syntax names: {joint-iso-ccitt asn1 (1) basic- encoding (1)} "Basic Encoding of a single ASN.1 type" Parameter Syntax PARAMETERS ::= SEQUENCE { universal-class-number [0] IMPLICIT INTEGER, maximum-string-length [1] IMPLICIT INTEGER, string-significance [2] IMPLICIT INTEGER {variable (0), fixed (1)}, character-set [3] IMPLICIT OCTET STRING OPTIONAL } file model {iso standard 8571 file-model(3) hierarchical(1)} "FTAM hierarchical file model" constraint set {iso standard 8571 constraint-set(4) sequential flat(2)} "FTAM sequential flat constraint set" 119 PART 10 - FTAM Phase 3 December 1993 (Stable) File contents Datatype1 ::= NBS-Text --as defined in the NBS Simple Text --Abstract Syntax registration entry Datatype2 ::= Node-Descriptor-Data-Element C.3.3 Scope and field of application The document type defines the contents of a file for storage, and for transfer and access by FTAM. NOTE - Storage refers to apparent storage within the Virtual Filestore. C.3.4 References ISO 8571, Information Processing Systems - Open Systems Interconnection - File Transfer, Access and Management ISO 8824, Information Processing Systems - Open Systems Interconnection-Specification of Abstract Syntax Notation 1 (ASN.1). ISO 8825, Information Processing Systems - Open Systems Interconnection-Basic Encoding Rules for Abstract Syntax Notation One (ASN.1). ISO 6429, Information Processing - ISO 7-bit and 8-bit coded character sets-Additional control functions for character imaging devices. C.3.5 Definitions This definition makes use of the terms data element, data unit and file access data unit as defined in ISO 8571-1. In addition, it makes use of the terms character string, graphics character, and format effector as defined in document type registration entry "FTAM-2" in ISO 8571-2. 120 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3.6 Abbreviations FTAM File Transfer, Access and Management C.3.7 Document semantics This document consists of zero, one, or more File Access Data Units. Each FADU consists of precisely one data unit which consists of precisely one character string. The order of each of these elements is significant. The semantics of the character strings is not specified by this document type. The document structure takes any of the forms allowed by the FTAM hierarchical file model as constrained by the sequential flat constraint set. These definitions appear in ISO 8571-2. As additional constraints, FADU identity will be limited to the following values: a) "begin" "and "end" when using the Transfer or Transfer and Management service classes; b) "begin," "end," "first," and "next" when using the Access service class. Each character string consists of characters from the character set defined by the ASN.1 (ISO 8824) character set type whose universal class number is given by the "universal-class-number" parameter and by the escape sequences contained in the optional "character-set" parameter. If the character set type allows explicit escape sequences, the "character-set" parameter, if present, contains escape sequences which designate and invoke specific character sets. If the "character-set" parameter is not present, character sets are assumed to be designated and invoked as specified in table 2 in ISO 8825. Character strings shall not contain escape sequences. There are no size or length limitations imposed by this definition, except those specified here. Each character string is of a length determined by the number of characters given by the "maximum-string-length" parameter. NOTE - The length restriction refers to the number of characters from the applicable character set, not to the number of octets in the encoding, nor to the line length in any rendition of the document, where these are different. The exact significance of the character strings is determined by the "string-significance" parameter. If its value is "variable," the length of the character strings is less than or equal to the 121 PART 10 - FTAM Phase 3 December 1993 (Stable) length given. If the value is "fixed," the length of each character string is exactly equal to the length given. If the document is interpreted on a character imaging device (outside the scope of ISO 8571), the interpretation depends on the character set in use. a) If the character set contains format effectors, they shall be interpreted as defined in ISO 6429; end of string and end of file access data unit are given no formatting significance, and do not contribute to the document semantics; b) If the character set does not contain format effectors, the end of each character string is interpreted as implying carriage return and line feed formatting actions in any rendition. The end of file access data unit is given no formatting significance beyond that attached to the end of the string in it. C.3.8 Abstract syntactic structure The abstract syntactic structure of the document is a hierarchically structured file as defined in the ASN.1 modules ISO8571-FADU and ISO 8571-CONTENTS in ISO 8571, in which each of the file contents data elements has the abstract syntactic structure of "NBS-Text." 122 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3.9 Definition of transfer C.3.9.1 Datatype definitions The file consists of data values which are of either a) Datatype1 defined in table 7, the ASN.1 datatype declared as "NBS-Text" in the NBS simple text abstract syntax definition. The choice in "NBS-Text" is determined by the universal-class-number parameter; or b) Datatype2 defined in table 7, the ASN.1 datatype declared as "Data-Element" in the ASN.1 module ISO 8571- FADU. C.3.9.2 Presentation data values The document is transferred as a series of presentation data values, each of which is either a) one value of the ASN.1 datatype "Datatype1," carrying one of the character strings of the document. Each character shall be transmitted using one of the character sets identified by the universal-class-number parameter. All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname1" declared in table 7; or b) one value of the ASN.1 datatype "Datatype2." All values are transmitted in the same (but any) presentation context established to support the abstract syntax name "asname2" declared in table 7. NOTES 1 Specific carrier standards may impose additional constraints on the presentation context to be used, where the above permits a choice. 2 Any document type defined in this entry either makes no use of Datatype2, or starts with a Datatype2 transmission. Boundaries between P-DATA primitives are chosen locally by the sending entity at the time of transmission, and carry no semantics of the document type. Receivers which support this document type shall accept a document with any of the permitted 123 PART 10 - FTAM Phase 3 December 1993 (Stable) transfer options. 124 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3.9.3 Sequence of presentation data values The sequence of presentation data values of type a) and the sequence of presentation data values of types a) and b) is the same as the sequence of character strings within a Data Unit, and Data Units in the hierarchical structure, when flattened according to the definition of the hierarchical file model in ISO 8571-2. C.3.10 Transfer syntax An implementation supporting this document type shall support the transfer syntax generation rules named in table 7 for all presentation data values transferred. C.3.11 ASE Specific Specifications C.3.11.1 Simplification and relaxation C.3.11.1.1 Simplification to FTAM-1 This simplification loses information. The document type NBS-12 may be accessed as a document type FTAM- 1. The resultant document contains the same sequence of data values as would result from accessing the structured text file in access context UA. That is, only the presentation data values in the abstract syntax "asname1" are present. If the "character- set" parameter was present before the simplification, its contents will be added to the beginning of each string. NOTE - The boundary between file access data units remains a boundary between strings, but any special significance given to it is lost. C.3.11.1.2 Relaxation to FTAM-2 The document type NBS-12 may be relaxed to the document type FTAM-2. If the "character-set" parameter was present before the relaxation, its contents will be added to the beginning of each string. 125 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3.11.1.3 Character set relaxation This operation loses explicit information in the document type identification. A document of type NBS-12 may be relaxed to a different document of type NBS-12 with a different "universal-class-number" parameter value; a different "character-set" parameter value; different values for both of these parameters; a different "universal-class-number" parameter value and no "character-set" parameter value; or no "character-set" parameter value if the resultant document type permits all characters from the original document type. If this relaxation involves including format effectors and none were present before the relaxation, the characters "carriage return" and "line-feed" shall be added to the end of each string. NOTE - If the characters "carriage return" and "line feed" are not part of the format effectors, the formatting action may be represented by "newline," or some other implementation specific choice if there is no representation of "newline" defined. C.3.11.1.4 String length relaxation This operation loses explicit information in the document type identification. A document of type NBS-12 may be relaxed to another document type NBS-12 with a larger "maximum-string-length" parameter. C.3.11.2 Access context selection A document of type NBS-12 may be accessed in any one of the access contexts defined in the sequential flat constraint set. The presentation data units transferred in each case are those derived from the structuring elements defined for that access context in ISO 8571-2. 126 PART 10 - FTAM Phase 3 December 1993 (Stable) C.3.11.3 The INSERT operation When the INSERT operation is applied at the end of file, the transferred material shall be the series of FADUs which would be generated by reading any NBS-12 document type with the same parameter values in access context FA. 127 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex D (normative) Constraint Sets D.1 NBS random access constraint set Table 8 - Basic constraints in the NBS Random Access Constraint Set Constraint set descriptor "NBS random access constraint set" Constraint set identifier {iso identified-organization oiw(14) ftamsig(5) constraint- set(4) nbs-random-access(2)} Node names All names shall be of the same type; the type of the names and an ordering of the names shall be defined when reference is made to the constraint set. File access actions Locate, Read, Insert, Erase, Replace Qualified actions None Available access context UA Creation state Root node without an associate data unit Location after open Root node Beginning of file Root node End of file No node selected Read whole file Read in access context UA with FADU-Identity of "begin" 128 PART 10 - FTAM Phase 3 December 1993 (Stable) Write whole file Transfer a series of leaf FADUs which would be generated by reading the whole file in access context UA; perform the transfer with a FADU Identity of "end" and a file access action of "insert," or with a FADU Identity of "begin" and an action of "replace," or with an FADU identity of "node number" and an action of "replace." Table 9 - Identity constraints in the NBS Random Access Constraint Set Action Begin End NodeSeq Node number Locate leaf Read whole leaf Insert leaf Erase whole leaf Replace whole leaf NOTE - NodeSeq = A sequence of Node-Names with a single member D.1.1 Field of application The NBS Random Access constraint set applies to files which are structured into a sequence of individual FADUs and to which access may be made randomly by NodeSeq. The structuring of the file into individual FADUs is determined by the Node-Name. D.1.2 Basic constraints The basic constraints in the NBS Random Access constraint set are given in table 8. 129 PART 10 - FTAM Phase 3 December 1993 (Stable) D.1.3 Structural constraints The root node shall not have an associated data unit; all children of the root node shall be leaf nodes and shall have an associated data unit; all arcs from the root node shall be of length one. D.1.4 Action constraints Insert: the insert action is allowed only at the end of the file, with FADU-Identity of "end"; the new node is inserted following all existing nodes in the file. The location following the insert is "end." Erase: the erase action is allowed at the root node to empty the file, with FADU-Identity of "begin." The result is a solitary root node without an associated data unit. Erase with the FADU- Identity of "node number" means truncation of the file. Replace whole file: the FADU-Identity is "begin" and the complete series of new FADU contents is sent. Replace new leaves: the FADU-Identity is "node number" and the number of FADUs being replaced is given by the number of FADUs sent. D.1.5 Identity constraints The FADU-Identity associated with the file action shall be one of the identities: begin, end, Node Number and NodeSeq. The actions with which these identities can be used are given in table 9. 130 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex E (normative) Abstract Syntaxes E.1 NBS Node Name Abstract Syntax Abstract Syntax Name { iso identified-organization oiw(14) ftamsig(5) abstract- syntax(2) nbs-node-name(3) } "NBS random access node name abstract syntax" This is an abstract syntax for the user-coded Node-Name in the FTAM FADU abstract syntax. NBS-AS3 DEFINITIONS::= BEGIN NBS-Node-Name::= SEQUENCE { starting-fadu [0] IMPLICIT INTEGER, fadu-count [1] IMPLICIT INTEGER } --a "fadu-count" of 0 specifies the --range of FADUs --beginning at "starting-fadu" and --ending at "end of file" END For this abstract syntax the following transfer syntax can be used. { joint-iso-ccitt asn1(1) basic-encoding(1) } "Basic Encoding of a single ASN.1 type" 131 PART 10 - FTAM Phase 3 December 1993 (Stable) E.2 NBS Random Binary Access File Abstract Syntax Abstract Syntax Name { iso identified-organization oiw(14) ftamsig(5) abstract- syntax(2) nbs-random-binary(4) } "NBS random binary access file abstract syntax" This is an abstract syntax for the transfer of the file contents for NBS random binary files. NBS-AS4 DEFINITIONS::= BEGIN NBS-Random Binary ::= OCTET STRING --contains one or more presentation data values --concatenated together. --Each presentation data value is defined as --Datatype1 in table 4. END For this abstract syntax, the following transfer syntax can be used: { joint-iso-ccitt asn1(1) basic-encoding(1) } "Basic Encoding of a single ASN.1 type" 132 PART 10 - FTAM Phase 3 December 1993 (Stable) E.3 NBS Simple Text Abstract Syntax Abstract Syntax Name {iso identified-organization oiw(14) ftamsig(5) abstract-syntax(2) nbs-simple-text(5) } "NBS simple text abstract syntax" NBS-AS5 DEFINITIONS::= BEGIN NBS-Text::= CHOICE { IA5String,--Universal Class 22 GraphicString, --Universal Class 25 VisibleString, --Universal Class 26 GeneralString --Universal Class 27 } END For this abstract syntax, the following transfer syntax can be used: {joint-iso-ccitt asn1(1) basic-encoding(1)} "Basic encoding of a single ASN.1 type" 133 PART 10 - FTAM Phase 3 December 1993 (Stable) 134 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex F (normative) Delta Protocol Implementation Conformance Statement (PICS) Pro forma (Refer to the Working Implementation Agreements.) 135 PART 10 - FTAM Phase 3 December 1993 (Stable) 136 PART 10 - FTAM Phase 3 December 1993 (Stable) Annex G (normative) Amendments and Corrigenda Implementations conforming to these agreements shall implement the defect report solutions contained in the following: FTAM: a) ISO 8571-1/Cor.1:1990; b) ISO 8571-2/Cor.1:1990; c) ISO 8571-3/Cor.1:1990; d) ISO 8571-4/Cor.1:1990; e) ISO 8571-3/Cor.2; f) ISO 8571-4/Cor.2. Editor's Note - The corrigenda ISO 8571-3/Cor.2, and ISO 8571-4/Cor.2 is to be published. Until it is available, the solutions can be found in the documents ISO/IEC JTC/SC21 N5234 and ISO/IEC JTC1/SC21 N 5235. 137