<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.moskowitz-radius-sec-roadmap" target="https://datatracker.ietf.org/doc/html/draft-moskowitz-radius-sec-roadmap-00">
   <front>
      <title>RADIUS Security Roadmap</title>
      <author initials="R." surname="Moskowitz" fullname="Robert Moskowitz">
         <organization>ICSAlabs a Division of Cybertrust</organization>
      </author>
      <date month="February" day="16" year="2005" />
      <abstract>
	 <t>   RADIUS has become the defacto protocol between network edge devices
   (e,g, dial NAS or Wireless AP) and a backend Authentication Server.
   In this environment the backend Server is often called a (RADIUS
   Server).  RADIUS is gaining very broad penetration, even into homes,
   because of its use with wireless authentication.  Because of the
   amount of deployed infrastructure already in place, we believe that
   RADIUS will not be supplanted by another authentication service in
   the foreseeable future.  Because the widespread deployment in
   wireless has different infrastructure requirements than what is
   required for dialup, RADIUS requirements, especially trust between
   Edge devices and RADIUS Servers needs to be addressed.  This document
   sets the requirements for RADIUS security and then sets forth
   technologies that will satisfy those requirements.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-moskowitz-radius-sec-roadmap-00" />
   
</reference>
