RIPE NCC

Doc-ID: RIPE-309
Date: 26 April 2004

% IPv6 Internet Exchange Points Assignment Request Form

#[GENERAL INFORMATION]#
request-type: ipv6-for-ixp
form-version: 1.1
x-ncc-regid: 

#[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 (ISPs).
%
% 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.
org-description:

#[REQUESTER TEMPLATE]#
%
% Please enter the details of the person at your Local 
% Internet Registry (LIR) who is submitting this request.
name: 
phone: 
fax-no: 
e-mail: 
nic-hdl:

#[USER TEMPLATE]#
%
% Please enter the name of the IPv6 contact (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
% AS Numbers and/or a URL where this information is clearly 
% visible. If the list is long, please include it as a MIME 
% attachment in PostScript file format. If you include an 
% attachment please state "Yes" in the "member-peering-attached" 
% field below.
member-peering-attached:
member-peering-list:

%
% b.) The requesting organisation must have at least three
% members with AS Numbers. The RIPE NCC will check the 
% registration of the AS Numbers in the appropriate 
% database and expect it to be up-to-date.
% Please list below the contact information of the three
% members and their AS Numbers referred to above.
organisation-1:
as-number-1:
e-mail-1:

organisation-2:
as-number-2:
e-mail-2:

organisation-3:
as-number-3:
e-mail-3:

%
% If possible, please list the URL of a "looking glass" where 
% we can verify this information:
looking-glass:

%
% The RIPE NCC may also verify the information by contacting 
% the mentioned peers.

#[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 and 
% future plans for the 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.
%
%                         Prefix Length Used
%       Actual Prefix      Current   1 yr   2 yr   Purpose
subnet:


#[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 detail it here.
% 
%       Prefix      When Used
%       Length      Immediate   1 yr    2 yr  Purpose
subnet: 


%
% Explanation: The prefix length should show the slash
% notation of the subnet size (for example, /64).
% The Immediate, 1 yr, and 2 yr fields should include an "x" 
% in one of the three columns, depending on when the addresses 
% will be used. For the other columns, a dash "-" must be used.
%
% For example:
%
%         Prefix      When Used
%         Length      Immediate   1 yr    2 yr  Purpose
% subnet: /64         -           x       x     Neutral Peering Mesh

#[DATABASE TEMPLATE(S)]#
%
% Please include the template below so that the Hostmaster
% can register the assignment in the RIPE Database.
% Please complete a maintainer template if you do not
% have a maintainer already leaving a blank line between the
% two templates.

inet6num:  
netname:   *specify a netname here*
descr:     *specify the name of the IXP's organisation*
country:   *specify the country code*
org:       *specify org ID here*
admin-c:   *insert nic-handle of administrative contact*
tech-c:    *insert nic-handle of technical contact*
status:    ASSIGNED
mnt-by:    RIPE-NCC-HM-PI-MNT
mnt-by:    *specify mntner here*
mnt-lower: RIPE-NCC-HM-PI-MNT
mnt-domains: *specify mntner name here*
changed:   hostmaster@ripe.net
source:    RIPE 


#[INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add any supplementary information that you think 
% may facilitate the evaluation of this request below.

#[END of REQUEST]#