Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht

Anthony Bryan <anthonybryan@gmail.com> Sat, 11 September 2010 22:21 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 E429D3A67E6 for <ftpext@core3.amsl.com>; Sat, 11 Sep 2010 15:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level:
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.271, 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 0VFzjr20aQ4U for <ftpext@core3.amsl.com>; Sat, 11 Sep 2010 15:21:08 -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 846013A677E for <ftpext@ietf.org>; Sat, 11 Sep 2010 15:21:08 -0700 (PDT)
Received: by iwn3 with SMTP id 3so4270863iwn.31 for <ftpext@ietf.org>; Sat, 11 Sep 2010 15:21:35 -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=UdpZHBwHEIPesaGKJKl3EYP644lQ9wUXc2M5O0mg2h0=; b=VvkSJDUIl+LgTy4ZWE9GkLt6pYsMwpvmlrjgxTuEOm4aEtPWGCoCoG8qmihLtl/LZW IOFeN0zIoaBpbhsuivh7U8nV2AhK/qN2hwqZNCEBTAXD5fP5C/lM3ZbwqofuTMCfrdxY rJ5KcI77G4U/b6uFtXmY1ibBIgVOeMm88abEI=
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=oiwVufAtVLyz30a8fvtgEUkMOME429AsjSO1I64wwAZvNS+xZ7p4cnMTt1T1Vzmskz wBn93RIunPhHjmwu51/IRU0160EYPWd1TpwwjZQGBTsu20dvb4StXveX1i2oAQROJOWE ssDxSDJbIu3a6cSTh3SqOwzG7qkkh2sNGakGY=
MIME-Version: 1.0
Received: by 10.231.185.142 with SMTP id co14mr3386290ibb.97.1284243690071; Sat, 11 Sep 2010 15:21:30 -0700 (PDT)
Received: by 10.231.15.141 with HTTP; Sat, 11 Sep 2010 15:21:29 -0700 (PDT)
In-Reply-To: <4C89F984.9050200@isode.com>
References: <4C8743B4.4030101@isode.com> <AANLkTin+h0G5d4Jw5yHdzKxFpMQyPRO0qzHb9Uuiy4A8@mail.gmail.com> <4C88A542.50400@isode.com> <AANLkTiksCU4a-3XGNedggTFbUVqp9i-0TtP31peVqRA3@mail.gmail.com> <4C89F984.9050200@isode.com>
Date: Sat, 11 Sep 2010 18:21:29 -0400
Message-ID: <AANLkTimyMqg3pFW8VOm9_f68beF497gUriB3utXRy-NZ@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: Sat, 11 Sep 2010 22:21:10 -0000

On Fri, Sep 10, 2010 at 5:25 AM, Alexey Melnikov
<alexey.melnikov@isode.com> wrote:
>>>> I've never worked on an IETF charter, but here's what I had, borrowing
>>>> from other charters and the BOF proposal.
>>>>
>>>>
>>>
>>> Thanks for proposing an initial version. Some quick feedback with my Area
>>> Director hat on.
>>>
>>
>> thanks! is there more info on charters/WGs/rechartering somewhere?
>>
> If you want to know about the process, there is BCP 25
> (http://www.rfc-editor.org/bcp/bcp25.txt). It might have some advice about
> charters, I don't remember of the top of my head.

thanks.

>> The following are active FTP related drafts:
>>
>>   draft-bryan-ftp-hash
>>   draft-hethmon-mcmurray-ftp-hosts (completed IETF Last Call in May)
>>
>
> I would omit the text in (), as this is not really relevant. This
> information gets dated very quickly and it can be sent to IESG directly.

ok.

>>   draft-ietf-behave-ftp64 (behave WG)
>>   draft-peterson-streamlined-ftp-command-extensions
>>   draft-preston-ftpext-deflate
>>
>> The Working Group will:
>> * Review and finalize already mature drafts that are close to
>>  completion.
>>
>
> This is probably Ok, but I would rather rephrase this as something like
> "Review and finalize drafts listed above".

ok.

> There is a question of whether draft-ietf-behave-ftp64 should be done here
> or in BEHAVE. I think the current plan is to review it in FTPEXT, but
> otherwise handle it in BEHAVE.

that was the feeling I got.

here is the attempter charter w/ changes. I'd like people to speak up
if they disagree with the drafts listed, deliverables/goals. I haven't
really put any dates, so I'd like to hear what kind of timeline people
are thinking would be good.


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

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