From: Spencer Shepler (spencer.shepler@sun.com)
Date: 04/14/04-01:02:41 AM Z
Message-Id: <572A7238-8DD9-11D8-B69B-000A95DBCB70@sun.com> From: Spencer Shepler <spencer.shepler@sun.com> Subject: Re: [nfsv4] more re: NFS4ERR_EXPIRED Date: Wed, 14 Apr 2004 01:02:41 -0500 <during the thread on EXPIRED and BAD_STATEID errors> On Apr 13, 2004, at 11:43 AM, rick@snowhite.cis.uoguelph.ca wrote: > Sounds good also (my server never does this), but I will note that > maybe > adding to the definition of NFS4ERR_EXPIRED in Sec. 12 might > be a good idea to help clarify this? Something along the lines of: > > and all state for the clientid and associated stateids has > been discarded by the server. > > I have no idea if such editorial changes are still feasible? RFC3530 is what it is; changes can not be made in the RFC itself. For error, errata can be submitted to the RFC editor and posted to the RFC editor's errata pages. I have an outstanding AI to gather what has been mentioned to date and get that posted. For interpretation items, the mailing list is the best place to start. For large issues, like the ACL mapping, an informational RFC may be appropriate. Spencer _______________________________________________ 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:24 AM Z CST