RFC 3583 (rfc3583) - Page 2 of 10

Requirements of a Quality of Service (QoS) Solution for Mobile IP

RFC 3583              Mobile IP QoS Requirements          September 2003


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
       1.1.  Problem Statement. . . . . . . . . . . . . . . . . . . .  2
       1.2.  An approach for solving QoS problem in Mobile IP . . . .  3
   2.  Terminology. . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Requirements of a QoS solution for Mobile IP . . . . . . . . .  3
       3.1.  Performance requirements . . . . . . . . . . . . . . . .  4
       3.2.  Interoperability requirements. . . . . . . . . . . . . .  5
       3.3.  Miscellaneous requirements . . . . . . . . . . . . . . .  6
       3.4.  Standard requirements. . . . . . . . . . . . . . . . . .  7
   4.  Security Considerations. . . . . . . . . . . . . . . . . . . .  7
   5.  Recommendation . . . . . . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
       7.1.  Normative References . . . . . . . . . . . . . . . . . .  8
       7.2.  Informative References . . . . . . . . . . . . . . . . .  8
   8.  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .  9
   9.  Full Copyright Statement . . . . . . . . . . . . . . . . . . . 10

1.  Introduction

   Mobile IP is a technology that allows a "mobile node" (MN) to change
   its point of attachment to the Internet while communicating with the
   "correspondent node" (CN) using IP.  The formal description of Mobile
   IP can be found in [1, 6].  Mobile IP primarily addresses the correct
   routing of packets to MN's current point of attachment with the
   Internet.

   It is also essential to provide proper Quality of Service (QoS)
   forwarding treatment to the packets sent by or destined to MN as they
   propagate along different routes in the network due to node mobility.
   This document will identify the requirements that Mobile IP places on
   an IP QoS mechanism.

1.1.  Problem Statement

   When an MN using Mobile IP undergoes handover from one access router
   to another, the path traversed by MN's packet stream in the network
   may change.  Such a change may be limited to a small segment of the
   end-to-end path near the extremity, or it could also have an end-to-
   end impact.  Further, the packets belonging to MN's ongoing session
   may start using a new care-of address after handover.  Hence, they
   may not be recognized by some forwarding functions in the nodes even
   along that segment of the end-to-end path that remains unaltered
   after handover.  Finally, handover may occur between the subnets that
   are under different administrative control.




Chaskar                      Informational