From: Noveck, Dave (dave.noveck@netapp.com)
Date: 11/05/99-12:09:30 PM Z
Message-ID: <4080CE03B682D311B589009027C2286638D341@tahoe.corp.netapp.com> From: "Noveck, Dave" <dave.noveck@netapp.com> Subject: RE: Transport requirements for NFSv4 (take 2) Date: Fri, 5 Nov 1999 10:09:30 -0800 > Comments? > > 2.1. Ports and Transports > > Historically, NFS version 2 and version 3 servers have resided on > UDP/TCP port 2049. For NFS version 4, the transport in use by the > RPC layer must provide reasonable congestion control. When TCP or > UDP is used, the default TCP port should be 2049 [RFC1700]. Using > the registered port for NFS services means the NFS client will not > need to use the RPC binding protocols as described in > [RFC1833]; this > will allow NFS to transit firewalls. I don't think this is the intention, but the way this reads, "the transport in use by the RPC layer must provide reasonable congestion control", it sounds like you can't use UDP, unless you are willing to stretch "reasonable" quite a bit. > > To provide for interoperability and congestion control, the RPC > service for NFS version 4 MUST use either TCP/IPv4 or TCP/IPv6. If > your network stack implements TCP/IPv4, NFSv4 SHOULD use TCP/IPv4. > If your network stack implements TCP/IPv6, NFSv4 SHOULD > use TCP/IPv6. > The NFS client and server may use other transports that provide > congestion control and in those cases a mechanism may be > provided to > override TCP usage in favor of another transport. The phrase "MUST use either TCP/IPv4 or TCP/IPv6" sounds like you can't use anything else. How about "MUST implement" or "MUST provide support for use of"? And again it sounds like UDP is not included here.
This archive was generated by hypermail 2.1.2 : 03/04/05-01:47:52 AM Z CST