文档介绍：Writing IPv6 applications
Fulvio Risso
NetGroup, Dipartimento di Automatica e Informatica
ico di Torino
/
Outline
Protocol version 6: overview
Writing IPv6 applications
Old and new socket programming styles
Adding IPv6 support to old IPv4 applications
Converting an IPv4 application into an IPv6 one
Writing new applications with IPv4 and IPv6 support
patibility issues
Using work abstraction (. Microsoft .NET)
What about if the application already exists and the source code is not available?
Some points related to the migration of applications within a work
Conclusions
Protocol version 6
A work-level protocol
It keeps the transport layer unchanged
Several improvements
More addresses
More efficient routing
Mobile support
Security support
Plug and play
Why writing applications?
Most of the work, so far, focused work-related issues
Definition of the IPv6 protocol and related work infrastructure
Operating System support
A few people are currently working on the application side
We must avoid the problem of ATM
Excellent technology, but no applications ready to work on it
The socket interface
We’work people, we don’t like .Net, Java, and friends
C/C++ only if you want flexibility and speed
The old programming code (BSD-style API)
#define PORT 2000 /* This definition is a number */
void server ()
{
int Sock; /* Descriptor for work socket */
struct sockaddr_in SockAddr; /* Address of the server socket descr */
if ( ( Sock = socket(, SOCK_STREAM, 0)) < 0 ) {
error("Server: cannot open socket.");
return;
}
memset(& SockAddr, 0, sizeof(SockAddr));
= ;
= htonl(INADDR_ANY); /* all local addresses */
= htons(PORT); /* Convert work byte order */
if (bind(Sock, (struct sockaddr *) &SockAddr, sizeof(SockAddr)) < 0) {
error("Server: bind failure");
return;
}
/* ... */
The code must be duplicated for each address family
The new programming style (RFC 3493 API)