------------------------------------------------------------------- APNIC Document identity Title: APNIC Confederation Internet Address Request Form Short title: confed-address-request Document ref: APNIC-075 Version: 003 Date of original publication: August 1998 Date of this version: 11 February 2002 Review scheduled: n/a Obsoletes: APNIC-063 Status: Obsolete Comments: n/a -------------------------------------------------------------------- APNIC Confederation Internet Address Request Form This form is intended for use by organisations representing confederations of service providers who are requesting address space for their member(s). If you are requesting address space as an individual service provider, please use the "APNIC IPv4 ISP Address Request Form". See: ftp://ftp.apnic.net/apnic/docs/isp-address-request If you are seeking address space under APNIC's small mulithoming assignment policy, then use the "Small Mulithoming Assignment Request Form", at: ftp://ftp.apnic.net/apnic/docs/small-multihoming-request If you are seeking address space for the transit LAN of an Internet Exchange Point, then use the "Internet Exchange Point Address Request Form", at: ftp://ftp.apnic.net/apnic/docs/ixp-assign-request If you are seeking an IPv6 allocation, then use the "IPv6 Sub-TLA Request Form" (web only), at: http://www.apnic.net/apnic-bin/ipv6-subtla-request.pl Only APNIC recognised confederations should use this form. For details on how to become an APNIC recognised confederation, please see "APNIC Confederation Concepts and Requirements" available from the following URL: ftp://ftp.apnic.net/apnic/docs/confed-requirements These documents are currently undergoing typographical review. Please see comments at the bottom of this form regarding how to complete this application. Note that this form is parsed by machine and modification of lines starting with #[ or the field names will likely result in strange errors being returned to you and your request not being processed. After completing this form, please submit it via email to: hostmaster@apnic.net or in type written English via fax (discouraged) to: 7-3858-3199 or in type written English via postal mail (as a last resort) to: Asia Pacific Network Information Center Level 1, 33 Park Road P. O. Box 2131 Milton, QLD 4064 Australia If you have any questions regarding this form, you may contact us via email at hostmaster@apnic.net (preferred), fax at the above number, postal mail at the above address or via telephone at 7-3858-3100 between 9:00 AM to 5:00 PM Australian Eastern Standard Time. Note that we do not accept address requests via telephone. Please allow up to one week for processing electronic mail requests and up to one month for other forms of submission. NOTE: PLEASE DO NOT INCLUDE THIS HEADER NOR THE INSTRUCTIONS AT THE BOTTOM OF THIS FORM WITH YOUR APPLICATION. - - - - - - - - - - - - - FORM STARTS - - - - - - - - - - - - - - - #[NETWORK TEMPLATE V:4.0]# netname: descr: descr: country: admin-c: tech-c: remarks: changed: mnt-by: APNIC-HM mnt-lower: source: APNIC #[PERSON TEMPLATE V:4.0]# person: address: address: country: phone: fax-no: e-mail: nic-hdl: remarks: changed: mnt-by: source: APNIC #[PERSON TEMPLATE V:4.0]# person: address: address: country: phone: fax-no: e-mail: nic-hdl: remarks: changed: mnt-by: source: APNIC #[CONFEDERATION TECHNICAL TEMPLATE V:3.0]# acct-name: confed-alloc-sum: member: member: reserved: reserved: allocation: allocation: mem-requirement: cust-network: cust-network: #[TEMPLATES END]# Additional Comments: - - - - - - - - - - - - - END OF FORM - - - - - - - - - - - - - - - 1. Instructions for completing this form _____________________________________________________________________ Below are the instructions for filling in an APNIC Confederation IP Address Request Form. It is *EXTREMELY* important you provide attributes for the tags listed below correctly. Failure to do so WILL result in delays in service and thus may delay when you will receive the IP addresses you require. Information provided in the "confederation technical template" will be kept in strict confidence, thus security reasons are not sufficient to leave fields blank. For further clarification on this issue, please contact hostmaster@apnic.net. Information provided in the "network" and "person" templates will be made available over the Internet via WHOIS and other mechanisms. This information is provided to the Internet community to aid in diagnosing and resolving issues related to the operation of the Internet. Any use outside of this context is expressly prohibited without written permission from APNIC Pty Ltd. As APNIC applications are machine processed, application forms *MUST* be submitted in plain ASCII, do not use MIME encoding unless that MIME encoding can be viewed without any form of decoding. In particular, do NOT encode your application using BASE64 encoding techniques. In addition, do not attempt to format your application in any fashion, e.g., do not justify text or insert extra blank lines between lines in a template. Failure to observe these restrictions will likely result in syntax errors being returned to you as the automated parsing system is not prepared to handle large deviations from the format presented in the form above. An example of a completed form is provided below. As always, if you have any questions or comments regarding this form, please contact hostmaster@apnic.net at your convenience. 2. Network template details _____________________________________________________________________ netname ------- Please provide a short but meaningfully descriptive name for this network. The "netname" is used mainly for administrative purposes such as consistency checking of the Internet Registry. The network name should be written as a SINGLE word of less than 25 capital alphanumeric characters ONLY. Please use a network name that relates to the member of the confederation for which the network is being requested. Please do NOT use domain names, such as FOO.COM, as the network name has no relation with the domain name system. There should be exactly one "netname" tag per "network" template. Example: netname: TBIT descr ----- Please complete with a short description of the organisation including the location to provide sufficient detail to distinguish your organisation from others in the APNIC Whois Database. For example, "descr: Computer Center" is not sufficient. Do NOT put advertising information such as 'The best ISP confederation in Foo' in your description and please limit the number of "descr" lines to 5. This tag is required for all "network" templates. Example: descr: Bunch 'O ISPs, Ltd. descr: 102-04 South Road, Suite 406 descr: Northtown country ------- Please give the two letter ISO 3166 country code appropriate for the confederation requesting address space. Do NOT provide the country name or three letter ISO 3166 country code. If you do not know the appropriate ISO 3166 code for your country, please see the table of ISO 3166 codes maintained on APNIC at: ftp://ftp.apnic.net/apnic/docs/iso-3166.txt We are aware listing a country may be ambiguous for confederations crossing national boundaries, so choose the most appropriate country based on the location of the administrative contact. This tag is required for all "network" templates, with only one "country" tag permitted per template. Example: country: JP admin-c ------- Please provide the APNIC NIC-handle (NIC-handles from other registries are not accepted) of the person who is the administrative contact for the confederation. If you do not have an APNIC NIC-handle, please see the section below entitled "Obtaining an APNIC NIC-handle". The administrative contact must be someone who is physically located at the site of the confederation and at least one "admin-c" tag is required for all "network" templates. Example: admin-c: JD1-AP tech-c ------ Please provide the APNIC NIC-handle (NIC-handles from other registries are not accepted) of the person who is the technical contact for the confederation. If you do not have an APNIC NIC-handle, please see the section below titled "Obtaining an APNIC NIC-handle". The technical contact need not be physically located at the site of the confederation, but rather is the person who is responsible for the confederation's day-to-day operation. At least one "tech-c" tag is required for all "network" templates. Example: tech-c: MS4-AP remarks ------ The "remarks" attribute contains any remarks about this address space that cannot be expressed in any of the other attributes. Although multiple lines are allowed, it should be only be used if it provides extra information to users of the database and usage should be kept to a minimum. Example: remarks: will be returned to NIC 19950101 changed ------- Please indicate the e-mail address of the person who is completing the template, followed by the current date in the format of YYYYMMDD (YYYY is the current year, MM is the month and DD is the day, all values 0 filled). You should supply exactly one "changed" tag per "network" template. Example: changed: johndoe@terabit.na 19950225 mnt-by ------ The highest level of authorisation control for updating an object protected by the "mnt-by" field. For the purposes of APNIC forms, it will always be APNIC. This information is always required in the database and has already been added to the forms. Example: mnt-by: APNIC-HM mnt-lower --------- A maintainer object is a database object used to authorise updates to the APNIC database. If your database details are protected by "mnt-lower", then only persons with access to the security information of that maintainer object will be able to change details. You must create a maintainer object to prevent unauthorised creation of assignment objects within your IP address range. To create a maintainer object, go to the APNIC Maintainer Object Request form at: ftp://ftp.apnic.net/apnic/docs/maintainer-request If you do not have a maintainer ID, you may either leave this field blank and a default maintainer ID will be created for you (one without any authentication protection) You should enter the maintainer in the "mnt-lower" field in the correct maintainer object format. There can be zero or more "mnt-by" tags per "network" template, however each maintainer object specified must already exist in the APNIC Whois Database. Example: mnt-lower: MAINT-AP-SPARKY source ------ Source of the information. For the purposes of APNIC forms, it will always be APNIC. This information is always required in the database and has already been added to the forms. Example: source: APNIC 3. Person template details ----------------------------------------------------------------- The fields of the "person" template(s) should only be filled in when an APNIC NIC-handle is being requested or when the contact information for an existing "person" object must be modified. If the administrative and technical contacts already have APNIC NIC-handles, please use them instead of requesting new APNIC NIC-handles. person ------ Please give the full name of the person this template will represent. Do not use formal titles like 'Dr' or 'Prof.' or 'Sir' and please provide full names, not initials. The name should be provided as the person would be addressed in a letter salutation (e.g., given name followed by family name or family name followed by given name depending on the custom in your country). There can be exactly one "person" field in a "person" template. Example: person: John E Doe address ------- Please complete with the full postal address written as you would for international postal mail (albeit without the country which is provided using the "country" field described below) using one line for each part of the address. Example: address: Bunch O' ISPs, Ltd. address: Industrial Estate North address: North Perpendicular Road 12 address: NL-1234 Northtown country ------- Please give the two letter ISO 3166 country code appropriate for the contact person. Do NOT provide the country name or the three letter ISO 3166 country code. If you do not know the appropriate ISO 3166 code for this person's address, please see the list of ISO 3166 codes maintained on APNIC at: ftp://ftp.apnic.net/apnic/docs/iso-3166.txt This tag is required for all "person" templates, with only one "country" tag permitted. Example: country: JP phone ----- Please provide the work telephone number of the person specified in this template as it would be dialed internationally in your country (WITHOUT the prefix necessary to reach an international line). Please do not include the leading zero when specifying the area/city code unless it is required to correctly dial the number internationally. The format for the telephone number is: --- If an extension is necessary, please add "ext ". Please do not put 'x' or other abbreviations for "extension". More than one telephone number is fine; each telephone number should be put on a separate line and written in order of the most appropriate number for the person to the least. Example: phone: 20-1233-4676 phone: 20-1233-4677 ext 4711 fax-no ------ Please complete with the facsimile number of the person as it would be dialed internationally (WITHOUT the prefix necessary to reach an international line) in the country. Please do not include the leading zero when specifying the area/city code unless it is required to correctly dial the number internationally. The format for the facsimile number is: --- More than one facsimile number is fine. Each facsimile number should be put on a separate line and written in order of the most appropriate to the least. If the person does not have a facsimile number, please leave blank. Example: fax-no: 20-1233-4678 e-mail ------ Please supply the electronic mail address for the person. The electronic mail address MUST be a valid Internet reachable RFC-822 address with a fully qualified domain name. Multiple e-mail addresses may be specified, with each on a separate line and written in order of the most appropriate to the least. Example: e-mail: johndoe@terabit.na nic-hdl ------- A NIC-handle is a unique identifier used within the Internet registry database to differentiate between people with the same names. NIC-handles are assigned by registries -- if you do not have one, please do not make one up, a handle will be automatically generated for you if you follow the procedures described below in the section entitled "Obtaining an APNIC NIC-handle". If you have an APNIC NIC-handle but do not remember it, please make a note of this in the "additiona comments" section of the application form and leave this field blank. If you have a NIC-handle assigned by another registry, e.g., InterNIC, please provide a full person template anyway and leave the "nic-hdl" field blank -- the regional registries are currently investigating ways in which information such as this can be shared, but no solution has yet been implemented. Example: nic-hdl: JD401-AP remarks ------- The remarks attribute contains any remarks about this person that cannot be expressed in any of the other attributes. Although multiple lines are allowed, it should be only be used if it provides extra information to users of the database, and usage should be kept to a minimum. Example: remarks: pager can be accessed by -pager changed ------- Please indicate the e-mail address of the person who is completing the template followed by the current date in the format of YYYYMMDD (YYYY is the current year, MM is the month and DD is the day, all values 0 filled). You should supply exactly one "changed" tag per "person" template if this is a new person object. Example: changed: johndoe@terabit.na 950225 mnt-by ------ Please provide the APNIC allocated maintainer ID. The maintainer ID provides some level of authorization control over who can update an object protected by a "mnt-by" field. If you do not have a maintainer ID, you may either leave this field blank and a default maintainer ID will be created for you (one without any authentication protection) or you may apply for one using the APNIC Maintainer Object Request Form found at: ftp://ftp.apnic.net/apnic/docs/maintainer-request There can be zero or more MNT-BY tags per request template, however each maintainer object specified must already exist in the APNIC Whois Database. Example: mnt-by: MAINT-FOO-AP source ------ Source of the information. For the purposes of APNIC forms, it will always be APNIC. This information is always required in the database and has already been added to the forms. Example: source: APNIC 4. Confederation technical template details _____________________________________________________________________ This section provides the information necessary to justify your request. As such, the information contained herein is considered strictly confidential And will not be entered into any publicly accessible database. acct-name --------- Please provide your APNIC account name. If you do not have an APNIC account name, please see the APNIC Membership Application available from: ftp://ftp.apnic.net/apnic/docs/membership-application The APNIC Confederation Agreement is available at: ftp://ftp.apnic.net/apnic/docs/confed-agreement Please note that applications without an account name will NOT be processed. Example: acct-name: APNIC-CONFED-AP confed-alloc-sum ---------------- Please provide a summary of all the allocations that your organisation has received from APNIC in the following format:
<%allocated> <%reserved> Where: address prefix - Prefix of address ranges that have been allocated to the confederation. %allocated - Percentage of the IP allocated from the block. %reserved - Percentage of IP reserved for members. date - The date the allocation has been received. Example: 2xx.xxx.xxx/12 92% 2% 19990120 2xx.xxx.xxx/13 75% 3% 20001128 2xx.xxx.xxx/13 68% 1% 20010217 2xx.xxx.xxx/14 90% 4% 20010217 member ------ Please provide the names of the member ISPs of your confederation, one per line in the following format: Where: member-name - Each "member-name" must be unique within your confederation and will be used to determine which blocks have been allocated to which member. Note: the "member-name" must NOT contain spaces. date - The date the member joined your confederation in the format: YYYYMMDD where YYYY is the year, MM is the (zero-filled) month, and DD is the (zero-filled) day. member-org - The "member-org" should be the official name of the member organisation, for example, the name under which it was incorporated (if applicable) and may be specified in free text. Please list all members, not just the new members which have joined your confederation since the last address request. You may use as many "member" lines as necessary to fully list all ISPs your confederation serves. Example: member: FREDNET 19970101 Fred's Network Services, Inc. member: NETSRUS 19970202 Networks 'R' Us, Ltd. member: INETISWE 19970303 Internet is We, Pte. reserved -------- The "reserved" field provides information on blocks you have reserved for service providers in accordance with the slow- start allocation procedures. If you have not been delegated networks in the past, please leave this field blank. If networks have been delegated to you, you must provide the reserved block information for those networks in the following format: Where: member-name - The name of the member as described in the "member" fields described above. prefix - The unique prefix of the reserved network. length - The length of the unique prefix. expires - The date the reservation expires if not consumed. Use the format: YYYYMMDD where YYYY is the year, MM is the (zero-filled) month, and DD is the (zero-filled) day. Note that allocations, shown by the "allocation" field described below, should come from "reserved" blocks. Example: reserved: FOO-AP 223.128.0.0/19 19980101 reserved: BAR-AP 223.128.32.0/19 20010101 reserved: BOO-AP 223.128.64.0/18 20010101 reserved: GOO-AP 223.128.128.0/17 19990101 allocation ---------- The "allocation" field provides a summary of the delegation information for allocations the confederation has made to its member organisations in the past. If you have not been delegated networks in the past, please leave this field blank. If networks have been delegated to you, you MUST provide the allocation information for those networks in the following format: 
 <0s/1s/sub/super/port>   

    Where:

        mem-name - The name of the member as provided in the
                   "member" fields described above.

        pre      - The unique prefix of the assigned network.

        len      - The length of the unique prefix.

        0s       - Indicate whether the organisation supports 
                   all zeros subnets. 'Y' for yes, 'N' for no.

        1s       - Indicate whether the organisation supports 
                   all ones subnets. 'Y' for yes, 'N' for no.

        sub      - Indicate whether the organisation supports
                   subnetting. 'Y' for yes, 'N' for no.

        super    - Indicate whether the organisation supports 
                   supernetting, 'Y' for yes, 'N' for no.

        date     - The date the allocation occurred. Use 
                   YYYYMMDD format

        aw       - The assignment window of the member when
                   the block was allocated 

    It is very important that the "allocation" field be specified
    correctly as APNIC bases future allocations on past allocations
    history. The information conveyed in the "allocation" fields
    allows APNIC to establish your address allocation patterns.

    Please make ABSOLUTELY SURE the member-name portion of the 
    "allocation" field corresponds EXACTLY with the member-name
    of the appropriate "member" field. Please use as many
    "allocation" fields as necessary to describe ALL networks which
    you have delegated using APNIC allocated addresses. 

    If you have delegated a network in non-CIDR fashion (that is, no
    single prefix/length pair which can describe the network),
    please submit multiple "allocation" fields which describe the
    delegation in CIDR fashion, repeating the member-name as
    necessary.

    Example:

        allocation: FOO-AP 202.12.28.0/25 Y/Y/Y/Y/N 19960501 16 
        allocation: BAR-AP 202.12.28.128/25 Y/Y/Y/Y/N 19960515 64


