Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht
liu dapeng <maxpassion@gmail.com> Mon, 13 September 2010 03:30 UTC
Return-Path: <maxpassion@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 4D6D13A68D4 for <ftpext@core3.amsl.com>; Sun, 12 Sep 2010 20:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 Ti2LgszStxGy for <ftpext@core3.amsl.com>; Sun, 12 Sep 2010 20:30:31 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 735253A68CF for <ftpext@ietf.org>; Sun, 12 Sep 2010 20:30:30 -0700 (PDT)
Received: by qyk9 with SMTP id 9so4988633qyk.10 for <ftpext@ietf.org>; Sun, 12 Sep 2010 20:30:56 -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; bh=sJWkM6bjGjZamkZVkGVKApGi8l6VpwyQ8Ou6tcHoJxo=; b=rglczHl9b1FrF13J4GY7K+R4ctcKINs1gsfvRRtKmJKoxbM6k6dose2PHYSjez1xOc TWGRBlzjE9eBlG+OMZ8/1Goy5J9H+CFKd3O0IN0u1HY5TQ8KetGInyPXwUzRKHRtwJmO NXEIZW556sWESZ8T9O9cs7k3IkS/uNiHRvXQw=
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; b=bV2dZmv9LoOXElqWQfpoAYdWCwjartoS3e3R6UskNZw+wa+097tkOIs1NE3NE+7sQg Q00XiMwvMTK6tuLVwmSZV0dP/bE5hlixrOUnhJJ+4jHSQK/M+qzeJgUVZRBTUOWnJjIe ieYygEYOfZAoP5HSFvWfDfjV2AHd2jjgNxVpU=
MIME-Version: 1.0
Received: by 10.224.1.42 with SMTP id 42mr2427984qad.91.1284348654865; Sun, 12 Sep 2010 20:30:54 -0700 (PDT)
Received: by 10.229.192.199 with HTTP; Sun, 12 Sep 2010 20:30:54 -0700 (PDT)
In-Reply-To: <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com>
References: <4C8743B4.4030101@isode.com> <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com>
Date: Mon, 13 Sep 2010 11:30:54 +0800
Message-ID: <AANLkTikL+QYbzr3BJG2XeYjP0Wep6SgKdDZ_Sa4W1XNJ@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Anthony Bryan <anthonybryan@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, 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: Mon, 13 Sep 2010 03:30:37 -0000
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. Regards, Dapeng Liu 2010/9/9, Anthony Bryan <anthonybryan@gmail.com>: > 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 mailing list > ftpext@ietf.org > https://www.ietf.org/mailman/listinfo/ftpext >
- [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