Re: [storm] [nfsv4] [tsv-area] Application protocol for distributed storage

Joe Touch <touch@ISI.EDU> Sat, 16 January 2010 06:14 UTC

Return-Path: <touch@ISI.EDU>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3EAD3A6897; Fri, 15 Jan 2010 22:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 FYnyizGR-QbR; Fri, 15 Jan 2010 22:14:38 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 77AD33A680D; Fri, 15 Jan 2010 22:14:38 -0800 (PST)
Received: from [192.168.1.95] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id o0G6EKp8008042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Jan 2010 22:14:22 -0800 (PST)
Message-ID: <4B51593C.70705@isi.edu>
Date: Fri, 15 Jan 2010 22:14:20 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Wesley Leggette <wleggette@cleversafe.com>
References: <C7766F8B.23E4A%wleggette@cleversafe.com>
In-Reply-To: <C7766F8B.23E4A%wleggette@cleversafe.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Sat, 16 Jan 2010 09:29:25 -0800
Cc: TSV Area <tsv-area@ietf.org>, "nfsv4@ietf.org" <nfsv4@ietf.org>, Nicolas Williams <Nicolas.Williams@sun.com>, "storm@ietf.org" <storm@ietf.org>
Subject: Re: [storm] [nfsv4] [tsv-area] Application protocol for distributed storage
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jan 2010 06:14:39 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Wesley Leggette wrote:
> On 1/15/10 16:12, "Nicolas Williams" <Nicolas.Williams@sun.com> wrote:
> 
>> On Fri, Jan 15, 2010 at 10:51:39AM -0600, Wesley Leggette wrote:
>>>>> When we are ready to submit something (it would be a submission which
>>>>> documents what we have currently implemented) is there a working group that
>>>>> would be appropriate, or should we just submit an I-D directly?
>>>> It's always easiest to submit an individual I-D first, then see where to
>>>> place it, AFAICT.
>>> Then we will do that for now, taking into account your other suggestions.
>> The process roughly goes like this:
>>
>>  - Submit some individual submission Internet-Drafts (e.g.,
>>    draft-leggette-my-distributed-storage-protocol-00).
>>
>>  - Request a BoF meeting at the next IETF meeting.
> 
> I've noticed that IETF 77 will be held in California in March. We'd be
> interested in requesting a meeting for that, but since the proposal request
> deadline is the 25th, it seems unlikely that we can have a I-D submitted by
> then. Can one request a BOF meeting without a prior submission (assuming we
> would finish our submission before March)?

As per my other post, I would encourage you to contact a WG chair in one
of the existing WGs or their parent area meetings to make a brief (5-10
minute) presentation at the next IETF. It would be useful to have the
I-D submitted before the deadline, but that would give you more time (to
the I-D deadline, not the BOF submission deadline).

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAktRWTwACgkQE5f5cImnZruGUwCgtxr4msPFktL70nc5lp61jPJq
QqsAoPKEE0cWDUwjRRVtWZUGPCveeIvg
=DGK1
-----END PGP SIGNATURE-----