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-537: ripe-454: This obsolete document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form".
delete: <p class="p1"> delete: <a data-val="046f7e54-4540-4541-adff-aceeea440a2f" href="resolveuid/046f7e54-4540-4541-adff-aceeea440a2f" data-linktype="internal" class="internal-link"> This RIPE document has been obsoleted due to the RIPE NCC reaching the last /8 of IPv4 address space. delete: </a> delete: </p>

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

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


delete: <a> delete: <strong> delete: </strong> delete: </a>  

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

insert: <blockquote>
 #[GENERAL INFORMATION]# delete: <br /> %  delete: <br /> %  % Please add your RegID. delete: <br /> delete: <br /> request-type: insert: <strong>  pi-ipv4 delete: <br /> insert: </strong>  form-version: 1.3  delete: <br /> insert: <strong>  1.1  insert: </strong>  x-ncc-regid:  insert: <span class="arial-small">  nl.bluelight delete: </strong> delete: </pre> insert: </span>  insert: </strong>  insert: </pre> 
insert: </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 ncc@ripe.net .

delete: <p> delete: <a name="user"> insert: <h2>

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

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

insert: <p>

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: <br /> delete: <br /> insert: </p>

insert: <p>

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: <br /> delete: <br /> insert: </p>

insert: <p>

You can find an example agreement online: delete: <br /> delete: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/membership/lir-end-user-agreement.html delete: </a> delete: <br /> delete: <br /> online. insert: </p>

insert: <p>

You can send us an agreement in your local language or use the English version. delete: <br /> delete: <br /> insert: </p>

insert: <p>

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. delete: </p> delete: <p> section

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

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

The RIPE NCC will assign additional IPv4 addresses to an End User in order to make the You cannot request a larger assignment size a multiple of a /24 if the End User demonstrates the intent to announce this of address space for the purpose of multihoming to two or more Autonomous Systems (AS) which the End User does not own or control. Cumulatively, no more than 255 additional IPv4 addresses may be assigned to any particular End User for the purposes outlined above. 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".

delete: <p> delete: <a name="plan"> insert: <h2>

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

insert: <blockquote>
 #[ADDRESSING PLAN]# delete: <br /> % As of 1 January 2010 assignments are for a period of up to 12 months.  delete: <br /> % As of 1 July 2010 assignments are for a period of up to 9 months.  delete: <br /> % As of 1 January 2011 assignments are for a period of up to 6 months.  delete: <br /> % As of 1 July 2011 assignments are for a period of up to 3 months.  delete: </pre> delete: <pre> %  delete: <br /> %  % How will the End User use this address space? delete: <br /> %  delete: </pre> delete: <pre> %  % Subnet Immediate Intermediate Entire  size Within Within Within % (/nn) 3 months 1 year 2 years  Purpose delete: <br /> % size (/nn) Requirement Requirement Period  delete: <br /> insert: </pre> 
insert: <pre>
 subnet:  /26 32 64 64 insert: <span class="arial-small">  Employee VPN Access delete: </strong> delete: <br /> insert: </span>  insert: </strong>  subnet:  /26 18 34 64 insert: <span class="arial-small">  Financial Services delete: </strong> delete: <br /> insert: </span>  insert: </strong>  subnet:  /26 22 30 60 insert: <span class="arial-small">  Workstations delete: </strong> delete: <br /> insert: </span>  insert: </strong>  subnet:  /27 11 15 28 insert: <span class="arial-small">  Public Services delete: </strong> delete: <br /> insert: </span>  insert: </strong>  subnet:  /27 7 18 30 insert: <span class="arial-small">  Operations delete: </strong> delete: <br /> insert: </span>  insert: </strong>  subnet:  /24 176 192 240 insert: <span class="arial-small">  Branch Offices delete: </strong> delete: <br /> insert: </span>  insert: </strong>  totals:  /23 266 353 486  delete: <br /> 
 number-of-subnets:  6  
delete: <p> insert: <pre>
 % Will the End User return any address space? delete: </p> insert: </pre> 
 address-space-returned:  insert: <span class="arial-small">  85.118.187/24 to nl.bluelight in 3 months delete: </strong> delete: <br /> delete: </pre> insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>

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

You can repeat the "subnet" " insert: <span class="pre"> subnet: insert: </span> " row as many times as needed. Delete any empty "subnet" " insert: <span class="pre"> subnet: insert: </span> " fields before you send the request.

In the "Subnet " insert: <span class="pre"> Subnet size (/nn)" (/nn): insert: </span> " 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. insert: </p>

insert: <p>

In the " insert: <span class="pre"> Within 3 months: insert: </span> ", " insert: <span class="pre"> Within 1 year: insert: </span> " and " insert: <span class="pre"> Within 2 years: insert: </span> " 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 period. delete: </p> delete: <p> In 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. periods if needed. 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). delete: <br /> 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: delete: </p> delete: <p> 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. delete: </p> delete: <p> 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 delete: <br /> the coming 9 months. delete: </p> delete: <p> 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 delete: <br /> the coming 6 months. delete: </p> delete: <p> 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 "Purpose" " insert: <span class="pre"> Purpose: insert: </span> " column, write a short description of each subnet. If needed, you can write a more detailed description in the "Network Description" " insert: <span class="pre"> Network Description: insert: </span> " section at the end of this form. delete: <br /> delete: <br /> insert: </p>

