TPTP feature: 165409

Author:	Igor Alelekov
email:	igor.alelekov@intel.com
Last updated:	10/08/2007 09:27:16

Rough workload estimate in person weeks:

Process	Sizing	Names of people doing the work
Design	1
Code	3
Test	1
Documentation	0
Build and infrastructure	0
Code review & other committer work (e.g. check-in, contribution tracking) if this is to be contributed by someone who is not a committer in the component	0	N/A - will be done by committer
Total	5

Requirement summary

This feature should cover the work required to enhance TPTP to support Internet Protocol Version 6 (IPv6) for all socket communication functionality within TPTP, including UI for user input and display of the 128-bit IPv6 addresses

User interactions

User interface

UI should support user input and display IPv6 addresses.

Code interfaces

Should not change API.

Design summary

Required modifications could be divided in the following groups:

Client and server sockets on client and AC side. For Java sockets no porting is necessary. For native server sockets, porting depends on target platform: for a dual-stack platform (Linux) and for a single-stack platform (Windows) porting should be done differently. On Windows, two server sockets should be created (one for IPv6 stack and one for IPv4) and multiplexed to listen connections from either IPv4 or IPv6 clients. On Linux, single IPv6 socket will be able to access either IPv4 or IPv6 connections. Table below illustrates affected components.
UI: support of user input and display IPv6 addresses.
Protocol messages should be updated as well. Currently IP addresses are passed from client to server and vice versa to redirect (hyades clients from unsecured to secured server, new API clients from CCTL to SocketTL) or to request callback (hyades API). Processing of these messages should be updated on the server and client sides to enable IPv6 addresses support.

Affected components in socket communications:

Java/native Component Functionality Modification required

Client sockets Java Platform.Execution
Hyades.Execution Control/Data channels No

Client sockets native AC.CCTL Callbacks to old hyades clients Yes

Server sockets Java AC.CCTL
Hyades.Execution Hyades file and security servers
Callback support No

Server sockets native AC.SocketTL Control/Data channels Yes

	Java/native	Component	Functionality	Modification required
Client sockets	Java	Platform.Execution Hyades.Execution	Control/Data channels	No
Client sockets	native	AC.CCTL	Callbacks to old hyades clients	Yes
Server sockets	Java	AC.CCTL Hyades.Execution	Hyades file and security servers Callback support	No
Server sockets	native	AC.SocketTL	Control/Data channels	Yes