[ftpext] ftpbis

Anthony Bryan <anthonybryan@gmail.com> Sun, 15 August 2010 22:17 UTC

Return-Path: <anthonybryan@gmail.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id E193C3A67EE for <ftpext@core3.amsl.com>; Sun, 15 Aug 2010 15:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[AWL=-0.528, BAYES_00=-2.599, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id m-1K5FAfx786 for <ftpext@core3.amsl.com>; Sun, 15 Aug 2010 15:17:20 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com []) by core3.amsl.com (Postfix) with ESMTP id C3BBF3A67A2 for <ftpext@ietf.org>; Sun, 15 Aug 2010 15:17:20 -0700 (PDT)
Received: by iwn3 with SMTP id 3so1110496iwn.31 for <ftpext@ietf.org>; Sun, 15 Aug 2010 15:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=XZmCwFI7fb8yfVeFiWGSQpDJ+uDfurcMvFGVvxIM+FQ=; b=kVFhhmUO722a1Kz9qEKJ2GBiOx5mG0L5NLee1tVpYEA9HcgJ0gcz6q6uvJ/fZXXeK0 DdQbNlt5rt5cK8wLkpPkSnA5TxPj3rGb/lnRJacQyEuNbryhDzYOOzvhZY7MpioDRETt GsT3u0lyPVKpkKMzSlU0Sg59hcEH/xg578qDk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=EE4JprfSUX6sQVaNc6coj9cuDEE37uHNPiu2z8ah7dZq13J9TuJEl6OX3JdjQagIaT YV3KXuEkGPreaA78sJBl9qOxwXMNYb7W25fdl+sqfRwj1zkzEUk194SITT1luPyrKaQM p4crAJeImGjgikHH12FkhlIGSm8CUkx4p/ITQ=
MIME-Version: 1.0
Received: by with SMTP id j6mr4560406iba.141.1281910676684; Sun, 15 Aug 2010 15:17:56 -0700 (PDT)
Received: by with HTTP; Sun, 15 Aug 2010 15:17:56 -0700 (PDT)
Date: Sun, 15 Aug 2010 18:17:56 -0400
Message-ID: <AANLkTikaytRR0YSR5yKu7m-Yi=YesaqoRhCg1CZZTtPO@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: [ftpext] ftpbis
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Aug 2010 22:17:22 -0000

hi everybody, I posted this before in another thread but wanted to
gauge if more than two people are interested.

with inspiration from httpbis, I've been working on a collection of
FTP RFCs: 959, 1123, 2389, 2428, 2577, 3659.

the idea would be to have an updated, coherent, harmonious document of
RFCs concerning FTP along with implementation and real world info like


in my completely unbiased opinion :), this is already an improvement
in that most (?) important FTP information is in one document that is
updated instead of 6-8 RFCs developed over a period of 25 years.
(reading them is like digital archaeology). the drawback is that it is
a long document, and would require more work to finish.

so far, besides collecting the RFCs and errata together, there are no
real changes to the text except where noted.
here's the changelog/TODO:

Changelog from RFC 959.

    Incorporate [RFC0959] Errata.
    Incorporate FTP specific clarifications (Sec 4.1) from [RFC1123]
“Requirements for Internet Hosts - Application and Support” into the
various sections that it updated.
    Incorporate [RFC2389] “Feature negotiation mechanism for the File
Transfer Protocol” at Section 4.1.4.
    Incorporate [RFC2428] "FTP Extensions for IPv6 and NATs" at Section
    Incorporate [RFC2577] "FTP Security Considerations" in Section 10.
    Incorporate [RFC3659] "Extensions to FTP" Section 3 through
Section 9 in Section 4.1.5 and its Section 2 into Section 2.
    Include abstract of [RFC4217] “Securing FTP with TLS” in Section 10.2.
    Update Appendix C to include all known FTP RFCs.
    Use BCP 14/[RFC2119] key words in text from [RFC0959] sections.


    BCP 14/[RFC2119] key words incomplete.
    [RFC3659] references currently incomplete; also, [RFC3659]
internal references to section 10 (which is not included in this
draft) are not updated.
    Triage and include or reference other FTP RFCs: [RFC2228] (more
reply codes and reply type 6yz), [RFC2640], 2773?, [RFC4217].
    File recently found errata to older RFCs. Figure out if [RFC1123]
errata should be filed against itself ("Updates: 959") or to [RFC0959]
("Updated by: 1123").
    Update BNF to ABNF.
    Should we organize commands in a standard format (subsections?)
like EPRT/EPSV (Section, with separated ABNF?
    Should we update IP Address:Port description to ABNF? Or
standardize on one example: h1,h2,h3,h4,p1,p2 or A1,A2,A3,A4,a1,a2?
    Should we move the whole sentence that is Section 8 into Section 3.2?
    Should we deprecate features that are no longer common?
    Should we obsolete outdated RFCs (like 1639) with "Obsoletes:"?
    Should we use old IPR value because we're using old text?
    Are the author listing/credits in compound document done
correctly? Some are deceased or inactive or may be otherwise hard to

any strong feelings one way or the other?
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads