Re: [nfsv4] draft haynes-nfsv4-versioning: Issues relating to opcode assignments etc.

Nico Williams <nico@cryptonector.com> Tue, 28 October 2014 16:01 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0941A902E for <nfsv4@ietfa.amsl.com>; Tue, 28 Oct 2014 09:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cq8JljKI1jIq for <nfsv4@ietfa.amsl.com>; Tue, 28 Oct 2014 09:01:45 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 22EDB1A8F36 for <nfsv4@ietf.org>; Tue, 28 Oct 2014 09:01:18 -0700 (PDT)
Received: from homiemail-a103.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTP id 00AF320047B83; Tue, 28 Oct 2014 09:01:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=EYPl8a0x7s7tY4 V7qrGtcVjbeVY=; b=qU2q14iGUWwNud6kCzbXka/ldgkGUTgJDCD5SRcNXw/tXp YwVpJbVnWVwYnZeRxxBuecjqNXVdOmfSCy4oGW5hRDjGFtroy68H3+ctoF6GZiFt xWUZN7/3oy9kXqpB98Vqwgq43IFBtPzNmePzvUOIcMoqsKOBHqrfuaUnybMPw=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a103.g.dreamhost.com (Postfix) with ESMTPA id 7DD5B20047B80; Tue, 28 Oct 2014 09:01:17 -0700 (PDT)
Date: Tue, 28 Oct 2014 11:01:17 -0500
From: Nico Williams <nico@cryptonector.com>
To: David Noveck <davenoveck@gmail.com>
Message-ID: <20141028160114.GC17213@localhost>
References: <CADaq8jcGEHYG8Y9+Lj6GBPhePC6vknPXaW9Yh+tbTJ4+bVxvJg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADaq8jcGEHYG8Y9+Lj6GBPhePC6vknPXaW9Yh+tbTJ4+bVxvJg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/nfsv4/bM2RZUtxC9lTS1-d0O98prbYS84
Cc: Christoph Hellwig <hch@lst.de>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] draft haynes-nfsv4-versioning: Issues relating to opcode assignments etc.
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2014 16:01:46 -0000

On Tue, Oct 28, 2014 at 11:23:30AM -0400, David Noveck wrote:
> I think we need to distinguish a couple of related issues:
> 
>    - How (or by whom) the assignment is made.
>    - When the assignment is made
> 
> I think the issue about which there is likely to be disagreement or
> controversy will be the question of when (i.e. how early) the assignment is
> to be made. My understanding of the connection between these two issues is
> as follows:
> 
>    - If the assignment is to be made when the RFC is published, then we
>    could implement IANA-based assignment by creating one or more registries
>    with a "specification required" assignment policy.  However, this could be
>    complicated to do, although it is relatively simple if you just do it for
>    operations.  The big issue is that doing this doesn't buy you anything (see
>    below for a discussion of this).
>    - If the assignment is to made earlier than that (e.g. when the document
>    becomes a working-group document as suggested in the current draft), it
>    isn't clear how to specify an assignment policy that IANA would accept.

There are a number of allocation policies that you can use.  Having a
Protocol Action from the IESG is not the only way.  You can have a
first-come-first-served-with-Expert-review process, which is what I
would recommend for any namespaces large enough that you're not going to
worry about running out.

Nico
--