Supporting Notes for the Initial IPv6 Allocation Request Form in the
RIPE NCC Service Region

   Leo Vegoda

   Document ID: ripe-248
   Date: 27June 2002
   Obsoletes: ripe-195
   See also: ripe-246, ripe-247
     _________________________________________________________________

Contents
        
     * Introduction
     * Supporting Notes for the Request Form Templates
     * Example of a Completed Initial IPv6 Allocation Request Form
     _________________________________________________________________

Introduction

This document contains the supporting notes for the set of
templates to be used when submitting an "Initial IPv6 Allocation
Request Form".

The set of clean templates provided in the RIPE document "Initial
IPv6 Allocation Request Form in the RIPE NCC Service Region" at:

http://www.ripe.net/ripe/docs/ipv6-initial.html

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. Additionally, modifying the templates is
likely to delay the request.

Supporting Notes for the Request Form Templates

X-NCC-RegID:

The Registry Identifier must be included in every message sent to
<hostmaster@ripe.net>. It is used to identify the Local Internet
Registry (LIR). More information about the Registry Identifier can
be found in the RIPE document "Guidelines for Setting Up a Local
Internet Registry at the RIPE NCC" at:

http://www.ripe.net/ripe/docs/new-lir.html

#[OVERVIEW OF ORGANISATION TEMPLATE]#

Q1: Please provide a short description of the organisation
requesting the IPv6 address space.

Q2: Is this IPv6 request for the entire organisation or will other
parts of the organisation also be requesting an allocation?

Q3: Will your organisation also be requesting (or do you already
have) an IPv6 allocation from another Regional Internet Registry
(RIR)?

Please note that an LIR can only request an allocation for itself
and not on behalf of another organisation.

#[REQUESTER TEMPLATE]#

name:
organisation:
country:
phone:
fax-no:
e-mail:
nic-hdl:

Please enter the details of the registered contact at your LIR
making the request.

#[IPv6 ALLOCATION USAGE PLAN]#

The requesting LIR must show that it plans to make 200 or more /48
assignments to End Users' sites within 24 months of receiving the
allocated IPv6 address space.

Please provide a plan showing how you intend to use the IPv6
allocation. In your diagram please describe any allocations you
intend to make and indicate where you expect to make /48
assignments to End Users.

Where an adequate explanation of the use of a segment cannot be
given in the table below please title each segment and provide a
detailed explanation below the table.


Prefix When Used
Length Immediate 1yr 2yr Description



It should also be noted that an LIR may assign a /48 per PoP as the
service infrastructure of an IPv6 service operator. Each assignment
to a PoP is regarded as a single assignment regardless of the
number of users connected to the PoP. A separate assignment can be
obtained for the in-house operations of the operator.


#[NETWORK TEMPLATE]#

inet6num:  *leave empty*
netname:   *leave empty*  
descr:     Provider Local Registry
descr:     Name of LIR's organisation
descr:     (You can add extra descriptive comments
descr:     in additional "descr:" attributes if
descr:     you want to do so.)
country:   *specify the country*
admin-c:   *insert nic-handle of administrative contact*
tech-c:    *insert nic-handle of technical contact*
status:    *This is generated by the database itself*
mnt-by:    RIPE-NCC-HM-MNT
mnt-lower: *specify LIR mntner name*
notify:    *specify e-mail address*
changed:   hostmaster@ripe.net
source:    RIPE 

Detailed information about the inet6num objects is available from
the RIPE Database using the link below:

http://www.ripe.net/perl/whois?-vinet6num 

The "inet6num:" attribute value (the IPv6 network prefix) should be
left blank. It will be chosen by the RIPE NCC from the available
IPv6 address space allocated to the RIPE NCC by the Internet
Assigned Numbers Authority (IANA).

The "netname:" will always be selected by the RIPE NCC. LIRs cannot
select their own netname for the inetnum describing their
allocation.  However, they must select their own netnames for any
assignments they register as inet6num objects in the RIPE Whois
Database.

The "descr:" attributes will always indicate that this network is
allocated to a Provider LIR. However, the LIR can add additional
"descr:" attributes that will be included in the object entered
into the RIPE Database.

The "country:" attribute describes the country or countries the
network will operate in. If the network is multinational a "#" can
be used to allow multiple country codes to be listed using a single
"country:" attribute.

The "admin-c:" and "tech-c:" are the contacts for the allocation at
the LIR. For more information please refer to the supporting notes
of the IPv4 address space request form found at:

http://www.ripe.net/ripe/docs/iprequestsupport.html#toc12

If the LIR has a role object it might want to reference this in the
"admin-c:" and "tech-c:" attributes. Role objects are an efficient
way of managing contact information for groups of people.  The
"status:" attribute will be generated by the RIPE Database, so this
attribute does not need to be filled in. The existing values are
deprecated and the RIPE and APNIC communities are discussing
replacement values. The discussion is archived at:

http://www.ripe.net/ripe/mail-archives/db-wg/20020401-20020701/msg00041.html

The "mnt-by:" attribute will always have a value of
<RIPE-NCC-HM-MNT>.

The "mnt-lower:" attribute provides hierarchical
authentication. They authenticate the creation of more specific
inet6num objects under the allocation inet6num object preventing
the unauthorised creation of objects.

It is essential that the LIR has their maintainer referenced in
this attribute. Where the LIR does not already have a maintainer
they should complete and include the maintainer template below. The
RIPE NCC will then create the maintainer for the LIR and reference
it in the inet6num object.

