Supporting Notes for the Anycast Assignment Request Form


RIPE NCC 

Document-ID: ripe-391
Date: September 2006



This document contains instructions for LIRs on how to complete the 
Anycast Assignment Request Form http://www.ripe.net/ripe/docs/anycast-request.html.

The instructions are based on the IPv4 Address Allocation and Assignment Policy for 
the RIPE region http://www.ripe.net/ripe/docs/ipv4-policies.html, 
the IPv6 Address Allocation and Assignment Policy http://www.ripe.net/ripe/docs/ipv6policy.html 
and also on RFC3258 http://www.ietf.org/rfc/rfc3258.txt. 


General Information
Address Space User
Initial Information
Anycast Node Plan
Network Description
Network Diagram
Database Template(s)
End of Request


General Information

#[GENERAL INFORMATION]#
%
% Please add your RegID.

request-type: anycast-assignment
form-version: 1.0
x-ncc-regid: nl.bluelight

Please do not change the value of the request-type: and form-version: fields.

Enter your Registry Identifier (RegID) in the x-ncc-regid: field. 
RegIDs have the following format:  <country code>.<name>. 
If you do not know your RegID, please contact <ncc@ripe.net>. 


Address Space User

#[ADDRESS SPACE USER]#
%
% Which TLD operator will use the requested address space?

legal-organisation-name: North Santa NIC 
tld(s): com biz nn
organisation-location: Santa City, NN
website-if-available: http://www.ns-nic.nn

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

space-available: No

 % Will the End User return any address space?

address-space-returned: 

Enter the legal name of the organisation that will use the anycast assignment 
in the legal-organisation-name: field and list all of their TLDs 
(Top-Level Domains) in the tld(s): field.

Enter the primary location of the organisation in the 
organisation-location: field and, if they have a website, 
enter the URL in the website-if-available: field.

If the End User already has address space in use for anycast, 
list this in the space-available: field.

If there is any address space assigned to the End User that they will return, 
list each prefix in separate address-space-returned: fields. 
The expected time for renumbering is three months. Y
ou can use the following syntax: 
<x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field.

 
Initial Information

#[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: Yes

% Can the End Users 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: No

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

ip-version: Both

% 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: Yes

The End User must read the IPv4 Address Allocation and Assignment Policies
and/or the IPv6 Address Allocation and Assignment Policy, and in particular
the sections that refer to anycast assignments. Enter yes in the confirmation: 
field if the End User agrees to follow these policies.

You must check if the End User needs to use anycast technology in order to pass
the IANA Administrative Procedure for Name Server Delegation and Glue Data. 
If they can do this without using an anycast assignment, 
enter yes in the iana-procedure:" field.

We need to know whether the End User would like us (RIPE NCC) to make an IPv4 
assignment or an IPv6 assignment. If they need both, enter 
Both in the ip-version: field and make any additional comments 
in the Network Description section.

If the End User is requesting an IPv4 assignment, please check 
that their TLD nameserver set conforms to the practices outlined in RFC3258.

 
Anycast Node Plan

#[ANYCAST NODE PLAN]#
%
% Which anycast nodes will be used?
%
%		Node Name		Peers			Location

node:		Z-root Santa		see Network Descr.	Santa City IX
node:		Z-root Rudolf		see Network Descr.	Rudolf Town IX
node:

number-of-nodes: 2

The Anycast Node Plan shows how the End User will use 
the requested address space.

You can repeat the node row as many times as needed. 
Delete any empty node: fields before you send the request.

In the Node Name column, enter the name of each node.

In the Peers column, enter the AS Numbers of the peers for each node.

In the Location column, enter the primary location of the node.

If needed, you can write more detailed descriptions of 
any of the fields in the Network Description section.


Network Description

#[NETWORK DESCRIPTION]#

% Please add more information if you think it will help us understand
% this request.

We plan to provide anycasting from Santa City and Rudolf Town. 
The peers at Santa City IX are listed at http://www.scix.nn/peers 
and the peers at Rudolf Town IX are listed at http://www.rtix.nn/peers.
 
You can use this space for additional information that you think will 
be helpful for us when we evaluate your request. 
A clearer understanding of the End Users addressing needs 
can help us to evaluate your request more quickly.


Network Diagram

#[NETWORK DIAGRAM]#

% Have you attached a network diagram to this request? (Yes/No)

diagram-attached: Yes

A network diagram (topology map) can also help us to 
understand the End Users addressing needs.

Database Template(s)

#[DATABASE TEMPLATES]#

% IPv4
% Please complete all of the fields below.

inetnum:	<leave empty>
netname:	NS-NIC
descr:	North Santa NIC
country:	NN
org:		ORG-NSN3000-RIPE
admin-c:	HOHO1-RIPE
tech-c:	HOHO1-RIPE
status:	ASSIGNED ANYCAST
mnt-by:	RIPE-NCC-HM-MNT
mnt-lower:	RIPE-NCC-HM-MNT
mnt-by:	SANTA-MNT
mnt-routes:	SANTA-MNT
mnt-domains:SANTA-MNT
changed:	hostmaster@ripe.net
source:	RIPE

% IPv6
% Please complete all of the fields below.

inet6num:	<leave empty>
netname:	NS-NIC
descr:	North Santa NIC
country:	NN
org:		ORG-NSN3000-RIPE
admin-c:	HOHO1-RIPE
tech-c:	HOHO1-RIPE
status:	ASSIGNED ANYCAST
mnt-by:	RIPE-NCC-HM-MNT
mnt-lower:	RIPE-NCC-HM-MNT
mnt-by:	SANTA-MNT
mnt-routes:	SANTA-MNT
mnt-domains:SANTA-MNT
changed:	hostmaster@ripe.net
source:	RIPE

If the End User is requesting an IPv4 assignment and an IPv6 assignment, 
please complete both templates. You can repeat each template as many times as needed.

Leave the inetnum:/inet6num: field empty as we will choose the address range.

The netname: should be a short and descriptive name for the network 
and should reflect the organisation name of the End User. 

Enter the End Users legal organisation name in the descr: field.

Use the ISO country code of the End Users location in the country: field. 
If the End User is multi-national, repeat the country: field as many times as needed.

Enter the org-ID of the End Users organisation object in the org: field.
If they dont have an organisation object, you can create one for 
them using the LIR Portal (https://lirportal.ripe.net).

The nic-handle of the role or person object in the admin-c: field 
should reflect someone who is administratively responsible for the network.

The nic-handle of the role or person object in the tech-c: field 
should reflect someone who has technical knowledge of the network.

The status: field must be ASSIGNED ANYCAST.

The mnt-by: and mnt-lower: fields must contain RIPE-NCC-HM-MNT.

The second mnt-by: field shows which maintainer authenticates object updates. 
The mnt-routes: and mnt-domains: fields show which maintainers 
authenticate the creation of route and domain objects.

The RIPE Database must contain all of the objects that you use.

The changed: field must be hostmaster@ripe.net.

The source: field must be RIPE.


End of Request

#[END of REQUEST]#

Best Regards,
Jan Janssen, Bluelight Admin

Please write your full name below the #[END of REQUEST]# header.
