Changes to Internet Exchange Point Request Supporting Notes
| Legend | (+) Added | (-) Deleted |
|---|---|---|
| Changed | Tag Added | Tag Deleted |
This document contains instructions for LIRs on how to complete the "Internet “ insert: <a class="external-link" href="https://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html" target="_self" title=""> IPv6 Internet Exchange Point Points Assignment Request Form". Form insert: </a> ”.
The instructions are based on the following policy documents: delete: </p> delete: <ol> delete: <li> delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region delete: </a> delete: </li> delete: <li> delete: <a href="http://www.ripe.net/ripe/docs/ipv6-policies"> “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy ”. insert: </p>
insert: <hr />insert: <ul>
- insert: <li>
- insert: <a href="#general"> General Information insert: </a>
- delete: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: <a href="#requester"> Requester Template delete: </ol> insert: <li>
- insert: <a href="#overview"> Overview of Organisation Template insert: </a> insert: </li> insert: <li>
- insert: <a href="#user"> User Template insert: </a> insert: </li> insert: <li>
- insert: <a href="#peering"> Member Peering Information Template insert: </a> insert: </li> insert: <li>
- insert: <a href="#current"> Current Address Space Usage Template insert: </a> insert: </li> insert: <li>
- insert: <a href="#plan"> Addressing Plan insert: </a> insert: </li> insert: <li>
- insert: <a href="#comments"> Supplemental Comments insert: </a> insert: </li> insert: <li>
- insert: <a href="#documentation"> Supporting Documentation insert: </a> insert: </li> insert: <li>
- insert: <a href="#database"> Database Template(s) insert: </a> insert: </li> insert: <li>
- insert: <a href="#end"> End of Request insert: </a> insert: </li> insert: </ul>
insert: <p>
insert: <a name="general"> insert: </a> insert: </p>
General Information
delete: <pre class="pre"> insert: <pre>#[GENERAL INFORMATION]#
%
% Please add your RegID.
request-type: ixp-assign ipv6-for-ixp
form-version: 1.0 1.2
x-ncc-regid: delete: <strong> insert: <b> nl.bluelight delete: </strong> insert: </b>
Please do not change the value of the "request-type:" “ insert: <tt> request-type: insert: </tt> ” and "form-version:" “ insert: <tt> form-version: insert: </tt> ” fields.
Enter your Registry Identifier (RegID) in the "x-ncc-regid:" “ insert: <tt> x-ncc-regid: insert: </tt> ” field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact delete: <a href="mailto:[email protected]"> [email protected] delete: </a> . delete: </p> delete: <h3> <[email protected]>. insert: </p>
insert: <p>insert: <a name="requester"> insert: </a> insert: </p>
insert: <h2>Requester Template insert: </h2>
insert: <pre>#[REQUESTER TEMPLATE]# insert: <br />insert: <p>
% insert: <br />
% Please add your contact details. insert: <br />
name: insert: <b> John Smith insert: </b> insert: <br />
phone: insert: <b> +123 45 678910 insert: </b> insert: <br />
fax-no: insert: <b> +123 45 678911 insert: </b> insert: <br />
email: insert: <b> [email protected] insert: </b> insert: <br />
nic-hdl: insert: <b> HOHO1-RIPE insert: </b> insert: </pre>
Enter your contact details in the requester template. You must be a registered contact for the LIR. insert: <a href="https://lirportal.ripe.net/"> The LIR Portal insert: </a> contains a list of registered contacts for your LIR. insert: </p>
insert: <p>Please use the international dialling codes (for example, +31 for the Netherlands,) in the “ insert: <tt> phone: insert: </tt> ” and “ insert: <tt> fax-no: insert: </tt> ” fields. insert: </p>
insert: <p>Enter your NIC handle, if you have one, in the “ insert: <tt> nic-hdl: insert: </tt> ” field. insert: </p>
insert: <p>insert: <a name="overview"> insert: </a> insert: </p>
insert: <h2>Overview of Organisation delete: </h3> Template insert: </h2>
#[OVERVIEW OF ORGANISATION]# delete: <br /> ORGANISATION TEMPLATE]# insert: <br />
%
% Is this request being sent by a sponsoring LIR on behalf of an insert: <br />
% End delete: <br /> % User? (Yes/No)
insert: <br />
end-user-of-sponsoring-lir: delete: <strong> insert: <b> Yes delete: </strong> insert: </b> insert: <br />
% If yes, please confirm that the "End User Assignment Agreement"
% contains all of the elements listed in paragraph 2.0 of insert: <br />
% "Contractual delete: <br /> % Requirements for Provider Independent Resource Holders insert: <br />
% in the RIPE delete: <br /> % NCC Service Region". (Yes/No)
insert: <br />
confirmation: delete: <strong> insert: <b> Yes delete: </strong> insert: </b> insert: <br />
insert: <br />
%
% Which IXP will use the requested address space?
% Please include the IXP's membership policy. insert: <br />
insert: <br />
org-description: delete: <strong> insert: <b> Ruritania IXP Ltd delete: </strong> IXP. The joining requirements are online at insert: </b> insert: <br />
insert: <b> http://www.rurixp.ripe.net/join_us.html insert: </b>
If you are an LIR sending this request on behalf of is sent for an End User, User of a sponsoring LIR, you should answer "Yes" in the "end-user-of-sponsoring-lir" 'Yes' in the “ insert: <tt> end-user-of-sponsoring-lir insert: </tt> ” field.
If you answered "Yes" 'Yes' you should also confirm that all of the elements of paragraph 2.0 of "Contractual “ insert: <a data-val="b4db2a127586d02986acbcc4f1cf8651" href="resolveuid/b4db2a127586d02986acbcc4f1cf8651" data-linktype="internal" class="internal-link"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" Region insert: </a> ” are listed in the “End 'End User Assignment Agreement” Agreement' that is signed by the End User and the sponsoring LIR. delete: </p> delete: <p> For all PI assignments that are requested through a can only be made to End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR for an End User, we need to receive a copy of the "End User Assignment Agreement" and the company registration papers of the End User.
You can find an example agreement at: delete: <br /> at at https://www.ripe.net/lir-services/resource-management/direct-assignments/independent-assignment-request-and-maintenance-agreement delete: </a> delete: </p> delete: <p> http://www.ripe.net/ripe/docs/lir-end-user-agreement.html insert: </a> . insert: <br />
You can send us an agreement in your local language or use the English version.
If this request is sent by a Direct Assignment User, you answer '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 "No" to the two questions above. There is no need to submit any additional documentation if the request is for an LIR. with 'No'.
In the “org-description:” “ insert: <tt> org-description: insert: </tt> ” field, write a short description of the organisation operating as an Internet Exchange Point (IXP). Please include references which show that the organisation operates as an IXP requesting the assignment(s). delete: </p> delete: <h3> Overview of the and that the requirements to join the IXP are open and clear. You can add a URL or attach a document which contains this information. insert: </p>
insert: <p>insert: <a name="user"> insert: </a> insert: </p>
insert: <h2>User delete: </h3> Template insert: </h2>
#[OVERVIEW OF THE USER]# delete: <br /> #[USER TEMPLATE]# insert: <br />
%
% Who is the contact person for this IXP?
Name: delete: <strong> insert: <br />
name: insert: <b> Fred Bloggs delete: </strong> delete: <br /> Organisation: delete: <strong> insert: </b> insert: <br />
organisation: insert: <b> Ruritania IXP delete: </strong> delete: <br /> Country: delete: <strong> insert: </b> insert: <br />
country: insert: <b> NN delete: </strong> delete: <br /> Phone: delete: <strong> insert: </b> insert: <br />
phone: insert: <b> +123 45 678910 delete: </strong> delete: <br /> E-mail: delete: <strong> insert: </b> insert: <br />
fax-no: insert: <b> +123 45 678911 insert: </b> insert: <br />
email: insert: <b> [email protected] delete: </strong> insert: </b>
Enter the legal name and primary location of the organisation in the “organisation:” “ insert: <tt> organisation: insert: </tt> ” and “country:” “ insert: <tt> country: insert: </tt> ” fields.
Please use international dialing dialling codes (for example, +31 for the Netherlands,) in the “phone:”field. delete: </p> delete: <h3> Existing “ insert: <tt> phone: insert: </tt> ” and “ insert: <tt> fax-no: insert: </tt> ” fields. insert: </p>
insert: <p>insert: <a name="peering"> insert: </a> insert: </p>
insert: <h2>Member Peering Information Template insert: </h2>
insert: <pre>#[MEMBER PEERING INFORMATION TEMPLATE]# insert: <br />insert: <p>
% insert: <br />
% If the IXP has an online list of members, please add the insert: <br />
% URL below. insert: <br />
insert: <br />
insert: <b> member-peering-list: http://www.rurixp.ripe.net/members.html insert: </b> insert: <br />
insert: <br />
% If you will include this list as an attachment, please insert: <br />
% enter "Yes" below. insert: <br />
insert: <br />
member-peering-attached: insert: <br />
insert: <br />
% Please add the contact details for three of these members. insert: <br />
insert: <br />
organisation-1: insert: <b> Bluelight B.V. insert: </b> insert: <br />
as-number-1: insert: <b> AS65444 insert: </b> insert: <br />
e-mail-1: insert: <b> [email protected] insert: </b> insert: <br />
insert: <br />
organisation-2: insert: <b> Bank of Ruritania Inc. insert: </b> insert: <br />
as-number-2: insert: <b> AS65333 insert: </b> insert: <br />
e-mail-2: insert: <b> [email protected] insert: </b> insert: <br />
insert: <br />
organisation-3: insert: <b> Ruritania Telecom insert: </b> insert: <br />
as-number-3: insert: <b> AS65222 insert: </b> insert: <br />
e-mail-3: insert: <b> [email protected] insert: </b> insert: <br />
insert: <br />
% If possible, please add the URL of a looking glass where insert: <br />
% we can verify this information: insert: <br />
insert: <br />
insert: <b> looking-glass: http://www.rurixp.ripe.net/looking-glass.cgi insert: </b> insert: </pre>
You must provide a list of the IXP's members. If this list is online, please add the URL of the IXP's website in the “ insert: <tt> member-peering-list: insert: </tt> ” field. If you attach the list to your request, enter ‘yes' in the “ insert: <tt> member-peering-attached: insert: </tt> ” field. insert: </p>
insert: <p>Enter the organisation name, Autonomous System (AS) number and the contact e-mail address for three of the IXPs members. insert: </p>
insert: <p>If possible, add the URL of a looking glass in the "looking glass:" field so we can verify this information. insert: </p>
insert: <p>insert: <a name="current"> insert: </a> insert: </p>
insert: <h2>Current Address Space Usage delete: </h3> Template insert: </h2>
#[EXISTING #[CURRENT ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % If the IXP has any IPv4 ranges(s) for their peering LAN, list them delete: <br /> % below. If any such space is being returned, then the return date delete: <br /> % should be specified. delete: <br /> subnet-ipv4: delete: <strong> 192.0.2.0/24 to nl.bluelight in 1 month. delete: </strong> USAGE TEMPLATE]# insert: <br />
%
% If the IXP has any IPv6 assignments, please list them below.
subnet-ipv6: delete: <strong> None delete: </strong> subnet: insert: <b> none insert: </b>
Please specify address prefixes using slash notation (for example, y:y:y::/yy). You can repeat the “subnet-ipv4 or subnet-ipv6:” “ insert: <tt> subnet: insert: </tt> ” field as many times as needed.
If there is any address space assigned that they will be returned, list each prefix in separate "address-space-returned" fields. The maximum renumbering is 180 days. You can use the following syntax: <x.x.x.x/xx> in <time period> for this field. delete: </p> delete: <h3> IPv4 Address Space Usage delete: </h3> insert: <a name="plan"> insert: </a> insert: </p>
insert: <h2>Addressing Plan insert: </h2>
#[IPv4 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How #[ADDRESSING PLAN]# insert: <br />
% insert: <br />
% When will the IXP use the requested IPv4 address space?
% ADDRESSING PLAN delete: <br /> % Subnet Immediate Intermediate Entire Purpose delete: <br /> % size (/nn) Requirement Requirement Period delete: <br /> subnet delete: <strong> : /27 16 24 32 Network Infrastructure delete: <br /> delete: </strong> subnet delete: <strong> : /24,/26 272 296 320 Members connections delete: <br /> delete: </strong> delete: <br /> totals delete: <strong> : /24,/26,/27 /24,/27 /24,/26 /24,/26,/27 delete: </strong> delete: <br /> number-of-subnets: delete: <strong> 2 delete: </strong> delete: </pre> delete: <p> The addressing plan shows how the End User will use the requested address space. delete: </p> delete: <p> You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request. delete: </p> delete: <p> In the "Subnet size (/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 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. These columns can either contain numbers (for example, 256) or slash notation prefixes (for example, /24). delete: </p> delete: <p> In the "Purpose" column, write a short description of each subnet. If needed, you can write a more detailed description in the "Supplemental Comments" section at the end of this form. delete: </p> delete: <p> In the "totals" row, add the totals of each column. The total of the "Subnet size (/nn)" column should be the total amount of address space you are requesting for this assignment. delete: <br /> delete: <br /> In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. delete: </p> delete: <h3> IPv6 Address Space Usage delete: </h3> delete: <pre> #[IPv6 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How will the IXP use the requested IPv6 address space? delete: <br /> % ADDRESSING PLAN
% Subnet Within Within Within Purpose
% size (/nn) 3 months 1 year 2 years delete: <strong> Purpose
subnet: insert: <b> /64 x - - Network Infrastructure *see supplemental insert: </b>
subnet: /55 insert: <b> /64 x - - Members connections* delete: </strong> comments section insert: </b>
The addressing plan shows when the IXP plans to use the address space.
Enter the size of each subnet in the “Subnet “ insert: <tt> Subnet size (/nn)” (/nn) insert: </tt> ” column. Please specify the size using IPv6 slash notation (for example, /48). You can repeat the “subnet:” “ insert: <tt> subnet: insert: </tt> ” field as many times as needed.
In the “Purpose” “ insert: <tt> Purpose insert: </tt> ” column, write a short description for each subnet. If needed, you can write a more detailed description in the “Insert “ insert: <tt> Insert Supplemental Comments” Comments insert: </tt> ” section at the end of the form.
Complete the remaining columns with a cross (x) or a dash (-). For example, if you will use a subnet within three months, enter a cross in the “Within “ insert: <tt> Within 3 months” months insert: </tt> ” column and a dash in both the “Within “ insert: <tt> Within 1 year” year insert: </tt> ” and “Within “ insert: <tt> Within 2 years” years insert: </tt> ” columns.
delete: <h3> insert: <p>insert: <a name="comments"> insert: </a> insert: </p>
insert: <h2>Supplemental Comments delete: </h3> insert: </h2>
#[SUPPLEMENTAL COMMENTS]#
%
% Please add more information if you think it will help insert: <br />
% us understand delete: <br /> % this request. You can attach a network diagram or other relevant delete: <br /> % supporting documentation. If the IXP has an online list of members, delete: <br /> % please add the URL below. delete: </pre> delete: <p> delete: <strong> Ruritania IXP has 62 IXP members, insert: <br />
insert: <br />
insert: <b> We will have 2 separate subnets. One for our 30 banking members who insert: <br />
require secure transactions, and add approximately six new members every month. one for our 200 regular ISP insert: <br />
members. Each member's connection requires one /30. delete: <br /> The IXP network consists of three routers (three IPs), three switches (three IPs) and two firewalls (eight IPs). Two more routers and switches member will be added next month. delete: <br /> We would like to return the current /24 used for our peering LAN and receive one /23 IXP assignment to renumber current members and connect new members. delete: </strong> delete: </p> delete: <pre> delete: <strong> The joining requirements are online at: delete: </strong> delete: <a href="http://www.rurixp.ripe.net/join_us.html"> http://www.rurixp.ripe.net/join_us.html delete: </a> use a /128. insert: </b>
You can use this space for additional information that you think will be helpful for us when we evaluate your request. insert: </p>
insert: <p>insert: <a name="documentation"> insert: </a> insert: </p>
insert: <h2>Supporting Documentation insert: </h2>
insert: <pre>#[SUPPORTING DOCUMENTATION]# insert: <br />insert: <p>
% 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 insert: <br />
% "End User Assignment Agreement" and the company registration papers insert: <br />
% of the End User. insert: <br />
% You can also attach a network diagram or other supporting documentation. insert: <br />
% insert: <br />
% Have you attached any files/documents to this request? (Yes/No) insert: <br />
insert: <br />
file-attached: insert: <b> Yes insert: </b> insert: </pre>
For each IPv6 IXP 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: </p>
insert: <p>If this request is for an LIR or a “ insert: <tt> Direct Assignment User insert: </tt> ”, you do not have to attach a copy of 'End User Assignment Agreement' and company registration papers.
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.
delete: <h3> Supporting Documentation delete: </h3> insert: <p>insert: <a name="database"> insert: </a> insert: </p>
insert: <h2>Database Template(s) insert: </h2>
#[SUPPORTING DOCUMENTATION]# delete: <br /> delete: <br /> % If this request is being sent by a sponsoring LIR on behalf of an delete: <br /> % 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 /> delete: <br /> % Have you attached any files/documents to this request? (Yes/No) delete: <br /> file-attached: delete: <strong> Yes delete: </strong> #[DATABASE TEMPLATE(S)]# insert: <br />delete: <p> For each assignment that is requested through a sponsoring LIR for an IXP, we need to receive a copy of “End User Assignment Agreement” and the company registration papers of the End User. delete: </p> delete: <p> 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: </p> delete: <h3> Database Templates delete: </h3>
% insert: <br />
% Please complete all of the fields below.
#[IPv4 DATABASE TEMPLATE]# delete: <br /> delete: <br /> % If you are requesting IPv4, complete this IPv4 database template. delete: <br /> % If you are not requesting IPv4, please remove this IPv4 database delete: <br /> % template. delete: <br /> delete: <br /> inetnum: <leave empty> delete: <strong> delete: <br /> delete: </strong> inet6num: insert: <br />
netname: delete: <strong> insert: <b> RURIXP delete: </strong> insert: </b>
descr: delete: <strong> insert: <b> Ruritania IXP Ltd delete: </strong> insert: </b>
country: delete: <strong> insert: <b> NL delete: </strong> insert: </b>
org: delete: <strong> insert: <b> ORG-Bb2-RIPE delete: </strong> insert: </b>
admin-c: delete: <strong> HOHO15-RIPE delete: </strong> insert: <b> HOHO1-RIPE insert: </b>
tech-c: delete: <strong> HOHO15-RIPE delete: </strong> insert: <b> HOHO1-RIPE insert: </b>
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: delete: <strong> insert: <b> SANTA-MNT delete: </strong> insert: </b>
mnt-domains: delete: <strong> insert: <b> SANTA-MNT delete: </strong> insert: </b>
mnt-routes: delete: <strong> insert: <b> SANTA-MNT delete: </strong> delete: <br /> changed: [email protected] delete: <br /> source: RIPE delete: <br /> delete: <br /> #[IPv6 DATABASE TEMPLATE]# delete: <br /> delete: <br /> % If you are requesting IPv6, complete this IPv6 database template. delete: <br /> % If you are not requesting IPv6, please remove this IPv6 database delete: <br /> % template. delete: <br /> delete: <br /> inet6num: <leave empty> delete: <br /> netname: delete: <strong> RURIXP delete: </strong> delete: <br /> descr: delete: <strong> Ruritania IXP Ltd delete: </strong> delete: <br /> country: delete: <strong> NL delete: </strong> delete: <br /> org: delete: <strong> ORG-Bb2-RIPE delete: </strong> delete: <br /> admin-c: delete: <strong> HOHO15-RIPE delete: </strong> delete: <br /> tech-c: delete: <strong> HOHO15-RIPE delete: </strong> delete: <br /> status: ASSIGNED PI delete: <br /> mnt-by: RIPE-NCC-END-MNT delete: <br /> mnt-lower: RIPE-NCC-END-MNT delete: <br /> mnt-by: delete: <strong> SANTA-MNT delete: </strong> delete: <br /> mnt-domains: delete: <strong> SANTA-MNT delete: </strong> delete: <br /> mnt-routes: delete: <strong> SANTA-MNT delete: </strong> insert: </b>
changed: [email protected]
source: RIPE
If the IXP is requesting IPv4 and IPv6, please complete all templates. If not, you should complete the relevant template(s) and delete the rest when sending the request. delete: </p> delete: <p> Leave the "inetnum/inet6num" fields “ insert: <tt> inet6num: insert: </tt> ” field empty as we (the RIPE NCC) will choose the address range. complete it.
The “netname:” “ insert: <tt> netname: insert: </tt> ” should be a short, descriptive name for the network and should reflect the name of the organisation operating the IXP.
Enter the legal name of the organisation operating the IXP in the “descr:” “ insert: <tt> descr: insert: </tt> ” field.
Enter the ISO country code of the organisation in the “country:” “ insert: <tt> country: insert: </tt> ” field.
Enter the org-ID of the delete: <strong> insert: <b> organisation delete: </strong> insert: </b> object in the “org:” “ insert: <tt> org: insert: </tt> ” field. You can create delete: <strong> insert: <b> organisation delete: </strong> insert: </b> objects using 'webupdates'.
delete: <strong> insert: <b> Person delete: </strong> insert: </b> and delete: <strong> insert: <b> role delete: </strong> insert: </b> objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create delete: <strong> insert: <b> person delete: </strong> insert: </b> and delete: <strong> insert: <b> role delete: </strong> insert: </b> objects using webupdates.
The nic-hdl of the delete: <strong> insert: <b> role delete: </strong> insert: </b> or delete: <strong> insert: <b> person delete: </strong> insert: </b> object entered in the “admin-c:” “ insert: <tt> admin-c: insert: </tt> ” field should be for someone who has administrative responsibilities for the network.
The nic-hdl of the delete: <strong> insert: <b> role delete: </strong> insert: </b> or delete: <strong> insert: <b> person delete: </strong> insert: </b> object entered in the “tech-c:” “ insert: <tt> tech-c: insert: </tt> ” field should be for someone who has technical knowledge of the network.
The “status:” “ insert: <tt> status: insert: </tt> ” field must be insert: <tt> ASSIGNED PI. insert: </tt> .
Maintainers protect objects in the RIPE Whois Database. They contain the information needed to authorise creation, deletion or modification of these objects. You can create maintainers using the “Maintainer Editor” 'Maintainer Editor' ( delete: <a href="https://lirportal.ripe.net/"> insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net ).
One of the “mnt-by:” “ insert: <tt> mnt-by: insert: </tt> ” fields must be RIPE-NCC-END-MNT. insert: <tt> RIPE-NCC-END-MNT insert: </tt> . Enter the IXP's maintainer in the other “mnt-by:” “ insert: <tt> mnt-by: insert: </tt> ” field. The IXP will be able to update the delete: <strong> inetnum/inet6num delete: </strong> insert: <b> inet6num insert: </b> object using webupdates.
The “mnt-lower:” “ insert: <tt> mnt-lower: insert: </tt> ” field must be RIPE-NCC-END-MNT. insert: <tt> RIPE-NCC-END-MNT insert: </tt> .
The “mnt-domains:” “ insert: <tt> mnt-domains: insert: </tt> ” field shows which maintainer authorises the creation of delete: <strong> insert: <b> domain delete: </strong> insert: </b> objects for the assignment.
The “mnt-routes:” “ insert: <tt> mnt-routes: insert: </tt> ” field shows which maintainer authorises the creation of delete: <strong> route/route6 delete: </strong> insert: <b> route6 insert: </b> objects for the assignment.
All of the objects that you enter in the template must already exist in the RIPE Whois Database.
The “changed:” “ insert: <tt> changed: insert: </tt> ” field must be [email protected]. insert: <tt> [email protected] insert: </tt> .
The “source:” “ insert: <tt> source: insert: </tt> ” field must be RIPE. delete: </p> delete: <p> delete: <strong> insert: <tt> RIPE insert: </tt> . insert: </p>
insert: <p>insert: <a name="end"> insert: </a> insert: </p>
insert: <h2>End of Request delete: </strong> delete: </p> delete: <p> insert: </h2>
insert: <pre>#[END of REQUEST]# insert: <br />
insert: <br />
insert: <b> Best Regards, delete: </p> delete: <p> Jan Janssen, insert: <br />
John Smith, Bluelight Admin delete: </p> insert: </b> insert: </pre>
Please write your full name below the "#[END of REQUEST]#" “ insert: <tt> #[END of REQUEST]# insert: </tt> ” header.
