Method and apparatus for connecting IPV4 devices through an IPV6 network using a tunnel setup protocol

• US 20040088385A1
• Filed: 11/01/2002
• Published: 05/06/2004
• Est. Priority Date: 11/01/2002
• Status: Abandoned Application

• Current Assignee: Hexago, Inc. (gogo6, Inc.)
• Original Assignee: Hexago, Inc. (gogo6, Inc.)
• Inventors: Blanchet, Marc, Parent, Florent
• Application Number:
  US10/286,137
• Publication Number:
  US 20040088385A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: H04L 61/251 between different IP versions
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• 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

Abstract

A tunnel setup protocol enables tunnel clients to set up IPv4-in-IPv6 tunnels to permit IPv4 nodes to communicate across the IPv6 network using IPv4 native packets. The tunnel setup protocol is a control channel for negotiating tunnel configuration parameters and exchanging tunnel configuration data between a tunnel client and a tunnel broker server. The tunnel setup is automatic, support of IPv4 nodes and networks in IPv6 networks is enabled, and support of IPv4 devices after migration to IPv6 is facilitated.

Claims

1. A method for connecting an IPv4 device through an IPv6 network to an IPv4 node in an IPv4 network using a tunnel setup protocol, comprising steps of:

sending a message from a tunnel client in the IPv6 network to a tunnel broker server in the IPv6 network to establish a control channel with the tunnel broker server;

sending to the tunnel broker server, via the control channel, a request to establish an IPv4-in-IPv6 tunnel through the IPv6 network, the request including tunnel configuration parameters desired by the tunnel client; and

receiving from the tunnel broker server, via the control channel, any one of;

an acceptance of the request with a specification of information respecting the tunnel configuration parameters desired by the tunnel client;

an acceptance of the request with a specification of at least one alternate parameter for the tunnel configuration desired by the tunnel client; and

, a refusal to establish the tunnel.

2. The method as claimed in claim 1 wherein after the control channel is established with the tunnel broker server, the method further comprises steps of:

sending from the tunnel client to the tunnel broker server a version of a tunnel session protocol installed on the tunnel client;

determining at the tunnel broker server whether the version of the tunnel session protocol is supported by the tunnel broker server; and

returning an error message if the version of the tunnel session protocol is not supported by the tunnel broker server.

3. A method as claimed in claim 2 wherein after the step of returning an error message, the method further comprises a step of returning, from the tunnel broker server to the tunnel client, a list of alternate tunnel broker servers to permit the tunnel client to attempt to obtain service from another tunnel broker server.

4. A method as claimed in claim 2 wherein if the tunnel broker server supports the version of the tunnel session protocol, the method further comprises a step of returning, from the tunnel broker server to the tunnel client, service capabilities of the tunnel broker server.

5. A method as claimed in claim 4 wherein the service capabilities comprise a specification of authentication types, and the method further comprises steps of selecting by the tunnel client an authentication type, and sending authentication information to the tunnel broker server to permit the tunnel broker server to verify that the client is authenticated for the service.

6. A method as claimed in claim 1 wherein the step of sending the message through the IPv6 network comprises a step of formulating either one of a Transmission Control Protocol (TCP) and an User Datagram Protocol (UDP) message that is sent to the tunnel broker server to establish the control channel.

7. A method as claimed in claim 1 wherein the step of sending the request comprises a step of formulating tunnel configuration parameters, comprising a tunnel action type, a tunnel type, and an IPv6 tunnel endpoint address.

8. A method as claimed in claim 7 wherein the tunnel configuration parameters further comprise a request for an IPv4 prefix of a specified length, and a domain name service (DNS) delegation and router peering.

9. A method as claimed in claim 1 wherein the step of receiving the acceptance from the tunnel broker server comprises a step of receiving information specifying a tunnel lifetime, a tunnel client endpoint IPv6 address, a tunnel client endpoint IPv4 address, a tunnel broker server endpoint IPv6 address, and a tunnel broker server endpoint IPv4 address.

10. A method as claimed in claim 9 wherein subsequent to receiving the information, the tunnel client further performs a step of configuring the tunnel client endpoint using the tunnel client endpoint IPv6 address and the tunnel client endpoint IPv4 address.

11. A method as claimed in claim 10 wherein the step of configuring the tunnel client endpoint comprises a step of configuring the tunnel client as the tunnel client endpoint.

12. A method as claimed in claim 10 wherein the step of configuring the tunnel client endpoint comprises a step of configuring a router or a host that is not the tunnel client as the tunnel client endpoint.

13. A method as claimed in claim 1 wherein prior to the step of sending an acceptance of the request with a specification of information respecting the tunnel configuration parameters desired by the tunnel client, the tunnel broker server performs a step of configuring a tunnel broker server endpoint selected from a list of tunnel endpoints available to the tunnel broker server.

14. A method as claimed in claim 13 wherein if the step of configuring the tunnel broker server endpoint is unsuccessful, the tunnel broker server returns an error message to the tunnel client, along with a refusal to establish the tunnel.

15. A method as claimed in claim 14 wherein the tunnel broker server further returns a list of alternate tunnel broker servers to the tunnel client, to permit the tunnel client to attempt to establish a tunnel using another tunnel broker server.

