%% You should probably cite draft-ietf-nfsv4-uncacheable-directories-11 instead of this revision.
@techreport{ietf-nfsv4-uncacheable-directories-05,
    number =    {draft-ietf-nfsv4-uncacheable-directories-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-nfsv4-uncacheable-directories/05/},
    author =    {Thomas Haynes},
    title =     {{Adding an Uncacheable Directory-Entry Metadata Attribute to NFSv4.2}},
    pagetotal = 14,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Network File System version 4.2 (NFSv4.2) clients may cache directory-entry (dirent) metadata returned by READDIR to improve performance. Such caching typically assumes that directory-entry metadata and visibility are identical for all users of a client. In some deployments, however, servers may present directory entries or associated metadata based on the identity of the requesting user. Reuse of cached directory-entry metadata across users can therefore result in clients presenting directory contents or attributes that do not reflect the server's current access control decisions. This document introduces an uncacheable dirent metadata attribute for NFSv4.2 that allows servers to advise clients that directory-entry metadata returned by READDIR and related operations should not be reused across users.},
}