Re: [ftpext] WG Status

Anthony Bryan <anthonybryan@gmail.com> Tue, 13 March 2012 20:33 UTC

Return-Path: <anthonybryan@gmail.com>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4A221F856F for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 13:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id evwQPZ0QElZL for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 13:33:52 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C32EF21F84C9 for <ftpext@ietf.org>; Tue, 13 Mar 2012 13:33:52 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so1155530ggm.31 for <ftpext@ietf.org>; Tue, 13 Mar 2012 13:33:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qVDDVCOMzdxiW8mzlyF2GNQ1zJNzH+VW2AxT0KhNfyw=; b=edYAX/HyfGTuMyAxspjPS/RMqTCxBee3QJL9ZL+rrIVMAl5zFyt+g4Pr3QJ671wG2e 7Spa+JZSWa4QrN6hiPKTLGzi+WF+6bPF3fLPKfFmdjpN40G1cVjuTLOYYUOKPpOxY6PI n0hKj8ofjAOTYxriG0j/MJtJVDl0X/QuqwAKrQSzirr5m60rSfUr4frm5DVmpJzHw1PQ XoLXQQOwm/UDre9Pfu1uPnLPkWash1CWZGoXNwV/L2j6stNpN/0kvm1/qP0g6DHBhNQY hV+G1LAVd3ho+fwpW2bndWKixnDGGTjOsFY0G+HRMUN6Hk0s19F+Vn3i5P4iuDS0YkSR K5ZQ==
MIME-Version: 1.0
Received: by 10.236.153.104 with SMTP id e68mr18277311yhk.74.1331670832434; Tue, 13 Mar 2012 13:33:52 -0700 (PDT)
Received: by 10.146.95.15 with HTTP; Tue, 13 Mar 2012 13:33:52 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1203130853340.3570@familiar.castaglia.org>
References: <8CC6BE90-16F4-41DB-835B-B8BC9722156A@frobbit.se> <4F5E0B4F.2080401@att.com> <8050883FA9D9EB809D8E848C@PST.JCK.COM> <4F5ED938.7090406@att.com> <alpine.DEB.2.00.1203130853340.3570@familiar.castaglia.org>
Date: Tue, 13 Mar 2012 16:33:52 -0400
Message-ID: <CANqTPeh=B9GG5AH_u232Qn7W5WGhnpmMQbmDoBZDXdYLE9u9rA@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: TJ Saunders <tj@castaglia.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] WG Status
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Mar 2012 20:33:53 -0000

On Tue, Mar 13, 2012 at 12:16 PM, TJ Saunders <tj@castaglia.org> wrote:
>
>>     *) the HOST document
>
> Given the paucity of IPv4 addresses (and their widespread use), I still
> consider name-based virtual hosting support in FTP, via the proposed HOST
> command, to be of considerable value.
>
> I will be implementing this command in proftpd for the next RC release; as
> such, I have been reading closely many of the comments on this topic.

thanks for letting us know.

here are the other implementations as of a year ago:

IIS FTP service
Serv-U server
WS_FTP service
SmartpFTP client
Beyond Compare client
FTP Voyager client.

> My impression is that the HOST command proposal will end up being
> implemented whether or not the WG continues to exist.  Without the WG
> pushing the proposal through to Standard status, however, those
> implementations are more likely to differ.  To ameliorate that
> possibility, I for one would like to see the WG continue.

as it already is implemented, I believe implementations would grow.

& I assume the draft would be submitted as an individual submission
which I think is more work than a WG submission?

I see HOST documented in an RFC better than it not.

> There have been, and will continue to be, questions about how to handle
> HOST edge cases (REIN, close the connection, etc), and how it will
> interact with e.g. TLS SNI.  These are excellent questions, and should be
> addressed -- but please do not let the lack of resolution on these
> questions cause the HOST draft to be stopped altogether.  "Don't let the
> perfect be the enemy of the good", as it were.

I agree, these issues must be addressed.

I think we ran into 2 problems here...

1) HOST passed IETF wide Last Call almost 2 years ago. so people are
not as interested in reviewing something that has been in limbo & held
up by being included in this WG.

2) non core FTP issues like internationalization & security where we
need outside help (& have gotten some).

> Just my thoughts on this particular topic.

thank you very much, they have been helpful!

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