mem-requirement
---------------

    Please provide an estimate of IP requirement for members that
    will require additional IP address for the next 6 months. Use
    the format:

          

    Where:

        prefix      - An estimated of the size of address this
                      particular member will require.

        member-name - The name of the member.
 


cust-network
------------

    The "cust-network" field provides a summary of the assignment
    information that a MEMBER ORGANISATION (NOT the confederation)
    has made to the MEMBER ORGANISATION's customers. 

    When a confederation has insufficient space to satisfy a
    particular member's address space needs, the confederation
    should request additional space. In order for APNIC to verify
    the member organisations are assigning address space
    appropriately, the confederation must collect and submit the
    MEMBER ORGANISATION's assignment information using the 
    "cust-network" field. 

    If confederation members have not been allocated networks in
    the past, please leave this field blank.

    If networks have been assigned by confederation members to
    customers, you MUST provide the re-assignment information for
    those networks in the following format: 

         
   
         

    Where:

        netname - The name the confederation member assigned as
                  shown in the APNIC Whois Database Note: this
                  name is of the member's choosing, but should
                  relate to the organisation the network is
                  assigned to by the member.

        address - The starting address of the assigned network.

        mask    - The subnet mask of assigned network in dotted
                  decimal format. Example:

                      255.255.248.0

        hinit   - The estimated number of devices initially.

        h6mo    - The estimated number of devices after 6 months.

	h1yr    - The estimated number of devices after one year.

        sinit   - The estimated number of subnets initially.

        s6mo    - The estimated number of subnets after 6 months.

	s1yr    - The estimated number of subnets after one year.

        date    - The date the assignment occurred in the
                  format YYYYMMDD. 

    It is VERY important that this field be specified correctly as
    APNIC bases future allocations on past assignment history. The
    information conveyed in the "cust-network" fields allows APNIC
    to establish the confederation member's address assignment
    patterns.

    Please make ABSOLUTELY SURE the netname portion of the 
    "cust-network" field corresponds EXACTLY with the NETNAME field
    of the reassignment in the APNIC Whois Database. Failure to do
    so will result in APNIC assuming the network indicated has NOT
    been reassigned.

    Please use as many "cust-network" fields as necessary to describe
    ALL customer networks assigned by the confederation member for the
    last confederation allocation block. 

    If the confederation member has assigned networks in non-CIDR
    fashion (that is, no single prefix/length pair which can describe
    the network), please submit multiple "cust-network" fields which
    describe the assignment in CIDR fashion, repeating the network
    name as necessary.

    Example:

  cust-network: FOO-AP 202.12.28.0   255.255.255.128 10/15/80  1/1/2 19960501
  cust-network: BAR-AP 202.12.28.128 255.255.255.128 60/70/100 2/3/4 19960515



Additional comments
-------------------

    This section is for you to provide whatever other details you
    feel may help justify your request.




5.  Supporting notes for confederations requesting address space
_____________________________________________________________________


The Internet registry system is hierarchical in nature, with the IANA
at the root of the hierarchy, the regional registries next, Internet
service provider and confederations of those providers below the
regional registries, and end users at the leaves of the tree.  Within
the Asia and Pacific Rim regions, APNIC uses the concept of
"confederations of ISPs" to act as intermediaries between groups of
service providers and APNIC.  These confederations, in many cases
referred to as national Internet registries or national NICs, can
provide enhanced services for service providers and end users in their
service area by providing local language support and knowledge of
local laws, customs, and situations.

It must be noted however that ISPs and end users are not required to
obtain address space from a confederation, regardless of whether the
confederation acts as a national Internet registry or not.  Any
organisation may approach APNIC directly and, assuming requests are
justified, obtain the required Internet addresses.

As per accepted Internet policy, APNIC is required to request from
confederations the same information we would request from
organisations applying directly to APNIC for address space.  However,
in order to keep the documentation requirements to a reasonable level,
APNIC requests summary information only except for the member whose
Request triggered the need for additional addresses.  The IANA or
APNIC may, at their option, spot-check specific organisations if
summary information looks out of the ordinary thus confederations
should maintain the same sort of information APNIC requires when they
sub-delegate addresses to members of their confederation.  This
information includes network engineering plans (topology diagrams,
subnetting plans, etc.), deployment plans, and any other information
which may provide justification for a particular allocation or
assignment.


5.1 Confederations and address assignments
------------------------------------------

APNIC strongly recommends against the assignment of addresses to
non-ISP organisations.  Assignment of such address space must, by
definition, be portable, thus routing entries must be created globally
if that address space is to be routed on the Internet.  As Internet
service providers are taking steps to limit the number of prefixes
entered into their routing tables, it is possible that any portable
address space assigned by a confederation will get filtered out of
specific Internet service providers' routers.

APNIC encourages all confederations to forward any portable assignment
requests to APNIC.  APNIC will allocate such requests from a block
reserved for portable assignments.  As with all portable assignments,
APNIC will explicitly state that routability of the assigned addresses
is no way insured and that the organisation should obtain addresses
from their provider if at all possible.




6.  Application example
_____________________________________________________________________


#[NETWORK TEMPLATE V:4.0]#

netname:        EXAMPLE-AP
descr:          An example of a completed confederation application
descr:          form.  Please don't send this verbatim to APNIC
country:        JP
admin-c:        DC1-AP
tech-c:         YF1-AP
changed:        davidc@apnic.net 19960501
mnt-by:         APNIC-HM
mnt-lower:	MAINT-AP-APNIC
source: APNIC

#[PERSON TEMPLATE V:4.0]#

person:         David R Conrad
address:        Asia Pacific Network Information Center
address:        Level 1, 33 Park Road
address:        Milton, QLD 4064
country:        AU
phone:          7-3367-0490
fax-no:         7-3367-0482
e-mail:         davidc@apnic.net
nic-hdl:        DC1-AP
changed:        davidc@apnic.net 19960401
mnt-by:         MAINT-APNIC-AP
source: APNIC

#[PERSON TEMPLATE V:4.0]#

person:         Yoshiko O Chong Fong
address:        Asia Pacific Network Information Center
address:        Level 1, 33 Park Road
address:        Milton, QLD 4064
country:        AU
phone:          7-3367-0490
fax-no:         7-3367-0482
e-mail:         yoshiko@apnic.net
nic-hdl:        YF1-AP
changed:        davidc@apnic.net 19960401
mnt-by:         MAINT-APNIC-AP
source: APNIC

#[CONFEDERATION TECHNICAL TEMPLATE V:3.0]#

acct-name: APNIC-AP
confed-alloc-sum: 202.10.0.0/14 82% 3% 19980223
confed-alloc-sum: 203.20.0.0/13 90% 2% 19990112
confed-alloc-sum: 210.220.0.0/12 93% 1% 19991102
confed-alloc-sum: 211.110.0.0/13 80% 4% 20000320
member: FREDNET 19970101 Fred's Network Services, Inc.
member: NETSRUS 19970202 Networks 'R' Us, Ltd.
member: INETISWE 19970303 Internet is We, Pte.
reserved: FREDNET 211.31.128.0/19 20020612 
reserved: INETISWE 211.32.159.0/20 20020323
reserved: ONENET 211.32.224.0/18 20020112 
reserved: CABLENET 210.10.0.0/20 20011203
allocation: FREDNET 202.128.0.0/22 Y/Y/Y/Y/N 19960501
allocation: NETSRUS 202.128.32.0/22 Y/Y/Y/Y/N 19960502
mem-requirement: 0.0.0.0/16 ComputerTech
mem-requirement: 0.1.0.0/16 Online ISP
mem-requirement: 0.2.0.0/17 ABC Internet
mem-requirement: 0.2.128.0/18 Cablenet
mem-requirement: 0.2.191.0/19 Top ISP
mem-requirement: 0.2.224.0/19 EduSystem
cust-network: FOO-AP 202.128.28.0 255.255.255.128 10/15/80 1/1/2 19960301
cust-network: BAR-AP 202.128.28.128 255.255.255.128 60/70/100 2/3/4 19960315



#[TEMPLATES END]#

Additional Comments:

A national network will begin initial deployment within the next 6
months.  It is expected this network will interconnect every city in
the country with a high speed infrastructure, thereby bringing
Internet connectivity to everyone.




- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


7.  Recommended reading
_____________________________________________________________________

RFC 1466  E. Gerich, "Guidelines for Management of IP Address Space",
          5/26/93, URL: ftp://ftp.apnic.net/ietf/rfc/rfc1466.txt

RFC 1517  R. Hinden, "Applicability Statement for the Implementation of
          Classless Inter-Domain Routing (CIDR), 9/24/93, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1517.txt

RFC 1518  Y. Rehkter, T. Li, "An Architecture for IP Address Allocation
          with CIDR", 9/24/93, URL: 
          ftp://ftp.apnic.net/ietf/rfc/rfc1518.txt

RFC 1519  V. Fuller, T. Li, J. Yu, K. Varadhan, "Classless Inter-Domain
          Routing (CIDR): an Address Assignment and Aggregation  
          Strategy", 9/24/93, URL: 
          ftp://ftp.apnic.net/ietf/rfc/rfc1519.txt

RFC 1744  G. Huston, "Observations on the Management of the Internet
          Address Space", 12/23/94, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1744.txt

RFC 1814  E. Gerich, "Unique Addresses are Good", 6/22/95, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1814.txt

