gogoNET

IPv6 products, community and services

As part of the gogoNET LIVE! conference we will have a three hour workshop on November 2 entitled: Migrating Software to v6.  Owen Delong from HE, who will be teaching this workshop, has produced a first pass outline.  I would like to solicit comments and suggestions from this group before presenting it to the gogoNET membership at large.  Please read below and provide us your feedback. 

Migrating Software to v6

Overview:
This workshop will explain the process of moving software forward from IPv4-only to IPv4/IPv6 dual-stack with working example code for TCP clients and servers in C, PERL, and Python.

Who should attend:
Anyone responsible for the maintenance of tools or software that uses network connections as part of its functionality, including developers, network administrators, systems administrators, and others.

What the attendee will learn:
Attendees will learn the basics of programming in a dual-stack environment and gain detailed knowledge of IPv6 socket programming principles along with detailed examples and working code in C, PERL, and Python.

Outline:
  1. Why add IPv6 capabilities to your software?
  2. Changes to IPv4 TCP servers in C
  3. Changes to IPv4 TCP clients in C
  4. Changes to IPv4 TCP servers in PERL
  5. Changes to IPv4 TCP clients in PERL
  6. Changes to IPv4 TCP servers in Python
  7. Changes to IPv4 TCP clients in Python
  8. Handy References
  9. Question and Answer period

Views: 3

Replies to This Discussion

Looks good, suggestions:
- Adding Java to the languages covered
- A hands on demo for the popular Microsoft Visual C++ tool would help
- Covering OS specific issues like creating two sockets (one for v4 and one for v6) could be helpful for earlier versions of Windows.
Ahmed,

If you would like to port the source code examples to Java, that would be great. I don't have enough familiarity with Java to do so in the time available.

I have no access to Microsoft tools, so, that would be difficult to accomplish.

Actually, I do cover the issue with BSD where you need to either create two sockets or correct their default definition of the V6_V6ONLY socket option (BSD and derivatives go against the RFCs in this behavior).

Earlier versions of windows violate the RFCs in a similar, but slightly more pathological manner. I don't know all the ins and outs of the microsoft bugs since I do not use or have access to any microsoft products on any of my systems.

RSS

Sponsors

Coming soon...

IPv6 Product Information

gogoNET LIVE! 3 Event

Nov. 12-14, 2012, Silicon Valley, USA

© 2012   Created by gogo6.

Badges  |  Report an Issue  |  Terms of Service