You are here: Home > Publications > RIPE Document Store > Supporting Notes for the Provider Independent (PI) Assignment Request Form

Changes to Supporting Notes for the Provider Independent (PI) Assignment Request Form

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-454: ripe-491: This obsolete document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form".

This document contains instructions for LIRs on how to complete the " delete: <a href="http://www.ripe.net/publications/docs/pi-requestform.html"> insert: <a href="https://www.ripe.net/publications/docs/pi-requestform.html"> Provider Independent (PI) Assignment Request Form ".

The instructions are based on the " delete: <a href="http://www.ripe.net/publications/docs/ipv4-policies.html"> insert: <a href="https://www.ripe.net/publications/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE region NCC Service Region ".

General Information
Address Space User
Initial Information
Addressing Plan
Equipment Description
Network Description
delete: <a href="#diagram"> Network Diagram insert: <a href="#documentation"> Supporting Documentation
Database Template(s)
End of Request

delete: `<a id="info" name="info">` insert: `<a name="info">` General Information

delete: <blockquote>

 #[GENERAL INFORMATION]# %  insert: <br /> 
 %  insert: <br /> 
 % Please add your RegID. insert: <br /> 
 insert: <br /> 
 request-type: delete: <strong> pi-ipv4 delete: </strong> insert: <br /> 
 form-version: delete: <strong> 1.1  delete: </strong> 1.3  insert: <br /> 
 x-ncc-regid:  delete: <span class="arial-small"> nl.bluelight delete: </span>

delete: </blockquote>

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 [email protected] .

insert: 

insert: <a name="user"> insert: </a> insert: 

delete: `<a id="user" name="user">` delete: `</a>` Address Space User

delete: <blockquote>

 #[ADDRESS SPACE USER]# %  insert: <br /> 
 %  insert: <br /> 
 % Who will use the requested address space? 
 insert: <br /> 
 insert: <br /> 
 legal-organisation-name:  North SantaBank  insert: <br /> 
 organisation-location:  Santa City, NN  insert: <br /> 
 website-if-available:  http://www.nsb.nn  insert: <br /> 
 insert: <br /> 
 
 % Is this request being sent by a sponsoring LIR on behalf of insert: <br /> 
 % an End User? (Yes/No) 
 insert: <br /> 
 end-user-of-sponsoring-lir:  Yes  insert: <br /> 
 
 % If yes, please confirm that the "End User Assignment Agreement" insert: <br /> 
 % contains all of the elements listed in paragraph 2.0 of "Contractual insert: <br /> 
 % Requirements for Provider Independent Resource Holders in the insert: <br /> 
 % RIPE NCC Service Region".(Yes/No) 
 insert: <br /> 
 confirmation:  Yes  insert: <br /> 
 
 % Does this End User already have address space that can be used for insert: <br /> 
 % this assignment? (Yes/No) 
 insert: <br /> 
 space-available:  No

delete: </blockquote>

Enter the legal name and primary location of the organisation that will use this PI address space in the "legal-organisation-name" and "organisation-location" fields. If this End User has a website, enter the URL in the "website-if-available" field. Otherwise, enter "none" in this field. delete:  delete:  insert:  
insert:  
If you are an LIR sending this request on behalf of an End User, you should answer ‘Yes' in the “end-user-of-sponsoring-lir” "Yes" in the "end-user-of-sponsoring-lir" field. delete:  delete:  insert:  
insert:  
If you answered “Yes” "Yes" you should also confirm that all of the elements of paragraph 2.0 of “Contractual "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region” Region" are listed in the 'End User Assignment Agreement' that is signed by the End User and the sponsoring LIR. PI assignments can only be made to End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR and the End User. delete:  delete:  insert:  
insert:  
You can find an example agreement online. delete:  delete:  online: insert:  
insert: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/membership/lir-end-user-agreement.html insert: </a> insert:  
insert:  
You can send us an agreement in your local language or use the English version. delete:  delete:  insert:  
insert:  
If this request is sent by a Direct Assignment User, you answer “No” "No" to the above two questions. Direct Assignment Users have already signed an 'End User Assignment Agreement' with the RIPE NCC. If the request is for an LIR, you should also answer with “No”. "No".

If there is any address space assigned to this End User that is not in use, indicate this in the "space-available" field. If you answer "yes", you can explain why the End User needs another assignment of address space in the "Network Description" section section. insert: 

insert: 

delete: `<a id="initial" name="initial">` insert: `<a name="initial">` Initial Information

