Re: (mobile-ip) Mobile-IP Layers

Gerald Maguire <> Sun, 10 May 1998 17:30 UTC

Delivery-Date: Sun, 10 May 1998 13:30:36 -0400
Received: from ( []) by (8.8.5/8.8.7a) with ESMTP id NAA06116 for <>; Sun, 10 May 1998 13:30:35 -0400 (EDT)
Received: from (hosaka.SmallWorks.COM []) by (8.8.5/8.8.7a) with ESMTP id NAA00768 for <>; Sun, 10 May 1998 13:33:03 -0400 (EDT)
Received: (from majordomo@localhost) by (8.8.7/8.8.7) id MAA03830 for mobile-ip-dist; Sun, 10 May 1998 12:05:54 -0500 (CDT)
X-Authentication-Warning: majordomo set sender to owner-mobile-ip using -f
Received: from ( []) by (8.8.7/8.8.7) with ESMTP id MAA03825 for <>; Sun, 10 May 1998 12:05:19 -0500 (CDT)
Received: (from maguire@localhost) by (8.8.8/8.8.8) id TAA13871; Sun, 10 May 1998 19:04:46 +0200 (MET DST)
Date: Sun, 10 May 1998 19:04:46 +0200 (MET DST)
Message-Id: <>
From: Gerald Maguire <>
In-reply-to: <> (message from Baher Esmat on Sun, 10 May 1998 16:54:19 +0300)
Subject: Re: (mobile-ip) Mobile-IP Layers
Precedence: bulk
Reply-To: Gerald Maguire <>

The whole point of doing Mobile IP at the network layers is that
nothing above it has to change (from a functionality point of view).
There are cases where the higher layers will want to be aware of the
change in bandwidth, delay, ... - but this is currently outside the
scope of Mobile IP it just gets the packets to the mobile (like any
good network layer should).

Note that there are various proposals for transport layer changes to
avoid performance problems when your links change characteristic, such
as when the error rate of a link (typically the last hop) changes

IETF Mobile IP Working Group Mailing List - Archives:
Unsubscribe:	unsubscribe mobile-ip		(as message body, not subject)
Direct all administrative requests to