@techreport{cel-nfsv4-rpc-tls-dane-01,
    number =    {draft-cel-nfsv4-rpc-tls-dane-01},
    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-rpc-tls-dane/01/},
    author =    {Chuck Lever},
    title =     {{Using RPC-with-TLS with DNS-Based Authentication of Named Entities}},
    pagetotal = 38,
    year =      2026,
    month =     oct,
    day =       2,
    abstract =  {RPC-with-TLS assumes that DNS-Based Authentication of Named Entities (DANE) is available on platforms where it is deployed, and recommends that a client operating under an opportunistic security policy check for a TLSA record before initiating an association, but does not say how. This document specifies the missing details, so that a TLSA record authenticates an RPC server with no certification authority trust anchor provisioned on the client. It updates RFC 9289.},
}