Re: [ftpext] FWD: ftp/959 reboot

Anthony Bryan <anthonybryan@gmail.com> Wed, 11 August 2010 01:31 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 007443A6877 for <ftpext@core3.amsl.com>; Tue, 10 Aug 2010 18:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277, 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 TcOc4hYzcfvY for <ftpext@core3.amsl.com>; Tue, 10 Aug 2010 18:31:12 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 24CD73A6967 for <ftpext@ietf.org>; Tue, 10 Aug 2010 18:31:08 -0700 (PDT)
Received: by yxj4 with SMTP id 4so4802307yxj.31 for <ftpext@ietf.org>; Tue, 10 Aug 2010 18:31:44 -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=hXNqE+EpquIPyKF84x0vk4ZM0UTLWk1Xhzb2LoQG02I=; b=LBbM8KycXdNvrP7SlyLnuyQHNLwhNA2l9dOub+Cp1EAH/mQjLqZm8N5PZhX6hthFAl A5O45i7hutgRrhMdEWkhFpM7QlJYSbKh0HtS8T4nufnFNE5awSiqoRSES1uw8VhxK5em /yjd4KOkmd31qCLiTborEcgvXpbo/bM/WHsgU=
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=PiPqqOE3RwqzkPMSrEViJrHXYwGL5Sa9SID7mDYy+NzR/kQ3oK8N16pNECqdoiLgRS SCxe/GdN4ZfVukXGbMdZpX3gmEEsfmg/2FCEgm/N6Qb/FtGFNCfjfEW0BKQ/+32ZM9dM DLS+AWNXAjOqdf5QTE5DTr67mj2//6G4Hd9a4=
MIME-Version: 1.0
Received: by 10.100.226.20 with SMTP id y20mr7878746ang.88.1281490303945; Tue, 10 Aug 2010 18:31:43 -0700 (PDT)
Received: by 10.100.132.2 with HTTP; Tue, 10 Aug 2010 18:31:43 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1008101303001.1146@iskra.ottix.net>
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> <AANLkTikB0J_aL7CTwnC17wH2+FS=QgQB5SCL2Jp9iJBd@mail.gmail.com> <Pine.LNX.4.64.1008101303001.1146@iskra.ottix.net>
Date: Tue, 10 Aug 2010 21:31:43 -0400
Message-ID: <AANLkTim1VnSPnhmuMa9RC5Ubjnnn=Q+rK6R2riRAznfj@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "William F. Maton" <wmaton@ottix.net>
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: Wed, 11 Aug 2010 01:31:15 -0000

On Tue, Aug 10, 2010 at 1:11 PM, William F. Maton <wmaton@ottix.net> wrote:
> On Mon, 9 Aug 2010, Anthony Bryan wrote:
>
>> 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.
>
> So I've had another read of RFC 1123 4.1 coming from a different light. All
> it seems to do is clarify what implementors of RFC 959 should be supporting.
>  "RFC 959 was SO barebones as to leave interpretation wide open, so he's a
> clarifcation on what to do to make FTP servers and clients right so they
> work."
>
> But I'm speculating because despite my efforts at looking for context
> (mailing lists, emails on the Internet), the RFC itself is all we have to go
> on.

I contacted the author, perhaps we'll hear from him.

reading RFC 3659 more, it refers to "STD 9, RFC 959 and STD 3, RFC
1123" as if they're to be taken together.

> If we look at 4.1.5 then we have an idea of what RFC 1123 is trying to say
> and perhaps compare that to the post Oct 1989 outcome:  Have implementations
> of the succeeding decade adopted any of that.

can some implementors chime in?

> Didn't someone here once say that a working group on FTP would require a lot
> of work? :-)

nahhh! :)

>>  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.
>
> OK, so FTPbis 'updates' RFC 1123, not obsoletes it.
>
>> 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.
>
> I'll have another look.

I merged in the changes from RFC 1123 now:

http://www.metalinker.org/test/ftp/draft-bryan-ftpbis-00.txt
http://www.metalinker.org/test/ftp/draft-bryan-ftpbis-00.html

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