%% You should probably cite draft-ietf-radext-deprecating-radius instead of this I-D.
@techreport{dekok-radext-deprecating-radius-00,
    number =    {draft-dekok-radext-deprecating-radius-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-dekok-radext-deprecating-radius/00/},
    author =    {Alan DeKok},
    title =     {{Deprecating RADIUS/UDP and RADIUS/TCP}},
    pagetotal = 17,
    year =      2022,
    month =     oct,
    day =       4,
    abstract =  {RADIUS crypto-agility was first mandated as future work by RFC 6421. The outcome of that work was the publication of RADIUS over TLS (RFC 6614) and RADIUS over DTLS (RFC 7360) as experimental documents. Those transport protocols have been in wide-spread use for many years in a wide range of networks. They have proven their utility as replacements for the previous UDP (RFC 2865) and TCP (RFC 6613) transports. With that knowledge, the continued use of insecure transports for RADIUS has serious and negative implications for privacy and security. This document formally deprecates the use of the User Datagram Protocol (UDP) and of the Transport Congestion Protocol (TCP) as transport protocols for RADIUS. These transports are permitted inside of secure networks, but their use even in that environment is strongly discouraged. For all other environments, the use of TLS- based transports is mandated.},
}