IETF Logo Mail Archive

Re: [nfsv4] RPCSEC-GSSv3 profiling

Dave Quigley <dpquigl@davequigley.com> Fri, 08 April 2011 04:02 UTC

Return-Path: <dpquigl@davequigley.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 5CD413A6A39 for <nfsv4@core3.amsl.com>; Thu, 7 Apr 2011 21:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599]
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 uaHzWRoqaVeR for <nfsv4@core3.amsl.com>; Thu, 7 Apr 2011 21:02:25 -0700 (PDT)
Received: from countercultured.net (countercultured.net [IPv6:2001:470:0:c0d3::2]) by core3.amsl.com (Postfix) with SMTP id 022CA3A6A36 for <nfsv4@ietf.org>; Thu, 7 Apr 2011 21:02:24 -0700 (PDT)
Received: (qmail 30375 invoked from network); 8 Apr 2011 04:04:10 -0000
Received: from c-76-21-220-25.hsd1.md.comcast.net (HELO ?192.168.15.109?) (merlin@76.21.220.25) by countercultured.net with ESMTPA; 8 Apr 2011 04:04:10 -0000
Message-ID: <4D9E8926.6090906@davequigley.com>
Date: Fri, 08 Apr 2011 00:03:50 -0400
From: Dave Quigley <dpquigl@davequigley.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: nfsv4@ietf.org
References: <4D95842E.70708@oracle.com> <4D95B41C.70509@oracle.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03E5EF1DC2@MX14A.corp.emc.com> <BANLkTi=9tu4Kt0Kc6QHn1H67oWEBtNwkrw@mail.gmail.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03E5EF260A@MX14A.corp.emc.com> <BANLkTi=TgjHgj9Ux3+iwjY2=rVuZKTUAVA@mail.gmail.com> <BANLkTimURCkWkCBsyZtyf+h0gwB1V2K4JQ@mail.gmail.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03E5EF265A@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E03E5EF265A@MX14A.corp.emc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [nfsv4] RPCSEC-GSSv3 profiling
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: Fri, 08 Apr 2011 04:02:26 -0000

So I'm unfamiliar with what profiling means in this context. How does 
that work in the context of RPCSEC_GSS?


On 4/6/2011 2:11 PM, david.black@emc.com wrote:
> That sounds like a promising approach.
>
> Thanks,
> --David
>
>
>> -----Original Message-----
>> From: Nico Williams [mailto:nico@cryptonector.com]
>> Sent: Wednesday, April 06, 2011 2:04 PM
>> To: Black, David
>> Cc: nfsv4@ietf.org; Moriarty, Kathleen
>> Subject: Re: [nfsv4] draft-quigley-nfsv4-labeled-00 - some comments ([A] - [D])
>>
>> Also, note that for RPCSEC_GSSv3, we could make it something that can
>> be profiled, so that clients that only need it for communicating
>> process labels need not implement the rest of it.  In fact, that's
>> already possible -- we just didn't write that out explicitly.
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.23.0 | Report a Bug | By Email