source: trunk/alloctypes.html@ 411

Last change on this file since 411 was 344, checked in by Kris Deugau, 18 years ago

/trunk

Backport changes to alloctypes.html from /branches/stable r270 and r332
File size: 4.6 KB
Line 
1<html><head>
2
3<title>IP Database</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
4
5<link rel="stylesheet" type="text/css" href="/ip/ipdb.css">
6
7</head>
8<body bgcolor="#ffffff" text="#000000" link="#000000" vlink="#000000" alink="#ff0000" leftmargin="0" topmargin="0" marginwidth="0">
9
10<table class="regular">
11
12<tr><td colspan=2 class="heading">Allocation Types:</td><tr>
13
14<tr class="color1">
15<td>Customer netblock (default)</td><td>A direct allocation /30 or larger to a
16customer. Note that this does NOT include RADIUS-routed "netblocks". Internal systems
17should use the "End-use netblock" type.</td>
18</tr>
19
20<tr class="color2">
21<td>Static IP - Server pool</td><td>A single IP from a pool designated for
22servers</td>
23</tr><tr class="color1">
24<td>Static IP - Cable</td><td>A single IP address from a designated pool
25on the cable network.</td>
26</tr><tr class="color2">
27<td>Static IP - DSL</td><td>A single IP address from a designated pool
28on the DSL network. Note that these are nominally in Sudbury or North Bay,
29even if the customer isn't.</td>
30</tr><tr class="color1">
31<td>Static IP - Dialup</td><td>A single IP address from a designated pool
32on a dialup RAS.</td>
33</tr><tr class="color2">
34<td>Static IP - Wireless</td><td>A single IP address from a designated pool
35on one of our wireless networks.</td>
36</tr>
37
38<tr class="color1">
39<td>Static pool - Servers</td><td>A pool of IP addresses available for one-by-one
40assignment to servers in a POP. This will usually only be in Sudbury.</td>
41</tr><tr class="color2">
42<td>Static pool - Cable</td><td>A pool of IP addresses available for one-by-one assignment
43to customers on cable.</td>
44</tr><tr class="color1">
45<td>Static pool - DSL</td><td>A pool of IP addresses available for one-by-one assignment to
46customers on DSL. Note that individual IPs will be "assigned" to the customer's
47city, but the pool they are a part of will normally be "assigned" to Sudbury or
48North Bay.</td>
49</tr><tr class="color2">
50<td>Static pool - Dialup</td><td>A pool of IP addresses available for one-by-one
51assignment to dialup customers.</td>
52</tr><tr class="color1">
53<td>Static pool - Wireless</td><td>A pool of IP addresses available for one-by-one
54assignment to customers on one of our wireless networks.</td>
55</tr>
56
57<tr class="color2">
58<td>End-use netblock</td><td>A /30 or larger allocation for arbitrary services (LAN
59management, servers we want fully subnet-isolated, etc)</td>
60
61</tr><tr class="color1">
62<td>Dialup netblock</td><td>Netblock assigned to one or more RAS units in a POP</td>
63</tr><tr class="color2">
64<td>Dynamic DSL block</td><td>Netblock for (mostly residential) PPPoE DSL. Nominally
65"assigned" to Sudbury</td>
66</tr><tr class="color1">
67<td>Dynamic cable block</td><td>Netblock for (mostly residential) DHCP cable.</td>
68</tr><tr class="color2">
69<td>Dynamic WiFi block</td><td>Netblock for (mostly residential) (mostly) PPPoE wireless.</td>
70</tr><tr class="color1">
71<td>Dynamic VoIP block</td><td>Netblock for DHCP-assigned VoIP services.</td>
72
73</tr><tr class="color2">
74<td>Static IP - LAN/POP</td><td>A single IP address from a designated pool for our
75internal LANs - either at a single POP or for a VPN.</td>
76</tr><tr class="color1">
77<td>Static pool - LAN/POP</td><td>A pool of IP addresses available for one-by-one
78assignment to our internal LAN systems or VPNs.</td>
79
80</tr><tr class="color2">
81<td>Reserve for WAN blocks</td><td>Reserve a chunk of IP space for core routers/etc.</td>
82</tr><tr class="color1">
83<td>Reserve for dynamic-route DSL netblocks</td><td>Reserve a chunk of IP space for
84RADIUS-assigned "netblocks" from a PPPoE pool. Note that this is similar to the static DSL
85pool, but IP space is to be allocated as /30 and larger netblocks, not single static IPs.</td>
86</tr><tr class="color2">
87<td>Reserve for ATM</td><td>Reserve a chunk of IP space for allocation to customers on ATM</td>
88</tr><tr class="color1">
89<td>WAN block</td><td>Individual netblock assignment for a core router. Always taken from a
90block which has previously been reserved for such assignments.</td>
91</tr><tr class="color2">
92<td>Dynamic-route DSL netblock</td><td>Customer assignment for a RADIUS-assigned PPPoE
93"netblock". Always taken from a block which has previously been reserved for such
94assignments.</td>
95</tr><tr class="color1">
96<td>ATM block</td><td>Customer assignment for a customer on ATM. Always taken from a
97block which has previously been reserved for such assignments.</td>
98
99</tr><tr class="color2">
100<td>Routing</td><td>Blocks not actually assigned to a service on their own, but which
101have been routed to individual POPs- typically /24, /23, /22</td>
102
103</tr><tr class="color1">
104<td>Master block</td><td>Our allocations from ARIN</td>
105</tr>
106
107</table>
108
109</body></html>
Note: See TracBrowser for help on using the repository browser.