[menog] Get Ready For World IPv6 Day Next Week

Thu Jun 2 06:54:50 GMT 2011

Turk Telekom will participate. www.turktelekom.com.tr<http://www.turktelekom.com.tr> is also available on ipv6.

Best Regards,
Oktay

On Jun 1, 2011, at 9:04 PM, Richard Barnes wrote:

Is anyone on this list planning on doing something special for v6 day?  Either participating as a web site or doing some IPv6 enabling on the ISP side?

For our part, BBN will be enabling v6 on www.bbn.com<http://www.bbn.com>, and doing some measurements.

Best,
--Richard

On Jun 1, 2011 3:32 AM, "Abdelfattah Abuqayyas" <aabuqayyas at citc.gov.sa<mailto:aabuqayyas at citc.gov.sa>> wrote:

Get Ready For World IPv6 Day Next Week<http://www.readwriteweb.com/enterprise/2011/05/get-ready-for-world-ipv6-day-n.php>
By David Strom<http://www.readwriteweb.com/enterprise/author/david-strom.php> / May 31, 2011

<image001.jpg>

Earlier this spring, as anticipated, the last of the IPv4 address blocks was given to the regional Internet registries that dole them out to ISPs and other corporations. Unlike many predictions that go back dozens of years, we have run out of room. Yes, it will take several months before the world is completely run out of address space, and you might be able to find an unused Class C range here or there. But for the most part, you need to get cracking on a transition plan for your company to migrate towards IPv6 now.

Of course, people have been saying this for years now. I recall writing a humorous article back in 1992 or so where I suggested that I start a brokerage service charging for unused address blocks. While it has taken several decades, we have gotten to the point where the end of IPv4 is near. And unlike the predictions for the Rapture, this is an actual event that will need our attention.

To highlight this situation, a group of engineers under the auspices of the Internet Society have set aside next Wednesday, June 8th, to test the new protocol for an entire 24-hour period. Various Web properties will put up IPv6 versions of their sites for the day as demonstrations. And several vendors have begun to assemble copious instructions and advice to help IT network managers figure out their plans.

What is needed for a successful transition? It is a huge undertaking, not unlike the early establishment of the Internet itself.
•         Internet service providers need to make IPv6 connectivity available to all of their users. In most cases this means replacing or upgrading routers and other network switchgear to handle the new protocols.
•         Web companies need to offer their services over IPv6. We'll see some of this next Wednesday, when major site operators such as Google, Facebook, Microsoft and Yahoo will provide IPv6 only versions as targets to connect to.
•         Operating system makers may need to implement specific software updates. Most of the modern desktop OSs include support for IPv6 (see the screenshot below from a Mac as an example). If you are running an older version of XP or MacOS, this can be an issue.
•         Backbone providers will need to establish IPv6 peering with each other.This has begun happening, but obviously more peering is needed, and part of next Wednesday's tests will be to find the non-working links in particular connection paths.
•         Hardware and home gateway manufacturers may need to update firmware to support IPv6. OpenDNS has a series of instructions on their site here<http://www.opendns.com/ipv6/> to enable their "sandbox" to try out IPv6 support for DNS.

Enterprises have basically four different strategies to follow in implementing IPv6:
1.   Dual Stack IPv4 and IPv6 protocols in your routers to connect to an ISP running dual stacks as well. This is probably the simplest solution, but it does break any NAT connections and if you rely on NAT as a primitive security perimeter, you might need to check into this further, since with IPv6, your entire subnet will be directly connected to the Internet.
2.   6to4 tunnels. My Mac uses this method, as can be seen with the 2002: prefix in its IPv6 address. What happens here is that the end of the IPv6 address uses the IPv4 address. This has major performance problems and some firewalls will block this particular protocol on port 41.
3.   Teredo tunnels is an alternative tunneling protocol that has both clients and servers to translate v4 into v6 addresses and vice-versa. Some firewalls block UDP port 3544, which will cause problems.
4.   Tunnel brokers and miscellaneous other mechanisms for coping.

Good luck with your transition. And don't put it off any longer: the time has come!

Abdelfattah ABUQAYYAS, PhD
ICT  Counselor/  www.citc.gov.sa
P.O. Box 75606, Riyadh 11588, Saudi Arabia
Mobile +966-556642230<tel:%2B966-556642230>; Tel. +966-1-263-9236
Twitter: http://twitter.com/abuqayyas
Facebook: abuqayyas at aim.com<mailto:abuqayyas at aim.com>

-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain legally
privileged information. If you are not the intended recipient, please contact the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this e-mail
are those of the sender, and do not necessarily reflect those of the Communications
and Information Technology Commission (CITC). CITC accepts no liability for damage
caused by this email.

_______________________________________________
Menog mailing list
Menog at menog.net<mailto:Menog at menog.net>
http://lists.menog.net/mailman/listinfo/menog

<ATT00001..c>

“This Message (including any attachments) contains confidential information and is intended only for the individual named. If you are not the named adressee or not related with the content of this Message, you are forbidden to read, disseminate, distribute, copy, reproduce or modify this mail by our Company. Please notfy the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmisson can not be guaranteed to be secure or error-free as the mail may arrive late or incomplete or the information could be intercepted, corrupted, lost, destroyed, amended, , or contain viruses. The sender therefore does not accept liability for any errors, loss of integrity or confidentiality or ommissions in the contents of this Message or for the information transmission, reception, storage of use of such in any way whatsoever, which arise as a result of e-mail transmission. Any opinions expressed in this message are those of the author and may not necessarily reflect the opinions of Our Company.

Copyright in documents created by or on behalf of our Company remains vested in us, and we assert all of our moral and intellectual property rights.”

“Bu mesaj (ve ekleri) gizli bilgi içermektedir ve sadece gönderilen kişiye yöneliktir. Bu e-mailin muhatabı değilseniz veya içeriği ile ilginiz yoksa, Şirketimizin onayı olmaksızın bu mesajın okunması, değiştirilmesi, kopyalanması, üçüncü kişilere açıklanması, yayınlanması, ifşa edilmesi veya iletilmesi yasaktır. Bu mesajın gönderilmek istendiği kişi değilseniz (ya da bu e-posta'yı yanlışlıkla aldıysanız), lütfen yollayan kişiyi hemen haberdar ediniz ve mesajı sisteminizden derhal siliniz. E-mail iletiminin güvenli veya hatasız olduğunun garantisi olmadığından geç veya eksik iletim veya içerik ve bilgilerde eksiklik, kayıp, değişiklik veya virüs olabilir. Bu nedenle, bu mesajın iletiminden dolayı, gönderen, içerikteki hata, eksiklik, doğruluğun ve gizliliğin ihlalinden veya bu yolla bilgi paylaşımı, iletimi, depolanması gibi herhangi bir kullanımından hiçbir şekilde sorumlu değildir. Bu mesajın içeriği yazarına ait olup, Şirketimizin görüşlerini içermeyebilir.

Bu mesajın içeriğinde geçen Şirketimizin ad veya nanıma yaratılan fikri ve sınai haklar Şirketimize ait olup, maddi ve manevi tüm hakları Şirketimizde saklıdır.”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20110602/f71e9b9b/attachment.html