AS/NZS 3646.

4:1993
ISO 8571-4:1988
ISO 8571-4:1988/Amdt 1:1992
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Australian/New Zealand Standard

Information processing systems—

Open Systems Interconnection—
File transfer, access and
management

Part 4: File protocol specification

 AS/NZS 3646.4:1993

This Joint Australian/New Zealand Standard was prepared by Joint Technical

Committee IT/1, Information Systems—Interconnection. It was approved on behalf of
the Council of Standards Australia on 17 May 1993 and on behalf of the Council of
Standards New Zealand on 26 July 1993. It was published on 16 August 1993.
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

The following interests are represented on Committee IT/1:

AOTC
Australian Association of Permanent Building Societies
Australian Bankers’ Association
Australian Bureau of Statistics
Australian Chamber of Commerce and Industry
Australian Computer Society
Australian Computer Users Association
Australian Information Industry Association
Australian Telecommunications Users Group
Australian Vice Chancellors Committee
Department of Defence
Department of Industry, Technology and Commerce
Information Exchange Steering Committee
Institute of Information and Communication Technologies, CSIRO
Life Insurance Federation of Australia
OPTUS
Standards New Zealand

Review of Standards. To keep abreast of progress in industry, Joint Australian/

New Zealand Standards are subject to periodic review and are kept up to date by the
issue of amendments or new editions as necessary. It is important therefore that
Standards users ensure that they are in possession of the latest edition, and any
amendments thereto.
Full details of all Joint Standards and related publications will be found in the
Standards Australia and Standards New Zealand Catalogue of Publications; this
information is supplemented each month by the magazines ‘The Australian Standard’
and ‘Standards New Zealand’, which subscribing members receive, and which give
details of new publications, new editions and amendments, and of withdrawn
Standards.
Suggestions for improvements to Joint Standards, addressed to the head office of either
Standards Australia or Standards New Zealand, are welcomed. Notification of any
inaccuracy or ambiguity found in a Joint Australian/New Zealand Standard should be
made without delay in order that the matter may be investigated and appropriate action
taken.
 AS/NZS 3646.4:1993
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Australian/New Zealand Standard

Information processing systems—

Open Systems Interconnection—
File transfer, access and
management
Part 4: File protocol specification

First publi shed as Joint Standard AS/NZS 3646.4:1993.

PUBLISHED JOINTLY BY:

STANDARDS AUSTRALIA
1 The Crescent,
Homebush NSW 2140 Australia

STANDARDS NEW ZEALAND

Level 10, Standards House,
155 The Terrace,
Wellington 6001 New Zealand
ISBN 0 7262 8307 X
 2

PREFACE

This Standard was prepared by the Joint Australia/New Zealand Standards Committee IT/1 on Information
Systems—Interconnection. It is identical with, and has been reproduced from, ISO 8571-4:1988, Information
processing systems—Open Systems Interconnection—File Transfer, Access and Management, Part 4: File Protocol
Specification.

Amendment 1 is bound at the back of this Standard. Text affected is marked by a marginal bar.

This Joint Standard is one of a series of Open Systems Interconnection (OSI) Standards which are currently under
development. Since OSI Standards are developmental, there may be some minor difficulties encountered in their
implementation. For this reason, Standards Australia will be providing, through the OSI Help Desk, a service to
coordinate and disseminate information concerning difficulties which are identified in using this Standard.

Under arrangements made between Standards Australia/Standards New Zealand and the international Standards
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

bodies, ISO and IEC, as well as certain other Standards organizations, users of this Joint Standard are advised
of the following:

(a) In Australia copyright is vested in Standards Australia. In New Zealand copyright is vested in Standards
New Zealand.

(b) The number of this Joint Standard is not reproduced on each page; its identity is shown only on the cover
and title pages.

For the purpose of this Joint Standard, the ISO text should be modified as follows:

(i) Terminology The words ‘Australian Standard’, ‘New Zealand Standard’ or ‘Joint Australian/New Zealand
Standard’ should replace the words ‘International Standard’ wherever they appear.

(ii) References The references to International Standards should be replaced by references to the following
Australian/New Zealand Standards:

Reference to International Standard Australian/New Zealand Standard

or other Publication