The "notify:" attribute should specify the e-mail address that will
receive notifications of any changes made to the allocation
inet6num object.

The "changed:" attribute will always be set to
<hostmaster@ripe.net>.

All objects within the RIPE Whois Database have <RIPE> as a fixed
value for the "source:" attribute.

#[MAINTAINER TEMPLATE]#

If you have already generated a maintainer, please reference it in
the inet6num template above and do not complete the mntner template
below.

mntner:
descr:
admin-c:
tech-c:
upd-to:
mnt-nfy:
auth:	
remarks:
notify:
mnt-by:
changed:
source:

Detailed information about the mntner object is available from the
RIPE Database using the link below:

http://www.ripe.net/perl/whois?-vmntner 

#[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-hdl in the inet6num object template for the
allocation request.

person:   
address:
address:
address:
e-mail:
phone:
fax-no:
mnt-by:
notify:
nic-hdl:
changed:
source: RIPE  

Detailed information about the person object is available from the
RIPE Database itself using the link below:

http://www.ripe.net/perl/whois?-vperson 

#[ADDITIONAL QUESTIONS]#

1. IPv6 address space is allocated to LIRs according to policies
set by the RIPE community.

It should be noted that, as stated in the IPv6 policy, IPv6 address
space is not considered property. IPv6 address space is licensed
for use rather than owned.

Please confirm that you have read the policy document "IPv6 Address
Allocation and Assignment Policies" and agree to abide by it. The
document can be found in the RIPE Document Store at:

http://www.ripe.net/ripe/docs/ipv6policy.html

2. Please provide a network diagram in PostScript or JPEG format
showing your IPv6 network. It should indicate expected dates for
completion of construction as well as how much IPv6 address space
is expected to be used in each segment.

The diagram can be sent either as a MIME attachment with your
e-mail to <hostmaster@ripe.net> or it can be faxed to
+31-20-535-4445. If you choose to fax the diagram please place the
ticket number you receive on the front page of the fax.

3. If your organisation has a web site detailing your planned IPv6
services, please provide the URL below: #[TEMPLATES END]#
_________________________________________________________________

Example of a Completed Initial IPv6 Allocation Request Form

#[IPV6 ALLOCATION REQUEST]#

#[REGISTRY ID]#

X-NCC-RegID: nn.nowhere

#[OVERVIEW OF ORGANISATION TEMPLATE]#

Northern Nowhere Internet is an ISP serving the Christmastown
Community in the barren wastes of the arctic north.  We are located
in Christmastown and peer at the XMAS-IX.  We provide GPRS, Cable,
DSL, Leased Line, Co-location and other Internet services.

Q1. Is this IPv6 request for the entire organisation or will other
parts of the organisation also be requesting an allocation?

This request is for all of Northern Nowhere Internet.

Q2. Will your organisation also be requesting (or do you already
have) an IPv6 allocation from another RIR?

Northern Nowhere Internet will only request an IPv6 allocation from
the RIPE NCC.

Please note that an LIR can only request an allocation for itself
and not on behalf of another organisation.

#[REQUESTER TEMPLATE]#

name: Santa Claus
organisation: Northern Nowhere Internet
country: NN
phone: +999 555 5555
fax-no: +999 555 5556
e-mail: santa.claus@nowhere.nn
nic-hdl: HOHO-RIPE

#[IPv6 ALLOCATION USAGE PLAN]#


Prefix When Used
Length Immediate 1yr 2yr  Description

/44      X                Northern Nowhere Internet HQ 
			 plus PoPs in 7 arctic locations
/42              X        The elves will each get a /48 
			 for their home networks   
/38              X        Cable services in the area of Christmastown   



#[NETWORK TEMPLATE]#


inet6num:
netname:
descr:     Provider Local Registry
descr:     Northern Nowhere Internet
descr:     The Arctic's only IPv6-ready ISP
remarks:   We make Xmas "X" rated :-)
country:   NN # EG NL GB RU AE
admin-c:   HOHO-RIPE
tech-c:    HOHO-RIPE
mnt-by:    RIPE-NCC-HM-MNT
mnt-lower: EXAMPLE-MNT
notify:    santa.claus@nowhere.nn
changed:   hostmaster@ripe.net
source:    RIPE


#[ADDITIONAL QUESTIONS]#

1. IPv6 address space is allocated to LIRs according to policies
set by the RIPE community.

It should be noted that, as stated in the IPv6 policy document,
IPv6 address space is not considered property. IPv6 address space
is licensed for use rather than owned.

Please confirm that you have read the policy document "IPv6 Address
Allocation and Assignment Policies" and agree to abide by it. The
document can be found in the RIPE Document Store at:

http://www.ripe.net/ripe/docs/ipv6policy.html

We have read the IPv6 policy document and agree to it. We do not
consider IPv6 address space as property.

2. Please provide a network diagram in PostScript or JPEG format
showing your IPv6 network. Submission instructions can be found in
the RIPE document "Supporting Notes for the Initial IPv6 Allocation
Request Form in the RIPE NCC Service Region" at:

http://www.ripe.net/ripe/docs/ipv6-supp-initial.html

It should indicate expected dates for completion of construction as
well as how much IPv6 address space is expected to be used in each
segment.

We have sent a network diagram in JPEG format as a MIME attachment
to this mail.

3. If your organisation has a web site detailing your planned IPv6
services, please provide the URL below: Please see:
http://xmas.nn/ipv6/itscoming.html

#[TEMPLATES END]#