16. A method as claimed in claim 13 wherein the tunnel broker server has an IPv6 stack and an IPv4 stack and the tunnel broker server configures itself as the tunnel broker endpoint using the tunnel broker server IPv6 endpoint address and the tunnel broker server IPv4 endpoint address.

17. A method as claimed in claim 13 wherein the tunnel broker server selects a tunnel broker server tunnel endpoint from a list of nodes having an IPv6 and an IPv4 stack and designated to serve as tunnel endpoints, and configures the selected node to serve as the tunnel endpoint using the IPv6 tunnel broker server endpoint address and the IPv4 tunnel broker server endpoint address.

18. A method as claimed in claim 1 wherein after the tunnel client receives an acceptance of the request with a specification of information respecting the tunnel configuration parameters desired by the tunnel client, the tunnel client closes the tunnel setup protocol session with the tunnel server broker.

19. A method as claimed in claim 1 wherein after the tunnel client receives an acceptance of the request with a specification of information respecting the tunnel configuration parameters desired by the tunnel client, the tunnel client periodically sends a keep-alive message to the tunnel broker server to maintain the tunnel setup protocol session with the tunnel broker server.

20. Apparatus for connecting an IPv4 device through an IPv6 network to an IPv4 node in an IPv4 network using a tunnel setup protocol, comprising:

a tunnel broker server adapted to function as a tunnel broker, the tunnel broker server being programmed to;

respond to a message establishing a control channel with a tunnel client;

authenticate a tunnel client wishing to establish an IPv4-in-IPv6 tunnel through an IPv6 network to which the tunnel broker server is connected;

accept desired parameters for a configuration of the IPv4-in-IPv6 tunnel from the tunnel client; and

configure a tunnel endpoint, if the desired parameters for the configuration of the tunnel client can be satisfied.

21. Apparatus as claimed in claim 20 wherein the tunnel broker server is further adapted to return to the tunnel client parameters for a configuration of the IPv4-in-IPv6 tunnel after accepting the desired parameters from the tunnel client.

22. Apparatus as claimed in claim 20 wherein the tunnel broker server is further adapted to select a tunnel endpoint to be configured from a list of tunnel endpoints adapted to terminate the IPv4-in-IPv6 tunnel.

23. Apparatus as claimed in claim 20 wherein the tunnel broker server is adapted to return a list of other tunnel broker servers which may be used by the tunnel client, if the tunnel broker server is not adapted to provide service in accordance desired parameters for a configuration of the IPv4-in-IPv6 tunnel from the tunnel client.

24. Apparatus as claimed in claim 21 wherein the tunnel broker server is adapted to configure a tunnel end point before returning parameters for a configuration of the IPv4-in-IPv6 tunnel to the tunnel client.

25. Apparatus as claimed in claim 24 wherein the tunnel broker server is adapted to roll back a configuration of the tunnel end point if the parameters for a configuration of the IPv4-in-IPv6 tunnel are rejected by the tunnel client.

26. Apparatus as claimed in claim 20 wherein the tunnel client is programmed to:

establish a control channel with the tunnel broker server;

provide authentication information to the tunnel broker server to permit the tunnel broker server to authenticate the tunnel client;

provide to the tunnel broker desired parameters for a configuration of the tunnel;

accept from the tunnel broker parameters for the configuration of the tunnel; and

configure a tunnel endpoint given the parameters for the configuration of the tunnel.

27. Apparatus as claimed in claim 26 wherein the tunnel client is a router and is further adapted to request an IPv4 prefix of a, specified length when providing the tunnel broker server with the desired parameters for a configuration of the tunnel.

28. Apparatus as claimed in claim 26 wherein the tunnel client is adapted to configure itself as a tunnel endpoint.

29. Apparatus as claimed in claim 26 wherein the tunnel client is adapted to configure another node in the IPv6 network as the tunnel endpoint.

30. Apparatus as claimed in claim 26 wherein the tunnel client is adapted to maintain the control channel with the tunnel broker server by periodically sending keep-alive messages to the tunnel broker server after the tunnel client has configured the tunnel endpoint.

31. A system for connecting IPv4 devices through an IPv6 network to an IPv4 node in an IPv4 network using a tunnel setup protocol, comprising:

a tunnel broker server and a tunnel client that function as respective nodes in the IPv6 network, the tunnel broker server being adapted to respond to a message sent from the tunnel client to establish a control channel between the tunnel client and the tunnel broker server, use the control channel to authenticate the tunnel client attempting to establish an IPv4-in-IPv6 tunnel through the IPv6 network, accept parameters for a configuration of the IPv4-in-IPv6 tunnel sent by the tunnel client via the control channel; and

the tunnel broker server and the tunnel client being respectively adapted to configure a tunnel endpoint for the IPv4-in-IPv6 tunnel.

32. The system as claimed in claim 31 wherein the tunnel client is a host in the IPv6 network.

33. The system as claimed in claim 31 wherein the tunnel client is a router having an IPv6 stack and an IPv4 stack, and at least one link to each of the IPv6 and IPv4 networks.

34. The system as claimed in claim 31 wherein the tunnel broker server is adapted to assign an IPv4 prefix to be used by the tunnel endpoint for a duration of the IPv4-in-IPv6 tunnel.

35. The system as claimed in claim 34 wherein the tunnel client is adapted to request the IPv4 prefix from the tunnel broker client.