------------------------------------------------------------------- APNIC Document identity Title: APNIC Confederation Internet Address Request Form Short title: confed-address-request Document ref: APNIC-063 Version: 001 Date of original publication: 20 July 1997 Date of this version: 20 July 1997 Review scheduled: n/a Obsoletes: APNIC-043 Status: Obsolete Comments: Obsoleted by APNIC-075 -------------------------------------------------------------------- APNIC Confederation Internet Address Request Form Issued: July 20, 1997 Expires: December 31, 1997* *) This form is valid until superseded by another form. After the date specified, please check the APNIC document store located at ftp://ftp.apnic.net/apnic/docs for a later version of this form. This form is intended for use by organizations representing confederations of service providers. If you are requesting address space as an individual service provider, please use the "APNIC Internet Service Provider Internet Address Request Form" (see ftp://ftp.apnic.net/apnic/docs/isp-address-request). If you are an end user, please use the "APNIC End User Internet Address Request Form" (see ftp://ftp.apnic.net/apnic/docs/end-user-address-request). Only APNIC recognized confederations should use this form. For details on how to become an APNIC recognized confederation, please see "APNIC Confederation Concepts and Requirements" available from the following URL: ftp://ftp.apnic.net/apnic/docs/confed-requirements. 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: confed-request@rs.apnic.net or in type written English via fax (discouraged) to: +81-3-5500-0481 or in type written English via postal mail (as a last resort) to: Asia Pacific Network Information Center Tokyo Central Post Office Box 351 Tokyo, 100-91, Japan 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 +81-3-5500-0480. 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. - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - #[NETWORK TEMPLATE V:4.0]# netname: descr: descr: country: admin-c: tech-c: 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 #[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:2.0]# acct-name: member: member: reserved: reserved: allocation: allocation: assignment: assignment: cust-network: cust-network: #[TEMPLATES END]# Additional Comments: - - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - - - 1.0 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 to whois.apnic.net and via WAIS to wais.apnic.net (database APNIC). 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, 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.0 Confederation Internet Address Request Network Template Details ------------------------------------------------------------------- NETNAME: Please complete with an appropriate name which is short and meaningful for your 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 do NOT use punctuation, special characters or a prefix or suffix of 'NET', 'LAN', etc (unless they are part of your company name). It is recommended you use a network name that relates to the organization the network is being assigned to. 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 organization, including the locatio providing sufficient detail as to distinguish your organization from others in the APNIC database, i.e., "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 country code (ISO 3166) which is appropriate for the confederation requesting address space. Do NOT provide the country name or three letter ISO 3166 country code. Please see the table of ISO 3166 codes maintained on APNIC at ftp://ftp.apnic.net/apnic/docs/iso-3166.txt if you do not know the appropriate ISO 3166 code for your country. 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 permited. Example: country: JP ADMIN-C: Please provide the NIC handle of the person who is the administrative contact for the confederation or the name of the person matching *EXACTLY* the name to provided in a subsequent PERSON template if you do not have a NIC handle. The NIC handle (if known) is greatly preferred and will result in minimal delays when processing your request. If you specify a name instead of a NIC Handle, please do NOT use titles like `Dr' or `Prof.' or `Sir' as the words which comprise a name are indexed and there are many people with the same titles. Further, please provide full given names, not initials as single characters are not indexed within the database and do not add periods between the names or initials. Please list the name as you 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). At least one ADMIN-C tag is required for all NETWORK templates. Example: admin-c: JD1-AP admin-c: John E Doe TECH-C: Please provide the NIC handle of the person who is the technical contact for the confederation or the name of the person matching *EXACTLY* the name to be provided in a subsequent PERSON template if you do not have a NIC handle. The NIC handle (if known) is greatly preferred and will result in minimal delays when processing your request. The technical contact is the person who is responsible for the day-to-day operation of the confederation. If you specify a name instead of a NIC Handle, please do NOT use titles like `Dr' or `Prof.' or `Sir' as the words which comprise a name are indexed and there are many people with the same titles. Further, please provide full given names, not initials as single characters are not indexed within the database and do not add periods between the names or initials. Please list the name as you 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). At least one TECH-C tag is required for all NETWORK templates. Example: tech-c: MS4-AP tech-c: Mark A Smith 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 950101 CHANGED: Please indicate the e-mail address of the person who is completing the template, followed by the current date in the format of YYMMDD (YY is the the current year, MM is the month and DD is the day, all values 0 filled). If you do not have e-mail connectivity please leave blank and it will be filled in for you. Do not put "Please Assign" or similar for this field. If you have an e-mail address, you should supply exactly one CHANGED tag per NETWORK template if this is an application for a new provider block. 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 NETWORK template, however each maintainer object specified must already exist in the APNIC Registration database. Example: mnt-by: MAINT-FOO-AP SOURCE: Source of the information. For the purposes of APNIC forms, it will always be APNIC. This is information which is always required in the database, so it has been added to the forms already. Example: source: APNIC 3.0 Confederation Internet Address Request Person Template Details ------------------------------------------------------------------ PERSON: Please give the full name of the person this template will represent. If you have provided in the person's name in a contact field of another template (e.g., the ADMIN-C or TECH-C fields of the NETWORK template), the names MUST be written identically to those provided in the fields. Please do not use formal titles like `Dr' or `Prof.' or `Sir' as the words which comprise a name is indexed and there are many people with the same titles. Further, as single characters are not indexed, please provide the full given name. Please do not add periods between the names or initials and list the name as you 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 using one line for each part of the address as shown below. 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 country code (ISO 3166) which is appropriate for the contact person. Do NOT provide the country name or the three letter ISO 3166 country code. Please see the table of ISO 3166 codes maintained on APNIC at ftp://ftp.apnic.net/apnic/docs/iso-3166.txt if you do not know the appropriate ISO 3166 code for this person's address. This tag is required for all PERSON templates, with only one COUNTRY tag permited. Example: country: JP PHONE: Please provide the work telephone number of the person specified above 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 their 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: +81-20-1233-4676 phone: +81-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 your country. Please do not include the leading zero when specifying their 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: +81-20-1233-4678 E-MAIL: Please supply the electronic mail address for the person. The electronic mail address MUST be an Internet reachable valid RFC-822 address with a fully qualified domain name. If you do not have Internet reachable e-mail connectivity, please leave this field blank. 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 identifer 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. APNIC will provide you with one or you can reserve one for yourself using the procedures described in the "APNIC Registry Database Record Addition, Modification, and Deletion Instructions" document found at ftp://ftp.apnic.net/apnic/docs/database-update-info If you have an APNIC NIC handle, but do not remember it, please make a note of this in the ADDITIONAL COMMENTS section of the application form. 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. If you do not have a NIC handle, please leave the field blank -- do NOT put 'Please Assign' or similar for this field. 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 YYMMDD (YY is the current year, MM is the month and DD is the day, all values 0 filled). If you do not have e-mail connectivity please leave blank and it will be filled in for you. Do not put "Please Assign" or similar for this field. If you have an e-mail address, you should supply exactly one CHANGED tag per PERSON template if this is a new person object. Example: changed: johndoe@terabit.na 960501 MNT-BY: Please provide the appropriate 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 NETWORK template, however each maintainer object specified must already exist in the APNIC Registration database. Example: mnt-by: MAINT-FOO-AP SOURCE: Source of the information. For the purposes of APNIC forms, it will always be APNIC. This is information which is always required in the database, so it has been added to the forms already. Example: source: APNIC 4.0 Confederation Internet Address Request Technical Details ------------------------------------------------------------ ACCT-NAME: Please provide your APNIC account name if you have one. 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 Note that applications without account name will NOT be processed. Example: acct-name: APNIC-AP MEMBER: Please provide the names of the member ISPs of your confederation, one per line in the following format: member: member-name date member-organization where: member-name - the unique internal name you have assigned to this member using the same format as NETNAME described above. Note: the MEMBER-NAME must NOT contain spaces. date - the date the member joined your confederation in YYMMDD format, where YY is the last two digits of the year, MM is the (zero-filled) month, and DD is the (zero-filled) day member-organization - the official organization name of the member, e.g., the name it was incorporated under Please list all members, not just the new members which have joined your confederation since the last address request. The member-name must be unique within your confederation and will be used to determine which blocks have been allocated to which member. The member-organization should be the official name of the member organization, e.g., the name under which it was incorporated (if applicable) and may be specified in free text. You may use as many lines as necessary to fully list all ISPs your confederation serves. Example: member: FREDNET 970101 Fred's Network Services, Inc. member: NETSRUS 970202 Networks 'R' Us, Ltd. member: INETISWE 970303 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: reserved: member-name prefix/length expires 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 in YYYYMMDD format where YYYY is the full year (including the first two digits of the year), MM is the (zero-filled) month and DD is the (zero-filled) day. Since it is possible for an expiration to occur after 1999, please specify the full year, not just the last two digits. Note that allocations (as described by the ALLOCATION field) 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 organizations 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: allocation: member-name pre/len 0s/1s/sub/super/port date where: member-name - the name of the member as described in the MEMBER fields described above. pre - the unique prefix of the assigned network len - the length of the unique prefix 0s - the organization supports all zeros subnets, 'Y' for yes, 'N' for no. 1s - the organization supports all ones subnets, 'Y' for yes, 'N' for no. sub - the organization supports subnetting, 'Y' for yes, 'N' for no. super - the organization supports supernetting, 'Y' for yes, 'N' for no. port - addresses have been assigned as portable (e.g., the customer does not need to return the addresses should they change service providers). date - the date the assignment occurred in YYMMDD format It is very important that this field be specified correctly as APNIC bases future allocations on past assignment history. The information conveyed in the ALLOCATION fields allow APNIC to establish your address assignment patterns. Please make ABSOLUTELY SURE the member-name portion of the ALLOCATION field corresponds *EXACTLY* with the 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 a non-CIDR fashion (e.g., there 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 960501 allocation: BAR-AP 202.12.28.128/25 Y/Y/Y/Y/N 960515 ASSIGNMENT: The ASSIGNMENT field provides a summary of the delegation information for assignments (e.g., sub-delegations to non-service providers) the confederation has made to member organizations 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 re-assignment information for those networks in the following format: assignment: netname prefix/length h0/h1/h2 s0/s1/s2 0s/1s/sub/super date where: netname - the name you assigned as found in the APNIC database prefix - the unique prefix of the assigned network length - the length of the unique prefix h0 - the estimated number of devices initially h1 - the estimated number of devices after one year h2 - the estimated number of devices after two years s0 - the estimated number of subnets initially s1 - the estimated number of subnets after one year s2 - the estimated number of subnets after two years 0s - the organization supports all zeros subnets, 'Y' for yes, 'N' for no. 1s - the organization supports all ones subnets, 'Y' for yes, 'N' for no. sub - the organization supports subnetting, 'Y' for yes, 'N' for no. super - the organization supports supernetting, 'Y' for yes, 'N' for no. date - the date the assignment occurred in YYMMDD format It is very important that this field be specified correctly as APNIC bases future allocations on past assignment history. The information conveyed in the ASSIGNMENT fields allow APNIC to establish your address assignment patterns. Please make ABSOLUTELY SURE the netname portion of the ASSIGNMENT field corresponds *EXACTLY* with the netname field of the reassignment in the APNIC database. Failure to do so will result in APNIC assuming the network indicated has NOT been reassigned. Please use as many ASSIGNMENT fields as necessary to describe ALL networks which you have delegated using APNIC allocated addresses. If you have delegated a network in a non-CIDR fashion (e.g., there is no single prefix/length pair which can describe the network), please submit multiple ASSIGNMENT fields which describe the delegation in CIDR fashion, repeating the netname as necessary. Example: assignment: FOO-AP 202.12.28.0/25 10/15/80 1/1/2 Y/Y/Y/Y 960501 assignment: BAR-AP 202.12.28.128/25 60/70/100 2/3/4 Y/Y/Y/Y 960515 CUST-NETWORK: The CUST-NETWORK field provides a summary of the assignment information MEMBER ORGANIZATIONS have made to their customers in the past in order for APNIC to verify the member organizations are assigning address space appropriately. 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: cust-network: netname address mask hinit/h6mo/h1yr sinit/s6mo/s1yr date where: netname - the name the confederation member assigned as found in the APNIC database (note: this name is of the member's choosing, but should relate to the organization the network is assigned to) address - the starting address of the assigned network mask - the subnet mask of assigned network in dotted decimal format, e.g. 255.255.248.0 hinit - the estimated number of devices initially h6mo - the estimated number of devices after six months h1yr - the estimated number of devices after one year sinit - the estimated number of subnets initially s6mo - the estimated number of subnets after six months s1yr - the estimated number of subnets after one year date - the date the assignment occurred in YYMMDD format 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 allow APNIC to establish the confederation member's address assignment patterns. Please make ABSOLUTELY SURE the netname portion of the CUST-NETWORK field corresponds *EXACLY* with the NETNAME field of the reassignment in the APNIC 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 which the confederation member(s) have assigned using APNIC allocated addresses. If you have assigned a network in a non-CIDR fashion (e.g., there is no single subnet mask which can describe the subnet), 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 960501 cust-network: BAR-AP 202.12.28.128 255.255.255.128 60/70/100 2/3/4 960515 ADDITIONAL COMMENTS: This section is for you to provide whatever other details you feel may help justify your request. 5.0 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 service providers within a country and APNIC. These confederations, in many cases refered to as national Internet registries, 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, than 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 organization can 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 organizations applying directly to APNIC for address space. However, in order to keep the documentation requirements to a reasonable level, APNIC requests summary information only. The IANA or APNIC may, at their option, spot-check specific organizations 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 organizations. 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 organization should obtain addresses from their provider if at all possible. 6.0 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 960501 mnt-by: MAINT-APNIC-AP source: APNIC #[PERSON TEMPLATE V:4.0]# person: David R Conrad address: Asia Pacific Network Information Center address: Tokyo Central Post Office Box 351 address: Tokyo 100-91 country: JP phone: +81-3-5500-0480 fax-no: +81-3-5500-0481 e-mail: davidc@apnic.net nic-hdl: DC1-AP changed: davidc@apnic.net 960401 mnt-by: MAINT-APNIC-AP source: APNIC #[PERSON TEMPLATE V:4.0]# person: Yoshiko O Chong Fong address: Asia Pacific Network Information Center address: Tokyo Central Post Office Box 351 address: Tokyo 100-91 country: JP phone: +81-3-5500-0480 fax-no: +81-3-5500-0481 e-mail: yoshiko@apnic.net nic-hdl: YF1-AP changed: davidc@apnic.net 960401 mnt-by: MAINT-APNIC-AP source: APNIC #[CONFEDERATION TECHNICAL TEMPLATE V:3.0]# acct-name: APNIC-AP member: FREDNET 970101 Fred's Network Services, Inc. member: NETSRUS 970202 Networks 'R' Us, Ltd. member: INETISWE 970303 Internet is We, Pte. reserved: FREDNET 223.128.0.0/19 19980101 reserved: NETSRUS 223.128.32.0/19 19980101 allocation: FREDNET 223.128.0.0/22 Y/Y/Y/Y/N 960501 allocation: NETSRUS 223.128.32.0/22 Y/Y/Y/Y/N 960502 assignment: INETISWE 223.128.64.0/18 2000/8000/34000 10/30/105 Y/Y/Y/Y 960503 cust-network: FOO-AP 223.128.28.0 255.255.255.128 10/15/80 1/1/2 960301 cust-network: BAR-AP 223.128.28.128 255.255.255.128 60/70/100 2/3/4 960315 #[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.0 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. Rekhter, 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. Rekhter, "CIDR and Classful 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. Rekhter, "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. Rekhter, 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. Rekhter, 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 APNIC-061 APNIC Staff, "Internet Service Provider Internet Address Request Form", 7/20/96 URL: ftp://ftp.apnic.net/apnic/docs/apnic-061.txt APNIC-062 APNIC Staff, "Enterprise Internet Address Request Form", 7/20/96 URL: ftp://ftp.apnic.net/apnic/docs/apnic-062.txt 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 (usally 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. Organizations 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.0 Acknowledgements -------------------- This document in derived in large part from documents written by the staff of the European Registry, RIPE-NCC .