Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht

Anthony Bryan <anthonybryan@gmail.com> Mon, 27 September 2010 06:40 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 490A53A6C7B for <ftpext@core3.amsl.com>; Sun, 26 Sep 2010 23:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level:
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[AWL=0.284, 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 nXohd6kRP6vl for <ftpext@core3.amsl.com>; Sun, 26 Sep 2010 23:39:59 -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 02B2F3A6C7A for <ftpext@ietf.org>; Sun, 26 Sep 2010 23:39:58 -0700 (PDT)
Received: by iwn3 with SMTP id 3so5260781iwn.31 for <ftpext@ietf.org>; Sun, 26 Sep 2010 23:40:37 -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=S3Y+6TybyLDPxHG2IjmH/6yR5p9rf1kfSiftOgIBiBI=; b=V1KwtGTofp8FJt+I3qi3ZrbYpSWaXUMFUrmx1XadqDDfL+DbUy45En+yUORP4GJmcx PCs9Imbi5vlSjVLklS6+hg54YPhzsezem8Xcq1c09a5EBJ4GS+xZ/DQt8h2huMFM0n90 YMJHm0VWej1MKMaN/qdH3/QgLBj2iPSROd7Zw=
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=UquRAA2x9W6T+j+I/0gVkziTLvk4QyhW0MMs2RPIDDyQm9yKhSvUuNef5hdND0W2i4 Ne1jwfWj2AxZ1faF8jkzmyt+m0vEHvyY/aYmL8XmQL/U8Bxmp0LfM+EFSwb/CVsAkjWe ODtDWrlYQvuL7byWNNRncAOYrv+e8VffhwF0M=
MIME-Version: 1.0
Received: by 10.231.35.138 with SMTP id p10mr8702270ibd.33.1285569636605; Sun, 26 Sep 2010 23:40:36 -0700 (PDT)
Received: by 10.231.12.72 with HTTP; Sun, 26 Sep 2010 23:40:36 -0700 (PDT)
In-Reply-To: <4C8F5A42.5000601@isode.com>
References: <4C8743B4.4030101@isode.com> <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com> <AANLkTikL+QYbzr3BJG2XeYjP0Wep6SgKdDZ_Sa4W1XNJ@mail.gmail.com> <AANLkTimZ2i79onC93eL=6LF--3M4kQp2z65367ttZChD@mail.gmail.com> <4C8F5A42.5000601@isode.com>
Date: Mon, 27 Sep 2010 02:40:36 -0400
Message-ID: <AANLkTi=nhkNYaG5SCYsJYJEZHZwQQjXTyzNxAV+_hZvG@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
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, 27 Sep 2010 06:40:01 -0000

On Tue, Sep 14, 2010 at 7:19 AM, Alexey Melnikov
<alexey.melnikov@isode.com> wrote:
> Anthony Bryan wrote:
>
>> 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?
>>
> I think listing a draft from another WG is confusing, so I would say yes.
>
> But note that it is Ok to have a Charter listing deliverables for which
> there is no draft.

thanks, good to know.

should I also add something like "Review other drafts which may touch
on FTP in some way" (like draft-ietf-tcpm-urgent-data-06), or is that
pretty much implied?

does anyone else have any comments? deliverables/goals?


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 RFC 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-peterson-streamlined-ftp-command-extensions
    draft-preston-ftpext-deflate
    FTP extensions to support IPv4/IPv6 translation scenario

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
Oct 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)
Oct 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