Changeset 344

Timestamp:

10/06/06 12:15:33 (18 years ago)

Author:

Kris Deugau

Message:

/trunk

Backport changes to alloctypes.html from /branches/stable r270 and r332

File:

• trunk/alloctypes.html (modified) (3 diffs)

trunk/alloctypes.html

@@ -14 +14 @@
 <tr class="color1">
 <td>Customer netblock (default)</td><td>A direct allocation /30 or larger to a
-customer.  Note that this does NOT include RADIUS-routed "netblocks".</td>
+customer.  Note that this does NOT include RADIUS-routed "netblocks".  Internal systems
+should use the "End-use netblock" type.</td>
 </tr>
 
@@ -67 +68 @@
 </tr><tr class="color2">
 <td>Dynamic WiFi block</td><td>Netblock for (mostly residential) (mostly) PPPoE wireless.</td>
+</tr><tr class="color1">
+<td>Dynamic VoIP block</td><td>Netblock for DHCP-assigned VoIP services.</td>
 
+</tr><tr class="color2">
+<td>Static IP - LAN/POP</td><td>A single IP address from a designated pool for our
+internal LANs - either at a single POP or for a VPN.</td>
 </tr><tr class="color1">
+<td>Static pool - LAN/POP</td><td>A pool of IP addresses available for one-by-one
+assignment to our internal LAN systems or VPNs.</td>
+
+</tr><tr class="color2">
 <td>Reserve for WAN blocks</td><td>Reserve a chunk of IP space for core routers/etc.</td>
-</tr><tr class="color2">
+</tr><tr class="color1">
 <td>Reserve for dynamic-route DSL netblocks</td><td>Reserve a chunk of IP space for
 RADIUS-assigned "netblocks" from a PPPoE pool.  Note that this is similar to the static DSL
 pool, but IP space is to be allocated as /30 and larger netblocks, not single static IPs.</td>
+</tr><tr class="color2">
+<td>Reserve for ATM</td><td>Reserve a chunk of IP space for allocation to customers on ATM</td>
 </tr><tr class="color1">
 <td>WAN block</td><td>Individual netblock assignment for a core router.  Always taken from a
@@ -79 +91 @@
 </tr><tr class="color2">
 <td>Dynamic-route DSL netblock</td><td>Customer assignment for a RADIUS-assigned PPPoE
-"netblock".</td>
+"netblock".  Always taken from a block which has previously been reserved for such
+assignments.</td>
+</tr><tr class="color1">
+<td>ATM block</td><td>Customer assignment for a customer on ATM.  Always taken from a
+block which has previously been reserved for such assignments.</td>
 
-</tr><tr class="color1">
+</tr><tr class="color2">
 <td>Routing</td><td>Blocks not actually assigned to a service on their own, but which
 have been routed to individual POPs- typically /24, /23, /22</td>
 
-</tr><tr class="color2">
+</tr><tr class="color1">
 <td>Master block</td><td>Our allocations from ARIN</td>
 </tr>