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

"jarrett.lu@oracle.com" <jarrett.lu@oracle.com> Thu, 12 May 2011 16:49 UTC

Return-Path: <jarrett.lu@oracle.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 E4916E068E for <nfsv4@ietfa.amsl.com>; Thu, 12 May 2011 09:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 MIMnWONKUXqO for <nfsv4@ietfa.amsl.com>; Thu, 12 May 2011 09:49:50 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by ietfa.amsl.com (Postfix) with ESMTP id 5A480E0682 for <nfsv4@ietf.org>; Thu, 12 May 2011 09:49:50 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p4CGnkwn010910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <nfsv4@ietf.org>; Thu, 12 May 2011 16:49:49 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p4CGnkqR006860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <nfsv4@ietf.org>; Thu, 12 May 2011 16:49:46 GMT
Received: from abhmt015.oracle.com (abhmt015.oracle.com [141.146.116.24]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p4CGneLK017176 for <nfsv4@ietf.org>; Thu, 12 May 2011 11:49:40 -0500
Received: from [10.132.149.111] (/10.132.149.111) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 12 May 2011 09:49:40 -0700
Message-ID: <4DCC0F9C.3040703@oracle.com>
Date: Thu, 12 May 2011 09:49:32 -0700
From: "jarrett.lu@oracle.com" <jarrett.lu@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.13) Gecko/20110228 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: nfsv4@ietf.org
References: <7B23B6EC-F9BC-4222-AC3E-36B843695060@netapp.com> <BANLkTi=E+aNY9dE=m-=y0Rsdm08OxBRmuw@mail.gmail.com> <E8BDDFBC-D7D6-4E73-9B77-9BA078171337@netapp.com>
In-Reply-To: <E8BDDFBC-D7D6-4E73-9B77-9BA078171337@netapp.com>
Content-Type: multipart/alternative; boundary="------------080607080608040601000400"
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090208.4DCC0FAD.0136:SCFMA922111,ss=1,fgs=0
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
Reply-To: jarrett.lu@oracle.com
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 16:49:51 -0000

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 
>> <mailto: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?

- Jarrett