insert: <p>

In the "totals" " insert: <span class="pre"> totals: insert: </span> " row, add the totals of each column. The total of the "Subnet " insert: <span class="pre"> Subnet size (/nn)" (/nn): insert: </span> " column should be the total amount of address space you are requesting for this assignment. delete: <br /> delete: <br /> insert: </p>

insert: <p>

In the "number-of-subnets" " insert: <span class="pre"> number-of-subnets: insert: </span> " field, enter the total number of subnets listed in the addressing plan. delete: <br /> delete: <br /> insert: </p>

insert: <p>

If there is any address space assigned to the End User that they will return, list each prefix in separate "address-space-returned" " insert: <span class="pre"> address-space-returned: insert: </span> " 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.

delete: <p> delete: <a name="equipment"> insert: <h2>

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

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

insert: <p>

In the "equipment-name" " insert: <span class="pre"> equipment-name: insert: </span> " field, enter the type of equipment requiring address space from this assignment. delete: <br /> delete: <br /> insert: </p>

insert: <p>

Enter the vendor name and model number for the piece of equipment in the "manufacturer-name" and "model-number" " insert: <span class="pre"> manufacturer-name: insert: </span> " and " insert: <span class="pre"> model-number insert: </span> :" fields. delete: <br /> delete: <br /> insert: </p>

insert: <p>

If you have any more information about how this piece of equipment will use the requested address space, add this in the "other-data" " insert: <span class="pre"> other-data: insert: </span> " field.

delete: <p> delete: <a name="network"> insert: <h2>

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

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

delete: <p> delete: <a name="documentation"> insert: <h2>

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

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

A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.

delete: <p> delete: <a name="database"> insert: <h2>

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

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

Leave the "inetnum" " insert: <span class="pre"> inetnum: insert: </span> " field empty as we will choose the address range. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The "netname" " insert: <span class="pre"> netname: insert: </span> " should be a short and descriptive name for the network and should reflect the organisation name of the End User. delete: <br /> delete: <br /> insert: </p>

insert: <p>

Enter the End User's organisation name in the "descr" " insert: <span class="pre"> descr insert: </span> :" field. delete: <br /> delete: <br /> insert: </p>

insert: <p>

Use the ISO country code of the End User's location in the "country" " insert: <span class="pre"> country: insert: </span> " field. If the End User is multi-national, repeat the "country" " insert: <span class="pre"> country: insert: </span> " 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: <br /> delete: <br /> insert: </p>

insert: <p>

Enter the org-ID of the End User's organisation object in the "org" " insert: <span class="pre"> org: insert: </span> " field. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The nic-handle of the delete: <strong> role delete: </strong> or delete: <strong> person delete: </strong> object in the "admin-c" " insert: <span class="pre"> admin-c: insert: </span> " field should reflect someone who is administratively responsible for the network. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The nic-handle of the delete: <strong> role delete: </strong> or delete: <strong> person delete: </strong> object in the "tech-c" " insert: <span class="pre"> tech-c: insert: </span> " field should reflect someone who has technical knowledge of the network. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The "status" " insert: <span class="pre"> status: insert: </span> " field must be ASSIGNED PI. delete: <br /> delete: <br /> PI . insert: </p>

insert: <p>

The "mnt-by" and "mnt-lower" " insert: <span class="pre"> mnt-by: insert: </span> " and " insert: <span class="pre"> mnt-lower: insert: </span> " fields must contain RIPE-NCC-END-MNT. insert: <span class="pre"> RIPE-NCC-END-MNT insert: </span> . You can put the LIR's or End User's maintainers in separate "mnt-by", "mnt-routes" and "mnt-domains" " insert: <span class="pre"> mnt-by: insert: </span> ", " insert: <span class="pre"> mnt-routes: insert: </span> " and " insert: <span class="pre"> mnt-domains: insert: </span> " fields. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The "mnt-by" " insert: <span class="pre"> mnt-by: insert: </span> " field shows which maintainer authenticates object updates. The "mnt-routes" and "mnt-domains" " insert: <span class="pre"> mnt-routes: insert: </span> " and " insert: <span class="pre"> mnt-domains: insert: </span> " fields show which maintainers authenticate the creation of delete: <strong> route delete: </strong> and delete: <strong> and domain delete: </strong> objects. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The RIPE Database must contain all of the objects that you use. delete: <br /> delete: <br /> insert: </p>

insert: <p>

The "changed" " insert: <span class="pre"> changed: insert: </span> " field must be hostmaster@ripe.net. delete: <br /> delete: <br /> insert: <span class="pre"> hostmaster@ripe.net insert: </span> . insert: </p>

insert: <p>

The "source" " insert: <span class="pre"> source: insert: </span> " field must be RIPE. delete: </p> delete: <p> delete: <a name="end"> insert: <span class="pre"> RIPE insert: </span> . insert: </p>

insert: <h2>

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

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

Please write your full name below the "#[END of REQUEST]#" " insert: <span class="pre"> #[END of REQUEST]# insert: </span> " header.