Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
Anthony Bryan <anthonybryan@gmail.com> Thu, 09 September 2010 00:38 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 2337B3A689B for <ftpext@core3.amsl.com>; Wed, 8 Sep 2010 17:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level:
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.303, 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 YX8Nkw9+BwZd for <ftpext@core3.amsl.com>; Wed, 8 Sep 2010 17:38:22 -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 A60A83A6912 for <ftpext@ietf.org>; Wed, 8 Sep 2010 17:38:19 -0700 (PDT)
Received: by iwn3 with SMTP id 3so591989iwn.31 for <ftpext@ietf.org>; Wed, 08 Sep 2010 17:38:47 -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=qzSTaf7zCoA4A9oAafK+GEvalnFNqLCAsI1AN4RkJmA=; b=YH+OibaGY4y8Z6QgVmo/tK/jlxKb7YDzw7Gpj+cA28i7MkfkrZylGzW7aNzSzTaTtu ao0nZZiFPjQ9I0zVwRJ8334atBPWHRW51XYMCUlzpoG90fbguA3VkR/cAQJl7yal8kYc AmviyPzNjZBlhpILvTSHxVuJndNYlcqJPdoV8=
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=uKEsNjoKC5EjEGCjNC6/ERM5v7ijsn9dy2EreQzqtOv54abQ+k4Yj8SNCQUodKYVq5 Y+b6J71ZSWd7f3YSF4AHNKa+QN2qbWIkzgY2dgJEMOyxtPYmkIm/w/JijwRrxTN2Mq0Y r2RLVFc+w60skv8XxPGfyeo5mH/tsFjjQvd1g=
MIME-Version: 1.0
Received: by 10.231.174.144 with SMTP id t16mr137434ibz.118.1283992727002; Wed, 08 Sep 2010 17:38:47 -0700 (PDT)
Received: by 10.231.15.141 with HTTP; Wed, 8 Sep 2010 17:38:46 -0700 (PDT)
In-Reply-To: <4C8743B4.4030101@isode.com>
References: <4C8743B4.4030101@isode.com>
Date: Wed, 08 Sep 2010 20:38:46 -0400
Message-ID: <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org, Robert McMurray <robmcm@microsoft.com>
Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
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: Thu, 09 Sep 2010 00:38:38 -0000
On Wed, Sep 8, 2010 at 4:05 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote: > 2). Propose and agree on WG charter on the mailing list. thanks, Alexey. I agree we need more participants, and I will continue to invite relevant people. I've never worked on an IETF charter, but here's what I had, borrowing from other charters and the BOF proposal. because of the maturity of HOST, I would say it deserves an accelerated schedule. FTP Extensions, 2nd edition (ftpext2) Charter Description of Working Group: The Standard File Transfer Protocol specification in RFC 959 has been updated several times with command extensions of one sort or another, including those based on the extension mechanism of RFCs 2389 (a complete list appears in RFC 5797 and the corresponding IANA registry at http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml ). The following are active FTP related drafts: draft-bryan-ftp-hash draft-hethmon-mcmurray-ftp-hosts (completed IETF Last Call in May) draft-ietf-behave-ftp64 draft-preston-ftpext-deflate The Working Group will: * Review and finalize already mature drafts that are close to completion. * Continue work on other drafts that are already in progress. * Identify additional areas of FTP that need extending, such as unofficial FTP commands that need documentation or new commands. * Review and confirm or reject errata of current FTP RFCs. * Discuss the differences between FTP in theory (current RFCs) and practice. The Working Group's specification deliverables are: * A document that specifies the HOST command (Proposed Standard). * A document that specifies the HASH command (Proposed Standard). The Working Group must not introduce a new version of FTP, e.g. an incompatible FTP 2.0. The following issues are specifically omitted from the working group's charter, but may be added by the Area Directors if time permits, once the above goals have been acheived. * A document on "FTP in the 21st Century" that gives implementation advice on FTP in the wild. (Informational or BCP) Goals and Milestones Sep 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be used as a starting point) Sep 2010 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will be used as a starting point) XXX 2010 Working group Last Call of HOST document XXX 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' to the IESG for consideration as a Proposed Standard XXX 2010 Working group Last Call of HASH document XXX 2010 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' to the IESG for consideration as a Proposed Standard XXX 2011 Identify other areas of FTP that need extending, or unofficial commands that need documenting XXX 2011 Close or recharter -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads
- [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht liu dapeng
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht liu dapeng
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Anthony Bryan
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alfred Hönes
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alexey Melnikov
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht John C Klensin
- Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht Alfred Hönes
- [ftpext] RFC 959Re: Followup on FTPEXT2 BOF in Ma… John C Klensin
- Re: [ftpext] RFC 959Re: Followup on FTPEXT2 BOF i… Anthony Bryan