ANSI-INCITS-343-2001.pdf

ANSI INCITS 343-2001 (formerly ANSI NCITS 343-2001) for Information Technology Scheduled Transfer Reliable Transport Profile (ST-RTP) Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- ANSI NCITS 343-2001 American National Standard for Information Technology Scheduled Transfer Reliable Transport Profile (ST-RTP) Secretariat Information Technology Industry Council (ITI) Approved February 20, 2001 American National Standards Institute, Inc. ® Abstract This American National Standard specifies limitations and requirements that may be accepted within the Scheduled Transfer (ST) protocol in order to facilitate interoperability for reliable data transports. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgement of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. American National Standard Published by American National Standards Institute, Inc. 11 West 42nd Street, New York, NY 10036 Copyright © 2001 by Information Technology Industry Council (ITI) All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America CAUTION: The developers of this standard have requested that holders of patents that may be required for the implementation of the standard disclose such patents to the publisher. However, neither the developers nor the publisher have undertaken a patent search in order to identify which, if any, patents may apply to this standard. As of the date of publication of this standard and following calls for the identification of patents that may be required for the implementation of the standard, no such claims have been made. No further patent search is conducted by the de- veloper or publisher in respect to any standard it processes. No representation is made or implied that licenses are not required to avoid infringement in the use of this standard. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- i Contents Page Forewordii Introduction v 1Scope. 1 2Normative reference 1 3Definitions and conventions. 1 3.1Definitions 1 3.2Editorial conventions 2 3.2.1Binary notation. 2 3.2.2Hexadecimal notation 2 3.2.3Bit/Byte naming conventions 2 3.2.4Acronyms and other abbreviations 2 3.3Applicability and use of this document. 2 4System overview 3 4.1General 3 4.2Compliance with ST. 3 4.3Environmental requirements beyond ST 3 5Profile settings . 3 Tables 1General behavior and options 4 2Connection behavior and options 4 3Flags during data transfers 5 4Transfer units. 5 5Other data transfer behaviors and options. 6 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- ii Foreword(This foreword is not part of American National Standard NCITS 343-2001.) This American National Standard specifies limitations and requirements that may be accepted within the Scheduled Transfer (ST) protocol in order to facilitate interopera- bility for reliable data transports. Requests for interpretation, suggestions for improvement or addenda, or defect re- ports are welcome. They should be sent to the National Committee for Information Technology Standards (NCITS), ITI, 1250 Eye Street, NW, Suite 200, Washington, DC 20005. This standard was processed and approved for submittal to ANSI by NCITS. Com- mittee approval of the standard does not necessarily imply that all committee mem- bers voted for approval. At the time it approved this standard, NCITS had the following members: Karen Higginbottom, Chair David Michael, Vice-Chair Kathleen McMillan, Acting Secretary Organization Represented Name of Representative Apple Computer, Inc. David Michael Wanda Cox (Alt.) Bull HN Information Systems, Inc. Randall Kilmartin Compaq Computer Corporation . Scott Jameson Stephen Heil (Alt.) John Hurd (Alt.) Hewlett-Packard Company. Karen Higginbottom Wendy Fong (Alt.) Hitachi John Neumann Harukazu Miyamoto (Alt.) IBM Corporation . Ronald F. Silletti Chuck Adams (Alt.) Institute for Certification of Computer Professionals Kenneth M. Zemrowski Thomas Kurihara (Alt.) Lucent Technologies, Inc. Herbert Bertine Tom Rutt (Alt.) Microsoft Corporation. Mike Deese George Willingmyre (Alt.) Joseph Zajaczkowski (Alt.) National Institute of Standards conformance can only be assured by ac- tual testing of interoperability with independently developed products that have the same profile. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- 1 AMERICAN NATIONAL STANDARD ANSI NCITS 343-2001 1 Scope This American National Standard specifies limita- tions and requirements that may be accepted within the Scheduled Transfer (ST) protocol (ANSI NCITS 337-2000) in order to facilitate interoperabil- ity for reliable data transports. This profile is an interoperability specification. The profile provides implementation guidelines for sys- tems manufacturers, system integrators, compo- nent manufacturers, and users seeking to design and select interoperable ST peripherals, hosts, and components. This profile specifies which settings of the ST parameters and protocol options have been selected for interoperable implementation. There should be no implication that this profile is suitable for all users or circumstances. Other map- pings for the ST protocol are being developed and may be more suitable for a particular set of needs. Requirements may also force implementors to operate outside of any profile definition. This profile is not a certification document; con- formance can only be assured by actual testing of interoperability with independently developed prod- ucts that have the same profile. This profile prohibits or requires features that are optional, and prohibits the use of some non- optional features in the referenced ANSI standard. Internal characteristics of conforming implementa- tions are not defined by this standard. 2 Normative reference The following standard contains provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the edi- tion indicated was valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standard listed below. Copies of the following documents can be obtained from ANSI: Approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC, ITUT) and approved foreign standards (including BSI, JIS, and DIN). For further information, contact ANSI Customer Service Department at 212-642-4900 (phone), 212-302-1286 (fax) or via the World Wide Web at http:/www.ansi.org. Additional availability contact information is provided below as needed. ANSI NCITS 337-2000, Information Technology - Scheduled Transfer Protocol (ST) 3 Definitions and conventions 3.1 Definitions Since this document does not allow any behavior that is not already specified by the Schedule Trans- fer protocol and the definitions of that document American National Standard for Information Technology Scheduled Transfer Reliable Transport Profile (ST-RTP) Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- 2 ANSI NCITS 343-2001 are included by reference, there are no new words to be defined herein. 3.2 Editorial conventions In this standard, certain terms that are proper names of signals or similar terms are printed in uppercase to avoid possible confusion with other uses of the same words (e.g., DATA). Any lower- case uses of these words have the normal techni- cal English meaning. A number of conditions, sequence parameters, events, states, or similar terms are printed with the first letter of each word in uppercase and the rest lowercase (e.g., State, Source). Any lowercase uses of these words have the normal technical English meaning. The word shall, when used in this American National Standard, states a mandatory rule or requirement. The word should, when used in this standard, states a recommendation. 3.2.1 Binary notation Binary notation is used to represent relatively short fields. For example a two-bit field containing a binary value of 10 is shown in binary format as b10. 3.2.2 Hexadecimal notation Hexadecimal notation is used to represent some fields. For example a two-byte field containing a binary value of b1100010000000011 is shown in hexadecimal format as x'C403'. 3.2.3 Bit/Byte naming conventions In a parameter that uses multiple bytes, the most- significant byte is the lowes numbered byte. In a parameter that uses multiple bits, the most-sig- nificant bit is the highest numbered bit. 3.2.4 Acronyms and other abbreviations FTPFile Transfer Protocol STScheduled Transfer WANWide Area Network 3.3 Applicability and use of this document Since the nature of this standard is a profile, the usual definitions of the following words do not apply. Prohibited: If a feature is Prohibited, it means that it shall not be used with this profile. An implemen- tation may use the feature to communicate with ST implementations when not using this profile. This document does not prohibit the implementa- tion of features, only their use between compliant implementations. Required: If a feature or parameter value is Required, it means that it shall be used between compliant implementations. Compliant implemen- tations are required to implement the feature. An implementation may use the feature or other fea- tures to communicate with non-compliant imple- mentations. Allowed: If a feature or parameter value is Allowed, it means that it may be used between compliant implementations. Compliant implemen- tations are not required to implement the feature, but if they do, the feature shall be used as described in this document. Typically, the potential user of a feature may determine if the potential recipient supports that feature via a Required dis- covery process. Invocable: If a feature or parameter value is Invo- cable, it means that it may be used between com- pliant implementations. Compliant implementations are required to implement the feature, and make available the use of the feature. Invocable is differ- ent than Allowable or Required in that an originator may invoke the feature if needed, but the originator is not required to invoke it, and may never need to. Tables in the following clauses list features described in the ST protocol. These tables indicate whether the feature is Required, Prohibited, Invo- cable, or Allowed for compliance with this profile; or whether a parameter is Required to be a particular value or limited range of values for compliance with this profile. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=Aramco HQ/9980755100 Not for Resale, 05/09/2007 07:24:37 MDTNo reproduction or networking permitted without license from IHS -,-,- 3 ANSI NCITS 343-2001 Features or parameters that are not listed do not affect the interoperability of ST implementations. The following legend is used for table entries in these clauses: -P the implementation is Prohibited from using the specified feature -R the implementation is Required to sup- port the specified feature -A use of the specified feature is Allowed -I the implementation may Invoke the speci- fied feature 4 System overview 4.1 General This subclause provides an overview of the struc- ture, concepts, and mechanisms used in this ST Reliable Transport Profile. This ST