ISO AS
7498 Information Processing Systems— 2777 Information processing systems—
Open Systems Interconnection— Open Systems Interconnection—
Basic Reference Model Basic reference model
7498-3 Part 3: Naming and Addressing 2777.3 Part 3: Naming and addressing

8326 Information Processing Systems— 3591 Information processing systems—

Open Systems Interconnection— Open Systems Interconnection—
Basic Connection Oriented Session Basic connection oriented session service
Service Definition definition

8571 Information processing systems— 3646 Information processing systems—

Open systems interconnection—
File transfer, access and management
8571-1 Part 1: General introduction
8571-2 Part 2: Virtual Filestore definition
8571-3 Part 3: File Service definition
Open Systems Interconnection—
File transfer, access and management
3646.1 Part 1: General introduction
3646.2 Part 2: Virtual filestore definition
3646.3 Part 3: File service definition

8649 Information Processing Systems— 3683 Information processing systems—

Open Systems Interconnection— Open Systems Interconnection—
Service definition for the Association Service definition for the Association
Control Service Element Control Service Element
 3

8650 Information Processing Systems— 3684 Information processing systems—

Open Systems Interconnection— Open Systems Interconnection—
Protocol specification for the Association Protocol specification for the Association
Control Service Element Control Service Element

8822 Information Processing Systems— 3615 Information processing systems—

Open Systems Interconnection— Open Systems Interconnection—
Connection-oriented Presentation Service Connection oriented presentation service
Definition definition

8824 Information Processing Systems— 3625 Information technology—

Open Systems Interconnection— Open Systems Interconnection—
Specification of Abstract Syntax Notation Specification of Abstract Syntax Notation
One (ASN.1) One (ASN.1)

8825 Information Processing Systems— 3626 Information technology—

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Open Systems Interconnection— Open Systems Interconnection—

Specification of basic encoding rules for Specification of basic encoding rules for
Abstract Syntax Notation One Abstract Syntax Notation One (ASN.1)

 Copyri ght STANDARDS AUSTRALIA/STANDARDS NEW ZEALAND

Users of Standards are reminded that copyri ght subsists in all Standards Austr alia and Standards New Zealand publications and
soft ware. Except where the Copyri ght Act all ows and except where provided for below no publications or software produced by
Standards Australi a or Standards New Zealand may be reproduced, stored in a retri eval system in any form or tr ansmit ted by any
means without pri or permission in wri ti ng fr om Standards Australi a or Standards New Zealand. Permission may be conditi onal on an
appropri ate royalty payment. Austr alian requests for permission and information on commercial software royalti es should be directed
to the head offi ce of Standards Austr alia. New Zealand requests should be directed to Standards New Zealand.
Up to 10 percent of the technical content pages of a Standard may be copied for use exclusively in-house by purchasers
of the Standard without payment of a royalt y or advice to Standards Australi a or Standards New Zealand.
Inclusion of copyri ght materi al in computer software programs is also permitt ed without royalty payment provided such
programs are used exclusively in-house by the creators of the programs.
Care should be taken to ensure that material used is from the current edit ion of the Standard and that it is updated whenever the
Standard is amended or revised. The number and date of the Standard should therefore be clearly identif ied.
The use of material in pri nt form or in computer soft ware programs to be used commercially, with or without payment, or in
commercial contr acts is subject to the payment of a royalty. This policy may be vari ed by Standards Austr alia or Standards
New Zealand at any time.
 4

CONTENTS

Page
0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Field of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 Definitions and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Section one: General

5 Overview of the file protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

5.1 Service supported by the file protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.2 Services assumed by the basic file protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.3 Functions provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.4 Model used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.5 Correspondence between service primitive names and FPD U names . . . . . . . . . . 13

5.6 Protocol functional units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Section two: Basic file protocol

6 State of the association provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.1 Operation of the protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.2 Additional state information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

7 File protocol data units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

