Subject: [nfsv4] Issue with SETCLIENTID ?

From: Fredric Isaman <[email-masked]>
Date: Thu, 4 Mar 2004 15:07:47 -0500 (EST)

Assuming I am reading the RFC correctly, I see a problem with SETCLIENTID.

Using the RFC's notation, if a client sends

SETCLIENTID{v,x,k} = {c,s}
SETCLIENTIDCONFIRM{c,s}
SETCLIENTID{v,x,l} = {c,t}
client crashes and loses {c,t} values

Now confirmed and unconfirmed lists on the server are such that a
SETCLIENTID{u,x,l} with u!=v will not meet ANY condition in the
implementation on page 210 of RFC 3530.  (The CITI server handles
this by returning NFS4ERR_INVAL.)

	Fred

_______________________________________________
nfsv4 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nfsv4