Obsolete: Anycast Assignment Request Form

This document is now obsolete. See ripe-473

RIPE NCC

Document ID: ripe-458
Date: February 2009
Obsoletes: ripe-390

------------------------88----------------------

% Anycast Assignment Request Form
 
% RIPE NCC members (LIRs) and Direct Assignment Users can use this form
% to request an anycast assignment. Please see 
% Supporting Notes for the Anycast Assignment Request Form 
% for instructions on how to complete this form.
% http://www.ripe.net/ripe/docs/anycast-request-support.html
%
% Please note that the End User should have a signed "End User 
% Assignment Agreement" with either the sponsoring LIR or the RIPE NCC.
 
#[GENERAL INFORMATION]#
%
% Please add your RegID.

request-type: anycast-assignment
form-version: 1.1
x-ncc-regid: 
 
#[ADDRESS SPACE USER]#
%
% Is this request being sent by a sponsoring LIR on behalf of an 
% End User? (Yes/No)

end-user-of-sponsoring-lir: 

% If yes, please confirm that the "End User Assignment Agreement" 
% contains all of the elements listed in paragraph 2.0 of 
% "Contractual Requirements for Provider Independent Resource Holders 
% in the RIPE NCC Service Region".(Yes/No)

confirmation:

%
% Which TLD operator will use the requested address space?

legal-organisation-name: 
tld(s): 
organisation-location: 
website-if-available: 

% Does this End User already have address space in use for
% anycast? (Yes/No)

space-available: 

 % Will the End User return any address space?

address-space-returned: 

#[INITIAL INFORMATION]#

% Does the End User accept the policies on anycast assignments?
% http://www.ripe.net/ripe/docs/ipv4-policies.html
% http://www.ripe.net/ripe/docs/ipv6policy.html (Yes/No)

confirmation: 

% Can the End User's TLD nameserver set pass the "IANA 
% Administrative Procedure for Root Zone Name Server Delegation
% and Glue Data" without using anycast technology? 
% http://www.iana.org/procedures/delegation-data.html (Yes/No)

iana-procedure: 

% Is the End User requesting an IPv4 assignment, an IPv6 
% assignment, or both? (IPv4/IPv6/Both)

ip-version: 

% If the End User is requesting an IPv4 assignment, will the TLD 
% nameserver set apply anycasting as described in RFC3258?
% http://www.ietf.org/rfc/rfc3258.txt (Yes/No)

rfc3258: 

#[ANYCAST NODE PLAN]#
%
% Which anycast nodes will be used?

      	Node Name       Peers     Location    

node: 
node: 
node: 

number-of-nodes: 

#[NETWORK DESCRIPTION]#
%
% Please add more information if you think it will help us understand
% this request.

<add more information>


#[SUPPORTING DOCUMENTATION]#
%
% If this request being sent by a sponsoring LIR on behalf of an 
% End User, please attach a copy of the signed "End User 
% Assignment Agreement" and the company registration papers of the 
% End User.
% You can also attach a network diagram or other supporting documentation.
%
% Have you attached any files/documents to this request? (Yes/No)

file-attached:


#[DATABASE TEMPLATE(S)]#
%	
% IPv4
% Please complete all of the fields below. 

inetnum:	<leave empty>
netname:	<add netname>
descr:		<add End User organisation name>
country:	<add country code>
org:		<add org-ID>
admin-c:	<add nic-handle of administrative contact>
tech-c:		<add nic-handle of technical contact>
status:		ASSIGNED ANYCAST
mnt-by:	        RIPE-NCC-END-MNT
mnt-lower:	RIPE-NCC-END-MNT
mnt-by:	        <add mntner name>
mnt-routes:	<add mntner name>
mnt-domains:	<add mntner name>
changed:	hostmaster@ripe.net
source:		RIPE
 
% IPv6
% Please complete all of the fields below. 

inet6num:	<leave empty>
netname:	<add netname>
descr:		<add End User organisation name>
country:	<add country code>
org:		<add org-ID>
admin-c:	<add nic-handle of administrative contact>
tech-c:		<add nic-handle of technical contact>
status:		ASSIGNED ANYCAST
mnt-by:	        RIPE-NCC-END-MNT
mnt-lower:	RIPE-NCC-END-MNT
mnt-by:	        <add mntner name>
mnt-routes:	<add mntner name>
mnt-domains:	<add mntner name>
changed:  	hostmaster@ripe.net
source:		RIPE

#[END of REQUEST]#