Le vendredi 3 août 2007, Nathan Ward a écrit : > > 1) There are proprietary Teredo extensions (AFAIK, at least one > > that allows working with symmetric NATs). Do these depend on > > additional code the servers? If so, one server is not necessarily > > equivalent to another, and I could understand why MSFT would be > > reticent to use anycast. If so, one also might need to reconsider > > whether an anycast prefix makes sense when servers may provide > > different feature sets. > > I'm not aware of these extensions, can anyone provide info? From http://www.microsoft.com/technet/network/ipv6/teredo.mspx : Symmetric NATs (...) Teredo in Windows Vista and Windows Server 2008 can work between Teredo clients if only one Teredo client is behind one or more symmetric NATs. For example, Teredo in Windows Vista and Windows Server 2008 will work if one of the peers is behind a symmetric NAT and the other is behind a cone or restricted NAT. As far as I can tell, symmetric NAT detection is already part of the base spec, so it is not unlikely that this unspecified extension does not involve any change to the servers. What's weirdest to me, as a regular of the BEHAVE WG, is support for symmetric-to-restricted traversal. Symmetric-to-cone is "easy", but symmetric-to-restricted, hmm?! At least, ICE cannot do that. -- Rémi Denis-Courmont http://www.remlab.net/
Attachment:
signature.asc
Description: This is a digitally signed message part.