Talk:Teredo tunneling

message: > and a costly relay would have to be used to perform triangle routing.
My understanding of triangle routing has mobile device A sending to B directly but with a care/of return address of a mobile proxy that knows where A is now. C forwards the message. A is moving and it's IP changes as it crosses cells. Thus B sends care/of C which forwards to A. A continues to send directly to B. This forms a triangle A->B->C->A.
I think they intended to talk about an outbound proxy that allows symmetric nat traversal. With an outbound proxy neither A or B communicate directly but both send packets to the outbound proxy which forwards all communication. This forms a V. A->D->B->D->A
I am still developing an understanding of this stuff and so did not want to make a change without validation. Although linked there is no triangle routing page.  —Preceding unsigned comment added by 69.157.5.200 (talk) 20:12, 29 November 2008 (UTC)
replies: text: Triangle routing in this context refers to all the packets between A and B doing a detour via an overloaded central server C.  Anyway, RFC 6081 now provides some workarounds for using Teredo through various kinds of symmetric NAT. 77.215.46.17 (talk) 01:57, 26 November 2012 (UTC)
thread_title:  Triangle router use appears wrong 

message: I could find no evidence of any BGP export requirement for Teredo relays in RFC 4380. For the Teredo service to operate properly, at least one relay as to export a route through BGP, because not all autonoumous systems will ever have their own Teredo relays. That does not imply all Teredo relays have to do BGP export (the same considerations apply to 6to4 relays).
RFC 4380 actually refers to “the IPv6 routing protocols” (§ 5.4, emphasis added), which supposedly include not only BGP, but also interior routing protocols (OSPF, IS-IS, or even RIPng and manual setup) and adds that a relay might serve as few as a single IPv6 host, i.e. itself.
In addition to that, RFC 4380 also mentions the “range of IPv6 addresses served by the relay” (§ 5.4.3). This hardly make sense if all relay have to use BGP, in which case the range of IPv6 would supposedly be the whole IPv6 Internet.
This accounts for my reversal of Jec's commit 54646349 (03:34, 23 May 2006). Someone might still want to clarify the text involved.
-- Rdenis
Confusion on my end -- the “direct connectivity test” procedure makes it possible to have symmetric routing without global IPv6 reachability of all relays.  Thanks for correcting. --Jec 19:39, 28 May 2006 (UTC)
thread_title:  Teredo relay route export 

message: I cannot reliably fix without background knowledge and I don't want to mess it, so someone please replace the words "host" with the proper phrase (client, relay, server, ...) in the section Teredo relays (and maybe other sections, I'm halfway through reading) in many places. --grin ✎ 09:42, 28 January 2010 (UTC)
thread_title:  Fix bad wording 

message: I work at the Department of Communications Engineering at Tampere University of Technology. www.atm.tut.fi is one of our old websites, from the 90s when ATM was hip and cool. Since then the department has had many face lifts and as a result, most of our old websites will probably be discontinued soon. I actually thought that www.atm.tut.fi had already been discontinued...
Anyway, the citation refers to an email message by Huitema on the ngtrans mailing list hosted by Sun Microsystems. The said mailing list probably has more official archives than the one the citation uses. Google found me the following link which seems as official an archive for the mailing list as is possible:
http://playground.sun.com/pub/ngtrans/mail-archive/ngtrans.200201
Unfortunately it's in mbox format where the www.atm.tut.fi archive is pretty printed and split into individual messages. So, rather than switching the citation link myself to this uglier one, I thought I'd ask the community to decide....
--Aleksi Suhonen, January 2011  —Preceding unsigned comment added by 91.155.191.20 (talk) 01:58, 17 January 2011 (UTC)
replies: text: Switched to IETF archive, it is uglier, but better than a broken link. --Cybjit (talk) 19:22, 17 January 2011 (UTC)
thread_title:  Citation at www.atm.tut.fi 

message: I am surprised that "Teredo tunnel" doesnt direct to the article on Shipworms. Shouldn't there be at least a link to the disambiguation page on top, or is the paleontological meaning of the word not used in English? --Polymeris (talk) 08:46, 18 April 2011 (UTC)
replies: text: you only do that if it's likely, but it's unlikely that somebody would get to the teredo tunneling article when they were looking for shipworms. If they type in teredo on its own they get the disamb page.Rememberway (talk) 14:11, 18 April 2011 (UTC)
replies: text: Happened to me. (Not saying that makes it likely) I wasn't looking for shipworms in general, but Teredolites a.k.a. "Teredo tunnels", which I thought was a (relatively) common term. --Polymeris (talk) 18:34, 18 April 2011 (UTC)
thread_title:  Disambiguation/Redirect: [[Shipworm]] or [[Teredolites]] 

message: Does anyone else feel giving an example where the public IPv4 is in the space reserved for private LAN and therefore commonly the LAN IPv4 of clients behind NAT potentially confusing? I understand we wouldn't want to use some random IPv4 of some random ISPs client, but how about something else like a Microsoft or Google or even wikimedia IPv4 (yes these may change but it's no big deal) 2001:0:4137:9E76:247C:A71:833A:FA41 (talk) 14:07, 7 June 2012 (UTC)
replies: text: The example 192.0.2.45 is not in the reserved spaces for local addresses (10.x.x.x, 172.16.x.x-172.31.x.x, 192.168.x.x and 169.254.x.x) but in the address space reserved for examples, documentation and fiction (192.0.2.x).  192.0.2.x addresses are made up public IP addresses that exist only in made up examples, just like North American 1-555-555-01xx phone numbers and Internet domains that contain the word example as last or second last part (silly.example, silly.example.com, silly.example.org etc.). 77.215.46.17 (talk) 02:19, 26 November 2012 (UTC)
thread_title:  Example potentially confusing 

message: https://www.ietf.org/proceedings/87/slides/slides-87-v6ops-5.pdf --211.127.228.179 (talk) 05:50, 22 April 2015 (UTC)
thread_title:  Microsoft Public Teredo Server has shutdowned