Domain name routing
DCFirst Claim
1. A method for communicating data, comprising the steps of:
- receiving a data unit, said data unit includes a destination address and a first set of information representing a first domain name, said destination address corresponds to each entity in a set of two or more entities, said domain name corresponds to a first entity in said set of entities;
translating said first domain name to a first address, said first address corresponds to said first entity and does not correspond to any other entity in said set of entities; and
sending said data unit to said first entity using said first address.
7 Assignments
Litigations
0 Petitions
Accused Products
Abstract
The present invention provides for a Domain Name Router (DNR) that uses domain names to route data sent to a destination on a network (e.g., a stub network). Each corporate entity or stub network can be assigned one or a small number of global addresses. Each of the hosts on the stub network can be assigned a global address. When a source entity sends data to a destination entity with a local address, the data is sent to the DNR using a global address. The source entity embeds the destination'"'"'s domain name and its own domain name inside the data. The DNR extracts the destination'"'"'s domain name from the data, translates that domain name to a local address and sends the data to the destination.
-
Citations
48 Claims
-
1. A method for communicating data, comprising the steps of:
-
receiving a data unit, said data unit includes a destination address and a first set of information representing a first domain name, said destination address corresponds to each entity in a set of two or more entities, said domain name corresponds to a first entity in said set of entities; translating said first domain name to a first address, said first address corresponds to said first entity and does not correspond to any other entity in said set of entities; and sending said data unit to said first entity using said first address. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A processor readable storage medium having processor readable code embodied on said processor readable storage medium, said processor readable code for programming a processor to perform a method comprising the steps of:
-
receiving a data unit, said data unit includes a destination address and a first set of information representing a first domain name, said destination address corresponds to each entity in a set of two or more entities, said domain name corresponds to a first entity in said set of entities; translating said first domain name to a first address, said first address corresponds to said first entity and does not correspond to any other entity in said set of entities; and routing said data unit toward said first entity using said first address. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29)
-
-
30. A method for communicating data, comprising the steps of:
-
receiving a first set of data; receiving a domain name associated with a destination; and creating a data unit for use with a protocol below an application layer, said step of creating a data unit includes the steps of creating a header, appending said header to said first set of data and adding a first set of information representing said domain name to said data unit, said header includes a destination address, said domain name being different than said destination address, said destination address corresponds to an intermediate entity associated with a set of two or more destination entities, said domain name corresponds to a first entity in said set of destination entities. - View Dependent Claims (31, 32, 33, 34, 35, 36)
-
-
37. A processor readable storage medium having processor readable code embodied on said processor readable storage medium, said processor readable code for programming a processor to perform a method comprising the steps of:
-
receiving a first set of data; receiving a domain name associated with a destination; and creating a data unit for use with a protocol below an application layer, said step of creating a data unit includes the steps of creating a header, appending said header to said first set of data and adding a first set of information representing said domain name to said data unit, said header includes a destination address, said domain name being different than said destination address, said destination address corresponds to an intermediate entity associated with a set of two or more destination entities, said domain name corresponds to a first entity in said set of destination entities. - View Dependent Claims (38, 39, 40, 41)
-
-
42. An apparatus for communicating data, comprising:
-
a processor; a first network interface in communication with said processor; a second network interface in communication with said processor; and a processor readable storage element in communication with said processor, said processor readable storage element storing processor readable code for programming said processor, said processor readable code comprising; first code for receiving a data unit at said first network interface, said data unit includes a global address and a first set of information representing a first domain name, said global address corresponds to said apparatus, said domain name corresponds to a first entity in a set of entities not including said apparatus, second code for translating said first domain name to a local address, said local address corresponds to said first entity and does not correspond to any other entity in said set of entities, and third code for sending said data unit to said first entity using said second network interface and said local address. - View Dependent Claims (43, 44, 45, 46, 47, 48)
-
Specification