Re: [ftpext] FWD: ftp/959 reboot

Anthony Bryan <anthonybryan@gmail.com> Tue, 10 August 2010 03:53 UTC

Return-Path: <anthonybryan@gmail.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE0193A69FA for <ftpext@core3.amsl.com>; Mon, 9 Aug 2010 20:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.285
X-Spam-Level:
X-Spam-Status: No, score=-2.285 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZtAIysxbvnC for <ftpext@core3.amsl.com>; Mon, 9 Aug 2010 20:53:53 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9D3613A69D9 for <ftpext@ietf.org>; Mon, 9 Aug 2010 20:53:53 -0700 (PDT)
Received: by iwn36 with SMTP id 36so4372485iwn.31 for <ftpext@ietf.org>; Mon, 09 Aug 2010 20:54:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Jel9h/gBB906lu9RDH0i6F8Yng/lV2Ap0dGSSaFbhYs=; b=LhJ/ivogRkTtpBaJX3pme+cxannBhTXDwlLYeg88BV9oXNOYZdfnFvvTOa6pzXlQdy Mfi5R6S/P3ssO6XGmyHm2K8bsk2q+3q7F3gTGvIXr3R6K7zhqilriMuuXp5qQUYrauU5 GZG1OXqnLHkdl0a1ypwBH6YZgHq+Pim5ypTyc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tg5wGaVMqMubf1E3rV1I669qDov59qu6fpxw+01HJOP8D5fjIkyxQ090Hf2AfULqJi 1IYXn4kfI78odcpLOD/we3FV1wap6yN0txJxxVbrzVgF9Gr6i9wAAykJpbwKMnp37eQm oRFmVIzxUJhTY3vbI8iBVM5ZKVXCc4+awSm2c=
MIME-Version: 1.0
Received: by 10.231.30.134 with SMTP id u6mr19674362ibc.121.1281412468259; Mon, 09 Aug 2010 20:54:28 -0700 (PDT)
Received: by 10.231.159.143 with HTTP; Mon, 9 Aug 2010 20:54:28 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1008092256460.10815@tvnag.unkk.fr>
References: <Pine.LNX.4.64.1008051641520.24282@iskra.ottix.net> <alpine.DEB.2.00.1008052249300.11871@tvnag.unkk.fr> <AANLkTi=1ePodG=2G9Ta-=5Fut6x-bQxvq8eLXsVgaUjh@mail.gmail.com> <alpine.DEB.2.00.1008092256460.10815@tvnag.unkk.fr>
Date: Mon, 09 Aug 2010 23:54:28 -0400
Message-ID: <AANLkTikB0J_aL7CTwnC17wH2+FS=QgQB5SCL2Jp9iJBd@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] FWD: ftp/959 reboot
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: Tue, 10 Aug 2010 03:53:55 -0000

On Mon, Aug 9, 2010 at 5:11 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Mon, 9 Aug 2010, Anthony Bryan wrote:
>
>> Daniel, any thoughts/insight into the RFC 1123 discussion, which appears
>> to update RFC 959?
>
> Yes, it seems to update or at least clarify a lot of RFC959 details but I
> must admit I've never really used 1123 much as a reference. I really can't
> tell at this point how valuable those sections are or aren't.

it would be nice to know how authoritative they are. it sounds like at
least some people are not familiar w/ 1123. I only came across it
after digging deep into stuff.

now reading RFC 3659 more in depth, it at least treats it as more up
to date than 959 in Section 5:

   Note that there
   are some flaws in the description of the restart mechanism in STD 9,
   RFC 959 [3].  See section 4.1.3.4 of RFC 1123 [9] for the
   corrections.

>> with inspiration from httpbis, I've been working on a collection of
>> FTP RFCs: 959, 2389, 2428, 2577 (for now).
>
> I would suggest 3659 to be one of the main RFCs for any modern FTP
> implementation, thanks mostly to SIZE and MTDM in my own case.

3659's absence is only due to my laziness. :) getting these old RFCs
into xml2rfc shape (even with rfc2xml) takes me quite a long time. the
sheer length of 3659 & the fact that no one might be interested kept
me from including it. it adds about 50 pages and is now included.

>> http://www.metalinker.org/test/ftp/draft-bryan-ftpbis-00.txt
>
> Very cool.

thanks!

> I noticed how it mentions RFC3659 describes REST as an extension, but that's
> slightly inaccurate. RFC959 includes REST already, it was just clarified and
> more detailed in RFC3659.

thanks. I removed the original description from the 959 text so it is
not duplicated. if I kept working on this, I would introduce some
uniformity to the commands section.

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads