IPv6 Request Form for Internet Exchange Points Timothy Lowe Nurani Nimpuno Sabrina Waschke Document ID: ripe-224 Date: 15 August 2001 Contents Overview Request Form Templates Overview This document contains the set of templates to be used when submitting an "IPv6 Request Form for Internet Exchange Points". Please submit the form via e-mail to "hostmaster@ripe.net". Warning: Requests sent to the RIPE NCC that lack a proper Registry Identifier (X-NCC-RegID) will be returned to the sender. Please include the Registry Identifier in the header of the message or at the top of this form. Further, any modifications to the templates may result in a delay in handling. X-NCC-RegID: Please enter your Registry ID here. #[OVERVIEW OF ORGANISATION TEMPLATE]# Please enter a short description of the organisation requesting the IPv6 address space. This should include an extract from the organisation's corporate documentation that confirms that the purpose of the organisation is to facilitate the exchange of Internet traffic between Internet Service Providers. It is required that the organisation has a clear and open membership policy. Therefore, please include the joining requirements as stated in the organisation's membership agreement. #[REQUESTER TEMPLATE]# Please enter the name of the person at your Local Internet Registry (LIR) who is submitting this request. name: organisation: country: phone: fax-no: e-mail: #[USER TEMPLATE]# Please enter the name of the IPv6 contact at your LIR (i.e., the person actually planning and setting up the network), if different from above. name: organisation: country: phone: fax-no: e-mail: #[MEMBER PEERING INFORMATION TEMPLATE]# a.) Please include a list of current members, including their Autonomous System numbers and/or a URL where this information is clearly visible. If the list is long, please include it as an attachment, preferably as a MIME attachment in PostScript file format. b.) The requesting organisation must have at least three members with BGP peering relationships in the default-free zone. By default-free zone, we mean receiving the full Internet routing table separately from neighbouring Autonomous Systems. The RIPE NCC will check the information in the RIPE Database, and expects it to be up-to-date. Please list and give the contact information of the three members and their Autonomous System numbers referred to above. Organisation, AS number, and e-mail address of contacts: 1. 2. 3. If possible, please list the URL of a "looking glass" where we can verify this information: The RIPE NCC may also verify the information by contacting the mentioned peers for their confirmation. #[CURRENT ADDRESS SPACE USAGE TEMPLATE]# In this section, please show how the organisation is using all IPv4 and IPv6 address space that has been assigned to it in the past, and what its future plans are for that space. Do not include information for address space being requested. Include an entry for each physically separate subnet in the network. Subnets are considered to be physically separate if there is an IP router between them. +-------------+----------------------------------+---------------+ | Address | Addresses Used | | | range |------------+----------+----------| Description | | | Current | 1 yr | 2 yr | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ #[ADDRESSING PLAN]# Please show an addressing plan of the organisation's intended IPv6 infrastructure. Include an entry for each physically separate subnet in the network. If you have an existing IPv4 network and expect to convert parts or all of the network into IPv6, you can show it here as well. +-------------+----------------------------------+---------------+ | Relative | When Used | | | |------------+----------+----------| Description | | Prefix # | Immediate | 1 yr | 2 yr | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ Explanation: An IPv6 addressing plan is somewhat different from an IPv4 addressing plan. The relative prefix should show the slash notation of the subnet size (for example, /64). The Immediate, 1 year, and 2 years fields should include an "x" in one of the three columns, depending on when the addresses will be used. For example: +-------------+----------------------------------+---------------+ | Relative | When Used | | | |------------+----------+----------| Description | | Prefix # | Immediate | 1 yr | 2 yr | | +-------------+------------+----------+----------+---------------+ | | | | |Neutral Peering| | /64 | x | | | Mesh | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ | | | | | | | | | | | | +-------------+------------+----------+----------+---------------+ #[NETWORK TEMPLATE]# inet6num: netname: descr: descr: country: admin-c: tech-c: mnt-by: RIPE-NCC-HM-MNT mnt-lower: notify: changed: source: RIPE #[TEMPLATES END]#