Re: [ftpext] WG Status

TJ Saunders <tj@castaglia.org> Tue, 13 March 2012 16:16 UTC

Return-Path: <tj@castaglia.org>
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 D04C321E8038 for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 09:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 uUWtK78oU9h2 for <ftpext@ietfa.amsl.com>; Tue, 13 Mar 2012 09:16:57 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id ACDF021E8039 for <ftpext@ietf.org>; Tue, 13 Mar 2012 09:16:56 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 93850205EB for <ftpext@ietf.org>; Tue, 13 Mar 2012 12:16:55 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 13 Mar 2012 12:16:55 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=castaglia.org; h= date:from:to:cc:subject:in-reply-to:message-id:references :mime-version:content-type; s=mesmtp; bh=0y+Pu4SbysG23urAFL6KkX9 ydH0=; b=gb0XmARvmnkRfcm5Lv0MJRlDyan1hvMAuBWvXydIiImuOJxjwEQvRtt NxwsliEbkR6RGPKpnpR3LRlMvRUVwV4IAVQERizwX0a8STTNieLtwHRN5kk0BWi7 qf2FMVSmyEJkxqQRVOCi26xgeDtQOgR83SiJhtCoUy0nQEVdONz0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:in-reply-to :message-id:references:mime-version:content-type; s=smtpout; bh= 0y+Pu4SbysG23urAFL6KkX9ydH0=; b=rctq48scVjX1hffLxL8U1YgjFTQvgf4+ pr8TBYqOtz6TJe7KyA4H6e0w7E423c8+TkVaUK2YMLP9sJiP6S+Rgnxn2N86UfM/ 3fHdhvkvzaB4LxGG9rnrepCgSr+TGXg/muxlVVcYYL9bS2xOlpYn61IMmb84kUpn Qnbt1IPZzF8=
X-Sasl-enc: HY/NWctAvHF0Q7ygzesCcEF+OgnyDko5zeiAIii6vPU/ 1331655415
Received: from familiar.local (64-71-23-251.static.wiline.com [64.71.23.251]) by mail.messagingengine.com (Postfix) with ESMTPSA id 0E0AB8E0109; Tue, 13 Mar 2012 12:16:54 -0400 (EDT)
Date: Tue, 13 Mar 2012 09:16:53 -0700 (PDT)
From: TJ Saunders <tj@castaglia.org>
To: Tony Hansen <tony@att.com>
In-Reply-To: <4F5ED938.7090406@att.com>
Message-ID: <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>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 16:16:57 -0000

>     *) 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.

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.

I am not much for document formatting and scheduling and such, but if the 
perceived lack of progress on the HOST draft is due to lack of 
implementations, then I can do my part to address that need for an 
implementation.  I suspect others have already implemented HOST, however.

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.

Just my thoughts on this particular topic.

Cheers,
TJ
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Drink to me only with thine eyes,
   And I will pledge with mine;
   Or leave a kiss but in the cup
   And I'll not look for wine.

   	-Ben Jonson

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~