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

Nicolas Williams <Nicolas.Williams@sun.com> Fri, 15 January 2010 22:27 UTC

Return-Path: <Nicolas.Williams@sun.com>
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 A5B593A69A7; Fri, 15 Jan 2010 14:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.021
X-Spam-Level:
X-Spam-Status: No, score=-6.021 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 xx6ERE+UJQwC; Fri, 15 Jan 2010 14:27:21 -0800 (PST)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by core3.amsl.com (Postfix) with ESMTP id AADC03A69A4; Fri, 15 Jan 2010 14:27:21 -0800 (PST)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id o0FMRIqg022897; Fri, 15 Jan 2010 22:27:18 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id o0FMRHSD014220; Fri, 15 Jan 2010 15:27:18 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id o0FMCGGB009054; Fri, 15 Jan 2010 16:12:16 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id o0FMCFq5009053; Fri, 15 Jan 2010 16:12:15 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Fri, 15 Jan 2010 16:12:15 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Wesley Leggette <wleggette@cleversafe.com>
Message-ID: <20100115221215.GJ1061@Sun.COM>
References: <4B509B99.8090502@isi.edu> <C775F93B.23E2A%wleggette@cleversafe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C775F93B.23E2A%wleggette@cleversafe.com>
User-Agent: Mutt/1.5.7i
X-Mailman-Approved-At: Sat, 16 Jan 2010 09:29:25 -0800
Cc: "storm@ietf.org" <storm@ietf.org>, TSV Area <tsv-area@ietf.org>, "nfsv4@ietf.org" <nfsv4@ietf.org>, Joe Touch <touch@ISI.EDU>
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: Fri, 15 Jan 2010 22:27:22 -0000

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.

   The goal of the BoF should be to determine IETF interest in your
   proposals.  Possible outcomes of a BoF include:

    - a second BoF is needed;

    - there's no interest in chartering a WG or re-chartering an
      existing one; you will be able to try again once more, and you
      will still be able to proceed with the individual submission
      track;

      (There's the possibility in this case that the IESG will
      ultimately oppose standards-track publication, in which case
      you'll end up with informational or experimental RFCs, or perhaps
      you'd abandon the effort.)

    - a WG will be chartered to host the work;
    
    - an existing WG will be re-chartered to host the work.

It will help to have an introductory I-D.  Do disclose mind IPR
dislosure rules.  Do familiarize yourself with the IETF standards
process.

Nico
--