<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.leung-cisco-mip4-host-config" target="https://datatracker.ietf.org/doc/html/draft-leung-cisco-mip4-host-config-04">
   <front>
      <title>Cisco&#x27;s Mobile IPv4 Host Configuration Extensions</title>
      <author initials="A." surname="Patel" fullname="Alpesh Patel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="K." surname="Leung" fullname="Kent Leung">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="G." surname="Tsirtsis" fullname="George Tsirtsis">
         <organization>Flarion Technologies</organization>
      </author>
      <author initials="E." surname="Klovning" fullname="Espen Klovning">
         <organization>Birdstep Technology ASA</organization>
      </author>
      <date month="September" day="21" year="2005" />
      <abstract>
	 <t>An IP device requires basic host configuration to be able to communicate.  For example, it will typically require an IP address and the address of a DNS server.  This information is configured statically or obtained dynamically using Dynamic Host Configuration Protocol (DHCP) or Point-to-Point Protocol/IP Control Protocol (PPP/IPCP).  However, both DHCP and PPP/IPCP provide host configuration based on the access network.  In Mobile IPv4, the registration process boots up a Mobile Node at an access network, also known as a foreign network.  The information to configure the host needs to be based on the home network.  This document describes the Cisco vendor-specific extensions to Mobile IPv4 to provide the base host configuration in Registration Request and Reply messages.  This memo provides information for the Internet community.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-leung-cisco-mip4-host-config-04" />
   
</reference>
