Michael Thomas wrote:
> I'm aware that this is only my scenario, but this is
> what I think a naive implementation would do. Ie,
> the mobile router would think it's supposed to send
> a BU when it see something come in from its home agent
> tunnel interface, the MN (or another MR) would
> think it's supposed to send a BU...
I agree that a MN behind the MR is supposed to send a BU, but I disagree
that the MR "is supposed to" do it as well. First, the MR is not the
final destination of the packet. Second, if you think about a naive
implementation, MR would send a BU to the sender that appears in the
inner header in the encapsulated packet, i.e. the CN of MN "behind"
MR. And what would contain the BU ? A binding between the MR's home
address and its COA. This does not give much usefuk information to the
CN. You would end up with a cache at the CN containing:
MR home address -> MR coa
MN home address -> MN coa
CN uses MR's coa if it ever want to communicate with MR directly (very
unlikely)
CN uses MN's coa for packets it wants to send to the MN. No problem
at the CN, although your datagram is going to be routed via the MR's HA
(because MN's coa has the same prefix has the MR's home address. The
issue is that the HA does not know how to redirect (same reason as
explained in my draft)
Then, the issue your are describing (including two addresses in the
routing header) would not happen with a naive implementation of MRs.
If any proposal would advocate such use of the routing header, I think
it should also describe how this should be done.
> If the MR subtends a prefix and can send a BU
> which is legal in -13 as you know, it would
Sorry, I don't catch you here. Could you refine ?
> send a BU when it sees the packet on the HA
> interface. Otherwise, you'd have triangular
> routing at the MR.
>
> I'm not trying to propose anything, actually. I'm just
> pointing out that the current set of drafts won't
> work as they are currently stated to more than
> one level of mobility.
This is right, but this is not the purpose of any existing draft to
address more than one level of mobility. More than one level of
mobility needs it's own set of drafts.
Thierry.
--
* mailto:[EMAIL PROTECTED] Tel +33 (0) 4 76 61 52 69
* INRIA Rhone-Alpes Projet PLANETE (fax 52 52)
* and MOTOROLA Labs Paris
* http://www.inrialpes.fr/planete/people/ernst/Welcome.html
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