delete: <blockquote>

 #[INITIAL INFORMATION]# %  insert: <br /> 
 %  insert: <br /> 
 insert: <br /> 
 % Why is PI address space required rather than PA address insert: <br /> 
 % space? delete: </pre> delete: <pre> insert: <br /> 
 insert: <br /> 
 why-pi:  delete: <span class="arial-small"> North SantaBank will be multihomed. insert: <br /> 
 We cannot use PA address space because our uplinks do not insert: <br /> 
 allow their address space to be announced by other Autonomous Systems. delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 % Is the End User requesting extra address space for routing insert: <br /> 
 % and/or administrative reasons? (Yes/No) delete: </pre> delete: <pre> insert: <br /> 
 insert: <br /> 
 routing-reasons:  delete: <span class="arial-small"> No. delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 % Have you made the End User aware of the consequences and insert: <br /> 
 % disadvantages of PI address space? (Yes/No) insert: <br /> 
 insert: <br /> 
 confirmation:  insert: <strong>  Yes.  insert: </strong>

delete: <pre> confirmation: delete:  delete:  Yes. delete:  delete:  delete: </pre> delete: </blockquote>

In the " why-pi: " field, explain why PA address space cannot be used for this assignment. Remember that you should encourage the use of PA address space where possible.

You cannot request a larger assignment of address space than needed as conservation is one of the most important goals of the Internet Registry System. You can state whether you are requesting more address space than needed in the " routing-reasons: " field.

You must ensure that the End User understands and accepts that PI address space may be more difficult or more expensive to route than PA address space and then confirm this in the " confirmation: " field. You can find more details on the consequences and disadvantages of PI address space in the document "IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region".

insert: 

insert: <a name="plan"> insert: </a> insert: 

delete: `<a id="plan" name="plan">` delete: `</a>` Addressing Plan

delete: <blockquote>

 #[ADDRESSING PLAN]# %  insert: <br /> 
 % As of 1 January 2010 assignments are for a period of up to 12 months.  insert: <br /> 
 % As of 1 July 2010 assignments are for a period of up to 9 months.  insert: <br /> 
 % As of 1 January 2011 assignments are for a period of up to 6 months.  insert: <br /> 
 % As of 1 July 2011 assignments are for a period of up to 3 months.  insert: </pre>

insert: <pre>

 %  insert: <br /> 
 % How will the End User use this address space? % % Subnet size Within Within Within % (/nn) 3 months 1 year 2 years Purpose  insert: <br /> 
 %

 % Subnet Immediate Intermediate Entire Purpose  insert: <br /> 
 % size (/nn) Requirement Requirement Period  insert: <br /> 
 subnet:  /26 32 64 64 delete: <span class="arial-small"> Employee VPN Access delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 subnet:  /26 18 34 64 delete: <span class="arial-small"> Financial Services delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 subnet:  /26 22 30 60 delete: <span class="arial-small"> Workstations delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 subnet:  /27 11 15 28 delete: <span class="arial-small"> Public Services delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 subnet:  /27 7 18 30 delete: <span class="arial-small"> Operations delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 subnet:  /24 176 192 240 delete: <span class="arial-small"> Branch Offices delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 totals:  /23 266 353 486  insert: <br />

 number-of-subnets:  6

delete: <pre> insert: 

% Will the End User return any address space? delete: </pre> insert: 

 address-space-returned:  delete: <span class="arial-small"> 85.118.187/24 to nl.bluelight in 3 months delete: </span> delete: </strong> insert: </strong>  insert: <br />

delete: </blockquote>

The addressing plan shows how the End User will use the requested address space.

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

In the " delete:  Subnet "Subnet size (/nn): delete:  " (/nn)" column, enter a slash notation prefix for each subnet. Each entry should be large enough to contain the number of addresses needed for that subnet over the next two years. time period.

In the " delete:  Within 3 months: delete:  ", " delete:  Within 1 year: delete:  " and " delete:  Within 2 years: delete:  " columns, enter the number of addresses needed immediately for each subnet, and the estimated need for the next two years. You can change the time periods if needed. order to demonstrate the predicted growth of your network, you must provide an estimate of the address space you will require over three distinct periods: Immediate, Intermediate and the Entire period. Your estimates should include interfaces used for hosts, routers, gateways, terminal concentrators and any other machines requiring one or more network interfaces. These columns can either contain numbers (for example, 128) or slash notation prefixes (for example, /25). Multiple slash notation prefixes must be separated by comma(s) with no blank spaces (for example, /25,/27). insert:  
Starting on 1 January 2010, a gradual reduction in the assignment period will be applied. As the assignment period changes, so to will the information required: insert: 

