Re: [nfsv4] Last call for NSDB Protocol for Federated Filesystems (Oct 4 - Oct 22nd)

James Lentini <jlentini@netapp.com> Thu, 04 November 2010 18:49 UTC

Return-Path: <jlentini@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C2083A6935 for <nfsv4@core3.amsl.com>; Thu, 4 Nov 2010 11:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pZcf7LYNapf4 for <nfsv4@core3.amsl.com>; Thu, 4 Nov 2010 11:49:42 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id F01A63A69EF for <nfsv4@ietf.org>; Thu, 4 Nov 2010 11:49:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,297,1286175600"; d="scan'208";a="477608839"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 04 Nov 2010 11:49:52 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id oA4InpBp007046; Thu, 4 Nov 2010 11:49:51 -0700 (PDT)
Date: Thu, 04 Nov 2010 14:49:50 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <A8AE7495-87AF-447B-AB3B-BB18CB9B643C@oracle.com>
Message-ID: <alpine.LFD.2.00.1011041426180.14303@jlentini-linux.nane.netapp.com>
References: <E043D9D8EE3B5743B8B174A814FD584F0A6BFD9C@TK5EX14MBXC126.redmond.corp.microsoft.com> <alpine.LFD.2.00.1010221251120.4707@jlentini-linux.nane.netapp.com> <A8AE7495-87AF-447B-AB3B-BB18CB9B643C@oracle.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] Last call for NSDB Protocol for Federated Filesystems (Oct 4 - Oct 22nd)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 04 Nov 2010 18:49:48 -0000

On Thu, 4 Nov 2010, Chuck Lever wrote:

> 
> On Oct 22, 2010, at 1:31 PM, James Lentini wrote:
> 
<snip>
> > 
> > Revised text for Section 4.2.1.12 
> > (if fedfsAnnotation is retained):
> > ------------------------------------------
> > 
> > 4.2.1.12. fedfsAnnotation
> > 
> > 
> >   A fedfsAnnotation contains an object annotation formatted as a 
> >   key/value pair.
> > 
> >   This attribute is multi-valued; an object type that permits
> >   annotations may have any number of annotations per instance.
> > 
> >   A fedfsAnnotation attribute is a human-readable UTF-8 string.
> >   The value MUST NOT contain a non-terminal NUL character and
> 
> Rob pointed out to me that UTF-8 strings by definition may not have 
> a non-terminal NUL character, so the above MUST NOT text is not 
> necessary.

Since arriving at this conclusion required some discussion, I think 
noting this point would be benefit future readers. The "MUST NOT" 
could be removed like this:

   A fedfsAnnotation attribute is a human-readable UTF-8 string.
   By definition, the value will not contain a non-terminal NUL character.
   The value MUST be formatted according to the following ABNF [RFC 5234]
   rules:

Is that better?