Browse Prior Art Database

The Data Transfer Protocol (RFC0264)

IP.com Disclosure Number: IPCOM000005903D
Original Publication Date: 1972-Jan-04
Included in the Prior Art Database: 2001-Nov-15
Document File: 10 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Bhushan: AUTHOR [+9]

Abstract

A common protocol is desirable for data transfer in such diverse applications as remote job entry, file transfer, network mail system, graphics, remote program execution, and communication with block data terminals (such as printers, card, paper tape, and magnetic tape equipment, especially in context of terminal IMPs). Although it would be possible to include some or even all of the above applications in an all-inclusive file transfer protocol, a separation between data transfer and application functions may provide flexibility in implementation, and reduce complexity. Separating the data transfer function from the specific applications functions may also reduce proliferation of programs and protocols.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 19% of the total text.

Network Working Group                                         A. Bhushan

Request for Comments: 264                                            MIT

NIC: 7812                                                      B. Braden

                                                                    UCLA

                                                             W. Crowther

                                                                     BBN

                                                              E. Harslem

                                                              J. Heafner

                                                                    Rand

                                                             A. McKenzie

                                                                     BBN

                                                               J. Melvin

                                                                     SRI

                                                             B. Sundberg

                                                                 Harvard

                                                               D. Watson

                                                                     SRI

                                                                J. White

                                                                    UCSB

                                                        15 November 1971

                       THE DATA TRANSFER PROTOCOL

   This paper is a revision of RFC 171, NIC 6793.  The changes to RFC

   171 are given below.  The protocol is then restated for your

   convenience.

CHANGES TO RFC 171

   1) The sequence number field is changed to 16 bits in the error (Type

      B5) transactions, thus resolving the ambiguity in the previous

      specification.  In addition, the information separators (Type B4)

      transactions shall also contain a 16-bit sequence number field.

   2) The modes available (Type B3) transactions shall define only the

      modes available for receive, instead of both receive and send.  In

      simplex connections modes available transactions should not be

      sent as they are meaningless.  In full-duplex connections, the

      modes available transactions are still required.

   3) The code assignments for "End Code" in information separators and

      for "function" in abort transactions have been changed to reflect

      a numerical order rather than "bit-coding".

   4) Minor editorial changes.

Bhushan, et. al.                                                [Page 1]

RFC 264                The Data Transfer Protocol       15 November 1971

I.  INTRODUCTION

      A common protocol is desirable for data transfer in such diverse

      applications as remote job entry, file transfer, network mail

      system, graphics, remote program execution, and communication with

      block data terminals (such as printers, card, paper tape, and

      magnetic tape equipment, especially in context of terminal IMPs).

      Although it would be possible to include some or even all of the

      above applications in an all-inclusive file transfer protocol, a

      separation between data transfer and application functions may

      provide flexibility in implementation, and reduce complexity.

      Separating the data transfer function from the specific

      applications functions may also reduce proliferation of programs

      and protocols.

      We have therefore defined a data transfer protocol (DTP) which

      should be used for transfer of data in file transfer, remote job

      entry, and other applications protocols.  This paper concerns

      itself only with the data transfer protocol.  A companion paper

      (RFC 265) describes the file transfer protocol.

II.  DISCUSSION

      The data transfer protocol (DTP) serves three basic functions.  It

      provides for convenient separation of NCP messages into "logical"

      blocks (transactions, units, records, groups, and files), it

      allows for the separation of data and control information, and it

      includes some error control mechanisms.

Transfer Modes

      Three modes of separating messages into transactions [1] are

      allowed by DTP.  The first is an indefinite bit stream which

      terminates only when the connection is closed (i.e., the bit

      stream represents a single transaction for duration of

      connection).  This mode would be useful in data transfer between

      hosts and terminal IMPs (TIPs).

      The second mode utilizes a "transparent...