From e5d009f58c79a8ecb9b29a81add3a294b4d1da5b Mon Sep 17 00:00:00 2001 From: Ted Lemon Date: Wed, 6 Mar 1996 10:42:34 +0000 Subject: [PATCH] Doesn't describe the current design --- Design | 78 ---------------------------------------------------------- 1 file changed, 78 deletions(-) delete mode 100644 Design diff --git a/Design b/Design deleted file mode 100644 index 59be2fd1..00000000 --- a/Design +++ /dev/null @@ -1,78 +0,0 @@ -Objects that need to be tracked: - -Node Names - - A node name is the name of a node attached to a network. - - Nodes can be any type of hardware that is attached to a - network and requires one or more addresses. - - Node names may be associated with a specific hardware - address or set of hardware addresses. - - Node names may also be associated with a specific IP address - or set of IP addresses. - -Interfaces - - An interface is known by its hardware address, which must be - unique. This works for Ethernet, but may be complicated by - PPP (?). What about IBM token ring and FDDI? - - An interface may be associated with a specific node name, - a specific address, or both. - -IP Addresses - - An interface may be associated with a single IP address. - 4.4BSD supports IP aliasing so that a single interface can - have multiple addresses, but this probably isn't worth - supporting explicitly. - -Transitions - - A machine may be moved to a different net - - If the machine's personality hasn't changed, we may want - to assign it a new IP address but keep the same node name. - - If the machine's personality *has* changed, we need to - assign it both a new node name and a new IP address. - - A machine's hardware may be upgraded. - - The new machine should get the old IP Address and Node Name. - - The old machine may need a new IP address and Node Name. - -Static Configuration File - - Addresses which server may assign to arbitrary hosts - - Addresses which are statically assigned to particular - hardware, but which server may need to provide - - Allowable lease length for a given address - -Dynamic Server Database - - Addresses which have been dynamically assigned - - The hardware addresses to which they have been assigned - - The lease expiry time on each assigned address - -Sample static configuration file: - -# One 12-bit subnet, may assign addresses 240 through 4190. -network 16.3.16.0 netmask 255.255.240.0 - address-range 240 through 4190; -# One 4-bit subnet, may assign addresses 2 through 6. -network 192.5.5.16 netmask 255.255.255.240 - address-range 192.5.5.2 through 192.5.5.6; -# 16 12-bit subnets, may assign addresses 128 through 4190 of each network. -# Address ranges are shared with listed servers [TBI]. -networks 16.1.0.0 through 16.1.240.0 netmask 255.255.240.0 - address-range 0.128 through 31.240 - shared-with dhcp-1.pa.dec.com, dhcp-2.pa.dec.com, dhcp-3.pa.dec.com; - - - -Sample database file: - -# January 12, 1996, 16:42:37 -timestamp 1049897235; -lease 204.254.239.7 starts 1049897235 ends 1049957235 - hardware ethernet 08:00:2b:4c:29:35 - uid 08:00:2b:4c:29:35 host minuet class decstations; -lease 204.254.239.8 starts 1049897235 ends 1049957235 - hardware ethernet 08:00:2b:22:09:27 - uid 08:00:2b:22:09:27 class decstations; -lease 204.254.239.9 starts 1049897235 ends 1049957235 - hardware ethernet 08:00:42:29:09:42 - uid 08:00:42:29:09:42; -lease 204.254.239.240 starts 1049897235 ends 1049957235 - uid 50:50:50:3a:6b:69:6d:62:61 host kimba-ppp; - -