insert: 

Up to 30 June 2010, assignments are for a period of up to 12 months. Therefore, your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for the coming 12 months. insert: 

insert: 

As of 1 July 2010, assignments are for a period of up to 9 months. Your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for insert:  
the coming 9 months. insert: 

insert: 

As of 1 January 2011, assignments are for period of up to 6 months. Your request should reflect your immediate requirements, predicted requirements for the coming 3 months, and predicted requirements for insert:  
the coming 6 months. insert: 

insert: 

As of 1 July 2011, assignments are for a period of up to 3 months. Your request should reflect your immediate requirements, predicted requirements for the coming 2 months, and predicted requirements for the coming 3 months.

In the " delete:  Purpose: delete:  " "Purpose" column, write a short description of each subnet. If needed, you can write a more detailed description in the " delete:  Network Description: delete:  " "Network Description" section at the end of this form. delete:  delete:  insert:  
insert:  
In the " delete:  totals: delete:  " "totals" row, add the totals of each column. The total of the " delete:  Subnet "Subnet size (/nn): delete:  " (/nn)" column should be the total amount of address space you are requesting for this assignment. delete:  delete:  insert:  
insert:  
In the " delete:  number-of-subnets: delete:  " "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. delete:  delete:  insert:  
insert:  
If there is any address space assigned to the End User that they will return, list each prefix in separate " delete:  address-space-returned: delete:  " "address-space-returned" fields. The expected time for renumbering is three months. You can use the following syntax: <x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field.

insert: 

insert: <a name="equipment"> insert: </a> insert: 

delete: `<a id="equipment" name="equipment">` delete: `</a>` Equipment Description

delete: <blockquote>

 #[EQUIPMENT DESCRIPTION]# %  insert: <br /> 
 %  insert: <br /> 
 % What equipment will be used and how will it use the %  requested insert: <br /> 
 %  address space? delete: </pre> delete: <pre> insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Core switches delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> Cisco delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> 25xx delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 3 units delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Servers delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> HP delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> various delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 40 units delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Firewalls delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> Cisco delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> PIX 515 E delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 2 units, 8 IP addresses delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Workstations delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> Dell delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> GX150 delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 22 units, 1 IP address each delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Routers delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> Cisco delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> 3825 delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 2 units delete: </span> delete: </strong> delete: </pre> delete: <pre> insert: </strong>  insert: <br /> 
 insert: <br /> 
 equipment-name:  delete: <span class="arial-small"> Routers delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 manufacturer-name:  delete: <span class="arial-small"> Cisco delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 model-number:  delete: <span class="arial-small"> AS5300 delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 other-data:  delete: <span class="arial-small"> 1 unit, 32 ports delete: </span>

delete: </blockquote>

The equipment description will help us to understand the requirements listed in the addressing plan and can be repeated as many times as needed. Leave an empty line before each new " delete:  equipment-name: delete:  " "equipment-name" field. delete:  delete:  insert:  
insert:  
In the " delete:  equipment-name: delete:  " "equipment-name" field, enter the type of equipment requiring address space from this assignment. delete:  delete:  insert:  
insert:  
Enter the vendor name and model number for the piece of equipment in the " delete:  manufacturer-name: delete:  " and " delete:  model-number delete:  :" "manufacturer-name" and "model-number" fields. delete:  delete:  insert:  
insert:  
If you have any more information about how this piece of equipment will use the requested address space, add this in the " delete:  other-data: delete:  " "other-data" field.

insert: 

insert: <a name="network"> insert: </a> insert: 

delete: `<a id="network" name="network">` delete: `</a>` Network Description

delete: <blockquote>

 #[NETWORK DESCRIPTION]# %  insert: <br /> 
 %  insert: <br /> 
 % Please add more information if you think it will help us %  understand insert: <br /> 
 %  this request. delete: </pre> delete: <pre> delete: <strong> delete: <span class="arial-small"> insert: <br /> 
 insert: <br /> 
 insert: <strong>  We have 11 branches across Santa City linked by corporate fibre insert: <br /> 
 channels. We will assign a /28 subnet for each branch. Each branch insert: <br /> 
 will have SMTP, WWW, file server, e-banking and dial-up pool. delete: </span> delete: </strong> delete: <strong> delete: <span class="arial-small"> insert: <br /> 
 insert: <br /> 
 Public Internet Services: SMTP (2 IP addresses), WWW (6 IP addresses, insert: <br /> 
 2 servers), FTP (1 IP address), DNS (2 IP addresses) Financial insert: <br /> 
 Services: 6 servers, 3 IP addresses each. Operations network: insert: <br /> 
 Security, Monitoring, VPN, Proxy, DNS delete: </span>

