<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.calhoun-diameter-framework" target="https://datatracker.ietf.org/doc/html/draft-calhoun-diameter-framework-09">
   <front>
      <title>DIAMETER Framework Document</title>
      <author initials="G." surname="Zorn" fullname="Glen Zorn">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Pan" fullname="Ping Pan">
         <organization>Bell Labs</organization>
      </author>
      <author initials="P. R." surname="Calhoun" fullname="Pat R. Calhoun">
         <organization>Sun Microsystems</organization>
      </author>
      <author initials="H." surname="Akhtar" fullname="Haseeb Akhtar">
         <organization>Nortel Networks</organization>
      </author>
      <date month="February" day="5" year="2001" />
      <abstract>
	 <t>Current Internet Service Providers (ISPs) scale their networks by
using the RADIUS protocol, which provides user Authentication,
Authorization and Accounting (AAA) of Dial-up PPP clients. The recent
work done in the Roaming Operations (ROAMOPS) Working Group was to
investigate whether RADIUS could be used in a roaming network, and
concluded that RADIUS was ill-suited for inter-domain purposes.
The IETF has formed a new NAS Requirements Working Group, and part of
their charter is to document the next generation NAS&#x27; AAA
requirements.  Recently, the Mobile-IP Working Group also documented
their own AAA requirements that would help Mobile IP scale for
Inter-Domain mobility.
The DIAMETER protocol is a follow-on to the RADIUS protocol. DIAMETER
addresses the known RADIUS deficiencies, and is intended for use with
the NASREQ and Mobile IP application space.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-calhoun-diameter-framework-09" />
   
</reference>