8 File initiating entity actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8.1 FTAM regime establishment (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8.2 FTAM regime termination (orderly) (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8.3 File selection (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8.4 File deselection (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8.5 File creation (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8.6 File deletion (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8.7 Read attributes (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8.8 Change attributes (Enhanced management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8.9 File open (Read, Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8.10 File close (Read, Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.11 Begin Group (Grouping) ........... ... .. .... ........ .... .. ... ..... 21

8.12 End Group (Grouping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

8.13 Recovery (Recovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

8.14 Locate (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

 5

Page
8.15 Erase (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

9 File responding entity actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9.1 FTAM regime establishment (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9.2 FTAM regime termination (orderly) (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9.3 File selection (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9.4 File deselection (Kernel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.5 File creation (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.6 File deletion (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9.7 Read attributes (Limited management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

9.8 Change attributes (Enhanced management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9.9 File Open (Read, Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9.10 File close (Read, Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

9.11 Begin Group (Grouping) ........... ... .. .... ........ .... .. ... ..... 26

9.12 End Group (Grouping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

9.13 Recovery (Recovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

9.14 Locate (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9.15 Erase (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

10 File general actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

10.1 FTAM regime termination (abrupt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

10.2 Protocol errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Section three: The basic bulk data transfer protocol

11 State of bulk data transfer activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

11.1 State of the connection endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

11.2 Additional state of the entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

12 Bulk data transfer protocol data units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

13 Bulk data transfer initiating entity actions ........... ... .. .... ........ .... .. . 30

13.1 Read (Read) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

13.2 Write (Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

13.3 Transfer end (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

14 Bulk data transfer responding entity actions ........... ... .. .... ........ .... . 31

14.1 Read (Read) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

14.2 Write (Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

14.3 Transfer end (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

15 Bulk data transfer sending entity actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

 6

Page
15.1 Send data (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

15.2 End of data transfer (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

15.3 Checkpoint insertion (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

16 Bulk data transfer receiving entity actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

16.1 Data transfer (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

16.2 End of data transfer (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

16.3 Checkpoint reception (Read, write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

17 Bulk data transfer general actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

17.1 Discarding (Read, Write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

17.2 Cancel (Read,write) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

17.3 Restarting (Restart data transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Section four: The error recovery protocol

18 Protocol mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

18.1 Error detection and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

18.2 Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

18.3 Negotiation of restart point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

18.4 Docket contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

19 Specification of the error control protocol ........... ... .. .... ........ .... .. . 36

19.1 Normal operation ........... ... .. .... ........ .... .. ... .......... 36

19.2 Recovery from errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Section five: Abstract Syntax

20 Abstract Syntax Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

20.1 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

20.2 Primitive Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

20.3 AS N.1 Module Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

20.4 Abstract Syntax Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

21 Application Context Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Section six: Conformance

22 Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

22.1 Statement requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

22.2 Static requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

22.3 Dynamic requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

 7

Page
Annexes

A Protocol state tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

B Reference to FTAM PDU definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

C AS N.1 cross reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Figures

1 Relationship between file protocol and service definitions ........... ... .. .... ... 9
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

2 File Protocol Machine model ........... ... .. .... ........ .... .. ... ....... 12

3 Extended File Protocol Machine model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Procedure for class I errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5 Procedure for class II errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 Procedure for class III errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7 FTAM regime PDU s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8 File selection and file open regime PDU s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

9 Bulk data transfer PDU s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

10 Application wide types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

11 File attribute types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

12 State machine system model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

 8

Page
Tables

1 Presentation and Session Services required by FTAM Functional Units . . . . . . . . . . . . . 11

2 Protocol Data Units, FTAM regime establishment ........... ... .. .... ........ . 14

3 Protocol data units, File regime control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Relationship of F-INITIALIZE parameters to A-AS SO CIATE parameters . . . . . . . . . . . . . 17

5 Protocol Data Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.
 9

Information processing systems—Open Systems

Interconnection—File transfer, access and management

Part 4:
File protocol specification

0 Introduction This part of ISO 8571 contains the following annexes

which form part of the standard:
ISO 8571 is one of a set of International Standards
Annex A - Protocol State Tables;
produced to facilitate the interconnection of computer
systems. Its relation to other International Standards in the Annex B - Reference to FTAM PDU Definitions;
set is defined by the Reference Model for Open Systems and the following annex which does not form part of the
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Interconnection (ISO 7498). The Reference Model sub- standard:

divides the area of standardization for interconnection into Annex C - ASN.1 cross reference.
a series of layers of specification, each of manageable
size.
1 Scope
The aim of Open Systems Interconnection is to allow, with ISO 8571-4 consists of four main sections:
a minimum of technical agreement outside the inter-
connection standards, the interconnection of computer a) the basic protocol (in sections two and three), which
systems: supports the internal file service;
a) from different manufacturers, b) the error recovery protocol (in section four), which
supports the external file service;
b) under different managements,
For each of these, ISO 8571-4 includes a formal state-
c) of different levels of complexity, ment of the nature of the automaton giving the necessary
d) of different ages. behaviour of each of the participating entities. It states:
ISO 8571 defines a file service and specifies a file 1) the actions to be taken on receiving request
protocol available within the application layer of the and response primitives issued by a file service
Reference Model. The service defined is of the category user;
Application Service Element (ASE). It is concerned with 2) the actions to be taken on receiving indication
identifiable bodies of information which can be treated as and confirm primitives issued by the Presentation
files, and may be stored within open systems or passed Service provider;
between application processes.
3) the actions to be taken as a result of events
ISO 8571 defines a basic file service. It provides sufficient within the local system.
facilities to support file transfer, and establishes a
c) the definition (in section five) of the abstract syntax
framework for file access and file management. ISO 8571
required to convey the file protocol control information.
does not specify the interfaces to a file transfer or access
facility within the local system. d) the conformance requirements to be met by imple-
mentors of this protocol (in section six).
ISO 8571 consists of the following four parts:
The scope of the File Protocol is limited to the inter-
Part 1: General introduction
connection of systems; it does not specify or restrict the
Part 2: Virtual Filestore definition
possible implementation of interfaces within a computer
Part 3: File Service definition
system.
Part 4: File Protocol specification

Figure 1—Relationship between file protocol and service definitions

COPYRIGHT
 10

2 Field of application ISO 8649, Information Processing Systems - Open

The purpose of ISO 8571-4 within the OSI scheme is to
specify the behaviour which must be exhibited by a
system in order to take part in the provision of the file
transfer access and management service.
The file protocol specification references three service
definitions in order to express the environment within
which it is applied. ISO 8571-3 defines the aims and
objectives that the protocol must achieve. The Presenta-
tion Service (ISO 8822) and ACSE Service (ISO 8649-2)
define the set of assumptions about the supporting
facilities which the protocol may exploit (see figure 1).
Systems Interconnection - Service definition for
the Association Control Service Element
ISO 8650, Information Processing Systems - Open
Systems Interconnection - Protocol specification for
the Association Control Service Element
ISO 8822, Information Processing Systems - Open
Systems Interconnection - Connection-oriented
Presentation Service Definition.

3 References ISO 8824, Information Processing Systems - Open

Systems Interconnection - Specification of Abstract
ISO 7498, Information Processing Systems - Open Syntax Notation One (ASN.1).
Systems Interconnection - Basic Reference Model

ISO 7498-3, Information Processing Systems - Open ISO 8825, Information Processing Systems - Open
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Systems Interconnection - Basic Reference Model Systems Interconnection - Specification of basic

- Part 3: Naming and Addressing encoding rules for Abstract Syntax Notation

ISO 8326, Information Processing Systems - Open

Systems Interconnection - Basic Connection Oriented
Session Service Definition.
4 Definitions and abbreviations
ISO 8571, Information processing systems - Open
systems interconnection - File transfer, access and
management. Terms and abbreviations are defined in ISO 8571-1. The
- Part 1: General introduction. definitions of service primitive names and service state
- Part 2: Virtual Filestore definition. names given in ISO 8571-3 are also used in this part of
- Part 3: File Service definition. ISO 8571.

COPYRIGHT
 This is a free preview. Purchase the entire publication at the link below:

AS/NZS 3646.4:1993, Information processing

systems - Open Systems Interconnection - File
transfer, access and management File protocol
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

specification

Looking for additional Standards? Visit SAI Global Infostore

Subscribe to our Free Newsletters about Australian Standards® in Legislation; ISO, IEC, BSI and more
Do you need to Manage Standards Collections Online?
Learn about LexConnect, All Jurisdictions, Standards referenced in Australian legislation
Do you want to know when a Standard has changed?
Want to become an SAI Global Standards Sales Affiliate?

Learn about other SAI Global Services:

LOGICOM Military Parts and Supplier Database

Metals Infobase Database of Metal Grades, Standards and Manufacturers
Materials Infobase Database of Materials, Standards and Suppliers
Database of European Law, CELEX and Court Decisions

Need to speak with a Customer Service Representative - Contact Us