delete: </blockquote>

You can use this space for additional information that you think will be helpful for us (RIPE NCC) when we evaluate your request. A clearer understanding of the network and its addressing needs can help us to evaluate your request more quickly.

insert: 

insert: <a name="documentation"> insert: </a> insert: 

delete: `<a id="diagram" name="diagram">` delete: `</a>` Network Diagram Supporting Documentation

delete: <blockquote>

 #[NETWORK DIAGRAM]# %  #[SUPPORTING DOCUMENTATION]#  insert: <br /> 
 %  insert: <br /> 
 % If this request is being sent by a sponsoring LIR on behalf of  insert: <br /> 
 % an End User, please attach a copy of the signed "End User Assignment  insert: <br /> 
 % Agreement" and the company registration papers of the End User.  insert: <br /> 
 % You can also attach a network diagram or other supporting  insert: <br /> 
 % documentation.  insert: <br /> 
 %  insert: <br /> 
 % Have you attached a network diagram  any files/documents  to this request? (Yes/No) diagram-attached:  delete: <strong> delete: <span class="arial-small"> insert: <br /> 
 insert: <br /> 
 file-attached:  insert: <strong>  Yes delete: </span>

delete: </blockquote> delete:  insert: 

For each PI assignment that is requested through a sponsoring LIR for an End User, we need to receive a copy of 'End User Assignment Agreement' and the company registration papers of the End User. insert:  
insert:  
If this request is for an LIR or a "Direct Assignment User", you do not have to attach a copy of 'End User Assignment Agreement' and company registration papers. insert:  
insert:  
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.

insert: 

insert: <a name="database"> insert: </a> insert: 

delete: `<a id="database" name="database">` delete: `</a>` Database Template(s)

delete: <blockquote>

 #[DATABASE TEMPLATE(S)]# %  insert: <br /> 
 %  insert: <br /> 
 % Please complete all of the fields below. insert: <br /> 
 insert: <br /> 
 inetnum: insert: <br /> 
 netname:  delete: <span class="arial-small"> NSB-NET delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 descr:  delete: <span class="arial-small"> North SantaBank delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 country:  delete: <span class="arial-small"> NN delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 org:  delete: <span class="arial-small"> ORG-NS31-RIPE delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 admin-c:  delete: <span class="arial-small"> ACM2-RIPE delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 tech-c:  delete: <span class="arial-small"> HOHO1-RIPE delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 status: insert: <strong>  ASSIGNED PI insert: </strong>  insert: <br /> 
 mnt-by: insert: <strong>  RIPE-NCC-END-MNT insert: </strong>  insert: <br /> 
 mnt-lower: insert: <strong>  RIPE-NCC-END-MNT insert: </strong>  insert: <br /> 
 mnt-by:  delete: <span class="arial-small"> SANTA-MNT delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 mnt-routes:  delete: <span class="arial-small"> SANTA-MNT delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 mnt-domains:  delete: <span class="arial-small"> SANTA-MNT delete: </span> delete: </strong> insert: </strong>  insert: <br /> 
 changed: [email protected] insert: <br /> 
 source: RIPE

delete: </blockquote>

