@techreport{cel-nfsv4-rpc-tls-pseudoflavors-02,
    number =    {draft-cel-nfsv4-rpc-tls-pseudoflavors-02},
    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-pseudoflavors/02/},
    author =    {Chuck Lever},
    title =     {{Pseudo-flavors for Remote Procedure Calls with Transport Layer Security}},
    pagetotal = 14,
    year =      2021,
    month =     dec,
    day =       27,
    abstract =  {Recent innovations in Remote Procedure Call (RPC) transport layer security enable broad deployment of encryption and mutual peer authentication when exchanging RPC messages. These security mechanisms can protect peers who continue to use the AUTH\_SYS RPC auth flavor, which is not cryptographically secure, on open networks. This document introduces RPC auth pseudo-flavors that an RPC service can use to indicate transport layer security requirements for accessing that service, and a mechanism the service can use to enforce those requirements.},
}