From owner-cvs-all@FreeBSD.ORG  Sun Mar  7 17:14:12 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3FA8516A4CE; Sun,  7 Mar 2004 17:14:12 -0800 (PST)
Received: from citi.umich.edu (citi.umich.edu [141.211.133.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1DA7943D41; Sun,  7 Mar 2004 17:14:12 -0800 (PST)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (dsl093-001-248.det1.dsl.speakeasy.net
	[66.93.1.248])	by citi.umich.edu (Postfix) with ESMTP
	id C3EBF2080F; Sun,  7 Mar 2004 20:14:09 -0500 (EST)
To: Robert Watson <rwatson@FreeBSD.org>
From: Jim Rees <rees@umich.edu>
In-Reply-To: Robert Watson, Sun, 07 Mar 2004 14:28:07 EST
Date: Sun, 07 Mar 2004 20:14:09 -0500
Sender: rees@citi.umich.edu
Message-Id: <20040308011409.C3EBF2080F@citi.umich.edu>
cc: Alexander Kabaev <kan@FreeBSD.org>
cc: "Brian F. Feldman" <green@FreeBSD.org>
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
cc: cvs-src@FreeBSD.org
Subject: 
	Re: cvs commit: src/sys/nfsserver nfs.h nfs_srvsock.c nfs_srvsubs.c 
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2004 01:14:12 -0000

We have big plans for the nfs rpc.  In particular, we'll be adding rpcsec
with gss soon, at least to the client.  Right now the v3 and v4 clients use
separate rpcs, but that's silly and will change.  The v3 client will use the
v4 rpc (in sys/rpc) and both will benefit from rpcsec.

I'm not sure yet what the server will look like.  We're just getting started
on the v4 server.  Rick Macklem has the beginnings of a v4 server and we
hope to build on that and get it in to FreeBSD.  The v4 server will
certainly have rpcsec, and the v3 server will want to use rpcsec too.

All help and suggestions welcome.