Leave the " delete:  inetnum: delete:  " "inetnum" field empty as we will choose the address range. delete:  delete:  insert:  
insert:  
The " delete:  netname: delete:  " "netname" should be a short and descriptive name for the network and should reflect the organisation name of the End User. delete:  delete:  insert:  
insert:  
Enter the End User's organisation name in the " delete:  descr delete:  :" "descr" field. delete:  delete:  insert:  
insert:  
Use the ISO country code of the End User's location in the " delete:  country: delete:  " "country" field. If the End User is multi-national, repeat the " delete:  country: delete:  " "country" field as many times as needed. Alternatively, you can use EU or ZZ if you do not wish to show the End User's location in the inetnum object. delete:  delete:  insert:  
insert:  
Enter the org-ID of the End User's organisation object in the " delete:  org: delete:  " "org" field. delete:  delete:  insert:  
insert:  
The nic-handle of the insert:  role insert:  or insert:  person insert:  object in the " delete:  admin-c: delete:  " "admin-c" field should reflect someone who is administratively responsible for the network. delete:  delete:  insert:  
insert:  
The nic-handle of the insert:  role insert:  or insert:  person insert:  object in the " delete:  tech-c: delete:  " "tech-c" field should reflect someone who has technical knowledge of the network. delete:  delete:  insert:  
insert:  
The " delete:  status: delete:  " "status" field must be ASSIGNED PI . delete:  delete:  PI. insert:  
insert:  
The " delete:  mnt-by: delete:  " and " delete:  mnt-lower: delete:  " "mnt-by" and "mnt-lower" fields must contain delete:  RIPE-NCC-END-MNT delete:  . RIPE-NCC-END-MNT. You can put the LIR's or End User's maintainers in separate " delete:  mnt-by: delete:  ", " delete:  mnt-routes: delete:  " and " delete:  mnt-domains: delete:  " "mnt-by", "mnt-routes" and "mnt-domains" fields. delete:  delete:  insert:  
insert:  
The " delete:  mnt-by: delete:  " "mnt-by" field shows which maintainer authenticates object updates. The " delete:  mnt-routes: delete:  " and " delete:  mnt-domains: delete:  " "mnt-routes" and "mnt-domains" fields show which maintainers authenticate the creation of insert:  route and insert:  and insert:  domain insert:  objects. delete:  delete:  insert:  
insert:  
The RIPE Database must contain all of the objects that you use. delete:  delete:  insert:  
insert:  
The " delete:  changed: delete:  " "changed" field must be delete:  [email protected] delete:  . delete:  delete:  [email protected]. insert:  
insert:  
The " delete:  source: delete:  " "source" field must be delete:  RIPE delete:  . RIPE. insert: 

insert: 

insert: <a name="end"> insert: </a>

delete: `<a id="end" name="end">` delete: `</a>` End of Request

delete: <blockquote>

 #[END of REQUEST]#  delete: </pre> delete: <pre> delete: <strong> delete: <span class="arial-small"> Best Regards  delete: </span> ,  delete: <br /> delete: </strong> delete: <strong> delete: <span class="arial-small"> Regards,  insert: <br /> 
 insert: <br /> 
 Jan Janssen, Bluelight Admin delete: </span> delete: </strong>

delete: </blockquote>

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

Supporting Notes for the Provider Independent (PI) Assignment Request Form

RIPE Documents Search

ripe-454

State:

Obsoleted

Updated by:

ripe-455 , ripe-491 , ripe-537

Updates:

ripe-357 , ripe-337 , ripe-318 , ripe-286 , ripe-220 , ripe-142 , ripe-138 , ripe-128 , ripe-124 , ripe-115 , ripe-107 , ripe-098 , ripe-095 , ripe-088 , ripe-083 , ripe-048

Authors:

RIPE NCC

Date:

February 2009

Download

File:
PDF | 146.0KB

Download

File:
ASCII

Changes to Supporting Notes for the Provider Independent (PI) Assignment Request Form

delete: <a id="info" name="info"> insert: <a name="info"> General Information

delete: <a id="user" name="user"> delete: </a> Address Space User

delete: <a id="initial" name="initial"> insert: <a name="initial"> Initial Information

delete: <a id="plan" name="plan"> delete: </a> Addressing Plan

delete: <a id="equipment" name="equipment"> delete: </a> Equipment Description

delete: <a id="network" name="network"> delete: </a> Network Description

delete: <a id="diagram" name="diagram"> delete: </a> Network Diagram Supporting Documentation

delete: <a id="database" name="database"> delete: </a> Database Template(s)

delete: <a id="end" name="end"> delete: </a> End of Request

RIPE Documents Search

ripe-454

delete: `<a id="info" name="info">` insert: `<a name="info">` General Information

delete: `<a id="user" name="user">` delete: `</a>` Address Space User

delete: `<a id="initial" name="initial">` insert: `<a name="initial">` Initial Information

delete: `<a id="plan" name="plan">` delete: `</a>` Addressing Plan

delete: `<a id="equipment" name="equipment">` delete: `</a>` Equipment Description

delete: `<a id="network" name="network">` delete: `</a>` Network Description

delete: `<a id="diagram" name="diagram">` delete: `</a>` Network Diagram Supporting Documentation

delete: `<a id="database" name="database">` delete: `</a>` Database Template(s)

delete: `<a id="end" name="end">` delete: `</a>` End of Request