Re: [nfsv4] [LNFS] Meeting Agenda for 05/12/2011 (new conference number)

Thomas Haynes <thomas@netapp.com> Thu, 12 May 2011 17:03 UTC

Return-Path: <Tom.Haynes@netapp.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCB0E070A for <nfsv4@ietfa.amsl.com>; Thu, 12 May 2011 10:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0FUtQgBkuqx for <nfsv4@ietfa.amsl.com>; Thu, 12 May 2011 10:03:15 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id E57EAE06DD for <nfsv4@ietf.org>; Thu, 12 May 2011 10:03:14 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.64,359,1301900400"; d="scan'208,217"; a="547493903"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 12 May 2011 10:03:03 -0700
Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p4CH33se027637; Thu, 12 May 2011 10:03:03 -0700 (PDT)
Received: from rtprsexc1-prd.hq.netapp.com ([10.100.161.114]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 May 2011 10:03:02 -0700
Received: from RTPMVEXC1-PRD.hq.netapp.com ([10.100.161.112]) by rtprsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 May 2011 13:03:01 -0400
Received: from sanshah-lxp.hq.netapp.com ([10.58.60.98]) by RTPMVEXC1-PRD.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 May 2011 13:03:01 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-2-495064962"
From: Thomas Haynes <thomas@netapp.com>
In-Reply-To: <4DCC0F9C.3040703@oracle.com>
Date: Thu, 12 May 2011 12:02:59 -0500
Message-Id: <2442B7F4-4765-4B56-925C-FDAE4421DDC2@netapp.com>
References: <7B23B6EC-F9BC-4222-AC3E-36B843695060@netapp.com> <BANLkTi=E+aNY9dE=m-=y0Rsdm08OxBRmuw@mail.gmail.com> <E8BDDFBC-D7D6-4E73-9B77-9BA078171337@netapp.com> <4DCC0F9C.3040703@oracle.com>
To: jarrett.lu@oracle.com
X-Mailer: Apple Mail (2.1084)
X-OriginalArrivalTime: 12 May 2011 17:03:01.0289 (UTC) FILETIME=[736B6990:01CC10C6]
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [LNFS] Meeting Agenda for 05/12/2011 (new conference number)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 12 May 2011 17:03:15 -0000

On May 12, 2011, at 11:49 AM, jarrett.lu@oracle.com wrote:

> On 05/11/11 08:38 AM, Thomas Haynes wrote:
>> 
>> 
>> On May 10, 2011, at 10:48 PM, Nico Williams wrote:
>> 
>>> On Tue, May 10, 2011 at 6:52 PM, Thomas Haynes <thomas@netapp.com> wrote:
>>>> 
>>> 
>>>> + LFS Registry
>>>> Sorin has proposed that we pull this into the I-D, which will finally
>>>> consolidate all LFS documentation into one. I've done this.
>>> 
>>> There's probably interactions here with other parts of the IETF.
>>> Surely NFSv4 will not be the last protocol to have labels on the wire
>>> (it certainly isn't the first).  The registry mught need to be
>>> generic.
>>> 
>> 
>> 
>> Good point, I agree.
>> 
>> 
>> 
> 
> Labeled IPsec has similar needs. 
> 
> The draft, http://tools.ietf.org/html/draft-quigley-label-format-registry-01 ,
> is intended to serve the needs. David Q. agreed to write a SELinux label
> format spec. Are there other things we should add to the draft?
> 


Where are we going to document PIs?





> - Jarrett
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4