RFC 1817  Y. Rehkter, "CIDR and Classfull Routing", 8/4/95, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1817.txt

RFC 1879  B. Manning, "Class A Subnet Experiment Results and  
          Recommendations", 1/15/96, URL: 
          ftp://ftp.apnic.net/ietf/rfc/rfc1879.txt

RFC 1878  T. Pummill, B. Manning, "Variable Length Subnet Table For
          IPv4", 12/26/95, URL:                 
          ftp://ftp.apnic.net/ietf/rfc/rfc1878.txt

RFC 1900  B. Carpenter, Y. Rehkter, "Renumbering Needs Work", 2/28/96,
          URL: ftp://ftp.apnic.net/ietf/rfc/rfc1900.txt

RFC 1916  H. Berkowitz, P. Ferguson, W. Leland, P. Nesser, 
          "Enterprise  Renumbering: Experience and Information 
          Solicitation", 2/28/96, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1916.txt

RFC 1917  P. Nesser, "An Appeal to the Internet Community to Return
          Unused IP Networks (Prefixes) to the IANA", 2/29/96, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc1917.txt
        
RFC 1918  Y. Rehkter, R. Moskowitz, D. Karrenberg, G. de Groot, E.
          Lear, "Address Allocation for Private Internets", 2/29/96,
          URL: ftp://ftp.apnic.net/ietf/rfc/rfc1918.txt

