![]() |
![]() |
You're here: Home » Resource services |
Sub-allocation templateThe sub-allocation template is used to provide information about existing and planned network of the customer to which your organisation wishes to sub-allocate address space to. Attributes in assignment template:Network name (netname)The network name (netname) should be a short, but meaningful name for this network. It is used mainly for administrative purposes such as consistency checking. Please use a name that identifies the network and relates to the organisation that is requesting the address space. The network name should be a single word of less than 25 capital alphanumeric characters. Example: netname: GLOBALNET Description of customer organisation (descr)The description of customer organisation (descr) should be a brief description of the organisation that will be sub-allocated the address space for further distribution by the organisation to end sites. This attribute should include the location of the organisation and enough detail to distinguish it from other organisations. This attribute should not be used to contain any advertising information. Please limit the descr attribute to no more than five lines. Example: descr: Globalnet Inc. descr: Software Company descr: Kuala Lumpur ISO 3166 code (country)The country attribute should contain the most appropriate two-letter ISO 3166 code for the organisation that will use the address space. In cases where more than one country or economy may be appropriate, please use the ISO 3166 code for the country or economy where the administrative contact is located. Example: country: MY Requested address space (prefix)The requested address space (prefix) attribute should indicate the total amount of IPv4 address space you believe would be appropriate to sub-allocate to this customer. Express this using an address prefix. Example: prefix: /23 Future network plan (network-plan)The network-plan attribute summarises how the customer you plan to sub-allocate address space to will use the space within the next year. You must provide a detailed network plan for each subnet in the following format (using multiple lines as necessary): network-plan: <address-prefix> <now/6mo/1yr> <remark>
Example: network-plan: 0.0.0.0/28 /29,/29,/28 application servers network-plan: 0.0.0.16/28 /29,/28,/28 admin/accounting department network-plan: 0.0.0.32/27 /28,/27,/27 network management/data center network-plan: 0.0.0.64/26 /27,/27,/26 Research and Development Network network-plan: 0.0.0.128/25 /29,/28,/26 120 internal dial-up ports network-plan: 0.0.1.0/24 /27,/25,/24 Virtual Private Network Customer's assignments to end sites (sub-alloc-cust-network)If the customer has received previous sub-allocations, please specify all assignments the customer has made from the sub-allocated address ranges. Please use the following format (using multiple lines as necessary): sub-alloc-cust-network: <address> <prefix-size> <netname>
Example: sub-alloc-cust-network: 202.12.28.0/29 FOO-AP sub-alloc-cust-network: 202.12.28.8/27 BAR-AP Infrastructure of network receiving the sub-allocation (sub-alloc-infrastructure)If the customer has received previous address space, please specify the address prefixes used for the infrastructure of the customer network receiving the sub-allocation. Note: do not specify the infrastructure of the end-site networks assigned space from the sub-allocation. Please use the following format (using multiple lines as necessary): sub-alloc-infrastructure: <address> <prefix-size> <remark>
Example: sub-alloc-infrastructure: 202.12.28.0/27 server farm sub-alloc-infrastructure: 202.12.28.32/27 admin department sub-alloc-infrastructure: 202.12.28.64/26 60 dial-up ports Top | Guide to the APNIC Second Opinion Request Form (text version) Home | MyAPNIC | Info & FAQ | Services | Training | Meetings | Membership | Policy | Internet community | Search Last modified Friday, 01-Jul-2005 12:18:23 EST | © 1999 - 2009 APNIC Pty. Ltd. Contact us | Privacy statement | RSS ![]() |