I-D ACTION:draft-ietf-ftpext-mlst-07.txt

Internet-Drafts@ietf.org Wed, 16 June 1999 11:39 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23606; Wed, 16 Jun 1999 07:39:37 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA08826 for ietf-123-outbound.10@ietf.org; Wed, 16 Jun 1999 07:35:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA08744 for <all-ietf@loki.ietf.org>; Wed, 16 Jun 1999 07:19:29 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23028; Wed, 16 Jun 1999 07:15:41 -0400 (EDT)
Message-Id: <199906161115.HAA23028@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: ftp-wg@hethmon.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ftpext-mlst-07.txt
Date: Wed, 16 Jun 1999 07:15:40 -0400
Sender: nsyracus@ns.cnri.reston.va.us

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Extensions to FTP Working Group of the IETF.

	Title		: Extensions to FTP
	Author(s)	: R. Elz, P. Hethmon
	Filename	: draft-ietf-ftpext-mlst-07.txt
	Pages		: 57
	Date		: 15-Jun-99
	
In order to overcome the problems caused by the undefined format of
the current FTP LIST command output, a new command is needed to
transfer standardized listing information from Server-FTP to Client-
FTP.  Commands to enable this are defined in this document.
In order to allow consenting clients and servers to interact more
freely, a quite basic, and optional, virtual file store structure is
defined.
 
   This proposal also extends the FTP protocol to allow character sets
   other than US-ASCII[1] by allowing the transmission of 8-bit
   characters and the recommended use of UTF-8[2] encoding.
 
   Much implemented, but long undocumented, mechanisms to permit
   restarts of interrupted data transfers in STREAM mode, are also
   included here.
 
   Lastly, the HOST command has been added to allow a style of 'virtual
   site' to be constructed.
 
   New in this version of this document: Servers now permitted to refuse
   to allow connections with no HOST command if they have good reason
   (ie: MUST NOT changed to SHOULD NOT).  Make it clear that REST is
   only defined to complete a partially completed transfer, and that
   other uses lead to undefined results.  Make it clear(er) that
   type=cdir names are allowed only when the type fact is included in
   the output.  Make it clear(er) that facts are only included when
   relevant, and that the order of their inclusion may be random.  Make
   it clear that a server is not required to list every file that might
   be in a directory listed (it may hide 'hidden' files if it desired).
   Allow OPTS MLST to be refused before authentication.  Several MLST
   related examples have been added.  Created IANA registries of OS
   specific MLST facts and filetypes.  This paragraph will be deleted
   from the final version of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ftpext-mlst-07.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ftpext-mlst-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ftpext-mlst-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ftpext-mlst-07.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ftpext-mlst-07.txt>