From: Robert Gordon (Robert.Gordon@Sun.COM)
Date: 01/31/05-05:22:09 PM Z
Date: Mon, 31 Jan 2005 17:22:09 -0600
From: Robert Gordon <Robert.Gordon@Sun.COM>
Message-id: <37ade2aa87f750a851d29b5fe66ad4e0@sun.com>
Subject: [nfsv4] Minor Versioning.
I've been pondering the following :-
a server may advertise support for a minor version but may not
(if the feature is classified as recommended) actually implement
one (or any) of the 'minor version' features.
It has occurred to me that in 4.1 we should recommend a mechanism to
query the server of it's capabilities and then make that mechanism
mandatory in 4.2; This way it should be easy for a client to figure
out if a server can handle sessions, pnfs etc...
Eg:
/* Operation values */
OP_GET_CAPABILITIES = 40
struct SUPPORTED_OPS {
bitmap4 ops; /* ops is a bitmap of nfs_opnum4 */
};
struct SUPPORTEDOPargs {
/* allows client to query multiple minor vers in one compound */
uint32_t minor_version;
};
struct SUPPORTEDOPSresok {
uint32_t minor_version;
SUPPORTEDOPS supported;
};
union SUPPORTEDOPSres switch (nfsstat4 status) {
case NFS4_OK:
SUPPORTEDOPSresok so;
case NFS4ERR_NOTSUPP:
default:
void;
};
--
Robert..
_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4
This archive was generated by hypermail 2.1.2 : 03/04/05-02:13:51 AM Z CST