____________________________________________________
IPv6 subTLA Request Form
(in the Bootstrap Stage)
K. Andresen P. Caslav P. Tate S. Waschke
Document ID: ripe-195
See also: ripe-196
Overview
This document contains the set of templates to be
used when submitting an IPv6 sub-TLA request. Please
submit the form via e-mail to "<hostmas-
ter@ripe.net>."
Warning: Requests that are sent to the RIPE NCC
which 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. Fur-
ther, any modifications to the templates may
result in a delay in handling.
____________________________________________________
ripe-195.txt Page 1
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
X-NCC-RegID:
#[ IPV6 SUBTLA REQUEST ]#
Section A (Administrative Information)
#[REGISTRY ID]#
Please enter your registry ID here.
#[OVERVIEW OF ORGANIZATION TEMPLATE]#
A short description of the organisation requesting
the IPv6 address space. Is this sub-TLA request for
the entire organisation or will other parts of the
organisation also be requesting a sub-TLA (perhaps
from the other Regional Registries)? Please note
that an LIR can only request a sub-TLA for them-
selves and not on behalf of another organisation.
#[REQUESTER TEMPLATE]#
Please enter the name of the person at your registry
who is filing this request.
name:
organisation:
country:
phone:
fax-no:
e-mail:
#[USER TEMPLATE]#
Please enter the name of the IPv6 contact at your
registry (the person actually planning and setting
up the network) if different from above.
name:
organisation:
country:
phone:
fax-no:
e-mail:
Section B (Criterion 1 & 2)
#[PEERING INFORMATION TEMPLATE]#
____________________________________________________
ripe-195.txt Page 2
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
The requesting organisation's network must have IPv4
BGP peering relationships with at least three other
public Autonomous Systems in the default-free zone.
By default-free zone, we mean that the organisation
is receiving the full Internet routing table sepa-
rately from 3 neighbouring ASes.
Please enter your AS number here:
aut-num:
The RIPE NCC will check the information in the
database, and expects to find up-to-date informa-
tion.
Please give contact information of 3 of the peers
mentioned in your aut-num template:
AS Number & e-mail address of contact
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 con-
tacting the mentioned peers for their confirmation.
#[Deployment Plan Template]#
The requesting organization must show that it plans
to provide production IPv6 service within 12 months
after receiving allocated address space. This must
be substantiated by such documents as an engineering
plan or a deployment plan.
Please answer as many of the questions below as pos-
sible. The more information, the faster we can eval-
uate the request.
1. Please give a general description of your IPv6
plans, including the services you will provide and
the types of customers you expect to have. Please
also give a general estimate of when parts of the
IPv6 network will be deployed.
In order to give us more information about the types
of services you will be offering (such as leased
line, dial-up, facilities management, multihoming,
web hosting, transit, etc..), please fill out the
table below along with a timeline of when these ser-
vices will be implemented and the locations.
____________________________________________________
ripe-195.txt Page 3
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
|--Service--|--Date--|--Location--|--Description--|
2. What kind of IPv6 connectivity will you (or do
you) have? Please explain how your network will be
connected to other IPv6 networks, this can include a
connection to 6REN, the 6Bone or other connections.
3. What kind of IPv6 equipment do you have (or plan
to have)? Please complete as much of the table below
as possible.
|Equipment|--------|Make &|---|Purchase|Install|
|--Type---|Quantity|Model-|URL|--Date--|-Date--|
4. #[IPv6 ADDRESSING PLAN]#
Please show an addressing plan of the registry's
planned IPv6 infrastructure. Include an entry for
each physically separate subnet in the network. If
you already have some future SLA/NLA customers lined
up, please include them here as well. We don't
expect you to show how you will use the entire sub-
TLA, only the addresses that you now have concrete
plans for. 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----|-----------|
|Prefix#-|Immediate|1yr|2yr|Description|
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, 1yr, 2yr
fields should include an "x" in the one of the three
columns depending on when the addresses will be put
into use (immediately, in 1 year, or in 2 years?)
For example:
|Relative|----When Used----|-----------|
|Prefix#-|Immediate|1yr|2yr|Description|
/64 x Web servers POP Amster-
dam
5. Have you publicised your IPv6 services to poten-
tial customers? (such as preparing a brochure,
sending out an e-mail with information, having a
web-site about IPv6 plans, etc..) If yes, please
____________________________________________________
ripe-195.txt Page 4
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
include a pointer (a URL) to where we can find pub-
lic information about your IPv6 plans, or for-
ward/fax us the information. This kind of informa-
tion is especially usefull if you do not yet have
IPv6 customers lined up since it shows the RIPE NCC
what you are doing to attract new customers.
6. Do you have a topology map of your planned (or
current) IPv6 network? If yes, please fax it to: +31
20 535 4445 with this request's ticket number in the
cover letter (or send is as a postscript attach-
ment).
Section C (Criterion 3 or 4)
Please fill in either the #[Transit Provider Tem-
plate]# or the #[6Bone Template]# below.
#[TRANSIT PROVIDER TEMPLATE]#
The requesting organization must be an IPv4 transit
provider and must show that it already has issued
IPv4 address space to 40 customer sites that can
meet the criteria for a /48 IPv6 assignment. In this
case, the organization must have an up-to-date rout-
ing policy registered in one of the databases of the
Internet Routing Registry, which the Regional IR may
verify by checking the routing table information on
one of the public looking glass sites).
Please list 40 of your IPv4 customers who can meet
the criteria for a /48 IPv6 assignment.
|--name of cust.--|-netname-|-IP address range-|
The RIPE NCC will verify this information in the
RIPE database and expects the assignments to be
entered correctly.
#[6BONE TEMPLATE]#
The requesting organization must demonstrate that it
has experience with IPv6 through active use of a
pseudo-TLA (pTLA) registered to it for at least six
months prior to requesting a sub-TLA. The regional
IRs may require documentation of acceptable 6Bone
routing policies and practice from the requesting
organization.
____________________________________________________
ripe-195.txt Page 5
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
Have you been a pTLA holder on the 6Bone for at
least 6 months? (If no, you need to fulfill the
criteria in the #[Transit Provider Template]# above
instead.)
Member since: (date of registration)
Length of time operating a pTLA: (in months)
6bone address allocation:
The RIPE NCC will check with the 6Bone IPv6 assign-
ment commitee whether they recommend this organisa-
tion for a sub-TLA.
List of NLA/SLAs you've given out on the 6Bone:
|-Company name-|--Address Range---|-NLA or SLA?-|
Section D (Database Information)
#[NETWORK TEMPLATE]#
inet6num:
netname:
descr:
descr:
country:
admin-c:
tech-c:
status:
mnt-by: RIPE-NCC-HM-MNT
mnt-lower:
notify:
changed:
source: RIPE
#[MNTNER TEMPLATE]#
It is highly recommended that the Registry puts
their mntner as mnt-lower for the sub-TLA block.
This will prevent any unauthorised people from
entering new inet6num objects within the Registry's
address range. If you already have a mntner object,
it is enough to reference it above, you do not need
to fill in this template (since the information is
in the database already).
mntner:
descr:
admin-c:
tech-c:
upd-to:
mnt-nfy:
auth:
____________________________________________________
ripe-195.txt Page 6
IPv6 subTLA Request Form (in the Bootstrap Stage)
____________________________________________________
remarks:
notify:
mnt-by:
changed:
source:
#[PERSON TEMPLATE]#
If the person(s) are already in the RIPE database,
you do not need to fill out person templates for
them here. It is enough to reference their nic-han-
dles in the inet6num object above.
person:
address:
address:
address:
e-mail:
phone:
fax-no:
mnt-by:
notify:
nic-hdl:
changed:
source: RIPE
#[TEMPLATES END]#
____________________________________________________
ripe-195.txt Page 7