On 04/24/2012 06:34 PM, Kaleb Keithley wrote:
From: "Niels de Vos"<ndevos@xxxxxxxxxx>
Sent: Tuesday, April 24, 2012 7:11:02 AM>
At the moment Gluster uses quite some RPC program numbers which are not
officially registered for Gluster usage.
RFC 5531 (http://tools.ietf.org/html/rfc5531) contains "Appendix B:
Requesting RPC-Related Numbers from IANA". I think it will be good to
request program numbers for the different RPC protocols. It should even be
possible to serve two program numbers at the same time, keeping compatibility
between minor releases, but at the same time prepare for the switch.
Thoughts?
I'm not sure we would solve anything by registering them.
Unlike NFS, where we run on non-standard ports, using registered prognums and progvers lets us advertise via portmapper to clients what port(s) to use for mountd, nfs, and nlm services.
If we ever intend to run glusterd on a port other than 24007, and advertise through portmapper, then I could imagine there would be some value in registering our prognums and progvers.
But we don't advertise in portmapper, and AFAIK, we're not planning to use any port other than 24007 (and 24009+)
I presume we've registered port 24007 at least with IANA. If not, we should.
This is currently under progress. We are also considering moving brick
ports to the IANA private port range.
--
Vijay
