Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
Anthony Bryan <anthonybryan@gmail.com> Mon, 13 September 2010 22:07 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 8D7773A67E3 for <ftpext@core3.amsl.com>; Mon, 13 Sep 2010 15:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level:
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[AWL=0.261, 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 nLn40xdxGve0 for <ftpext@core3.amsl.com>; Mon, 13 Sep 2010 15:06:59 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id A921A3A67BE for <ftpext@ietf.org>; Mon, 13 Sep 2010 15:06:56 -0700 (PDT)
Received: by gxk20 with SMTP id 20so2843819gxk.31 for <ftpext@ietf.org>; Mon, 13 Sep 2010 15:07:22 -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=mA2lxMjc7HJCayBYfXDqMFuixBqhd+n4brwLtYMli70=; b=lThII8LYCLlShbW4KaZC7K9HJQ2Ltf3RrXppX3+sPXgCgYcDjAHkxjjo+jsVyraXKT nOwF+WBuJdR+BaVpxZXnT0P6nr/I20KuVXBdmaH0ple8o23B6rEn2BgzJk1gkt1eaVjN gMkaREEeZksZ3R362bok5fK9AqLYPISFZk8Jg=
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=XZnOU2CNiNayTwLHdAUyGAO5Ts38vmyALY8yXlgvna57Cu3YX6yB7MqFdTspqhZLd5 VxlpFIRjw5p41TKOWBZe3OpCEtIGLPECYePHyEIw1JtwrSp2XP9+DkryAeppr8IIanCA CNsLX6bgFTuMlhXlL86xBWf8RGfXjFj8bLark=
MIME-Version: 1.0
Received: by 10.101.165.35 with SMTP id s35mr5055425ano.258.1284415642515; Mon, 13 Sep 2010 15:07:22 -0700 (PDT)
Received: by 10.231.15.141 with HTTP; Mon, 13 Sep 2010 15:07:22 -0700 (PDT)
In-Reply-To: <AANLkTikL+QYbzr3BJG2XeYjP0Wep6SgKdDZ_Sa4W1XNJ@mail.gmail.com>
References: <4C8743B4.4030101@isode.com> <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com> <AANLkTikL+QYbzr3BJG2XeYjP0Wep6SgKdDZ_Sa4W1XNJ@mail.gmail.com>
Date: Mon, 13 Sep 2010 18:07:22 -0400
Message-ID: <AANLkTimZ2i79onC93eL=6LF--3M4kQp2z65367ttZChD@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: liu dapeng <maxpassion@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ftpext@ietf.org
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: Mon, 13 Sep 2010 22:07:00 -0000
On Sun, Sep 12, 2010 at 11:30 PM, liu dapeng <maxpassion@gmail.com> wrote: > Hi Anthony, > > For the draft: draft-ietf-behave-ftp64, during last IETF meeting, > people are agreed to split the draft to two separate ones, ALG related > wrok goes to Behave WG, FTP protocol related work goes to FTPEXT. > Shall we include this work item to the charter? > > Following text for your refernece: > Deliverables: FTP extensions to support IPv4/IPv6 transiation scenario. hi, thanks for the info. should I remove draft-ietf-behave-ftp64 from the list? does the FTP related draft exist yet, so I can list it? FTP Extensions, 2nd edition (ftpext2) Charter Chair(s): ? IETF Area: Applications Area Applications Area Directors: Alexey Melnikov <alexey.melnikov@isode.com> Peter Saint-Andre <stpeter@stpeter.im> Responsible Area Director: Alexey Melnikov <alexey.melnikov@isode.com> Mailing list: General Discussion: ftpext@ietf.org Archive: http://www.ietf.org/mail-archive/web/ftpext/current/maillist.html 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 draft-ietf-behave-ftp64 draft-peterson-streamlined-ftp-command-extensions draft-preston-ftpext-deflate The Working Group will: * Review and finalize drafts listed above. * Continue work on other drafts that are already in progress. * Review and confirm or reject errata of current FTP RFCs. * Investigate the differences between FTP in theory (current RFCs) and practice, and recommend future work to align them. 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). * A document that specifies FTP extensions to support IPv4/IPv6 translation scenario. The Working Group must not introduce a new version of FTP, e.g. an incompatible FTP 2.0. 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) ??? 2010 Working group Last Call of HOST document ??? 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' to the IESG for consideration as a Proposed Standard ??? 2011 Working group Last Call of HASH document ??? 2011 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' to the IESG for consideration as a Proposed Standard ??? 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