Re: Opportunistic Tunneling

[Erik Nordmark <Erik.Nordmark@sun.com>]

> Actually, it doesn't.  I think they are the same.
> 
> The vendor supplies the application requires (or benefits) from IPv6 that 
> the user wants to use.  The vendor can supply it so it requires the user to 
> acquire IPv6 service, or it build into its product the ability to detect 
> existing IPv6 connectivity on the users system and if there isn't there, 
> initiate create it via one of the automatic tunneling mechanisms.
> 
> Both scenarios are vendor and user.  The only difference I can see is if 
> the vendor includes the capability to automatically create IPv6 
> connectivity. Both are driven by the user (wanting to use an application) 
> and enabled by the vendor (including it in the product).  The vendor can't 
> make the user do anything (or even buy it's products).  I don't see the 
> distinction you are proposing as being useful.

Agree on all points.

I think vendors can provide the infrastructure in their software that Bob talks
about (detecting existing IPv6 connectivity and prompting the user with "cool
application X needs IPv6 connectivity - should I set up such connectivity?").
Having vendors provide a common framework for this would make their platform
attractive to 3rd party application developpers which want to take
advantage the p2p possibilities with IPv6.

  Erik