[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: addition of TLV to locator ID or locator ID set

To: "Jason Schiller (schiller@uu.net)" <jason.schiller@mci.com>
Subject: Re: addition of TLV to locator ID or locator ID set
From: Paul Jakma <paul@clubi.ie>
Date: Fri, 23 Sep 2005 02:29:39 +0100 (IST)
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, shim6-wg <shim6@psg.com>
In-reply-to: <Pine.GSO.4.20.0509221614300.28499-100000@meno.corp.us.uu.net>
Mail-copies-to: paul@hibernia.jakma.org
References: <Pine.GSO.4.20.0509221614300.28499-100000@meno.corp.us.uu.net>

On Thu, 22 Sep 2005, Jason Schiller (schiller@uu.net) wrote:

We can certainly move the shim function from the host to some network level device; router, traffic engineering server, etc...

The problem is that the current traffic engineering in IPv4 is done at the network level based on lots of routing state. Shim6 is between two end hosts with no routing state. Shim6 is not site multihoming, it is host multihoming.

I, for one, would be very disappointed if shim6 is formulated in such a way as to preclude 'shimming' by intermediaries on behalf of one or more networks.

regards,
--
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
"Life is too important to take seriously."
		-- Corky Siegel

Follow-Ups:
- Re: addition of TLV to locator ID or locator ID set
  - From: Brian E Carpenter <brc@zurich.ibm.com>

References:
- Re: addition of TLV to locator ID or locator ID set
  - From: "Jason Schiller (schiller@uu.net)" <jason.schiller@mci.com>

Prev by Date: Re: addition of TLV to locator ID or locator ID set
Next by Date: Re: addition of TLV to locator ID or locator ID set
Previous by thread: Re: addition of TLV to locator ID or locator ID set
Next by thread: Re: addition of TLV to locator ID or locator ID set
Index(es):
- Date
- Thread