OPTIMIZATIONS FOR IMPLEMENTING MULTI-STACK STACK HOSTS

• US 20120066695A1
• Filed: 09/13/2010
• Published: 03/15/2012
• Est. Priority Date: 09/13/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Berezansky, Yury, Sapir, Moshe, Bernstein, Ben, Braitmaiere, Maxim
• Granted Patent: US 8,484,666 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: H04L 2101/668 Internet protocol [IP] address subnets
• CPC Class Codes: H04L 61/251 between different IP versions
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level

Abstract

Architecture that includes optimizations for “Bump-in-the-API” (BIA) as employed for multi-stack hosts. These optimizations reduce the limitations imposed by the existing translation technologies by simplifying the implementation and addressing possible compatibility issues. More specifically, the architecture discloses optimizations that use a preconfigured NAT64 prefix for mapping of NAT64 IPv6 addresses in the prefix subnet to IPv4 addresses, without a mapping table (stateless), use configuration information for enabling API translation per application (resolves possible compatibility issues), and use a local IPv4 socket and a data pump to reduce the number of translated API calls.

Claims

1. A computer-implemented system having computer readable media that store executable instructions executed by a processor, comprising:

a multi-stack local host having an application of a first transport address version application program interface (API) that seeks communication with a remote host of a second transport address version API; and

an API translation component that facilitates the communication between the application and the remote host based on automatic stateless transport address version translation between the local host and the remote host, application configuration information, and a localized transport address version socket.

2. The system of claim 1, wherein the API translation component accesses the configuration information associated with the application to determine if translation is needed for the application.

3. The system of claim 1, wherein the API translation component comprises an address mapper that performs the transport address version translation, the address mapper reconstructs a second transport address version into a first transport address version by stripping a prefix from the second transport address version and adding the prefix to the first transport address version, the transport address version translation performed without an address table.

4. The system of claim 1, wherein the API translation component comprises a connect mapper that intercepts a function call to connect to a transport address, creates a local connect socket, and establishes a connection with the remote host via the local connect socket.

5. The system of claim 4, wherein the connect mapper creates a listening socket that monitors communications between the remote host and the application via the local connect socket.

6. A computer-implemented system having computer readable media that store executable instructions executed by a processor, comprising:

a multi-stack local host having an application of a first transport address version application program interface (API) that seeks communication with a remote host of a second transport address version API;

a configuration component that stores application configuration information accessible for a given application seeking communications with the remote host; and

an API translation component that facilitates the communication between the application and the remote host, the API translation component associated with,

a name resolver component that performs name resolution based on the application configuration information;

an address mapper component that statelessly deduces and reconstructs an address of the first transport address version into an address of the second transport address version; and

a connect mapper component that creates sockets for the application and the remote host via which the application communicates with the remote host.

7. The system of claim 6, wherein the connect mapper component creates a data pump with an application listening socket and remote host socket that enables communications between the application and the remote host.

8. The system of claim 6, wherein the address mapper component performs transport address version translation, the address mapper reconstructs a second transport address version into a first transport address version by stripping a prefix from the second transport address version and adding the prefix to the first transport address version.

9. The system of claim 8, wherein the first transport address version is IPv4 and the second transport address version is IPv6.

10. The system of claim 8, wherein the prefix is based on a network address translation device imposed between the remote host and the application.

11. The system of claim 6, wherein the application is of the first transport address version that seeks to communicate with remote host which is of the first transport address version, via a network address translation component.

12. The system of claim 6, wherein the stack is based on a bump-in-the-API technology.

13. A computer-implemented method executed by a processor, comprising:

in a multi-stack host, receiving a call from an application to access a remote host, the application of a first transport address version and the remote host of a second transport address version;

mapping the first transport address version to the second transport address version using a reversible stateless transformation process;

creating a remote host socket of the second transport address version that facilitates communication with remote host;

creating a listening socket of the first transport address version that facilitates communication with application; and

transmitting data between the listening socket and the remote host socket for communications between the application and the remote host.

14. The method of claim 13, further comprising accessing application configuration information to determine if to intercept the call from the application.

15. The method of claim 14, further comprising performing name resolution based on the application configuration information.

16. The method of claim 13, further comprising enabling or disabling API translation for the application based on the application configuration information.

17. The method of claim 13, further comprising intercepting a connection call associated with creation of a local application socket for the application, using a connect mapper.

18. The method of claim 13, further comprising obtaining from an address mapper an address in the second transport address version for the remote host socket.

19. The method of claim 13, wherein the first transport address version is IPv4 and the second transport address version is IPv6.

20. The method of claim 13, further comprising deducing an address of the remote host based on a prefix of an address of the second transport address version.