RFC 2008  Y. Rehkter, T. Li, "Implications of Various Address
          Allocation Policies for Internet Routing", 10/14/96, URL:
          ftp://ftp.apnic.net/ietf/rfc/rfc2008.txt

RFC 2036  G. Huston, "Observations on the use of Components of the
          Class A Address Space within the Internet, 10/30/96,
          URL: ftp://ftp.apnic.net/ietf/rfc/rfc2036.txt

RFC 2050  K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel,
          "Internet Registry IP Allocation Guidelines", 11/6/96,
          URL: ftp://ftp.apnic.net/ietf/rfc/rfc2050.txt

isp-addresss-request APNIC Staff, "IPv4 ISP Address Request Form",
          1/12/2001, URL: 
          ftp://ftp.apnic.net/apnic/docs/isp-address-request
 
small-multihoming-request APNIC Staff, "Small Mulithoming Assignment
           Request Form", 1/12/2001, URL:
           ftp://ftp.apnic.net/apnic/docs/small-multihoming-request

ixp-assign-request APNIC Staff, "Internet Exchange Point Address 
           Request Form", 1/12/2001, URL:
           ftp://ftp.apnic.net/apnic/docs/ixp-assign-request

confed-agreement APNIC Staff, "Confederation Agreement", 7/25/98 URL:
           ftp://ftp.apnic.net/apnic/docs/confed-agreement

confed-requirements APNIC Staff, "Confederation Concepts and
           Requirements", 7/25/98 URL:
           ftp://ftp.apnic.net/apnic/docs/confed-requirements

These documents are all available from the APNIC document store in the
directories mentioned in the URLs.  The APNIC document store can be
accessed in a number of ways:

1. via anonymous FTP from host ftp.apnic.net

   Using your ftp application (usually called simply 'ftp'), connect to
   host ftp.apnic.net using your email address as the password.
   For RFCs, use the "change directory" command (typically 'cd') to
   '/ietf/rfc'.  For APNIC documents, 'cd' to '/apnic/docs'.  You
   may then use the "get" command (typically 'get') to retrieve the
   file.

2. via electronic mail through the APNIC FTP Email gateway

   You may send mail to 'ftpmail@postoffice.apnic.net' with the body
   of the message being standard Unix 'ftp' commands.  For more help,
   send an email message to 'ftpmail@postoffice.apnic.net' with a
   message body consisting of 'help'.  Results will be mailed back to
   you.

Organisations without connectivity wishing to obtain copies of the
"Recommended Reading" articles should contact the APNIC or their local
or national registry to arrange postal delivery of one or more of the
above documents.  Note that some fee may be associated with the
delivery of hardcopy versions of documents.

8.  Acknowledgements
_____________________________________________________________________

This document in derived in large part from documents written by the
staff of the European Registry, RIPE-NCC .