Reply to sender DHCP option

Details Reply to sender DHCP option Reply to sender DHCP option

1999-02-10

2003-07-01

Ngo, Ricky (Department: 2731)

Multiplex communications

Pathfinding or routing

Switching a message which includes an address header

C370S410000, C370S475000, C709S245000

Reexamination Certificate

active

06587468

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to the Dynamic Host Configuration Protocol (DHCP) used in conjunction with large scale data communications networks such as the Internet. More particularly, the present invention relates to utilizing a DHCP server to allocate dynamic network addresses to various devices, rather than just to dial-up users.
2. The Background
As shown in
FIG. 1
, the Internet, or any large data communications network,
10
may be described as a group of interconnected computing networks (not shown) that are tied together through a backbone
12
. The computing networks, in turn, provide access points, such as access points
14
,
16
and
18
, through which users may connect to the Internet via a station (a computer having a connection to a network) or host, such as hosts
20
,
22
,
24
, and
26
. An access point is essentially a location on the Internet that permits access to the Internet. An access point may include a modem pool (not shown) maintained by an ISP (Internet Services Provider) which enables its subscribers to obtain Internet access through a host having a dial-up connection. Those of ordinary skill in the art will recognize that other types of access methods may be provided by an ISP such as frame relay, leased lines, ATM (asynchronous transfer mode), ADSL, and the like.
Regardless of the access method used, each device (e.g., a host or router) that receives, sends and/or routes information between or among other devices on Internet
10
is configured to communicate with other devices using a communication protocol that may be understood by the other devices. The current communication protocol used by these devices on the Internet is TCP/IP (transmission control protocol/internet protocol). In addition, each device that can send or receive information (e.g., a host device) must also have a unique host address. The type of host address used for the Internet, or an equivalent switched network that uses TCP/IP, is commonly referred to as an IP address. A standard TCP/IP address in accordance with current standards is 4 bytes (32 bits) in length, providing a total of 2
32
possible IP addresses. Those of ordinary skill in the art will readily recognize that not all of these possible IP addresses are available due to administrative expediencies, such as reserving blocks of IP addresses for future use.
Sending or receiving information using the TCP/IP protocol requires encapsulating information into packets. Each packet includes a header and a payload. The header contains information related to the handling of the payload by a receiving host or routing device, while the payload contains part or all of the user information. The information in the header includes the sender's and the recipient's addresses and is used to route the packet through the Internet until the packet is received by a host having an IP address that matches the packet's destination address (when referring to the source IP address and destination IP address of a packet, the source IP address and destination IP address are commonly referred to as “SA” and “DA”, respectively). This enables users to accurately send and receive information with each other through their respective host computers.
By implementing a protocol common to all devices using Internet
10
, users may send and receive information with other users on the Internet in a seamless manner regardless of geographic location or the type of host and/or interconnected network used.
The dramatic increase in popularity of the Internet in recent years has created a concern about the number of available IP addresses under the current standard (known as IP v.4). ISPs and domains are generally allocated a finite number of IP addresses. The ISPs and domains, therefore, are constantly looking for ways to limit the number of IP addresses they use while still providing access to the greatest number of users.
One solution for mitigating the effect of the number of users requiring host addresses is to dynamically allocate host addresses for users who do not have dedicated connections to the Internet, such as users who use dial-up access methods to connect to an ISP. Dynamic allocation of IP addresses entails having a pool of IP addresses, such as IP address pool, from which an ISP can draw from each time a valid subscriber (who does not use a dedicated connection or a connection that does not have a framed IP address, i.e., a static IP address) seeks to access the Internet. Once the subscriber logs on to an ISP and is properly authenticated, the ISP allocates an IP address for use by the user. This task is normally performed by a Dynamic Host Configuration Protocol (DHCP) server or service existing at the ISP (or other local segment of the Internet).
Upon log-off, the DHCP server releases the assigned/allocated IP address, rendering that IP address available for subsequent use by another user. In this way, a set of IP addresses can be used to provide access to a number of users that exceed the number of IP address comprising the IP address pool, assuming that at any given time the number of users seeking to log-on and obtain dynamic IP addresses is less than or equal to the number of IP address available in the IP address pool.
FIG. 2
is a diagram illustrating the format of a DHCP message. Message
50
includes an op field
52
, which indicates whether the message is a request or a reply. An htype field
54
indicates the hardware address type. An hlen field
56
indicates the hardware address length. An hops field
58
is initially sent to zero by the client and is used by relay-agents. An xid field
60
indicates the transaction ID, which is a random number chosen by the client and used to associate messages with responses. A secs field
62
indicates the elapsed time (in seconds) since the client started trying to boot. The flags field
64
includes a number of different flags utilized by the client and server. The ciaddr field
66
indicates the client's IP address. The yiaddr field
68
indicates the offered or assigned temporary IP address. The siaddr field
70
is used to indicate the next server in a bootstrap. A bootstrap is a network of devices utilizing a bootstrap protocol, such as BOOTP (Bootstrap Protocol). The bootstrap protocol allows the devices to deliver assigned IP addresses and dynamically configure software to remote devices. The siaddr field
70
would then indicate the next server or device in the bootstrap. A giaddr field
72
indicates the relay agent's (if any) IP address. A chaddr field
74
indicates the client hardware address. Sname field
76
indicates an optional server host name. Afile field
78
indicates a boot file name or options to be used by the client. Finally, a variable length options field
80
may utilize a number of predefined options, while allowing for new options to be created.
A subnet is an independent division of a network interconnected with the network. If a client is on the same sub-net as the DHCP server, the DHCP server simply broadcasts its reply, as every host on the local subnet can receive the broadcast. However, in large networks such as the Internet, a DHCP request packet is not directly sent from a client on the local subnet. Instead, the packet is indirectly passed from the client to the DHCP server through the use of relay agents or servers. In this case, the DHCP server will send its reply packet to the address found in the giaddr field
72
, which is the address of the last relay agent or server. This relay agent or server will then pass the reply packet along to other relay agents or servers until it eventually reaches the client. However, the giaddr field
72
also is used as the subnet ID, which is depended upon by a DHCP server in allocating an IP address. The DHCP server will allocate an IP address that has the same subnet as the giaddr field
72
. There may be times when this may create problems. For example, if one wants to allocate an IP address that has a different subnet from that of t

Affiliated with

Also associated with

Rating

Reply to sender DHCP option does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Reply to sender DHCP option, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Reply to sender DHCP option will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3021395