%% You should probably cite draft-cel-nfsv4-rpcrdma-reliable-reply-05 instead of this revision.
@techreport{cel-nfsv4-rpcrdma-reliable-reply-03,
    number =    {draft-cel-nfsv4-rpcrdma-reliable-reply-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-cel-nfsv4-rpcrdma-reliable-reply/03/},
    author =    {Chuck Lever},
    title =     {{Improving the Performance and Reliability of RPC Replies on RPC-over-RDMA Transports}},
    pagetotal = 16,
    year =      2018,
    month =     jul,
    day =       16,
    abstract =  {RPC transports such as RPC-over-RDMA version 1 require reply buffers to be in place before an RPC Call is sent. However, RPC consumers sometimes have difficulty estimating the expected maximum size of a particular RPC reply. This introduces the risk that an RPC Reply message can overrun reply resources provided by the requester, preventing delivery of the message, through no fault of the requester. This document describes a mechanism that eliminates the need for pre-allocation of reply resources for unpredictably large replies.},
}