This paper describes the add-on adaptation techniques envisaged for an IPv6 end-terminal with several wireless interfaces. Finally, the last part describes a generic model, which makes possible the adaptation of different kinds of applications, by interacting with the various profiles. Because of the fluctuating resources provided by wireless network interfaces compared to wired ones, the classical adaptation for application (i.e. adaptation inside the application when starting it or setting it up) is not enough. The main objective is to facilitate and optimize the IP network access of a mobile end-user roaming from one access network to another one of different technologies (e.g. between IEEE 802.11 WLAN and GPRS network).

While this simplification of QoS requires small processing latency in routers, there is no distinction between packets with various delay requirements. The introduction of the Type of Service (ToS) field in Internet Protocol version 6 (IPv6), addresses this deficiency. The feasibility of mapping IPv6 ToS onto various Asynchronous Transfer Mode (ATM) service categories has been recently suggested. By adding this new user-attribute to the IPv6 source node, users can experiment the effects and consequences of sending IPv6 packets with different ToS over SVC with different service categories. Figures 8 and 9 show the "ATM switch" attribute windows that allow configuration of the weight of the queue (minimum guaranteed bandwidth) by the user.

The SPIE system calculates several small hash values for each packet as it traverses a router, then stores these values in a data structure called a Bloom filter. Every packet traversing a SPIE-enhanced router is recorded in a digest table; digest tables are paged at a specified rate and are representative of the traffic forwarded by the router during a particular time interval. It is important to ensure that the input into the digest function provide sufficient entropy---that is, changes in input values from packet to packet---for the resulting hash value to uniquely identify a packet. Porting SPIE to an IPv6 network environment requires analysis similar to that conducted for IPv4: The IPv6 header must be analyzed for mutable fields and for sufficient entropy.

Network Address Translation--Protocol Translation (NAT-PT) can provide network protocol translation, and Application Layer Gateways (ALGs) can handle the cases where peer addresses are embedded in application-layer messages. As packets move between the IPv4 region and the IPv6 region, it is necessary to rebuild their headers, since the IPv4 and IPv6 packet headers have different formats. The extended address specifies the network protocol (IPv6 or IPv4), as well as the IP address and the port to be used. Upon these requirements, the Internet Engineering Task Force (IETF) issued the Session Initiation Protocol (SIP) to enable the Internet endpoints (called user agents in SIP) to discover one another and to agree on the parameters of a session.

NTT Laboratories are developing the IPv6 technology to implement global Internet services, with the aim of making the Internet society's infrastructure for future communication. To satisfy this need, NTT Laboratories have developed technology for providing a test environment capable of performing efficient measurements of IP network performance. NTT's next-generation conference system is a presentationoriented conferencing environment called ComComWare that makes conferencing more functional and convenient while downsizing the system. In this research, we have developed an application called CyberPedia to support the construction of learning materials as part of the "look up and learn" concept at the core of "comprehensive learning time."

Migrating from the current IPv4 to the new IPv6 will not just solve the problem of IPv4 addresses running out, IPv6 will carry great significance in a wide range of activities, such as allowing the networking of not only computers but also mobile phones, home appliances, automobiles and other equipment; enabling a variety of communications as required between people, between people and devices, and between devices; and providing improvements in security and communications quality to suit various utilization scenarios. Part 2 introduces multiple IPv6 migration scenarios so that network administrators can choose the most appropriate IPv6 migration method for the various conditions in the network environment.

The X-Pedition switch router family is widely recognized for delivering wire-speed performance, pinpoint application control and advanced security features to IP/IPX networks. With the X-Pedition IPv6 routing modules (X-Pedition ER16-IPV6-00 and SSR-IPV6-000), Enterasys extends these benefits to next-generation protocol environments. The X-Pedition IPv6 routing modules combine the powerful features of a hardware-based platform, capable of forwarding 1.6 Gbps of throughput per module, with the flexible manageability of a software-based routing solution. The X-Pedition ER16-IPV6-00 and SSR-IPV6-00 modules provide the capability to successfully deploy and integrate IPv6 into today's productionquality IPv4 networks, leveraging the proven market-leading routing capabilities of the X-Pedition solution set.

IPv6 as a service enabler, providing IPv6 connectivity for end-user services and applications. The usage of IPv6 in the lower layers interconnecting nodes on specific network segments (e.g. RAN, CS core network, GPRS Gn/Gp network, Sigtran, OAM) or over specific reference points. How are IPv6 addresses assigned to Mobiles? Why do we need Proxies and Translators? IPv6-connected users require easy access to IPv4 services (web-browsing, email etc.) All users activate at least 2 PDP Contexts (one IPv4, one IPv6) Reduces network capacity, requires user to wait until new PDP Context is active and does not solve IPv4 address scarcity problem Tunnel IPv4 packets in IPv6 packets Does not solve IPv4 address scarcity problem, requires more functionality in processing/memory limited terminals (dhcpv6 with extensions) Dual-Stack Application Proxies for well-known services (http, ftp etc.) IPv6<->IPv4 Translation for non-proxied and non-IMS traffic.

IPv4, the workhorse protocol of the currently popular TCP/ IP protocol suite, is fast becoming obsolete. Tanenbaum [2], defines a computer network as an "interconnected collection of autonomous computers". Like most other networking protocols, the TCP/IP is made up of different layers, with each layer responsible for a different role in data communication. The main aim of this part of the paper was to present the basics of Internet Protocol and motivate the need for an upgraded version of this protocol. With this foundation, in the next part we will understand how the successor of IPv4, viz., IPv6 is all set to overcome the shortcomings of IPv4 and continue to cater to the ever growing number of TCP/IP users.

many companies are using the FreeBSD code base in their products e.g. the Interjet from Whistle Inc. (an internet appliance), many router products. the core FreeBSD networking utilities (telnet,ftp) support IPv6. the default FreeBSD 4-STABLE install is IPv6 enabled. NetBSD is perhaps the most portable open source OS today  OpenBSD has their own implementation of IPSec  KAME IPv6 code is used in fOpen,NetgBSD projects  The developer community for these projects is active, but is not as large as that of FreeBSD. A simple 3-step procedure:  build and install a kernel with IPv6 capabilities (default IPv6 capable).