From owner-freebsd-fs@FreeBSD.ORG  Tue May  8 01:35:34 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1B9A81065670
	for <freebsd-fs@freebsd.org>; Tue,  8 May 2012 01:35:33 +0000 (UTC)
	(envelope-from bfriesen@simple.dallas.tx.us)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by mx1.freebsd.org (Postfix) with ESMTP id 6E49E8FC0C
	for <freebsd-fs@freebsd.org>; Tue,  8 May 2012 01:35:33 +0000 (UTC)
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	q481ZPbK023829; Mon, 7 May 2012 20:35:26 -0500 (CDT)
Date: Mon, 7 May 2012 20:35:25 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Rick Macklem <rmacklem@uoguelph.ca>
In-Reply-To: <1357768784.50127.1336434018113.JavaMail.root@erie.cs.uoguelph.ca>
Message-ID: <alpine.GSO.2.01.1205072034320.1678@freddy.simplesystems.org>
References: <1357768784.50127.1336434018113.JavaMail.root@erie.cs.uoguelph.ca>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Mon, 07 May 2012 20:35:26 -0500 (CDT)
Cc: freebsd-fs@freebsd.org
Subject: Re: NFSv4 Questions
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 01:35:34 -0000

On Mon, 7 May 2012, Rick Macklem wrote:
>>
> It is my understanding that NFSv4 servers are not supposed to require
> a "reserved" port#. However, at a quick glance, I can't find that stated
> in RFC 3530. (It may be implied by the fact that NFSv4 uses a "user" based
> security model and not a "host" based one.)
>
> As such, the client should never need to "waste" a reserved port# on a NFSv4
> connection.

Firewalls might use the reserved port as part of a filtering 
algorithm.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/