Connected: An Internet Encyclopedia
RFC 1123 - 4.1.2.2 Telnet Format Control: RFC-959 Section 3.1.1.5.2

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 4. FILE TRANSFER
Up: 4.1 FILE TRANSFER PROTOCOL -- FTP
Up: 4.1.1 INTRODUCTION
Prev: 4.1.2.1 LOCAL Type: RFC-959 Section 3.1.1.4
Next: 4.1.2.3 Page Structure: RFC-959 Section 3.1.2.3 and Appendix I

### 4.1.2.2 Telnet Format Control: RFC-959 Section 3.1.1.5.2

A host that makes no distinction between TYPE N and TYPE T SHOULD implement TYPE T to be identical to TYPE N.

DISCUSSION:

  This provision should ease interoperation with hosts that do make this distinction.

  Many hosts represent text files internally as strings of ASCII characters, using the embedded ASCII format effector characters (LF, BS, FF, ...) to control the format when a file is printed. For such hosts, there is no distinction between "print" files and other files. However, systems that use record structured files typically need a special format for printable files (e.g., ASA carriage control). For the latter hosts, FTP allows a choice of TYPE N or TYPE T.

Next: 4.1.2.3 Page Structure: RFC-959 Section 3.1.2.3 and Appendix I

Connected: An Internet Encyclopedia
RFC 1123 - 4.1.2.2 Telnet Format Control: RFC-959 Section 3.1.1.5.2