Abstract: An Internet Protocol (IP) network node attempts to establish and maintain connectivity to both the Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) networks on initialization of one of the operating system and a program application. The IP node includes program instructions for determining IP addresses of all network interfaces associated with the node; program instructions for identifying all usable Internet protocols available on the node; program instructions for determining whether one of IPv4 and IPv6 are usable for communications with other IP nodes; and program instructions for establishing a tunnel through one of the IPv4 and IPv6 networks to a gateway for the other of IPv4 an IPv6 networks if the program instructions determine that either one of the IPv4 and IPv6 networks are not usable for communications with the other IP nodes.
Abstract: An extended Routing Policy Specification Language (RPSL) permits registry of independent routing policies for different Internet Protocol versions, while being compatible with existing RPSL. Address family identifiers (afis) for identifying a protocol version are inserted into attributes of objects that carry IP address prefixes. RPSL is also extended to permit separate handling of multicast routing policies in any protocol, by including subsequent address family indicators (safis).
Abstract: A tunnel setup protocol enables tunnel clients to set up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across the IPv4 network using IPv6 native packets. The tunnel setup protocol uses a control channel to negotiate tunnel configuration parameters and exchange tunnel configuration data between a tunnel client and a tunnel broker server. The tunnel setup is automatic, and migration to IPv6 is ameliorated.
Abstract: A tunnel setup protocol enables tunnel clients to set up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across the IPv4 network using IPv6 native packets, even if the IPv4 network contains a Network Address Translation function. The tunnel setup protocol uses a control channel to negotiate tunnel configuration parameters and exchange tunnel configuration data between a tunnel client and a tunnel broker server. The tunnel setup is automatic, and migration to IPv6 is ameliorated.
Type:
Grant
Filed:
January 7, 2003
Date of Patent:
December 4, 2007
Assignee:
Hexago Inc.
Inventors:
Marc Blanchet, Florent Parent, Jean-Francois Boudreault
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.
Abstract: An Internet Protocol (IP) network node attempts to establish and maintain connectivity to both the Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) networks on initialization of one of the operating system and a program application. The IP node includes program instructions for determining IP addresses of all network interfaces associated with the node; program instructions for identifying all usable Internet protocols available on the node; program instructions for determining whether one of IPv4 and IPv6 are usable for communications with other IP nodes; and program instructions for establishing a tunnel through one of the IPv4 and IPv6 networks to a gateway for the other of IPv4 an IPv6 networks if the program instructions determine that either one of the IPv4 and IPv6 networks are not usable for communications with the other IP nodes.
Abstract: A tunnel setup protocol enables tunnel clients to set up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across the IPv4 network using IPv6 native packets, even if the IPv4 network contains a Network Address Translation function. The tunnel setup protocol uses a control channel to negotiate tunnel configuration parameters and exchange tunnel configuration data between a tunnel client and a tunnel broker server. The tunnel setup is automatic, and migration to IPv6 is ameliorated.
Type:
Application
Filed:
January 7, 2003
Publication date:
July 8, 2004
Applicant:
HEXAGO INC.
Inventors:
Marc Blanchet, Florent Parent, Jean-Francois Boudreault
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.
Abstract: An extended Routing Policy Specification Language (RPSL) permits registry of independent routing policies for different Internet Protocol versions, while being compatible with existing RPSL. Address family identifiers (afis) for identifying a protocol version are inserted into attributes of objects that carry IP address prefixes. RPSL is also extended to permit separate handling of multicast routing policies in any protocol, by including subsequent address family indicators (safis).
Abstract: A tunnel setup protocol enables tunnel clients to set up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across the IPv4 network using IPv6 native packets. The tunnel setup protocol uses a control channel to negotiate tunnel configuration parameters and exchange tunnel configuration data between a tunnel client and a tunnel broker server. The tunnel setup is automatic, and migration to IPv6 is ameliorated.