<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.muhanna-diameter-mip4-performance" target="https://datatracker.ietf.org/doc/html/draft-muhanna-diameter-mip4-performance-02">
   <front>
      <title>MIPv4 Authentication Using a New Diameter MIPv4 Application</title>
      <author initials="A." surname="Muhanna" fullname="Ahmad Muhanna">
         <organization>Nortel</organization>
      </author>
      <author initials="M." surname="Khalil" fullname="Mohamed Khalil">
         <organization>Nortel</organization>
      </author>
      <author initials="A." surname="Lior" fullname="Avi Lior">
         <organization>Bridgewater Systems</organization>
      </author>
      <date month="July" day="14" year="2008" />
      <abstract>
	 <t>Current Mobile IPv4 deployments use RADIUS based MIPv4 user
authentication and authorization.  Diameter Mobile IPv4 Application
[RFC4004] offers another method for MIPv4 authentication,
authorization, and dynamic mobility security association allocation,
e.g.  MN-HA SA allocation.  Some SDOs are considering the use of
Diameter Mobile IPv4 Application to replace RADIUS based mechanism.
However, these SDos use a link layer access authentication mechanism,
e.g., using an EAP application, to derive the related MIP4 shared
keys and security association.  This document an overview of these
respected architectures and their handling to MIP4 security
association and keys derivation and distribution.  It presents an
analysis of the performance and impact of Diameter MIPv4 Application
and RADIUS based solutions on the time the mobile node uses during
the initial session setup.  Some common MIPv4 scenarios which require
the mobile node to retransmit its initial RRQ message have been
identified and used.  The set of assumptions and requirements used
for this study has been clearly documented under section 5.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-muhanna-diameter-mip4-performance-02" />
   
</reference>
