# MIME FTP Access-types

Brian Capouch (brianc@saintjoe.EDU)
Wed, 3 Nov 1993 21:23:51 -0600 (CST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mitra: "URN to URC resolution scenario"
- Previous message: Michael Mealling: "Re-write of (formerly) URM paper!"

    Message-Id: <4gq7L7O3LE06M1pV5V@saintjoe.edu>

    Date: Wed,  3 Nov 1993 21:23:51 -0600 (CST)

    From: Brian Capouch <brianc@saintjoe.EDU>

    To: uri@bunyip.com

    Subject: MIME FTP Access-types

As I promised the group yesterday morning, here is the relevant portion
of the MIME RFC relating to FTP access modes:

-- Included file begins here --

MODE -- A case-insensitive string indicating the mode to be used
when retrieving the information. The legal values for access-type
"TFTP" are "NETASCII", "OCTET", and "MAIL", as specified by the
TFTP protocol [RFC-783]. The legal values for access-type "FTP"
are "ASCII", "EBCDIC", "IMAGE", and "LOCALn" where "n" is a
decimal integer, typically 8. These correspond to the
representation types "A" "E" "I" and "L n" as specified by the FTP
protocol [RFC-959]. Note that "BINARY" and "TENEX" are not valid
values for MODE, but that "OCTET" or "IMAGE" or "LOCAL8
should be used instead. IF MODE is not specified, the default value is
"NETASCII" for TFTP and "ASCII" otherwise.

    --

    Brian

- Next message: Mitra: "URN to URC resolution scenario"
- Previous message: Michael Mealling: "Re-write of (formerly) URM paper!"