e network ID for a data packet destination by doing a "logical AND" operation on the packet's destination IP address and its own subnet mask. The device determines its own network ID by doing the same operation using its own IP address and subnet mask. Table 2-2: Local and Remote IP Addresses Sending Device IP Address: 200.100.50.10 11001000.01100100.00110010.00001010 Subnet Mask: 255.255.255.240 11111111.11111111.11111111.11110000 Network ID: 200.100.50.000 11001000.01100100.00110010.00000000 Local IP address IP Address: 200.100.50.14 11001000.01100100.00110010.00001110 Subnet Mask: 255.255.255.240 11111111.11111111.11111111.11110000 Network ID: 200.100.50.000 11001000.01100100.00110010.00000000 Remote IP address IP Address: 200.100.50.18 11001000.01100100.00110010.00010010 Subnet Mask: 255.255.255.240 11111111.11111111.11111111.11110000 Network ID: 200.100.50.016 11001000.01100100.00110010.00010000 Wireless Network Logical Architecture Private IP Addresses In February 1996, the Network Working Group requested industry comments on RFC 1918, which proposed three sets of so-called private IP addresses (Table 2-3) for use within networks that did not require Internet connectivity. These private addresses were intended to conserve IP address space by enabling many organisations to reuse the same sets of addresses within their private networks. In this situation it did not matter that a computer had an IP address that was not globally unique, provided that that computer did not need to communicate via the Internet. Table 2-3: Private IP Address Ranges Class Private address range start Private address range end 10.0.0.0 10.255.255.255 172.16.0.0 172.31.255.255 192.168.0.0 192.168.255.255 Subsequently, the Internet Assigned Numbers Authority (IANA) reserved addresses 169.254.0.0 to 169.254.255.255 for use in Automatic Private IP Addressing (APIPA). If a computer has its TCP/IP configured to obtain an IP address automatically from a DHCP server, but is unable to locate such a server, then the operating system will autom