Thanks Jordi for this information<br>Alex<br><br><br><div><span class="gmail_quote">2007/6/6, JORDI PALET MARTINEZ <<a href="mailto:jordi.palet@consulintel.es">jordi.palet@consulintel.es</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>This is the first email, as indicated a few days ago and in the last AfriNIC<br>meeting, in order to show 6to4 and Teredo, a couple of very interesting<br>transition mechanisms, that automatically setup IPv6 connectivity for hosts
<br>and consequently allow IPv6 traffic even if the ISPs don't support it.<br><br>Remember that users with Operating Systems supporting IPv6 (most of them<br>today, some enabled by default), will start using automatic transition
<br>mechanisms (such as 6to4 and Teredo) and there will be more and more IPv6<br>"transition" traffic in your networks even if you don't deploy IPv6. See the<br>presentation "The cost of NOT deploying IPv6", which become more relevant in
<br>developing regions where the upstream bandwidth is much more expensive and<br>some times slower because using satellites. The latest set of slides on this<br>topic are available at:<br><a href="http://www.ripe.net/ripe/meetings/ripe-54/presentations/cost_not_deploying_I">
http://www.ripe.net/ripe/meetings/ripe-54/presentations/cost_not_deploying_I</a><br>Pv6.pdf<br><br>The purpose of the complete set of emails is to show how to take advantage,<br>with almost no cost, of deploying 6to4 and Teredo relays in your networks,
<br>in order to a) be able to save some bandwidth (traffic will stay in your<br>network or peers instead of traversing long paths looking for third party<br>relays), b) deliver a much better non-managed IPv6 "quality of service" to
<br>your users (lower RTT).<br><br>Please, feel free to make any questions that you have by replying to each<br>email.<br><br>As there will be several emails for each protocol, I will suggest that you<br>restrict the questions to the contents of each email and keep the same
<br>subject, so people that later on join the topic, can follow easily the email<br>archive and we avoid answering the same question several times.<br><br>For general information about IPv6, please take a look to the training
<br>material at:<br><a href="http://www.afrinic.net/training/ipv6training.htm">http://www.afrinic.net/training/ipv6training.htm</a><br><br>Regards,<br>Jordi<br><br><br><br>Introduction to 6to4<br>=====================<br>
<br>6to4 is a transition mechanism that allows IPv6 to be encapsulated in IPv4<br>packets (using protocol 41), in order to traverse IPv4-only networks and for<br>example, allow transit of IPv6 thru ISPs that only offer IPv4 service.
<br><br>In principle, it requires a public IPv4 address.<br><br>According to RFC3056 there are two ways a router could support the 6to4<br>transition mechanism.<br><br>The first is called 6to4 Router and the second 6to4 Relay Router.
<br><br>1) 6to4 Router: An IPv6 router supporting a 6to4 pseudo-interface. It is<br>normally the border router between an IPv6 site and a wide-area IPv4<br>network.<br><br>For example, think in an isolated IPv6 cloud. This cloud could use 6to4
<br>addresses and get connected to other IPv6 nodes through the 6to4 router.<br><br>2) 6to4 Relay Router: A 6to4 router configured to support transit routing<br>between 6to4 addresses and native IPv6 addresses.<br><br>The main difference with the 6to4 Router is that the Relay router is
<br>connected to the native IPv6 world. Or what is the same, they announce the<br>2002::/16 prefix to their routing peers.<br><br>Note that an isolated host could be configured as 6to4 router just to<br>obtain IPv6 connectivity (this is called a 6to4 router/host). This
<br>configuration is automatic in many operating systems, and in practice, in<br>means that when a host has IPv6 enabled and a public IPv4 address, if it<br>supports 6to4, it will gain automatic access to IPv6 even if the ISP doesn't
<br>provide the service.<br><br>The 6to4 addresses use the prefix 2002::/16<br><br>For the automatic configuration of the 6to4 hosts in order to reach a 6to4<br>relay, the 6to4 relays need to use an anycast address, which is
<a href="http://192.88.99.1">192.88.99.1</a>.<br>More info on this in RFC3068.<br><br><br>More information and pictures are available at:<br><a href="http://www.ipv6tf.org/index.php?page=using/connectivity/6to4">http://www.ipv6tf.org/index.php?page=using/connectivity/6to4
</a><br><br><br><br><br><br><br><br>**********************************************<br>The IPv6 Portal: <a href="http://www.ipv6tf.org">http://www.ipv6tf.org</a><br><br>Bye 6Bone. Hi, IPv6 !<br><a href="http://www.ipv6day.org">
http://www.ipv6day.org</a><br><br>This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
<br><br><br><br>_______________________________________________<br>afripv6-discuss mailing list<br><a href="mailto:afripv6-discuss@afrinic.net">afripv6-discuss@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo.cgi/afripv6-discuss">
https://lists.afrinic.net/mailman/listinfo.cgi/afripv6-discuss</a><br></blockquote></div><br><br clear="all"><br>-- <br>Alex Corenthin<br>ISOC Sénégal<br>BP 11542 Dakar-Peytavin - Senegal<br>Tel : +221 667 07 75