Re: shim proxy (was Re: failure detection)

Paul Jakma <paul@clubi.ie> Tue, 23 August 2005 15:55 UTC

Envelope-to: shim6-data@psg.com
Delivery-date: Tue, 23 Aug 2005 15:56:21 +0000
Date: Tue, 23 Aug 2005 16:55:56 +0100
From: Paul Jakma <paul@clubi.ie>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
cc: shim6 <shim6@psg.com>
Subject: Re: shim proxy (was Re: failure detection)
Message-ID: <Pine.LNX.4.63.0508231651180.5291@sheen.jakma.org>
Mail-Copies-To: paul@hibernia.jakma.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"

On Tue, 23 Aug 2005, marcelo bagnulo braun wrote:

> Some questions about the scheme that you are considering:

> - What upper layer identifiers are used in the endpoints? in particular which 
> prefixes do they contain? global unicast or a special purpose prefix (as in 
> GSE)?

To Be Assigned, I guess. I don't know.

> - Are the endpoints of the communication aware of the prefix sets (their own 
> and the peer)? or just the proxy is aware of them?

The proxied hosts, no. They'd happily think they're using normal 
IPv6. Just the proxies with intermediate their access to rest of 
world would recognise their IPv6 network prefix and host identifier 
as being a shim6 ULID.

> - How do they (endpoint and/or proxy) learn the prefix set of the peer? how 
> are they secured?

The remote shim6 peer? Via the TBD shim6 protocol.

> - How does the security mechanism for securing the prefix set and the 
> identifier interact with the proxy and endpoint?

I'm not sure I understand, could you elaborate?

> i was referring to the threats described in 
> draft-ietf-multi6-multihoming-threats-03.txt which need to be dealt with

Thanks, I'll have a look.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Practice is the best of all instructors.
 		-- Publilius