[4] | 1 | <html><head>
|
---|
| 2 |
|
---|
| 3 | <title>IP Database</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
---|
| 4 |
|
---|
[10] | 5 | <link rel="stylesheet" type="text/css" href="/ip/ipdb.css">
|
---|
[4] | 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" width=630>
|
---|
| 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 customer.</td>
|
---|
| 16 | </tr>
|
---|
| 17 |
|
---|
| 18 | <tr class="color2">
|
---|
| 19 | <td>Customer static IP - Cable</td><td>A single IP address from a designated pool
|
---|
| 20 | on the cable network.</td>
|
---|
| 21 | </tr><tr class="color1">
|
---|
| 22 | <td>Customer static IP - DSL</td><td>A single IP address from a designated pool
|
---|
| 23 | on the DSL network. Note that these are nominally in Sudbury, even if the customer
|
---|
| 24 | isn't.</td>
|
---|
| 25 | </tr><tr class="color2">
|
---|
| 26 | <td>IP from server pool</td><td>A single IP from a pool designated for servers</td>
|
---|
| 27 | </tr>
|
---|
| 28 |
|
---|
| 29 | <tr class="color1">
|
---|
| 30 | <td>Pool - Cable</td><td>A pool of IP addresses available for one-by-one assignment to
|
---|
| 31 | customers on cable.</td>
|
---|
| 32 | </tr><tr class="color2">
|
---|
| 33 | <td>Pool - DSL</td><td>A pool of IP addresses available for one-by-one assignment to
|
---|
[10] | 34 | customers on DSL. Note that individual IPs will be "assigned" to the customer's
|
---|
| 35 | city, but the pool they are a part of will normally be "assigned" to Sudbury or
|
---|
| 36 | North Bay.</td>
|
---|
[4] | 37 | </tr><tr class="color1">
|
---|
| 38 | <td>Pool - Servers</td><td>A pool of IP addresses available for one-by-one assignment to
|
---|
| 39 | servers in Sudbury.</td>
|
---|
| 40 | </tr>
|
---|
| 41 |
|
---|
| 42 | <tr class="color2">
|
---|
| 43 | <td>End-use netblock</td><td>A /30 or larger allocation for arbitrary services (LAN
|
---|
| 44 | management, servers we want fully subnet-isolated, etc)</td>
|
---|
| 45 |
|
---|
| 46 | </tr><tr class="color1">
|
---|
[10] | 47 | <td>Dialup netblock</td><td>Netblock assigned to one or more RAS units in a POP</td>
|
---|
[4] | 48 | </tr><tr class="color2">
|
---|
| 49 | <td>Dynamic DSL block</td><td>Netblock for (mostly residential) PPPoE DSL. Nominally
|
---|
| 50 | "assigned" to Sudbury</td>
|
---|
| 51 | </tr><tr class="color1">
|
---|
| 52 | <td>Dynamic cable block</td><td>Netblock for (mostly residential) DHCP cable.</td>
|
---|
| 53 |
|
---|
| 54 | </tr><tr class="color2">
|
---|
| 55 | <td>Routing</td><td>Blocks not actually assigned to a service on their own, but which
|
---|
| 56 | have been routed to individual POPs- typically /24, /23, /22</td>
|
---|
| 57 |
|
---|
| 58 | </tr><tr class="color1">
|
---|
| 59 | <td>Master block</td><td>Our allocations from ARIN</td>
|
---|
| 60 | </tr>
|
---|
| 61 |
|
---|
| 62 | </table>
|
---|
| 63 |
|
---|
| 64 | </body></html>
|
---|