Re: [v6tc] Make myself clearer...

Thanks for your reply Tim,

If you say some work is needed to refine the TSP specs it's fine. This 
is what the group should do I think. Thanks for that input.

> * Mobile users for whom the first hop to your TB is significant (e.g. if 
>   they are at the IETF here).   Then discovering a 'nearby' TB is quite
>   useful (putting aside the issue of trust).

Now for this one I don't agree. I am not sure this falls under some real 
business case. The question is what do we want to achieve?
   - give IPv6 connectivity to host whatever it is?
   - have service (monitored, secured) offered from provider to customer?

 From what was presented, the group targets for now the second goal. In 
this case you connect to a broker you know, so I am sorry we can't let 
aside the issue of trust. When you roam, the network where you seats can 
provide you some connection information with TEP information. Like it's 
done today for WEP key (like here in Minneapolis). Now if you don't have 
a tunnel broker in the network you are visiting, then I don't think it's 
a good idea to find the closest one.

It's much better I think:
   - to use your ISP tunnel broker (that can be using an anycast TEP)
   - to target the IPv6 VPN scenario. This is much closer to reality I 
think. Here for example many people have VPNs to theiur home network, 
and almost all traffic goes to their home network (It could be better 
for network security, people rely on ACL's they trust) I think this is 
something much more important to consider. I don't know at all if there 
is some v6ops work on it, sorry about it.

Jerome

_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc