Ftp-WG: Fwd: to mlst-15 from mlst-14

==================BEGIN FORWARDED MESSAGE==================
>Return-Path: [email protected]
>Received: from mail.hethmon.com (mail.hethmon.com [208.171.56.195]) by mail.hethmon.com
>    (Hethmon Smtpd Perseus) id 20020408180705-12780-8 ; Mon, 08 Apr 2002 18:07:05 -0500
>Message-Id: <[email protected]>
>Date: Mon, 8 Apr 2002 18:07:05 -0500
>Sender: Steward-owner <[email protected]>
>From: Steward <[email protected]>
>Reply-To: [email protected]
>Subject: Approval Request for ftp-wg
>To: [email protected]
>

----- Steward Marker Line -- Do Not Modify -------
Original-From:  "Pat LaVarre" <[email protected]>
Original-To:  <[email protected]>
Original-Subject:  to mlst-15 from mlst-14
----- Steward Marker Line -- Do Not Modify -------
Remember in January we here reviewed how we got to mlst-14 from mlst-13? =
 Here
now ...

> - ftp://munnari.oz.au/internet-drafts/draft-ietf-ftpext-mlst-14.txt.Z
> - [50360 bytes]
> -Expiration Date: July 2002
> -                                                            January =
2002
...
> + ftp://munnari.oz.au/internet-drafts/draft-ietf-ftpext-mlst-15.txt.Z
> + [52106 bytes]
> +Expiration Date: October 2002
> +                                                              April =
2002


The substantive diff's I see to April mlst-15 from January mlst-14 are =
as
follows ...

>   2.1. Basic Tokens
...
> +        SCHAR          =3D RCHAR / "=3D" ;
...
>     ALPHA, in particular, is case sensitive.
>     That implies that a "token" is a case sensitive
>     value.
> -   That implication is correct.
> +   That implication is correct, except where explicitly stated
> +   to the contrary in this document, or in some other specification
> +   which defines the values this document specifies be used in a
> +   particular context.

>   2.2. Pathnames
...
>     Implementations are advised against converting a UTF-8 pathname
> -   to a local encoding, and
> -   then attempting to invert the encoding later.
> +   to a local charset that
> +   isn't capable of representing the full Unicode character =
repertoire,
> +   and then attempting to invert the charset translation later.

>   7.1. Format of MLSx Requests
...
>     If no argument is given then MLSD must return a listing of the
>     contents of the current working directory, and MLST must return a
>     listing giving information about the current working directory
>     itself.
>     For these purposes, the contents of a directory are whatever
> -   file names (not pathnames)
> +   file or directory names (not pathnames)
>     the server-PI will allow to be referenced when the current
>     working directory is the directory named, and which the
>     server-PI desires to reveal to the user-PI.

>   7.2. Format of MLSx Response
...
> -        value            =3D *RCHAR
> +        value            =3D *SCHAR
...
>     Facts
>     should be provided in each output line only if they both provide
>     relevant information about the file named on the same line, and =
they
>     are in the set requested by the user-PI.
> +   See section 7.9 (page 51).

>  7.5.1. The type Fact
> +   The value of the type fact (the "type-val") is a case independent
> +   string.

>  Acknowledgments
> +        Bill Fenner (and the rest of the IESG)



The less substantive diff's includes fuller and more perfectly =
consistent
examples:

>  7.7.9. Example from another server
...
>     Finally notice that the NVFS supported
>     by this server, in contract to the earlier ones, implements its
>     pathnames in a case independent manner.
> +   The server seems to return
> +   files using the case in which they were requested, when the name =
was
> +   sent by the client, and otherwise uses an algorithm known only to
> +   itself to select the case of the names it returns.

> +7.7.11. A server with a difference
> +
> +C> ... S> ... D> ...
> +
> +   The server shown here returns its directory listings in seemingly
> +   random order, and even seems to modify the order of the directory =
as
> +   its contents change -- perhaps the underlying directory structure =
is
> +   based upon hashing of some kind.  Note that the "pdir" and "cdir"
> +   entries are interspersed with other entries in the directory.  =
Note
> +   also that this server does not show a "pdir" entry when listing =
the
> +   contents of the root directory of the virtual filestore, it does
> +   however include multiple "cdir" and "pdir" entries when it fees
> +   inclined.  The server also uses obnoxiously "cute" messages.

>   3.4. MDTM Examples
...
> -   If we assume the existence of three files, A B and C,
> -   and a directory D, and no other files at all,
> -   then the MDTM command may behave as indicated.
> +   If we assume the existence of three files, A B and C,
> +   a directory D, two files with names that end with the string
> +   "ile6", and no other files at all,
> +   then the MDTM command may behave as indicated.
...
> -   C was modified 21 days and several hours later.
> +   C was modified 20 days and several hours later.

>  7.5.1.5. System defined types
> -        os-type   =3D "OS." os-name "=3D" os-type
> -        os-type   =3D token
> +        os-type   =3D "OS." os-name "=3D" os-kind
> +        os-kind   =3D token

>     OS specific types are registered by the IANA
> -   using the procedures specified in section 10.  The "os-type" =
provides
> -   the system dependent information as to the type of the file =
listed.
> -   The os-name and os-type strings in an os-type are case =
independent.
> +   using the procedures specified in section 10.  The "os-kind" =
provides
> +   the system dependent information as to the type of the file =
listed.
> +   The os-name and os-kind strings in an os-type are case =
independent.

> 7.8.1. Examples
> -   All of the facts supported by
> -   this server are enabled by default.
> +   All but one of the facts
> +   supported by this server are enabled by default.


The "to me not clearly substantive" diff's include:

> -   directory has a file name relative to the directory that contains =
it,
> +   directory has a name relative to the directory that contains it,

> -   storage structure,
> +   storage structure.
=20
> -   The VCHAR (from [5]), TCHAR, and RCHAR types
> +   The VCHAR (from [5]), RCHAR, SCHAR, and TCHAR types

> -   is returned over the control connection,)
> +   is returned over the control connection)

Also I see we're again swapping "modelled" with "modeled" and "labelled" =
with
"labeled".

As in January, before comparing the texts, ... gleefully I stripped page
numbers, headers, trailers and I compressed runs of blank lines to =
single
blank lines.  And this time I also ended by ignoring all whitespace in =
the
comparison.


x4402 Pat LaVarre   [email protected]
http://members.aol.com/plscsi/




===================END FORWARDED MESSAGE===================

Paul Hethmon
[email protected]
http://www.hethmon.com