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