The current Charging Scheme model is based on the principle that members should have equal fees for each LIR they hold. This model has no categories and no differences in fees between LIRs: “One LIR, one fee”. The Executive Board proposes to continue with this model in 2014.

RIPE NCC Charging Scheme 2014

For 2014, the annual fee per LIR will be lowered by 3% to EUR 1,750 (EUR 1,800 in 2013). Based on existing RIPE Policy, the separate charge of EUR 50 per Provider Independent number resource assignment will be continued. Independent Internet number resources are: IPv4 and IPv6 PI assignments; Anycasting assignments; and IPv6 IXP assignments. AS Numbers are excluded from this separate charge.

The sign-up fee for new LIRs will be continued and will remain at EUR 2,000.

Comparison RIPE NCC Annual fees

Billing and Invoicing

The Independent Internet number resource information for members will be determined based on data gathered on 30 September 2013.

All members will be notified of their annual fee for 2014 by email in the last quarter of 2013. Invoices will be sent in January 2014.

1.0 Definitions

2.0 Introduction

3.0 Transfer of Internet Number Resource Records

3.1 Submission of the Request

3.2 If the Receiving Party is not yet a Member

3.3 Billing Issues

3.4 Internet Number Resource Registration and RIPE Database Issues

4.0 The Member Changes its Official Legal Name

1.0 Definitions

For the purposes of this document Internet Number Resource records refer to:

• The registered allocations and assignments of a Member
• The independent Internet Number Resources assigned through the Member as a “sponsoring LIR” to an End User

2.0 Introduction

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:

• The natural or legal persons holding the registration of Internet Number Resources
• The Internet Number Resource records that are registered to the natural or legal persons

This means that any transfer of Internet Number Resources from one party to another, or any change to the legal status of a party holding the registration of Internet Number Resources, must be communicated to the RIPE NCC.

The Member must inform the RIPE NCC if one or both of the following changes occurs:

1. Internet Number Resource records are transferred. Such transfers may take place:
   • Because of a change in the business structure of the Member, for example in the case of a merger or acquisition of the Member’s organisation; or
   • In the case of a pure transfer of an allocation from a Member to another Member according to RIPE Policies (section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region). Such a transfer may also be facilitated through the RIPE NCC Listing Service

1. The Member changes its official legal name. Such a change may occur, for example, because of a merger or acquisition of the Member’s organisation.

This document describes the procedures to be followed for such changes to be properly communicated to, and registered with, the RIPE NCC.

Note:

If a change in the Member’s official legal name is accompanied by a transfer of Internet Number Resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in the Member’s business structure is not accompanied by a transfer of Internet Number Resource records or a change in the Member’s official legal name, then the RIPE NCC does not need to be informed of this change.

3.0 Transfer of Internet Number Resource Records

If a Member transfers their Internet Number Resource records to a third party for any reason, this transfer must be declared to, and approved by, the RIPE NCC.

3.1 Submission of the Request for Transfer

One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed:

• If the transfer is due to a change in the business structure of the Member (e.g. merger or acquisition), the request must be submitted to ncc@ripe.net
• If the transfer is a transfer of allocation from one Member to another Member according to RIPE Policies (section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region), the request must be submitted to lir-help@ripe.net

A registered contact or an authorised person (e.g. senior manager, legal successor) must send the request.

The RIPE NCC will ask for the following information:

i. Information regarding the parties involved, including:

• The full official legal names of all parties involved
• Which party will transfer the Internet Number Resource records and which party will receive them
• Recent registration papers issued by the relevant national authorities for all involved parties

If the current official legal names of the involved Members are different from the ones in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described under section 4.0 must be followed prior to the transfer of the Internet Number Resource records. The procedure described under section 4.0 is not necessary for the transferring Member if the RIPE NCC Standard Service Agreement of the transferring Member is terminated (see Closure of LIR and Deregistration of Internet Number Resources, section A.1.1. and section A.1.2.).

ii. A description of the reason for the transfer (for example, due to merger, acquisition, or transfer of allocation according to the RIPE policies)

If the transfer is taking place due to a change in the structure of the organisation(s) involved, a description of the changes among the organisation(s) is necessary. The description must be accompanied by all official legal documents proving/supporting the changes the request is based on.

iii. A list of the Internet Number Resource records that are requested to be transferred. If all of the transferring Member’s Internet Number Resource records registered are being transferred, a confirmation of this is requested.

The Member must also indicate any End User assignment agreements that are requested to be transferred.

If a Member transfers all of their Internet Number Resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (see Closure of LIR and Deregistration of Internet Number Resources, section A.1.1.).

iv. The correct contact details of all organisations involved

The RIPE NCC may ask the organisations involved to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details.

v. A Transfer Agreement signed by both parties or by their legal successors

The RIPE NCC will make a template of the Transfer Agreement available. Either party may submit the Transfer Agreement to the RIPE NCC, signed by authorised persons for both parties. The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a contact person or authorised person (e.g. senior manager, legal successor).

If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:

• An official document (issued by a national authority) confirming the closure of the transferring party; and
• A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet Number Resource records. If such an agreement is not available, the receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g. senior manager, legal successor). The RIPE NCC reserves the right to reverse the transfer should another party object to this transfer and provide an agreement that proves that the Internet Number Resource records should have been transferred to them

vi. An overview of the utilisation of all allocations and of the status of all independent Internet Number Resource assignments

The RIPE NCC may ask for an overview of the utilisation of all Internet Number Resources registered to the Member and of all End User assignment agreements signed by the Member.

3.2 The Receiving Organisation is not yet a Member

Members may wish to transfer their Internet Number Resource records to another Member or to an organisation that is not yet a Member.

If the Internet Number Resource records are transferred to a non-Member, the receiving organisation can:

• Apply to be a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place (more information on how to become a Member is available); or
• Undertake all rights and obligations from the RIPE NCC Standard Service Agreement signed by the transferring Member. This might happen if all Internet Number Resource records are transferred. The transferring party is then no longer considered to be a Member

If the receiving organisation refuses to do either of the above, the RIPE NCC will not transfer the Internet Number Resource records to them.

The request for the transfer can be submitted as described in section 3.1.

3.3 Financial Consequences

All outstanding invoices and all outstanding financial obligations must be paid in full. If the RIPE NCC Standard Service Agreement is terminated in the course of the RIPE NCC financial year, the service fee for this Member must be paid for the full year. The payment is the responsibility of the receiving Member.

If the receiving organisation decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see RIPE NCC Charging Scheme).

3.4 Internet Number Resource Registration and RIPE Database Issues

The RIPE NCC will review the status of any IP address allocation or independent Internet Number Resource assignment maintained by the organisations involved in compliance with the RIPE Policies current at the time of the transfer.

The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The transferring Member must update all RIPE Database objects maintained by them that are related to this transfer.

4.0 The Member Changes its Official Legal Name

It is the obligation of the Member to inform the RIPE NCC immediately if any change in the Member’s official legal name occurs.

The Member must send an email to ncc@ripe.net informing the RIPE NCC of the name change. This email must include:

• New registration papers from the national authority; and
• The official legal documents supporting this change

The RIPE NCC will send a new RIPE NCC Standard Service Agreement for the Member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the Member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The Member must update all RIPE Database objects maintained by them that are related to this change.

Section B describes the valid reasons for deregistration of Internet number resources and the procedure that applies in each circumstance.

Table of Contents

A. Closure of Member – Termination of the RIPE NCC Standard Service Agreement

1. Grounds for termination and procedure in each case

1.1. Termination by the Member

1.2. Termination by the RIPE NCC

1.2.1. Termination with a three-month notice period

1.2.1.1. Violation of RIPE Policies and RIPE NCC procedures

a. Unresponsiveness

b. Allocations/assignments contravening RIPE Policies

c. Incorrect registration in the RIPE Database

d. Non-compliance with an arbiter ruling

1.2.1.2 Other reasons

1.2.2. Termination with immediate effect

a. Member files for bankruptcy, is liquidated, suspends its payments or becomes insolvent

b. Member damages the name, trademarks or intellectual property rights of the RIPE NCC

c. Member fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register

d. The Member fails to observe any rule of applicable law

e. Non-payment

f. Termination of the RIPE NCC member status

g. Untruthful information

h. Non-compliance with RIPE NCC audit

i. Discontinuation of RIPE NCC services

2. Consequences

2.1. End of provision of RIPE NCC services

2.1.1. General services

2.1.2. Registration of distributed Internet number resources

2.1.3. Request for independent Internet number resources as a “sponsoring LIR”

2.2. End of RIPE NCC member status

B. Deregistration of Internet number resources

1. Reasons for deregistration of Internet number resources - Allocations and Independent Internet number resources assigned for the Member’s own network or assigned through a “sponsoring LIR”

a. Termination of the SSA

b. Invalidity of original allocation/assignment criteria

c. Incorrect registration of the allocation/assignment in the RIPE Database

d. Falsified/incorret information

e. Fraudulent request

f. Non-compliance with a RIPE NCC audit

g. Court order

h. Independent Internet number resources assigned through a “sponsoring LIR” without a valid contractual relationship

2. Procedures for deregistration of different types of Internet number resources

2.1. Allocations and Independent Internet number resources for Member’s own network

2.2. Independent Internet number resources assigned through a “sponsoring LIR”

A. Closure of Member - Termination of the RIPE NCC Standard Service Agreement

An organisation or an individual person can receive services from the RIPE NCC if they:

• Agree and sign the RIPE NCC Standard Service Agreement (SSA); and

• Conform to RIPE Policies.

An organisation or an individual person signing the SSA is called a “Member”. The RIPE NCC SSA is entered into for an indefinite period of time, unless terminated by either party.

1. Grounds for termination and procedure in each case

The SSA can be terminated by the Member (see section 1.1) or by the RIPE NCC. The termination by the RIPE NCC can either be with a notice period of three months (see section 1.2.1.) or for specific reasons with a shorter notice period and immediate effect (see section 1.2.2.).

1.1. Termination by the Member

According to Article 9.2 of the SSA, the Member can terminate the SSA with a notice period of three months. Possible reasons why Members might want to terminate their SSA include:

• The Member decides to close or to change their business

• The Member decides to merge with another Member and therefore they do not need to be Members themselves

• The Member decides to assign Internet number resources from another Member

Procedure

The notice will formally request the termination of the SSA.

It must be:

• Dated and signed by an authorised representative of the Member. A registered contact cannot give notice unless the registered contact is an authorised representative.

• Sent to the RIPE NCC by email to <ncc@ripe.net> or by postal mail to: RIPE NCC, Singel 258, 1016 AB Amsterdam, The Netherlands.

The RIPE NCC will send an acknowledgement of the receipt of the notice. Upon receipt of such notice, the progress of any open requests for RIPE NCC services is terminated.

The termination of the SSA will take place three months after the receipt of the notice by the RIPE NCC.

Billing issues

If the termination takes place in the course of a financial year, the annual contribution shall nevertheless remain due in full by the Member (see also paragraph 6.6 of the RIPE NCC Articles of Association (AoA) and the RIPE NCC Billing Procedure).

1.2. Termination by the RIPE NCC

1.2.1. Termination with a three-month notice period

According to Article 9.3 of the SSA, the RIPE NCC can terminate the SSA with a notice period of three months. Grounds for such termination may be the following:

1.2.1.1 Violation of RIPE Policies and RIPE NCC procedures

The Member must comply with RIPE Policies and RIPE NCC procedures (see Article 6 of the SSA). The RIPE NCC will terminate the SSA if the Member commits any of the following violations of RIPE Policies or RIPE NCC procedures:

1. Unresponsiveness

   The Member is unresponsive for a significant period of time.

   Members are considered to be unresponsive if they do not react to a specific email/request made by the RIPE NCC relating to an incorrect/ambiguous registration of Internet number resources, regardless of whether they are at the same time responsive to a different email/request from the RIPE NCC or they continue paying the RIPE NCC fees.

2. Allocations/assignments contravening RIPE policies

   Allocations or transfers of allocations and assignments are not made and used in accordance with the RIPE community’s policies.

3. Incorrect registration in the RIPE Database

   Registration data is repeatedly maintained incorrectly (allocations and assignments must be properly registered in the RIPE Database).

   Proper registration must be as follows:

   • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC

   • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC

   • The data must be valid and must allow the RIPE NCC to contact the natural person referenced directly in the inetnum or inet6num object(s) or via the maintainers of the inetnum or inet6num object(s) within a reasonable time without having to get information from another source

4. Non-compliance with an arbiter ruling

   For more information, please see RIPE NCC Conflict Arbitration Procedure.

Procedure

If the RIPE NCC becomes aware of any of the aforementioned reasons for terminating the SSA, the RIPE NCC will:

• Send an email to the registered contact(s) indicating:

• the violation

• the Member’s obligation to stop/repair the violation

• the termination of the SSA in three (3) months if the violation continues

• Terminate the progress of any open requests for RIPE NCC services

If the Member does not comply within 30 days of the date of the email, the RIPE NCC will send a reminder email to the registered contact(s) indicating:

• The violation

• The Member’s obligation to stop/repair the violation

• The termination of the SSA in two (2) months if the violation continues

After 60 days from the date of the first email, if the Member still does not comply, the RIPE NCC will send a second reminder email and a reminder by postal mail to the registered email and email addresses indicating:

• The violation

• The Member’s obligation to stop/repair the violation

• The termination of the SSA in one (1) month if the violation continues

After 90 days from the date of the first email, if the Member continues not to comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

The RIPE NCC concludes the SSA and provides services to Members in good faith. The Member is in breach of good faith in the following cases:

1.2.1.2. Other reasons

Termination for any other reason by the RIPE NCC is only executed when the Member consents to the termination, unless the termination is for reasons above and beyond control of the RIPE NCC.

For example, such termination has taken place in the past in the case of the emergence of AfriNIC, the RIR for the African region, when, with the consent of the African Members, the SSAs with the RIPE NCC were terminated and new contracts with AfriNIC were signed.

Procedure

The notice will officially inform about the termination of the SSA, state the reasons for the termination and detail the planned arrangements regarding the Internet number resources that were distributed to the Member.

Unless otherwise required by the circumstances:

• The RIPE NCC will terminate the progress of any open requests for RIPE NCC services

• Section A.2. (Consequences of termination of the SSA) and section B (Deregistration of Internet number resources) of this document are applicable

The notice will be dated and signed by an authorised representative of the RIPE NCC.

Notice will be sent to the registered contact(s) of the Member by electronic and postal mail.

Upon receipt of such notice, the progress of any open requests for RIPE NCC services is terminated. The termination of the SSA will take place after three months from the date the RIPE NCC sends the notice, unless the Member requests a longer period and this is agreed upon.

Billing issues

All outstanding amounts for the full year must be settled unless otherwise agreed.

1.2.2. Termination with immediate effect

According to Article 9.4 of the SSA, the RIPE NCC is entitled to terminate the SSA with immediate effect in the following cases:

1. Member files for bankruptcy, is liquidated, suspends its payments or becomes insolvent

   Upon receipt of the documents stating the bankruptcy, liquidation, suspension of payments or insolvency of the Member

   by the relevant authority or by public announcement of the fact, the RIPE NCC will terminate the SSA. If the relevant national authority decides that the Member’s operations can continue, and provided that the Member fulfills the obligations coming from the SSA, the RIPE NCC will not terminate the SSA.

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) and/or to the legal successor indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the member) to all registered contacts of the Member or to the legal successor, both by electronic and registered postal mail.

2. Member damages the name, trademarks or intellectual property rights of the RIPE NCC

   Examples:

   • The Member pretends to be, or to act on behalf of, the RIPE NCC through misuse of the RIPE NCC name or logo

   • The Member unreasonably makes allegations against the RIPE NCC in order to damage the RIPE NCC’s reputation and operations, resulting in irreversible damage to the RIPE NCC

   Procedure:

   The RIPE NCC will

   • Send an email to the registered contact(s) indicating:

     • the violation

     • the Member’s obligation to stop/repair the violation

     • the termination of the SSA if the violation continues

   • Terminate the progress of any open requests for RIPE NCC services

   If the Member does not comply within 30 days of the date of the email, the RIPE NCC will send a reminder email to the registered contact(s) indicating the same as above.

   After 60 days from the date of the first email, if the Member still does not comply, the RIPE NCC will:

   • Send a second reminder email to the registered contact(s) indicating the same as above

   • Not approve any Internet number resource requests

   After 90 days from the date of the first email, if the Member continues not to comply, the RIPE NCC will:

   • Send a third reminder email and a reminder by postal mail to the registered email and postal addresses indicating the same as above

   • Stop providing any services to the Member

   After 120 days from the date of the first email, if the Member still does not comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

3. Member fails to submit to the RIPE NCC a valid extract from the Commercial Trade Register or equivalent register

   When initially signing the SSA, the Member must submit to the RIPE NCC an extract from the Commercial Trade Register or equivalent document providing the registration of the Member’s business with the national authorities (see Article 2.2 of the SSA).

   If the Member is a natural person, the RIPE NCC requires submission of any identification papers (passport, driving license or other official document proving the identity of the individual).

   If the Member is a legal person, identification papers are also required for the authorised person signing the SSA on behalf of the legal person.

   If there is any change in the Member’s business after signing the SSA (for example, the Member has merged with another company, has changed name, etc.) and, because of this change, the Member’s registration with the relevant register has been changed, then the Member is obliged to submit the updated registration papers to the RIPE NCC.

   If the Member does not submit the aforementioned documents within one month of them being requested by the RIPE NCC, the RIPE NCC will terminate the SSA (see Article 9.4.d of the SSA).

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • the Member’s obligation to submit the relevant documents

     • the termination of the SSA if the documents are not submitted

   • Terminate the progress of any open requests for RIPE NCC services

   If the Member does not comply within 15 days of the date of the email, the RIPE NCC will send a reminder email and a notification by postal mail to the registered email and postal addresses indicating the same as above.

   After 30 days from the date of the first email, if the Member continues not to comply, the RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

4. The Member fails to observe any rule of applicable law

   The SSA is exclusively governed by the laws of the Netherlands because the RIPE NCC is an association under Dutch law. The RIPE NCC is allowed to terminate the SSA of a Member with immediate effect, provided it receives a Dutch court order to do so.

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

5. Non-payment.

   In case of non-payment, in accordance with the RIPE NCC Billing Procedure, the SSA is terminated after 120 days. For more information, please see the RIPE NCC Billing Procedure.

6. Termination of the RIPE NCC member status

   By signing the SSA, Members become members of the RIPE NCC association. If Members terminate their member status with the RIPE NCC association, the SSA is automatically terminated (see also Article 6 of the AoA).

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

7. Untruthful information
   

   The RIPE NCC concludes the SSA and provides services to Members in good faith. The Member is in breach of good faith in the following cases:

   • Falsified/incorrect information

   If the Member repeatedly provides falsified data or information, or purposefully and/or repeatedly provides incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.)

   • Fraudulent requests

   If the Member submits repeatedly fraudulent requests for Internet number resources (for example, providing incorrect purpose/need or falsified information about the network, etc.)

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

8. Non-compliance with RIPE NCC audits
   

   Non-compliance with RIPE NCC audits includes repeated unresponsiveness to or failure to cooperate with the RIPE NCC auditors’ requests regarding registrations of Internet number resources for the Member’s own network. For more information about the audit procedure, please see RIPE NCC audit activity.

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

9. Discontinuation of RIPE NCC services
   

   If the RIPE NCC cannot reasonably be required to continue the SSA for reasons that can not be attributed to the RIPE NCC and for which the RIPE NCC cannot be held accountable by virtue of law, a juridical act or generally accepted principles.

   Procedure

   The RIPE NCC will:

   • Send an email to the registered contact(s) indicating:

     • The reason for termination of the SSA

     • The immediate termination of the SSA

   • Terminate the progress of any open requests for RIPE NCC services

   The RIPE NCC Managing Director will send an official notification of termination of the SSA (i.e., closure of the Member’s account) to all registered postal and email addresses of the Member.

2. Consequences

Upon termination of the SSA, Members lose all rights to RIPE NCC services and their RIPE NCC member status.

2.1. End of provision of RIPE NCC services

2.1.1. General services

The RIPE NCC will stop providing RIPE NCC services, including:

• Distribution of Internet number resources

• Authority to maintain Internet number resource records in the RIPE Database

• Access to the LIR Portal

• Use of the RIPE NCC Certification Service

• Participation in RIPE NCC Training Courses

2.1.2. Registration of distributed Internet number resources

The RIPE NCC will deregister the relevant Internet number resource records. The procedure for deregistration is described in section B.2. The RIPE NCC will also revoke any certificates generated by the RIPE NCC Certification Service.

2.1.3. Request for independent Internet number resources as a “sponsoring LIR”

Members lose their right to request independent Internet number resources as a “sponsoring LIR”. For independent Internet number resources already assigned by them, see below at section B.2.2.

2.2. End of RIPE NCC member status

Members will also lose their RIPE NCC member status and all relevant rights, such as the right to attend and vote at RIPE NCC General Meetings.

B. Deregistration of Internet Number Resources

1. Reasons for deregistration of Internet number resources - Allocations and Independent Internet number resources assigned for the Member’s own network or assigned through a “sponsoring LIR”

1. Termination of the SSA

   For more information, see section A. For Independent Internet number resources through a “sponsoring LIR”, see Independent Internet Number Resources – Contractual Relationship Changes between Sponsoring LIR and End User.

2. Invalidity of original allocation/assignment criteria

   Internet number resources are allocated/assigned based on a specific need. When the original technical requirements or the business purpose for the use of the Internet number resources change, the allocation/assignment becomes invalid. If the RIPE NCC notices any change in the original technical criteria or the original business purposes for using the Internet number resources, the RIPE NCC is authorised to deregister the relevant Internet number resources.

3. Incorrect registration of the allocation/assignment in the RIPE Database

   If the allocation/assignment approved by the RIPE NCC is not properly registered in the RIPE Database, the RIPE NCC is authorised to deregister the relevant Internet number resources.

   Proper registration must be as follows:

   • The inetnum and the inet6num object(s) for approved assignments must use the netname(s) approved by the RIPE NCC and not be larger than the size approved by the RIPE NCC

   • The date in the first “changed:” attribute must not be earlier than the date of approval from the RIPE NCC

   • The data must be valid and must allow the RIPE NCC to contact the natural person mentioned directly in the inetnum or inet6num object(s) or via the maintainers of the inetnum or inet6num object(s) object within a reasonable time without having to get information from another source

4. Falsified/incorrect information

   If a Member has provided falsified data or information, or purposefully provided incorrect data or information (for example, falsified registration documents or IDs, incorrect/inaccurate contact details, etc.) regarding an allocation or an Independent resource, the RIPE NCC will deregister the relevant records.

5. Fraudulent request

   If a Member has submitted a fraudulent request for an allocation or an Independent resource (for example, by providing incorrect purpose/need or falsified information about the network, etc.), the RIPE NCC will deregister the relevant records.

6. Non-compliance with a RIPE NCC audit

   If a Member does not comply with a RIPE NCC audit regarding the registration of an Independent resource that the Member is responsible for as “sponsoring LIR”, the RIPE NCC will deregister the relevant records. Non-compliance includes, but is not limited to, unresponsiveness to or failure to cooperate with the RIPE NCC auditors’ requests. For more information about the audit procedure, please see RIPE NCC Audit Activity.

7. Court order

   The RIPE NCC is an association under Dutch law. In the event a Dutch court orders deregistration of specific Internet number resources, the RIPE NCC must and will comply.

8. Independent Internet number resources assigned through a “sponsoring LIR” without an valid contractual relationship

   See Independent Internet Number Resources – Contractual Relationship Changes between Sponsoring LIR and End User.

2. Procedures for deregistration of different types of Internet number resources

2.1 Allocations and independent Internet number resources for Member’s own network

The RIPE NCC will send an official notification by email to all registered contacts stating that the allocation/independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure of the deregistration. The Member will not be able make any further assignments from the allocations.

Should the Member respond within four weeks, the RIPE NCC will provide a timeframe of three months for the Members to take care of any actions necessary for the deregistration of the Internet number resources. In the case of allocations, Members are responsible for requesting that their customers renumber immediately and for providing them with all available options. In particular, Members must refer their customers to the list of other Members. This list is available at:

http://www.ripe.net/membership/indices

During the three-month period:

• The Member must stop announcing the allocation/independent Internet number resources

• The RIPE NCC will change the mnt-by object on the Member’s records to the status “deregistered maintainer”

• A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources

• The RIPE NCC will revoke any certificates generated by the RIPE NCC Certification Service

After the three-month period, the allocation/assignment will be deregistered from the RIPE Database.

Should the Member not react within four weeks, the RIPE NCC will:

• Change the mnt-by object on the Member’s records to the status “deregistered maintainer”; and/or

• Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or

• Withdraw the reverse delegation; and/or

• Contact the upstream to investigate possible hijacking of Internet number resources; and/or

• Delete all relevant objects in the RIPE Database, including allocation/assignment and route objects

• Revoke any certificates generated by the RIPE NCC Certification Service.

The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.

Please note:

If the Member responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for the deregistration of the Internet number resources or to request arbitration (see RIPE NCC Conflict Arbitration Procedure). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the mnt-by object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter’s ruling.

2.2 Independent Internet number resources assigned through a “sponsoring LIR”

The RIPE NCC will send an official notification to all registered contacts stating that the Independent Internet number resources will be deregistered, explaining the reasons for this deregistration and the procedure for the deregistration. The Member must immediately inform the End User about the imminent deregistration.

During this period:

• The End User must stop announcing the Independent Internet number resources

• The RIPE NCC will change the mnt-by object on the relevant records to the status “deregistered maintainer”

• A warning statement is added to the relevant records of the RIPE Database mentioning the upcoming deregistration of the Internet number resources

After the three-month period, the independent Internet number resources will be deregistered from the RIPE Database.

Should the Member not react within four weeks, the RIPE NCC will:

• Change the mnt-by object on the relevant records to the status “deregistered maintainer”; and/or

• Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the Internet number resources; and/or

• Withdraw the reverse delegation; and/or

• Contact the upstream to investigate possible hijacking of Internet number resources; and/or

• Delete all relevant objects in the RIPE Database, including allocation/assignment and route objects

The sole purpose of these actions by the RIPE NCC is for deregistration of the Internet number resources to reflect reality. As a result, if the Internet number resources are no longer announced after one of these actions, the RIPE NCC might not perform any other actions.

Please note:

If the Member responds but with no intention to comply or objects at some point within the four-week period, the RIPE NCC will allow the time remaining in this four-week period for the Member to submit evidence that there is no reason for deregistration of the Internet number resources or to request arbitration (see RIPE NCC Conflict Arbitration Procedure). However, if the four-week period expires without the submission of such evidence by the Member or without the submission of a request for arbitration, the RIPE NCC will proceed as if the Member had never reacted (see relevant procedure above). The Member may still request arbitration according to the timeframes of the RIPE NCC Conflict Arbitration Procedure. If the Member requests arbitration, the RIPE NCC will change the mnt-by object on the relevant records to the status “maintainer in dispute” and a warning statement will be added to the relevant records of the RIPE Database until the communication of the arbiter’s ruling.

NOTE: This document might change due to future policy changes. If this happens, the RIPE NCC will send a notification to the RIPE NCC Services Working Group mailing list.

The purpose of the RIPE NCC Charging Scheme is to generate sufficient income for the operations of the RIPE NCC in a stable and predictable manner. The Charging Scheme defines the annual fee per LIR charged to members and sets the sign-up fee for new members.

The Charging Scheme model is based on the principle that members should have equal fees for each LIR they hold. This model has no categories and no differences in fees between LIRs: one LIR, one fee.

Based on existing RIPE Policy, the separate charge of EUR 50 per Provider Independent number resource assignment will be continued. Independent Internet number resources are IPv4 and IPv6 PI assignments, Anycasting and IPv6 IXP assignments. Contrary to previous years, AS Numbers are excluded from this separate charge.

Non-members that are currently charged fees for using specific services such as DNSMON and NRTM, as well as Direct Assignment Users, must also become members, paying the same standard fee per LIR as other members. Organisations that wish to support the RIPE NCC or particular activities should also become members.

The sign-up fee for new LIRs will be continued and will remain at EUR 2,000.

Comparison RIPE NCC Annual fees 2007 - 2013

The Independent Internet number resource information for members will be determined based on data from 30 September 2012. Every LIR will be notified of their annual fee for 2013 by email.

Change matrix for categories

All members will merge into one category. Below is an overview of the changes in fee for existing LIRs:

* This table excludes the additional fee for Provider Independent resources

This document describes the modifications that might be made to a contractual relationship between a sponsoring LIR and an End User of independent Internet number resources as well as the possible consequences of such changes or of failure to communicate these changes to the RIPE NCC. This document does not describe any procedures applicable to contractual relationship changes for users of independent Internet number resources who have a contractual relationship directly with the RIPE NCC. Nor does it describe the deregistration of independent Internet number resources for any reason other than contractual relationship changes. For information on deregistration of independent resources for any other reason, please see the RIPE NCC procedural document, Closure of LIR and Deregistration of Internet Number Resources.

1. Change in End User’s Business Structure

When the End User and the sponsoring LIR initially sign a contract, the sponsoring LIR must submit to the RIPE NCC an extract from the Commercial Trade Register or an equivalent document proving the registration of the End User’s business with the relevant national authorities (see also the RIPE NCC procedural document, Due Diligence for the Quality of the RIPE NCC Registration Data).

If the End User is a natural person, the sponsoring LIR must submit the identification papers of the End User. This can be a passport, driving license or other official document proving the identity of the individual (see also the RIPE NCC procedural document, Due Diligence for the Quality of the RIPE NCC Registration Data).

If there is any change in the End User’s business structure after signing the contract with the sponsoring LIR (for example, the End User has merged with another company or has changed name), and, because of this change, the information held by the RIPE NCC on the End User is not up-to-date, then the sponsoring LIR is obliged to submit the updated/new registration papers of the End User to the RIPE NCC, as well as any documents verifying this change.

Procedure

The sponsoring LIR must send an email to lir-help@ripe.net informing the RIPE NCC of the End User’s business change. This email must include new registration papers from the national authority and the official legal documents supporting this change.

The RIPE NCC will update all RIPE Database objects maintained by the RIPE NCC that are affected by this change. End Users must update all RIPE Database objects that they maintain themselves that are affected by this change.

If the sponsoring LIR does not submit the aforementioned documents within 10 working days of the RIPE NCC requesting them, the RIPE NCC will send a reminder to the sponsoring LIR’s contact email addresses and to the End User’s contact email addresses as listed in the relevant RIPE Database object, asking the sponsoring LIR to submit the requested documents within 10 working days of the day of the reminder.

If the RIPE NCC has not received the requested documents 10 working days from the date of the reminder, the RIPE NCC will begin deregistering the Independent Internet number resources according to the procedure described in the RIPE NCC procedural document Closure of LIR and Deregistration of Internet Number Resources (section B.2.2).

2. Termination of Contractual Relationship

An End User of Independent Internet number resources must have a contractual relationship with a sponsoring LIR at all times. If the contractual relationship between the End User and the sponsoring LIR is terminated for any reason, the RIPE NCC must be notified. The End User must at that point enter into a contractual relationship with a different sponsoring LIR or with the RIPE NCC directly.

Procedure

Preferably, for registration purposes, the RIPE NCC must be notified before the contractual relationship terminates. It is the responsibility of the sponsoring LIR to submit this notification to the RIPE NCC prior to termination.

If the RIPE NCC has not been notified prior to the termination and the End User has already entered into a new contractual relationship with a different sponsoring LIR, this new sponsoring LIR must notify the RIPE NCC and submit the new contract they signed with the End User. The RIPE NCC will notify the previous sponsoring LIR of this change. Should the previous LIR object to the termination of their contract with the End User, the RIPE NCC will only accept the contract of the sponsoring LIR that submits a confirmation signed by the End User. This confirmation must clearly state that the End User has or has not terminated the contractual agreement with the previous sponsoring LIR.

The End User may also enter into a contractual relationship directly with the RIPE NCC. For more information, please see:

https://www.ripe.net/lir-services/resource-management/direct-assignments

If the RIPE NCC is informed of the termination of the contractual relationship between the sponsoring LIR and the End User and, after 10 working days, no new contractual relationship has been established between the End User and a different sponsoring LIR or the RIPE NCC, the RIPE NCC will send a notification to the End User’s contact email addresses, as listed in the relevant RIPE Database object, asking the End User to sign a new contractual agreement with another sponsoring LIR within 10 working days of the day of the notification or to sign an agreement directly with the RIPE NCC.

If the RIPE NCC has not received a new contractual agreement 10 working days from the date of the notification, the RIPE NCC will start deregistering the independent Internet number resources according to the procedure described in the RIPE NCC procedural document, Closure of LIR and Deregistration of Internet Number Resources (section B.2.2).

3. Closure of Sponsoring LIR

If the sponsoring LIR has their RIPE NCC Standard Service Agreement terminated, the RIPE NCC will send a notification to the End User’s contact email addresses, as listed in the relevant RIPE Database object, asking the End User to sign a new contractual agreement with another sponsoring LIR or with the RIPE NCC within 10 working days of the notification.

If the End User does not submit a new contractual agreement with another sponsorship LIR within 10 working days of the RIPE NCC requesting them, the RIPE NCC will send a reminder to the End User’s contact email addresses as listed in the relevant RIPE Database object, asking the sponsoring LIR to submit the requested documents within 10 working days of the day of the reminder.

If the RIPE NCC has not received a new contractual agreement 10 working days from the date of the reminder, the RIPE NCC will begin deregistering the independent resources according to the procedure described in the RIPE NCC procedural document, Closure of LIR and Deregistration of Internet Number Resources (section B.2.2).

The RIPE Network Coordination Centre (RIPE NCC) is an independent, not-for-profit membership organisation that serves a membership base of over 8,500 members in 75 countries across Europe, the Middle East and parts of Central Asia. It supports the operations of its members and the activities of network operators throughout its service region, specifically activities that require a neutral, impartial and authoritative organisation.

In addition to running a strong, reliable Regional Internet Registry, and associated tools such as the RIPE Database and the LIR Portal, the RIPE NCC provides a range of other services to support the operations of its members. These services offer a complete view of the real-time or historical, state of any IP address range as well as a global network for testing reachability from thousands of nodes. The RIPE NCC also provides training courses such as an introductory course in requesting address space and managing Internet number resources.

While the registry activities and services provided by the RIPE NCC are focused on offering services that support its members’ operations, the coordination activities serve the membership and the Internet community at large by supporting critical elements of the Internet’s infrastructure and policy development. As well as operating the K-root server, and providing a range of important DNS services, the RIPE NCC organises RIPE Meetings and a range of regional, government and law enforcement meetings. These meetings, and the RIPE NCC’s outreach activities in general, are part of efforts to support the RIPE Policy Development Process and to ensure the involvement of all stakeholders from across the public and private sector.

An important aspect of the RIPE NCC’s work in this respect is to ensure that government representatives have an informed understanding of the policy and technical processes that are responsible for the success of the Internet. These relationships, established through Roundtable Meetings, participation in OECD and UN working groups and at the Internet Governance Forum (IGF), enable the RIPE NCC to represent the interest of its members and the RIPE community and to promote the robust community-driven processes that underlie the success of the RIPE NCC and the RIPE community.

At the same time, in conjunction with its registry activities and services, the RIPE NCC strives to maintain the stable registration and distribution of Internet number resources and to provide useful tools, services and coordination activities that support the businesses of its members and the technical coordination of the Internet.

In all these processes, the RIPE NCC relies on the input it receives from its members and those in the RIPE community to ensure the organisation is best placed to meet its stakeholders’ needs.

Activity Plan Process

Since its inception the RIPE NCC has run an open and transparent process regarding its activities and budget. A variety of feedback mechanisms are utilised throughout the year to gather membership and community input on activities that the RIPE NCC carries out. These feedback mechanisms include, but are not limited to: the RIPE NCC Membership and Stakeholder Survey; the RIPE NCC Services Working Group; RIPE Meetings; Regional Meetings. The input that is received is then incorporated by the RIPE NCC Management into its strategy for the following year. In line with good Corporate Governance, this strategy is then discussed at length with the RIPE NCC Executive Board who then develop and produce the draft Activity Plan and Budget published in advance of the Autumn General Meeting for further discussion. Following the discussion that takes place on the relevant mailing lists and at the General Meeting, the RIPE NCC Executive Board make any necessary amendments before they formally approve the final Activity Plan and Budget, which is published annually in December.

This is an ongoing process that provides all RIPE NCC members with opportunities for providing feedback on the RIPE NCC's strategy, activities and budget. Ultimately the RIPE NCC Executive Board, which is made up of five representatives elected by RIPE NCC members, approve the final Activity Plan and Budget. The membership is able to express their confidence in the individuals on the Executive Board by voting for their preferred candidates during Executive Board elections at RIPE NCC General Meetings.

Overview of RIPE NCC Costs per Activity 2013

Below is an overview of the Full-Time Equivalents (FTEs), operational expenses (OPEX) and capital expenses (CAPEX) per activity. All amounts are in kEUR. The overview is presented on two levels. It is possible to click on any level 1 or level 2 activity for more detailed information.

* RIPE NCC strategic focus point for 2013

Notes on Overview of RIPE NCC Activities

FTE

Full-Time Equivalents (FTEs) are given to one decimal place for Level 2 activities and rounded to a whole number for Level 1 activities. These figures include both the personnel dedicated to each activity as well as supporting staff.

OPEX (Operational Expenses)

Operational expenses are all direct costs that relate to the activity / project and a portion of overhead that is related to absence (vacation, illness, education) that has been allocated to the project. The overhead allocation is based on the percentage of FTEs involved in the activity divided by the overall FTEs. Operational expenses exclude depreciation and bad debts expenses.

CAPEX (Capital Expenditure)

Capital expenses are all items that are taken as an asset. These items include hardware and software, infrastructure, office furniture and software development. Hardware and software consists of hardware and purchased activated software. All items under EUR 500 are expensed, as is required by the tax code. Intangible fixed assets includes only in-house software development. Software development costs are capitalised insofar as they are incurred in respect of potentially valuable projects and are stated at costs. These costs comprise the costs of direct labour as well as outsourced consultancy costs.

RIPE NCC Activities 2013

1) Regional Internet Registry

*** 1.1 Registry Maintenance *** STRATEGIC FOCUS POINT 2013

Since 1992, the RIPE NCC has been responsible for distributing Internet number resources in its service region. One of the organisation’s key responsibilities is the strength and quality of the Internet number resources registry associated with the distribution of these resources.

With the exhaustion of unallocated IPv4 address space, the RIPE NCC will ensure that it continues to fulfill its stewardship duties by adapting its registry function appropriately. This will involve a focus on legacy address space to ensure that it is accurately registered in the RIPE NCC registry. At the same time, the registry will be evolved to ensure that it can accurately deal with the transfer of IPv4 space, a scenario that has become increasingly likely given the scarcity of unallocated IPv4 address space.

With the exhaustion of the unallocated IPv4 address pool, there will be increased scrutiny on the processes involved in IP address space allocation, the possibility of a growing demand for resource transfers and an increased potential for conflicts over address space. Given these developments, the RIPE NCC will continue to provide a robust and authoritative registry at the same time as responding to any community-driven initiatives for increasing the accuracy and range of data stored in the registry of Internet number resources.

The accuracy of this data, vital for day-to-day network operations, is also of increasing importance to governments, regulators and law enforcement agencies. In ensuring that this data is comprehensive, accurate and up-to-date, the RIPE NCC’s registry function will not only support these stakeholders and its members but will also provide invaluable authoritative data for future Internet coordination, statistical and research activities. The RIPE NCC will continue work to measure, monitor and enhance the data quality of Internet number resource registrations. The focus here will be on the legacy address space allocated before the Regional Internet Registry (RIR) system existed. The goal of these activities will be to bring legacy space registration records up to the same standards of accuracy as address space distributed by the RIPE NCC since 1992.

A range of services, such as the Certification system and enhanced audit activities, will provide an incentive for holders of such space to make sure that their Internet number resources are accurately registered in the registry. The focus will be on tools and value-added services that the RIPE NCC can provide to its members to improve both their day-to-day operations and the accuracy of the registration data of Internet number resources in the RIPE NCC registry.

The RIPE NCC will also continue to work with the other RIRs to increase data quality and to make this improved data readily available to the Internet community.

Benefits for RIPE NCC members / RIPE community:

• Improves the accuracy and range of data stored in the registry of Internet number resources

• Enables the registry to evolve so that it can deal with changes resulting from the exhaustion of the unallocated IPv4 address pool

• Improves the accuracy of legacy address space registration records

1.1.1 Distribution and Management of Internet Number Resources

In its role as a Regional Internet Registry (RIR), the RIPE NCC provides allocation and registration services to Local Internet Registries (LIRs) in Europe, the Middle East and parts of Central Asia. The overall goal of the RIPE NCC’s allocation and registration services is to provide fair, impartial and stable distribution of Internet number resources in its service region.

Benefits for RIPE NCC members / RIPE community:

• Provides a fair, impartial distribution of Internet number resources guided by policies developed by the RIPE community

• Ensures the uniqueness of IP addresses, aggregation of routing information and the conservation of IP address space

• Implements the necessary procedures to enable the processes defined in the policies developed by the RIPE community

• Enables the accurate registration of network management and contact information

1.1.2 IPv4 / IPv6 Address Space and Autonomous System (AS) Numbers

The RIPE NCC allocates and assigns Internet number resources according to RIPE community policy. The RIPE NCC allocates and assigns IPv4 and IPv6 address space to RIPE NCC members. The RIPE NCC also assigns AS Numbers and registers these numbers and the initial associated routing policy, ensuring the uniqueness of AS Numbers and collecting data for the Routing Registry. From 2007, the RIPE NCC has assigned AS Numbers from both the 16-bit and 32-bit pools.

Benefits for RIPE NCC members / RIPE community:

• Enables the fair distribution of Internet number resources

• Promotes the efficient use of IP address space and AS Numbers

• Facilitates the optimal aggregation of routing information

• Supports members with the relevant processes and procedures

1.1.3 Auditing

For 2013, the RIPE NCC will increase the number of annual audits it performs from the current figure of 400 to around 2,000. Currently, the audit process focusses on the correctness of registry and RIPE Database data and compliance with policies related to Internet number resources in use. In 2013, the audit activity will become more detailed in order to provide added value to the RIPE NCC membership. Audits will look at reverse DNS setup and RIPE Database entries. They will also use RIPE Atlas in order to determine the reachability of a particular network and will check for Certification usage and consistency.

Benefits for RIPE NCC members / RIPE community:

• Enables the fair and neutral application of policies set by the RIPE community

• Educates RIPE NCC members on how to achieve compliance with RIPE Policies

• Offers added value to RIPE NCC members by providing an overview of how their networks are perceived by an independent entity

1.1.4 Data Accuracy

For 2013, the RIPE NCC will continue work to implement the RIPE Policy related to establishing an indirect or a direct contractual link between the End Users of Provider Independent (PI) address space and the RIPE NCC (ripe-452). The RIPE NCC will also continue work on registering legacy Internet number resources that were allocated before the current RIR system was in place.

Benefits for RIPE NCC members / RIPE community:

• Keeps the data in the RIPE Registry as current, complete and correct as possible

• Ensures that Internet number resources are registered to the legitimate End Users, possibly Legacy resource holders

1.1.5 Filtered Resource Assistance

The RIPE NCC offers assistance to members whose IP address space is being filtered.

Benefits for RIPE NCC members / RIPE community:

• Helps members understand who is filtering their address space and what can be done to have these filters updated

• Assists members in contacting the party that is filtering the relevant IP address space so that the filters can be updated

1.1.6 Listing Service

The Listing Service facilitates the transfer of IPv4 PA address space between RIPE NCC members according to the IPv4 Address Allocation and Assignment Policies for the RIPE NCC service region.

Benefits for RIPE NCC members / RIPE community:

• Allows holders of unused IPv4 PA allocations to voluntarily re-allocate complete or partial blocks of their allocated IPv4 address space to entities that have a demonstrated need for IPv4 addresses

1.1.7 Resource transfers between Sponsoring LIRs

Subject to the RIPE Policy on contractual requirements for PI resource holders (ripe-452), the RIPE NCC facilitates the transfer of independent Internet number resources from a sponsoring LIR to a new sponsoring LIR.

Benefits for RIPE NCC members / RIPE community:

• Enables transfers between sponsoring LIRs

• Helps to improve the accuracy and currency of the RIPE Registry

• Enhances independence of address holder from sponsoring LIR

1.1.8 Reputation Service

This new service will show RIPE Database users the last time each object was audited either by the RIPE NCC or by the LIR itself. A feature will be added to the LIR Portal in 2013 that will enable LIRs to ‘self-audit’ their objects and to easily perform mass updates.

Benefits for RIPE NCC members / RIPE community:

• Provides an incentive and an easy way for LIRs to keep their RIPE Database objects up to date

• Increases the accuracy of the RIPE Database

1.1.9 History of RIPE Database Object Updates

The RIPE NCC checks for unauthorised changes in RIPE Database objects for which it is administratively responsible (mainly independent Internet number resources).

Benefits for RIPE NCC members / RIPE community:

• Provides active investigation of the reason for unauthorised changes to RIPE Database objects, helping to improve the correctness of data in the registry

• Educates LIRs in the case of a mistaken update, de-registration, RIPE Policy violation or updates related to transfers of resources

• Contributes to maintaining a correct and accurate RIPE Registry

1.1.10 Resources De-registration

The RIPE NCC de-registers Internet number resources that have been allocated or assigned under false pretenses; that contravene RIPE Policies; or that have been hijacked. This activity also applies to LIRs that have been closed for non-payment of their service fee or for termination of their contract.

Benefits for RIPE NCC members / RIPE community:

• Helps to keep the RIPE Registry accurate and current

• Prevents hijacking of Internet number resources

Registry Maintenance Costs for 2013:

*** 1.2 Resource Certification (RPKI) *** STRATEGIC FOCUS POINT 2013

The Resource Certification (RPKI) system allows RIPE NCC members to request a digital certificate listing the Internet number resources they hold. It offers cryptographic proof that a certain organisation holds a certain set of resources that have been registered with the RIPE NCC. The practical application offered today is the ability to use resource certificates to help secure Internet routing, particularly BGP origin validation.

For 2013, the RIPE NCC will develop the RPKI system with a focus on security, resilience and operator autonomy. The service will also be expanded, as requested by the RIPE NCC membership, so that legacy address space holders and PI End Users who have address space registered in the RIPE Database will be eligible for a resource certificate.

Resilience will be improved so that all elements of the service are available at all times for LIRs’ daily operations and that there is no single point of failure. This will involve providing a Hosted Certificate and Route Origin Authorisation (ROA) management system via the LIR portal; offering a non-hosted Parent Certificate system; and enabling data retrieval via the ROA repository.

The RIPE NCC has taken steps so that operators are fully in control when making BGP routing decisions based on the RPKI data set. For example, the RIPE NCC RPKI Validator has the option to specify local overrides on the global data set. In 2013, we will expand our efforts to enable operator autonomy with periodic audits of the RPKI system by an independent party.

Benefits for RIPE NCC members / RIPE community:

• Offers validated proof of holdership

• Offers a platform that helps making Internet routing more secure

• Certifies all types of Internet number resources

• Makes the RIPE NCC Registry more robust

RPKI Costs for 2013:

1.3 RIPE Database

The RIPE Database contains registration details of IP addresses and AS Numbers used by networks based in the RIPE NCC service region. It shows the organisations that hold the resources, where the allocations were made and contact details for the networks. The organisations that hold those resources are responsible for updating their information in the RIPE Database. An Internet Routing Registry (IRR), primarily for the RIPE NCC service region, is also part of the RIPE Database.

Benefits for RIPE NCC members / RIPE community:

• Enables a range of users, including network engineers, system administrators, researchers and End Users, to find the information they need for network troubleshooting or determining abuse contacts

1.3.1 RIPE Database: Maintenance and Development

The RIPE NCC regularly makes improvements to the interface for the RIPE Database. This includes implementing community-driven changes as they arise, making software and system modifications in response to feedback from users and decisions made by the RIPE community.

Benefits for RIPE NCC members / RIPE community:

• Provides users with more useful features and easier ways to update the database

• Improves the accuracy and the usefulness of the data in the RIPE Database

1.3.2 User Support and Software Maintenance
The RIPE NCC provides user support for the RIPE Database and related services. This includes incident handling and problem resolution as well as responding to user questions and comments.

The RIPE NCC also performs regular software maintenance activities, including bug fixes and minor modifications. The results of these software development efforts are made publicly available, both in the production software as well as by means of providing the source code to the community.

This activity includes the maintenance and improvement of documentation associated with the RIPE Database.

Benefits for RIPE NCC members / RIPE community:

• Provides user support for the RIPE Database and related services

• Incorporates user feedback into the developments of the service

• Keeps the user community informed about new developments as well as planned and emergency maintenance

• Ensures the high quality of the system software and the reliable operation of the database and related services

1.3.3 New Database Features

The RIPE NCC designs and implements new database features as requested by the user community or proposed by the RIPE NCC. It performs the development work based on the priorities established in the appropriate RIPE Working Groups.

Benefits for RIPE NCC members / RIPE community:

• Ensures that the RIPE Database continues to serve the needs of the user community and the priorities of the RIPE Working Groups

• Provides new features to the RIPE Database that reflect the changing requirements of the Internet community

1.3.4 Implementation of New Version of RIPE Database

The current version of the RIPE Database has been in production for more than ten years and, as a consequence, maintaining and adding features to this old platform has become costly, time-consuming and difficult to scale.

As a result, the RIPE NCC has focused on implementing a new version of the RIPE Database software with the latest tools and technologies. Most of the new version is already in production but the code base is still being improved before public release of the source code.

There is currently a lot of activity in the IETF about standardising the global whois query and response format. The RIPE NCC is committed to adding support for these standards to the RIPE Database software.

Benefits for RIPE NCC members / RIPE community:

• Enables the RIPE Database software to scale to new performance and hardware requirements

• Makes the software more maintainable and so enables the implementation of new features in a timely fashion and without spending resources to create more legacy code

• Incorporates the latest changes in Internet standards and complies with current standards and practices designed to achieve global compatibility

RIPE Database Costs for 2013:

1.4. LIR Portal

The LIR Portal is the primary place where members interact with the RIPE NCC. This ranges from resource requests to billing. For 2013, the RIPE NCC plans to enhance the LIR Portal to make it the single place where members can manage and analyse everything related to their Internet number resources.

The first results of these efforts can already be seen in the IP Analyser tool, which will be expanded to encompass all types of address space and to offer an overview of the resources and RIPE Database objects that require attention.

In addition, we will make all information retrievable through an application programming interface (API) so that it can be used in the IP address management tools that members use in their organisation.

Benefits for RIPE NCC members / RIPE community:

• Provides a central place where members can efficiently manage and analyse all aspects of the Internet number resources they receive from the RIPE NCC

• Makes resource requests easier and more efficient

• Enables members to incorporate LIR Portal functionality into their own IP address management tools

• Strengthens the registry

1.4.1 IP Analyser

The IP Analyser is a service accessible through the LIR Portal that gives RIPE NCC members detailed information about their IPv4 and IPv6 allocations and assignments. The ultimate goal is to offer a complete overview of all the IP resources an LIR holds and to inform them about everything related to those resources.

Benefits for RIPE NCC members / RIPE community:

• Gives a complete insight into the status of the IP resources that are held by an LIR, including:

• which allocations are held

• which assignments have been made

• how much of the allocations are in use

• which free address space can be assigned to customers

• which overlapping and invalid assignments have been made

• whether the LIR is eligible for an additional allocation

LIR Portal Costs for 2013:

2) Services

2.1 Training

2.1.1 LIR Training Course

The LIR Training Course is a one-day introduction to the administrative procedures and policies related to obtaining and distributing Internet resources (i.e. IP addresses, AS Numbers and reverse DNS delegations) and operating an LIR. Training Courses are offered across the whole RIPE NCC service region.

Benefits for RIPE NCC members / RIPE community:

• Increases understanding of the RIPE NCC’s processes and procedures and how resources are distributed

• Ensures LIRs know how to send correctly prepared Internet number resource requests to the RIPE NCC, enabling a more timely completion of these requests

• Ensures LIRs know the correct procedure for registering and updating registry data relating to Internet number resources and how to work with the RIPE Database

• Increases awareness of the RIPE Policy Development Process

• Gives LIRs the opportunity to meet RIPE NCC staff face-to-face

2.1.2 IPv6 Training Course

The IPv6 Training Course is a one-day course about the need for IPv6 and includes basic information on how to plan IPv6 deployment.

Benefits for RIPE NCC members / RIPE community:

• Increases awareness about IPv4 depletion

• Increases IPv6 uptake

• Removes fears about IPv6 and the deployment process

• Increases awareness about IPv4 and IPv6 coexistence

2.1.3 Routing Registry and Resource Certification (RPKI) Training Course

The Routing Registry Training and Resource Certification (RPKI) Training Course is a one-day course that covers Internet Routing Registry (IRR) usage, Routing Policy Specification Language (RPSL) and Resource Certification (RPKI). This course is intended for members that have basic experience with the RIPE Database and who understand the BGP protocol and inter-domain routing.

Benefits for RIPE NCC members / RIPE community:

• Increases understanding of how to make Internet routing more secure and reliable with the information available in the Routing Registry and Resource Certification (RPKI) systems

• Explains how to document routing policy in the RIPE Database with RPSL

• Increases understanding of how to set up the Resource Certification system in the LIR Portal

• Explains how to use resource certificates to create Route Origin Authorisations (ROAs)

• Demonstrates the use of ROAs in the BGP decision-making process

2.1.4 RIPE NCC E-Learning Centre

The RIPE NCC provides a range of courses to members and non-members, using a variety of teacher-based courses and additional training strategies. A key strategy in this respect is the RIPE NCC E-Learning Centre. This is a free resource allowing members and non-members to access online modules on a variety of courses, ranging from IPv6 and DNSSEC to the RIPE Database.

Benefits for RIPE NCC members / RIPE community:

• Enables members and non-members to access learning resources online at a time and place that is convenient for them

2.1.5 RIPE NCC Webinars

The RIPE NCC Webinars are live, one-hour online training courses that allow participants to interact with RIPE NCC trainers without leaving their desks. The RIPE NCC will focus on topics and issues most important for LIRs. The following webinars are currently available:

• Introduction to the RIPE Database

• RIPE Database - Advanced Topics

• Resource Certification (RPKI)

The following topics will be developed:

• IPv6 - how to achieve 4* RIPEness

• New LIR webinar – How to Get Started

Benefits for RIPE NCC members / RIPE community:

• Enables members to interact with RIPE NCC trainers and to learn about a variety of topics quickly and without having to travel

Training Course Costs for 2013:

*** 2.2 RIPEstat *** STRATEGIC FOCUS POINT 2013

RIPEstat provides a one-stop shop for comprehensive information about the current state and history of specific Internet number resources (IP Addresses, ASNs). It presents information from the RIPE registry, various measurements and third party databases such as geo-location and blacklists and provides both near real-time and historical information about a specified IP address range or ASN.

By the end of 2012, RIPEstat will incorporate virtually all public data available at the RIPE NCC to describe Internet number resources. It will enable users to query for raw data or by using default or customised visualisations while responding with relevant answers and reasonable performance.

For 2013, the RIPE NCC will focus on expanding the infrastructure used by this service and on keeping up with the usage growth. Measurement data from RIPE Atlas will be incorporated into RIPEstat. In particular, measurement results related to the queried resources will be shown, if such results are available.

Using feedback from RIPEstat users, the RIPE NCC will also make an evaluation of possible tools or features that can be incorporated into RIPEstat to make the service more useful for RIPE NCC members and the broader user base.

Benefits for RIPE NCC members / RIPE community:

• Provides the RIPE community and RIPE NCC members with current and historical information about any Internet number resource

• Provides RIPE NCC members with historic information about the Internet number resources they are responsible for

• Provides RIPE NCC members with routing-specific functions, such as alarms

• Provides targeted analysis and user interface options aimed specifically at members

RIPEstat costs for 2013:

*** 2.3 RIPE Atlas *** STRATEGIC FOCUS POINT 2013

RIPE Atlas provides active measurements of packet flows from thousands of vantage points across the Internet with emphasis on the RIPE NCC service region This augments the current routing based measurements with actual data traffic: RIPE Atlas does not measure how packets should flow but if and how they actually do.

RIPE Atlas allows users to run their own measurements that test reachability and round trip times, traceroutes, DNS measurements and more. Users can select from thousands of vantage points. All measurements are pooled and provide a big-picture view of the Internet presented as “traffic maps”.

By the end of 2012 the RIPE Atlas network will consist of approximately 2,500 active measurement probes, mostly operating in the RIPE NCC service region.

In 2013, the RIPE NCC will continue to expand the RIPE Atlas command, control and collection infrastructure to accommodate the growing number of probes. The RIPE NCC plans to distribute 4,000 additional RIPE Atlas probes in order to gain more vantage points and thereby a more detailed picture of the forwarding plane of the Internet.

In addition, we will deploy approximately 50 RIPE Atlas Anchors. These larger nodes, which will be provided by hosting organisations, will function as high capacity measurement probes and will provide a cooperating target for measurement traffic. This will allow users to examine measurement traffic at both the source and the destination.

The measurable goals for RIPE Atlas in 2013 are:

• 6,000 active probes

• 50 active RIPE Atlas Anchors

• Three new traffic maps

• Data sharing codified and available for all interested parties

The RIPE NCC will extend RIPE Atlas with components that can notify users in the case of pre-defined events occurring (alarms) and will continue expanding data sharing (availability and access) to interested parties.

Based on the data back-end used by RIPE Atlas, all Atlas data will be stored in such a way that allows this data to be used in other services, such as RIPEstat. In addition, the RIPE NCC will create and document application programming interfaces (APIs) for measurement specification and data access. The goal is to enable RIPE Atlas users to access its functionality from scripted environments, giving more flexibility to incorporate RIPE Atlas services into other business or monitoring processes.

The RIPE NCC will actively maintain a public roadmap for RIPE Atlas and will hold continued dialogue with the RIPE community, especially the RIPE MAT Working Group, about future developments and functionality.

Benefits for RIPE NCC members / RIPE community:

• Enables users to send actual active measurement traffic from thousands of vantage points across the Internet and to record the responses

• Provides Internet traffic maps that show the general state of the Internet for situational awareness

• Provides timely, hard data on topical issues

• Offers topical measurements, data analysis and alarms for RIPE NCC members

• Reinforces the credibility and standing of the RIPE NCC

2.3.1 RIPE Atlas Anchors

The RIPE NCC will deploy approximately 50 RIPE Atlas Anchors in 2013. The Anchors will have two main functions:

• Provide a cooperating target for measurement traffic that will allow measurement traffic to be observed at both the source and the destination

• Act as high-capacity probes, compared to the standard RIPE Atlas probes, generating measurement traffic

The RIPE Atlas Anchors will be capable of carrying out part of the functionality currently offered by the Test Traffic Measurements (TTM) service (see 2.4.5). RIPE Atlas Anchors will be capable of evolving into a more advanced “RIPE NCC box” offering additional services such as local instances of K-root.

Benefits for RIPE NCC members / RIPE community:

• Perform part of the measurement functionality provided by TTM

• Perform active measurements

• Attract active measurements from others to RIPE Atlas Anchors

• Capable of hosting local node of K-root

• Will allow RIPE NCC services to be obtained more quickly at the local level
  

RIPE Atlas Costs for 2013:

2.4 Other Services

2.4.1 Routing Information Service (RIS)

The RIPE NCC operates a worldwide network of Border Gateway Protocol (BGP) monitoring probes, known as Remote Route Collectors (RRCs). They provide a fully integrated global view of routing information at key locations around the world. All collected data is time-stamped, stored in a database and used as the input for various tools, as well as being made available for download.

Benefits for RIPE NCC members / RIPE community:

• Provides a comprehensive collection of data from Internet routing plane

• Offers one of only two major efforts worldwide to capture routing data: route views and RIS

• Provides a long-time series of routing data from a neutral and impartial source

2.4.2 DNS Measurements
The RIPE NCC’s DNS measurements are focused on the DNS Monitoring Service (DNSMON), which provides a comprehensive, objective and up-to-date overview of the quality of the service offered by certain DNS root, Top-Level Domain (TLD) and ENUM tier-1 name servers. The data is updated regularly and presented at various levels of granularity.

While DNSMON will continue to run in 2013, DNSMON data will be incorporated into RIPE Atlas.

Benefits for RIPE NCC members / RIPE community:

• Provides neutral and impartial measurements and high-quality monitoring of important DNS servers

• Enables users to view historical data, enabling a quick analysis of both past and present DNS issues

• Monitors authoritative servers focused on high-level DNS zones operated by members

2.4.3 Administrative Support

The RIPE NCC provides administrative support for services such as RIPE Atlas, the DNS Monitoring service (DNSMON), Test Traffic Measurements (TTM) and the Routing Information Service (RIS). This includes incident handling and problem resolution as well as responding to user questions and comments.

Benefits for RIPE NCC members / RIPE community:

• Ensures new user applications run smoothly and efficiently from beginning to end

• Initiates and activates RIPE Atlas probes

• Provides first line user support for these services

• Collects user feedback regarding these services

2.4.4 RIPE NCC Access

RIPE NCC Access is the RIPE NCC’s single sign-on system, which allows RIPE NCC members to use a single set of credentials to access our various services without being prompted to log in again at each of them. Currently, the following services are supported by RIPE NCC Access:

• LIR Portal

• IS Alarms

• RIPE Labs

• RIPEstat

• RIPE Atlas

• RIPE Meeting website

Benefits for RIPE NCC members / RIPE community:

• Offers a simplified and unified access to RIPE NCC services and improves the overall user experience

2.4.5 Test Traffic Measurements (TTM)

The RIPE NCC will wind down the Test Traffic Measurements (TTM) service in 2013. It is intended that the benefits of the TTM service will be offered in a more focused and up-to-date way through RIPE Atlas. Where possible, the current TTM test-box hosts will be able to host RIPE Atlas Anchors once the TTM systems are fully migrated to that system.

Benefits for RIPE NCC members:

• The measurements and trend analysis benefits for RIPE NCC members arising from TTM will be continued in more focused ways through RIPE Atlas

2.4.6 Near Real Time Mirroring

The Near Real Time Mirroring (NRTM) service provides RIPE NCC members with a local copy of the RIPE Database. This local copy is kept up to date with modifications from the RIPE Database in near real time. The NRTM feeds do not contain any personal or private data.

Benefits for RIPE NCC members / RIPE community:

• Provides members with a local copy of the RIPE Database

• Enables members to use RIPE Database data (e.g. routing data) in near real time to manage their networks without the need to continuously query the RIPE Database for changes

2.4.7 RIPE Database Proxy Service

The RIPE Database Proxy Service is specifically aimed at RIPE NCC members who send queries to the RIPE Database on behalf of their clients. It ensures that the daily access limits that apply to all users of the RIPE Database are correctly applied. For example, if a member provides their clients with a web-based query gateway to the RIPE Database, the proxy service ensures that daily limits are calculated based on the clients’ queries and avoids the possibility of a member’s server being denied access to the RIPE Database because of too many queries from that member’s clients.

Benefits for RIPE NCC members / RIPE community:

• Provides members with a mechanism for ensuring that their clients’ RIPE Database queries are not added to the member’s daily access limit

• Helps to ensure the accessibility of query gateways to the RIPE Database that members provide to their clients

Other Services Costs for 2013:

3) Coordination Activities

3.1 DNS Services and K-root Operations

The RIPE NCC provides DNS coordination and support activities as well as reverse DNS services for IPv4 and IPv6 address space managed by the RIPE NCC. For reverse DNS associated with address space managed by other RIRs, the RIPE NCC provides secondary DNS to support the reliability of reverse lookups. The scalability of the DNS infrastructure for secondary, reverse and primary DNS services is improved based on the requirements specific to each of these services.

In 2013, the RIPE NCC plans to expand the authoritative and secondary DNS services currently provided from Amsterdam and London cluster nodes by adding a third cluster node to improve resilience and geographical coverage.

Benefits for RIPE NCC members / RIPE community:

• Stability and diversity of the DNS root name server system

• Neutral, impartial and professional provision of key high-level DNS services

• Reverse DNS service for RIPE NCC members with registered IP addresses

3.1.1 Reverse DNS

The RIPE NCC delegates reverse DNS zones for the address ranges managed by the RIPE NCC. To support this service, the RIPE NCC provides reliable, authoritative name servers and checks all zones under its responsibility to ensure they are properly set up and functioning correctly.

As part of its efforts in the area of DNSSEC deployment, the RIPE NCC publishes signed zones and provides tools for users to secure delegations received from the RIPE NCC. In addition, the RIPE NCC shares experience through publishing operational white papers, documentation and software toolkits.

Benefits for RIPE NCC members / RIPE community:

• Supports the proper address-to-name mapping for addresses allocated to the RIPE NCC

• Provides reliable and secure reverse DNS services

• Supports the operation and maintenance of DNSSEC

3.1.2 Secondary DNS Service

The RIPE NCC offers a secondary name service to the other Regional Internet Registries (RIRs) along with some country code Top-Level Domain (ccTLD) operators, although it no longer provides this service to well-established ccTLDs.

Benefits for RIPE NCC members / RIPE community:

• Supports the stability of the global DNS by offering a professional and stable service to the other RIRs and developing ccTLD operators that require it

3.1.3 DNS Services in the e164.arpa Domain (ENUM)

The Internet Architecture Board (IAB) has an agreement with the RIPE NCC under which the RIPE NCC provides technical operation of the e164.arpa domain. This domain implements support in the DNS for the ENUM protocol, allowing mapping of telephone numbers to domain names in order to help facilitate such services as Voice over IP (VoIP).

Benefits for RIPE NCC members / RIPE community:

• Supports operations of one of the systems required for the deployment of the ENUM protocol, promoting increased integration between the Internet and services provided through the traditional telephony infrastructure

• Supports security of the e164.arpa domain by deploying and maintaining DNSSEC and allowing secure delegations from ENUM operators

3.1.4 DNS and Reverse DNS (First Line Support)

The RIPE NCC provides DNS coordination and support activities as well as reverse DNS services for IPv4 and IPv6 address space managed by the RIPE NCC.

Benefits for RIPE NCC members / RIPE community:

• Provides first line user support for DNS, Reverse DNS and related services

• Continuously collects user feedback regarding these services

3.1.5 K-root Operations

The RIPE NCC operates the K-root server. Root name servers are a crucial part of the Internet DNS infrastructure. The RIPE NCC has operated the K-root server since 1997, when the first server was installed at the London Internet Exchange (LINX) in the United Kingdom.

Since 2003, the RIPE NCC has been deploying anycast instances of the K-root server with local reachability. The RIPE NCC has also deployed five global nodes of the K-root name server. The RIPE NCC collects and analyses data to evaluate the performance of the K-root anycast nodes that have been deployed and to determine if, and where, other anycast nodes should be deployed.

Benefits for RIPE NCC members / RIPE community:

• Improves the resiliency, efficiency, security and quality of the K-root service

• Isolates the impact of an "external" Denial of Service (DoS) attack and localises the impact of a "local" DoS attack

• Efficiently maintains the network of anycast instances of K-root by monitoring network and instance problems, performing trend analysis and determining if, and where, other anycast nodes should be deployed

DNS Services and K-root Costs for 2013:

3.2 RIPE Labs

RIPE Labs is a platform focused on developing innovative Internet-related tools and ideas that have developed both within the RIPE NCC and the community at large. It enables direct user engagement during the production and development process of many RIPE NCC services as well as acting as a platform for knowledge sharing.

RIPE Labs is seen as another channel to gain both member and community feedback about the services provided by the RIPE NCC, especially those that are continuously being developed. The RIPE NCC wants to get more feedback about the services being developed so that we can better serve the needs of the membership.

We also want to increase the amount of community articles that appear on RIPE Labs and will also look to increase interaction so that those publishing their articles will get more feedback from their peers.

The RIPE NCC plans to build on the success of RIPE Labs since its launch in 2009 and wants to continue building on this success in 2013. In addition, the RIPE NCC wants to develop RIPE Labs over 2013 so that it can act as the definitive portal for RIPE NCC associated statistics. These statistics, which will include dynamic and historical statistics, will be presented in an easy-to-find and logical format.

Benefits for RIPE NCC members / RIPE community:

• Stimulates community building

• Enables rapid prototyping of new ideas in a pre-production environment

• Allows for community feedback during the RIPE NCC service development phases

• Provides an iterative, effective and community-driven process of presenting potential tools and services that can be discussed, tested and improved

• Gives community members an easily accessible platform to showcase their ideas and research

RIPE Labs Costs for 2013:

3.3 Measurements and Data Collection

The RIPE NCC operates globally distributed measurement networks for the purpose of collecting data on Internet infrastructure usage and development. The RIPE NCC continues to integrate new services, such as RIPEstat and RIPE Atlas, into its existing portfolio (see sections 2.2 and 2.3). We also continue to work in cooperation with a range of stakeholders to unify, streamline, optimise and develop new interfaces to this data.

Benefits for RIPE NCC members / RIPE community:

• Provides datasets that can be used to analyse the operation and growth of the Internet

• Provides the data that can be used in tools such as RIPEstat and RIPE Atlas

Measurements and Data Collection Costs for 2013:

3.4 Government and LEA Liaison

The RIPE NCC's leadership in engaging all Internet stakeholders to work toward a stable, secure and global Internet has been recognised by many governments and international organisations. The RIPE NCC has received positive recognition for its contributions to the World Summit on the Information Society (WSIS), held from 2003-2005, the ongoing Internet Governance Forum (IGF) and the Organisation for Economic Cooperation and Development (OECD) Committee for Information, Computer and Communications Policy (ICCP). The RIPE NCC has also organised regular Roundtable Meetings for Governments and Regulators, meetings for law enforcement agencies (LEAs) and has contributed to a wide range of forums and task forces with individual governments and regional authorities in countries including Belgium, Germany, Lebanon, Moldova, Netherlands, Norway, Qatar, Saudi Arabia, Sweden, the United Arab Emirates and the United Kingdom. The RIPE NCC has also been actively involved in coordinating capacity-building events such as the IPv6 Roadshow, regional technical and Internet governance forums, and training events. Continuing to build on this work is essential to promoting public/private sector dialogue and to guarantee the future growth, stability and security of the Internet.

The RIPE NCC will continue to explore new ways to engage with the public sector and continue the dialogue between governments and the Internet technical community. This will include working to expand the audience of RIPE NCC Roundtable Meetings, in which the RIPE NCC can represent the view of the RIPE community and the RIPE NCC’s members while explaining new developments in the Internet landscape and the impact that these developments could have on public policy. Alongside the Roundtable Meetings, the RIPE NCC will establish new, targeted forums for stakeholder groups and build on the work already done in the area of capacity building, particularly related to IPv6 training and awareness.

The RIPE NCC will also continue to engage where appropriate with international public sector and industry organisations, including the International Telecommunication Union (ITU), the Conference of European Postal and Telecommunications Administrations (CEPT) and national policy groups.

Benefits for RIPE NCC members / RIPE community:

• Promotes public/private sector dialogue

• Ensures that the interests and concerns of the RIPE NCC membership and RIPE community are heard in multi-stakeholder Internet governance discussions at the national, regional and global level

• Promotes openness and transparency in the development of public policy relating to the Internet, as well as raising any specific concerns of the RIPE NCC membership or the RIPE community

• Enables the future growth, stability and security of the Internet

Government & LEA Liaison Costs for 2013:

*** 3.5 Outreach and External Relations *** STRATEGIC FOCUS POINT 2013

The RIPE NCC supports the open, multi-stakeholder model of Internet governance through engaging with a broad and growing range of stakeholder groups. The RIPE NCC has identified stakeholder groups that we have, or are developing, relationships with, including:

• RIPE NCC membership

• Internet technical community (including Network Operators Groups)

• Internet industry and professional groups

• Industry partners (RIRs, ICANN, the Internet Society)

• Academia and the research community

• The Free and Open Source Software (FOSS) and online gaming communities

• Public sector (governments and regulators)

• Law Enforcement Authorities (LEAs)

Benefits for RIPE NCC members / RIPE community:

• Engaging with these groups and embracing them as part of the RIPE community strengthens the authority and legitimacy of the bottom-up policy development process

• Positions the RIPE NCC to facilitate expert technical input into policy and decision-making processes outside the RIPE forum that may impact on, or be affected by, IP addressing issues.

• Enables the effective, coordinated representation of the Internet technical community's interests, including the model of open, bottom-up, industry self-regulation, in multi-stakeholder Internet governance forums

Outreach and External Relations Costs for 2013:

3.6 Regional Support and Outreach

In 2013, it is expected that two RIPE NCC Regional Meeting/MENOG Meetings will be held in the Middle East region, two RIPE NCC Regional Meeting/ENOG Meeting in the Russia/CIS region and one RIPE NCC Regional Meeting in South East Europe. IPv6 tutorials, workshops and presentations will take place at all regional events.

With the significant growth of the IT and Internet industries in the Middle East, Russia and South Eastern Europe (and the resulting increase in RIPE NCC members), the RIPE NCC is focused on increasing the participation of Internet stakeholders from these areas of its service region. By working with the different communities in these areas, the RIPE NCC is encouraging increased regional participation both in the activities of the RIPE NCC and the RIPE Policy Development Process. The aim is to strengthen the RIPE community by enabling regional communities to participate more fully in policy development and to ensure that regional concerns, issues and needs are represented.

The RIPE NCC has provided extensive support in the establishment of regional Network Operator Groups (NOGs). Building on the establishment of the Middle East Network Operators Group (MENOG) in 2007 and the Eurasian Network Operators Group (ENOG) in 2011, the RIPE NCC will continue to supply the technical and administrative expertise required to develop existing NOGs and assist in the creation of any new groups required by the Internet community.

Regional Support and Outreach Costs for 2013:

3.7 RIPE Meetings

The RIPE NCC organises RIPE Meetings, providing all administrative and technical support.

Benefits for RIPE NCC members / RIPE community:

• Supports the open, bottom-up, industry self-regulatory structure common to all RIR communities in managing Internet number resources

• Stimulates participation of the RIPE community in the IP policy-making process and the technical coordination of IP networking

• Contributes to the stable operation of the RIPE NCC by allowing for guidance and advice from the RIPE Working Groups

• Enables meeting attendees to provide feedback on the RIPE NCC Activity Plan (in the RIPE NCC Services Working Group)

• Encourages participation of individuals who have little or no experience of the RIPE community

• Provides a full set of minutes that keeps the RIPE community, the RIPE NCC membership and other interested parties up-to-date with the discussions and decisions that took place at a RIPE Meeting

• Through live webcasting and online feedback mechanisms, enables remote participation in the discussions taking place at RIPE Meetings

• Facilitates networking opportunities with key players in the Internet industry in the RIPE community and beyond

3.7.1 Customer Service Centre (at RIPE Meetings)

At RIPE Meetings, the RIPE NCC provides staff who are available for face-to-face consultation about:

• Internet resource requests (IPv4, IPv6, Autonomous System Numbers)

• The RIPE Database

• Changes to registry file information

• Invoice and billing queries

• RIPE NCC Training Courses and the RIPE NCC E-Learning Centre

• The Routing Information Service (RIS) and BGPlay

• Reverse DNS setup, DNSSEC, DNSMON, K-root, the Test Traffic Measurements (TTM) service and email services

• How to become a Local Internet Registry (LIR)

• The RIPE NCC and its services

Benefits for RIPE NCC members / RIPE community:

• Assists members and the RIPE community with any outstanding issues

• Promotes greater cooperation between the RIPE NCC, its members and the RIPE community

RIPE Meeting Costs for 2013:

3.8 RIPE Policy and Community Support

The RIPE NCC provides support to all stakeholders who wish to participate in formulating RIPE Policy or who wish to be part of the RIPE community.

Benefits for RIPE NCC members / RIPE community:

• Promotes the RIPE Policy Development Process

• Strengthens the RIPE community

3.8.1 Supporting the RIPE Policy Development Process (PDP)

The RIPE NCC provides support to the PDP and gives all assistance required by RIPE Working Groups and Working Group Chairs so that they are able to develop policy in a consensus-based, bottom-up manner.

The RIPE NCC also provides information and statistics to various working group mailing lists and creates impact analyses of potential RIPE Policy proposals.

Benefits for RIPE NCC members / RIPE community:

• Promotes the PDP

• Educates the RIPE community about the PDP

• Helps to anticipate potential problems related to the PDP or policy proposals

3.8.2 Policy Implementation (procedures)

The RIPE NCC implements procedures as part of the RIPE Policy Development Process (PDP). The implementation of RIPE Policy is done in the RIPE NCC Policy Implementation Coordination Group (PICG).

Benefits for RIPE NCC Members / RIPE Community:

• Provides transparency and consistency of the procedures

• Provides procedural information and responses to the RIPE community

• Supports and promotes global Internet IP address policies

• Translates RIPE Policy into RIPE NCC procedures

• Documents and maintains a clear overview of new and changed procedures

3.8.3 Mailing List Management

The RIPE NCC maintains a number of high-volume external mailing lists. The processing of mailing list traffic is constantly monitored and all mailing lists are archived. Efforts are made to support subscribers with problems and to reduce or control the spam on external mailing lists so that they can be easily and efficiently moderated without losing any End User functionality.

Benefits for RIPE NCC Members / RIPE Community:

• Ensures the exchange of information among the RIPE community and the RIPE NCC membership

• Provides support for subscribers of the RIPE and RIPE NCC mailing lists

• Reduces/controls spam on external mailing lists so that they can be easily and efficiently moderated without losing any end user functionality

RIPE Policy and Community Support Costs for 2013:

3.9 IPv6 Support

3.9.1 Training and Education

i) RIPE NCC IPv6 for LIRs Training Course (see 2.1.2)

ii) RIPE NCC/MENOG IPv6 Roadshows

The IPv6 Roadshow events are a joint initiative from the Middle East Network Operators Group (MENOG), the RIPE NCC and APNIC. They consist of three- and five-day hands-on training events targeted at an audience of government and enterprise network operators.

In 2013, there will be around ten IPv6 Roadshow events scheduled throughout the Middle East region. The RIPE NCC will also work with regional partners, including governments, to launch the IPv6 Roadshow Train the Trainer Program, which will enable local trainers to deliver the IPv6 Roadshow course material in their community.

Benefits for RIPE NCC members / RIPE community:

• Provides education and capacity building, in a context that recognises the Middle East region's specific needs

• Builds relationships with public sector bodies and actors in the Middle East

• Enables local trainers to acquire the knowledge and skills to educate their communities

iii) RIPE NCC/ENOG IPv6 Roadshows

Building on the success of the RIPE NCC/MENOG IPv6 Roadshows, these events will be rolled out in Russia and the CIS countries during 2013. The IPv6 Roadshow Train the Trainer Program will also enable local trainers to deliver these courses.

Benefits for RIPE NCC members / RIPE community:

• Provides education and capacity building in a context that recognises the specific needs of stakeholders in Russia and the CIS countries

• Builds relationships with public sector bodies and actors in Russia and the CIS countries

• Enables local trainers to acquire the knowledge and skills to educate their communities

3.9.2 IPv6 Outreach

i) RIPE NCC Representation at IPv6-related Events

During 2013, the RIPE NCC will continue to send representatives to relevant IPv6-related events throughout the RIPE NCC's service region and beyond. We will also reach out to some audiences that we have not actively targeted in the past.

Benefits for RIPE NCC members / RIPE community:

• Builds awareness among all Internet stakeholders of the need to deploy IPv6

• Ensures that the interests of the RIPE NCC membership and the technical community are represented at global events

• Highlights the work being done by the RIPE NCC and RIPE community in data-gathering and analysis

• Promotes capacity building, particularly in developing areas, and facilitates knowledge sharing with global experts

• Enables the RIPE NCC to offer expert input into IPv6 related fora and events

ii) Outreach to Governments, Regulators and LEAs

The RIPE NCC will continue its efforts to inform and educate governments, regulators and LEAs about IPv6 deployment in their sectors via regular RIPE NCC Roundtable Meetings for Governments and Regulators, engagement with national forums and task forces, and meetings with LEAs from around the world. We will also continue to work closely with the OECD on their IPv6-related activities.

Benefits for RIPE NCC members / RIPE community:

• Builds awareness among public sector stakeholders of the need to facilitate the deployment of IPv6

• Promotes public/private sector dialogue, with the goal of more informed policy-making

• Ensures that the interests of the RIPE NCC membership and the technical community are represented

• Facilitates effective cooperation between the Internet technical community and the public sector in areas such as capacity-building projects and law enforcement

• Highlights the advantages of the community-driven, bottom-up system for managing and distributing Internet number resources

iii) IPv6ActNow.org

The RIPE NCC's IPv6ActNow.org website is a comprehensive resource for IPv6-related information for all stakeholders.

In 2013, IPv6ActNow.org will be continually updated with the latest information on IPv6 deployment, equipment and events.

Benefits for RIPE NCC members / RIPE community:

• Provides a comprehensive collection of impartial information to help every stakeholder prepare to deploy IPv6

• Offers a platform for all stakeholders to share their own experiences with IPv6 deployment and learn from community best practices

• Promotes IPv6 deployment

iv) General Outreach

During 2013, The RIPE NCC’s general IPv6 outreach will continue by developing printed and online materials to facilitate all stakeholders with their IPv6 deployment programs. We will enhance our IPv6 messaging and communication in the traditional and online media, utilising our PR agency and social media networks. We will also work closely with the other RIRs on global education and capacity building goals.

Benefits for RIPE NCC members / RIPE community:

• Keeps all stakeholders informed about developments on IPv6-related matters

• Ensures that the interests of the RIPE NCC membership and the technical community are represented

• Highlights the work being done by the RIPE NCC and RIPE community in data-gathering and analysis

• Highlights the advantages of the community-driven, bottom-up system for managing and distributing Internet number resources

3.9.3 IPv6 and RIPE NCC Membership Support

i) IPv6 RIPEness

IPv6 RIPEness is a rating system that awards stars to RIPE NCC members depending on specific indicators of IPv6 preparedness.

In 2013, the RIPE NCC will continue to analyse its members’ IPv6 preparedness and increase the profile of this activity.

Benefits for RIPE NCC members / RIPE community:

• Encourages RIPE NCC members to become IPv6-ready and rewards them for doing so

• Provides all stakeholders with a unique indicator of IPv6 readiness across the RIPE NCC service region (and at more specific levels, including by country, sector, LIR size)

• Enables analysis of regional IPv6 penetration

3.9.4 Regional and Community Support

i) Community Support

In 2013, the RIPE NCC will continue to support relevant RIPE Working Groups and the RIPE Meeting Programme Committee with IPv6 content development and other community-led initiatives.

Benefits for RIPE NCC members / RIPE community:

• Ensures that the community is well-informed on IPv6 and related developments

• Facilitates and supports community-driven activities and projects

• Ensures the continued effectiveness of RIPE as a policy-making and information sharing forum

ii) Regional Support

RIPE NCC Regional Meetings bring together RIPE NCC members, local governments, key players in the global and local Internet industry and RIPE NCC staff. These events are free of charge and open to everyone.

In 2013, it is expected that two RIPE NCC Regional Meetings/MENOG Meetings will be held in the Middle East region, two RIPE NCC Regional Meetings/ENOG Meetings in the Russia/CIS region and one RIPE NCC Regional Meeting in South East Europe. IPv6 tutorials, workshops and presentations will take place at all regional events.

Benefits for RIPE NCC members / RIPE community:

• Ensures that stakeholders in all regions are well informed about IPv6 and related developments

• Provides opportunities to address specific regional concerns and challenges

• Brings the RIPE NCC to those members who are unable to attend RIPE Meetings

iii) CPE Survey

The Customer Premises Equipment (CPE) survey collects data on the IPv6 readiness of CPEs from various vendors. In 2013, we will periodically update the CPE survey with information from vendors and conduct analysis on the results.

Benefits for RIPE NCC members / RIPE community:

• Keeps all stakeholders informed about hardware-related IPv6 developments

• Encourages vendors to ensure their equipment is IPv6 ready

• Provides a neutral overview of equipment features derived from community collaboration

3.9.5 IPv6 Statistics

The RIPE NCC provides a number of IPv6-related statistics based on a set of data that helps the membership and the community at large, including government institutions, to follow the rate of IPv6 deployment in the RIPE NCC service region.

In 2013, we will make IPv6-related statistics more accessible through RIPE Labs and IPv6ActNow. We will continue to provide up-to-date statistics and measurement results based on RIPE Atlas, RIPEstat and other tools.

Benefits for RIPE NCC members / RIPE community:

• Provides all stakeholders with accurate, impartial information and analysis on the rate of IPv6 deployment

• Offers all Internet stakeholders the opportunity to use neutral data to help build the case for IPv6 deployment

• Establishes the RIPE NCC and RIPE community as authoritative sources of data and analysis

IPv6 Support Costs for 2013:

3.10 ICANN/IANA/IETF/ISOC/RIRs

The RIPE NCC is strongly committed to maintaining close relationships with its industry partners, including the four other Regional Internet Registries (RIRs), ICANN, the IETF and the Internet Society (ISOC). These relationships are vital to ensuring coordinated administration of the resources that each organisation is responsible for. The RIPE NCC supports ICANN, particularly in relation to its role in managing the IANA functions, and works with the IETF and ISOC to ensure implementation of agreed technical standards and coordination among those who support the global operation of the Internet.

Benefits for RIPE NCC members / RIPE community:

• Promotes the open, bottom-up, industry self-regulatory structure common to all RIR communities in managing Internet number resources

• Allows collaboration for implementation of global policies developed by the Policy Development Processes (PDPs) of the five RIRs

• Assists the general technical coordination needed to support the stable operation of the Internet

ICANN/IANA/IETF/ISOC/RIRs:

4) Internal

4.1 IT

This RIPE NCC activity includes the operation of the internal network and all related infrastructure (its colocation facilities, archiving and storage), the internal support for staff, and IT support and enhancement for all services.

In 2013, IT automation improvements and a focus on efficiency to facilitate service improvements will be the key focus areas.

Benefits for RIPE NCC members / RIPE community:

• Support efficient deployment of services and enhancements of services

• Provision of 24/7 support for services

• Efficient IT support to staff to facilitate RIPE NCC service delivery

4.1.1 Technical Emergency Hotline

The RIPE NCC monitors its critical services 24/7. This monitoring includes RIPE NCC websites, the RIPE Database, K-Root, DNS and reverse DNS, the LIR Portal and Resource Certification (RPKI).

Following feedback from RIPE NCC members and the RIPE community, the RIPE NCC launched a Technical Emergency Hotline in November 2012. The hotline, which will continue in 2013, enables users to contact an after-hours call centre that evaluates incoming calls and forwards the details of legitimate reports immediately to the appropriate RIPE NCC 24/7 team.

Benefits for RIPE NCC members / RIPE community:

• Enables the RIPE NCC members and the RIPE community to flag technical emergencies outside of the RIPE NCC’s regular office hours

• Ensures the details of technical emergencies are forwarded to the RIPE NCC’s 24/7 teams in a timely manner

• Supports the efficient operation of the RIPE NCC’s technical services

IT Costs for 2013:

4.2 Facilities - Rent and Utilities

In 2013, the RIPE NCC will continue to improve its infrastructure in order to provide a productive work environment to its employees.

Apart from the rental agreement, facilities include utilities, security, repair and maintenance costs for the RIPE NCC building and equipment.

Benefits for RIPE NCC members / RIPE community:

• Provides a secure, healthy environment for employees

• Provides up-to-date and well-maintained equipment

Facilities Costs for 2013:

4.3 HR & Management

The RIPE NCC continuously reviews its organisational structure to make it as efficient as possible. We provide excellent management support to facilitate decision-making and engagement with relevant third parties. At the same time as supporting management in maintaining effective and healthy RIPE NCC staff, we also keep the educational level of managers and staff at the highest possible level.

Benefits for RIPE NCC members / RIPE community:

• Ensures the RIPE NCC's organisational structure and staff skillset are optimised so as to fulfil the strategic goals of the organisation as discussed with the RIPE NCC membership and approved by the RIPE NCC Executive Board.

HR & Management Costs for 2013:

4.4 Finance & Admin

The RIPE NCC maintains an accurate and efficient administrative process. We are continually enhancing our procedures to make them more efficient. We have a set of automated reporting tools in place to proactively provide up-to-date financial and administrative summaries to the RIPE NCC Management. In addition, we focus on improving our billing processes and offering more efficient online payment methods.

Benefits for RIPE NCC members / RIPE community:

• Provides lower costs through offering online payment methods

• Ensures a professionally managed organisation with efficient administrative processes and cost-effective processes

• Facilitates the financial needs of organisation in different parts of the RIPE NCC service region

Finance & Admin Costs for 2013:

4.5 Specialist Support (Legal & Information Security)

i) Legal

The RIPE NCC continually follows national and international legal developments and ensures that our internal activities are updated accordingly. We also provide a range of corporate governance documents that set the standards and procedures for our internal and external operations.

The RIPE NCC focuses efforts on helping legislators and law enforcers to understand how the self-governing mechanism of the RIPE community and the RIR system as a whole functions, and how they can participate.

Benefits for RIPE NCC members / RIPE community:

• Ensures that the RIPE NCC is run within an up-to-date legal framework and with a full set of corporate governance documents

• Improves legislators and LEAs’ understanding of the Internet governance model and the role of RIRs to gain their support for the current, successful model

ii) Information Security

In 2013, there will be a sustained focus on the security of the RIPE NCC’s public and member services. Activities will include implementing and maturing our security baselines and performing in-depth security audits of the provided services.

Other activities are aimed at expanding our abilities to detect security incidents and further developing the RIPE NCC’s capabilities to react quickly and efficiently to those incidents.

Benefits for RIPE NCC members / RIPE community:

• Ensures a high level of availability, confidentiality and integrity of the RIPE NCC services and its (member) data

• Minimises the impact of security incidents on the RIPE NCC’s services and subsequently minimises the possible impact on our members

Specialist Support Costs for 2013:

4.6 Organisational Activities (GM and EB Meetings)

The RIPE NCC supports twice-yearly RIPE NCC General Meetings (GMs). At these GMs, members vote annually on the Financial Report of the organisation and on the Charging Scheme for the following year. At GMs, members can also exercise their rights to vote in Executive Board elections and on amendments to corporate governance documents. In order to facilitate an informed membership at the GM, the RIPE NCC prepares various sets of documentation including a draft activity plan and budget, a draft charging scheme and an annual report, which includes a summary of the RIPE NCC’s financial status from year to year. The RIPE NCC provides remote participation facilities and electronic voting capabilities for those members who are unable to attend the GM in person but who wish to follow proceedings and vote in elections and on resolutions.

The RIPE NCC also facilitates multiple meetings for its executive board over the course of each year. These meetings deal with strategic and financial issues pertinent to the organisation as well as the RIPE NCC’s relationship with industry partners. At these meetings the RIPE NCC Executive Board incorporate the feedback from the membership and the RIPE NCC Management into their discussion and final decision on the RIPE NCC’s Activity Plan and Budget for the following year.

Benefits for RIPE NCC members / RIPE community:

• Allows RIPE NCC members’ interests to be represented by Executive Board

• Gives members the opportunity to give feedback directly to the Executive Board on the RIPE NCC’s Activity Plan and Budget

• Allows members to approve the RIPE NCC Charging Scheme and Financial Report

• Members can elect representatives to the Executive Board

• Provides opportunities to follow GM proceedings and cast votes from anywhere in the world

Organisational Activities Costs for 2013:

5. Unforeseen Activities

There may be activities that are entirely unforeseen at the time of writing the RIPE NCC Activity Plan 2013 or have started recently and are not at the stage where they can be quantified as a budgeted activity. A quick, well-focused reaction to the changing environment and new requirements of the RIPE NCC members and other stakeholders has always been a strong point of the RIPE NCC. In line with good Corporate Governance, any activities that fall under this category are developed in close consultation with the RIPE NCC Executive Board.

Appendix 1: Membership Services

The RIPE NCC provides the following member-only services:

• Distribution and Management of Internet Number Resources
• Auditing
• Resource Certification
• Listing Service

• Resource Transfers
• Reputation Service
• Filtered Resource Assistance
• LIR Portal
• IP Analyser
• Training Courses: LIR; IPv6; Routing Registry and Resource Certification (RPKI)
• DNSMON
• Near Real Time Mirroring (NRTM)
• RIPE Database Proxy Service

Appendix 2: Budget Figures 2013

RIPE NCC Budgeted Statement of Income & Expenditure 2013

Development of the RIPE NCC Reserves

The table below summarises the RIPE NCC’s capital development. The capital consists of the RIPE NCC reserves, including the surplus/deficit for the year at issue.

Note: *The expenses in 2008 include a payback from the Personnel Fund of EUR 1.5 million

Specification of Budgeted Income

Over the last several years, the RIPE NCC, the Regional Internet Registry (RIR) for Europe, the Middle East and parts of Central Asia, has led a wide range of IPv6 capacity building activities, working with partners in both the private and public sectors. This document details some of those activities already undertaken, and points to new strategies and relationships that will help ensure all Internet stakeholders are prepared for and aware of the role they can play in IPv6 deployment.

Contents

• Training activities
• Working with government and the public sector
• Supporting technical and industry forums
• Providing statistics and analysis
• Supporting RIPE community initiatives
• Online resources
• Multi-stakeholder forums
• World IPv6 Launch
• Contact RIPE NCC

Training activities

Hands-on training and education is the most significant element in ensuring the successful and widespread deployment of IPv6. The RIPE NCC has provided financial, administrative and technical support to a number of programs, cooperating with its members, the RIPE community, governments and regional groups.

The IPv6 Roadshow is an initiative from the Middle East Network Operators Group (MENOG) and the RIPE NCC that brings together international technical trainers and local government and enterprise network operators for 3-5 day practical workshops. Launched in 2010 and delivered to public sector participants free of charge, 11 IPv6 Roadshow events have been held in eight countries throughout the Middle East, with plans for further events throughout 2012-2013. They build on the IPv6 workshops that the RIPE NCC has been delivering as part of MENOG meetings since the initial event in 2008 (held alongside the RIPE 57 Meeting). The RIPE NCC is also investigating opportunities to launch an IPv6 Roadshow program in the Commonwealth of Independent States (CIS) region.

In addition, the RIPE NCC is coordinating with technical experts and trainers in several regions to roll out a "Train the Trainer" program. This will prepare teams of local trainers to spread the technical knowledge required to build and operate IPv6 networks far beyond what might be achieved by the RIPE NCC alone.

Meanwhile, RIPE NCC Training Services has been delivering a dedicated "IPv6 For LIRs" course since 2009, free for RIPE NCC members. Over 100 courses have been delivered to more than 2,000 technical and administrative staff.

Members of RIPE NCC staff also conduct outreach to universities in the RIPE NCC service region, helping to ensure that tertiary courses are incorporating the latest developments in policy and technology.

Working with government and the public sector

Government and public sector institutions have a key role to play in promoting the adoption of IPv6, and governments around the world have adopted a range of strategies and programs. The RIPE NCC has been proactive in bringing together representatives from government, the Internet technical community, regulators and law enforcement agencies in a several fora.

RIPE NCC Roundtable Meetings for Governments and Regulators have been held regularly since 2005, providing governments with an invite-only session for information sharing on issues including IPv6 deployment. Government and public sector staff who would like to take part in future RIPE NCC Roundtable Meetings are invited to send an email to roundtable@ripe.net.

The RIPE Cooperation Working Group provides an open forum to explore government-related issues further, and has regularly included presentations from government participants on their national IPv6 strategies. The Cooperation Working Group holds discussions on an open, publicly archived mailing list and meets at each RIPE Meeting.

In addition, the RIPE NCC has provided technical advice and expertise to government-led national IPv6 initiatives, task forces and meetings in countries including Norway, Germany, Netherlands, United Kingdom, Sweden, Qatar, Moldova, Belgium, UAE, Lebanon and Saudi Arabia. We welcome the opportunity to work further with these countries and others over the coming years.

Finally, the RIPE NCC has worked closely with Law Enforcement Agencies (LEAs) to build understanding of the security and registration issues relating to IPv6 deployment. This work has included targeted training sessions and regular RIPE NCC LEA Meetings alongside security industry events.

Supporting technical and industry forums

Raising awareness of IPv6 among all Internet stakeholders has been a priority for the RIPE NCC for many years. RIPE NCC staff and RIPE community representatives attend technical and non-technical events and conferences around the world to talk about the urgent need for IPv6 deployment for every kind of Internet stakeholder.

The RIPE NCC has also been instrumental in helping to establish two major new Network Operators’ Groups (NOGs) in recent years: the Middle East Network Operators Group (MENOG) and the Eurasian Network Operators Group (ENOG). These groups are important fora for sharing knowledge and expertise and facilitate the cooperation necessary to address specific local, national and regional concerns or issues. They are also an invaluable opportunity for local communities to build relationships with Internet experts and colleagues from around the world.

By contributing financial, technical and administrative expertise vital to developing and maintaining these organisations, the RIPE NCC is helping to ensure that network operators in some of the most rapidly growing parts of our service region have the opportunity to build expertise and experience through education, information sharing and professional networking.

RIPE NCC Regional Meetings also serve as important opportunities to bring together operators and other stakeholders in the Russian region, the Middle East and South-East Europe and allow them to meet with RIPE NCC staff, international experts and local peers about IPv6, whether through case studies, statistics, regional updates or hands-on workshops.

Providing statistics and analysis

Accurate statistics and in-depth analysis are key to developing IPv6 strategy in both the public and private sector. This is another area where the RIPE NCC has taken strong initiatives, both independently and with partner institutions.

The RIPE NCC has developed several publicly available tools that can be used to determine the progress of IPv6 deployment in countries, sectors or other groupings. IPv6 RIPEness measures the IPv6 preparedness of RIPE NCC members, while our study of IPv6 Enabled Networks provides insight into IPv6 deployment over time. More information on these and many other IPv6 measurement and analysis projects is available on RIPE Labs.

The Global IPv6 Deployment Monitoring Survey has been held annually since 2009. Initially backed by the European Commission, it has been developed by GNKS Consult in collaboration with TNO and the RIPE NCC, with input from the RIPE community. This survey provides an insight into Internet community readiness and attitudes to IPv6 deployment.

Data and analysis from each of the annual surveys is available on the website of the Number Resource Organization (NRO).

Supporting RIPE community initiatives

The RIPE community is an open forum of people interested in IP address policy, and an important source of knowledge and technical cooperation. As the secretariat for RIPE, the RIPE NCC has facilitated community-led initiatives such as the RIPE Document "Requirements For IPv6 in ICT Equipment", a document that provides government and large enterprise stakeholders with specific information to assist them in producing requests for proposals (RFPs) that include IPv6-compatibility.

The IPv6 CPE (Customer Premises Equipment) Survey is another community project coordinated by the RIPE NCC, which aims to identify the status of various CPEs in terms of IPv6 compatibility, specifically comparing company claims with real-world user experiences.

Online resources

The RIPE NCC maintains several online resources that provide a range of information for Internet stakeholders wanting to learn about IPv6.

IPv6 Act Now was first published in 2009 as a general resource for all Internet stakeholders seeking relevant information on IPv6. Alongside up-to-date statistics, presentations given at events, news and links, it includes a “How To Act Now” section, outlining the steps that different stakeholder groups can take in deploying IPv6.

RIPE Labs is a community platform for network operators, developers and industry experts to present, test and discuss innovative Internet-related tools, ideas and analysis. Users can browse the wide range of IPv6-related RIPE Labs articles and content.

Multi-stakeholder forums

The deployment of IPv6 is an issue that reaches far beyond the Internet technical community. The RIPE NCC - often working with the other RIRs under the umbrella of the NRO - has played a prominent role in the promotion of multi-stakeholder Internet governance events and forums over the past decade. Through these forums, the RIPE NCC has sought to educate and engage all Internet stakeholders in discussing IPv6-related issues. Find out more about the regional efforts undertaken by each RIR and coordinated global efforts on the NRO website.

Beginning with the second Internet Governance Forum (IGF) event held in Rio de Janeiro in 2007, the NRO has helped organise workshops and dedicated sessions at each IGF to examine the global progress of IPv6 adoption, and its implications for all Internet stakeholders. The RIPE NCC has also been active in promoting IPv6 awareness at regional and national Internet governance events, including EuroDIG and the Arab IGF (the first Arab IGF is scheduled to take place in October 2012).

In addition, RIPE NCC staff and members of the RIPE community have been active participants in discussions with the OECD and ITU, providing expertise, information and statistics to aid in the development of effective government strategies and policy in relation to IPv6. The RIPE NCC was also an active contributor to the ITU's IPv6 Group, which recently concluded its work by recognising the important cooperative efforts being undertaken by the Internet technical community and the public sector, particularly in emerging economies.

World IPv6 Launch

World IPv6 Launch was a global event that took place on 6 June 2012, bringing together thousands of leading Internet organisations and businesses, ranging from Google to Deutsche Telekom, in permanently enabling IPv6. The event built on the success of World IPv6 Day, which was held on 8 June 2011, and also celebrated the successful collaboration and contributions of the multi-stakeholder community to safeguarding the future growth of the Internet.

The RIPE NCC took an active role in World IPv6 Launch, including:

-  Co-organising an event with the University of Amsterdam on the day itself, briefing local and international press, monitoring Internet data and providing real-time information and analysis.

-  Collection and analysis of Internet data in the period leading up to and following 6 June 2012. Some results of this analysis have already been published on the RIPE Labs website:

• World IPv6 Launch - RIPEstat Case Studies
• First Measurement Results from IPv6 Launch
• Measuring World IPv6 Launch Participants From All Over The World
• RIPEstat DNS Widget for World IPv6 Launch

These articles can be found on RIPE Labs.

More information on the RIPE NCC's involvement in the World IPv6 Launch is available at: http://www.ripe.net/ipv6launch

Contact RIPE NCC

The RIPE NCC is keen to build relationships with all Internet stakeholders, including governments, regulators, law enforcement, industry and academe, and explore possibilities for IPv6 capacity building and awareness-raising.

We encourage all stakeholders to contact the following RIPE NCC staff members with any questions regarding our IPv6-related activities or proposals for collaborative projects and events.

You can contact the RIPE NCC at ipv6actnow@ripe.net. Specific requests or questions can also be sent directly to:

Paul Rendek

Director of External Relations

rendek@ripe.net

Chris Buckridge

External Relations Officer

chrisb@ripe.net

Susannah Gray

Communications Specialist

susannah@ripe.net

Learn more about:

• The RIPE NCC: https://www.ripe.net/lir-services/ncc
• The RIPE community: https://www.ripe.net/ripe
• RIPE Meetings: https://www.ripe.net/ripe/meetings

The RIPE NCC has a mandate from the RIPE community to keep an up-to-date and correct Internet number resource registry. In order to comply with this mandate, the RIPE NCC performs due diligence on organisations the RIPE NCC registers Internet number resource for.

Due diligence refers to the controls the RIPE NCC performs:

• Before the registration of Internet number resources (see section 1)
• After the registration of Internet number resources (see section 2)

This document outlines the minimum information and documentation the RIPE NCC requires to make sure that the registration data is valid and up-to-date.

1. Before the registration of Internet number resources

The RIPE NCC registers Internet number resources to legal or natural persons that:

• Are contractually bound with either the RIPE NCC or a sponsoring LIR (see below section 1.1) and
• Meet the criteria defined by the RIPE Policies (see below section 1.2)

1.1. Establishment of an agreement

Legal or natural persons requesting the registration of Internet number resources and related services must have signed an agreement with either the RIPE NCC or a sponsoring LIR.

The RIPE NCC performs due diligence on these contractual agreements to verify that the contractual parties exist (and are valid) and that they are properly represented in the signing of the agreement.

For consistency purposes, all legal or natural persons that sign an agreement with the RIPE NCC are considered as intending to request Internet number resources.

Agreements signed with a sponsoring LIR must be submitted to the RIPE NCC. If there are doubts over the correctness of this information, the RIPE NCC reserves the right to contact the person that appears to have signed the agreement with the sponsoring LIR and to confirm the correctness of this information.

Each agreement signed with either the RIPE NCC or with a sponsoring LIR must be accompanied by supporting documentation proving the existence (and validity) of the legal or natural person (see below).

If the signing party is a natural person

If the signing party is a natural person, we have to be sure of their identity (before an agreement is concluded with them). Proof of identification could be:

• Valid identification documents (e.g., identification card, passport)
• Valid driving license with photo, birth certificate issued by the relevant municipality, notary declaration proving the existence of the person, etc. in the case of countries with non-official identification documents (e.g., the UK)

If the signing party is a legal person

If somebody is signing on behalf of a legal person, the RIPE NCC must verify that:

• The legal person is appropriately established by the local authorities or registered with the local authorities (see below under a. Proof of establishment/registration) and
• An authorised representative of the legal person approves this application (see below under b. Approval by authorised representative)

a. Proof of establishment/registration

Normally, proof of establishment of a legal person can be registration with the local authorities. When this is not available, another proof of establishment may be required (e.g., the law according to which the legal person was established).

The RIPE NCC reserves the right to check the validity of this documentation by requesting further documentation or additional information from third parties.

b. Approval by authorised representative

A contract with either the RIPE NCC or a sponsoring LIR must be signed by an authorised representative of the legal person.

In order to obtain a degree of certainty that the person that signs a contract is indeed authorised to represent the legal person, they must indicate:

- Their name

- Their position in the structure of the legal person

If there are doubts over the correctness of this information, the RIPE NCC will request proof of identity of the signing person.

1.2. Compliance with RIPE policies

The RIPE NCC performs due diligence on requests for Internet number resources and the validity of the distribution criteria before registration in order to ensure compliance with the appropriate RIPE Policies (IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region, IPv6 Address Allocation and Assignment Policy, Autonomous System (AS) Number Assignment Policy).

During these checks, the RIPE NCC may ask for information about the network the Internet number resources are meant to be assigned to, as well as for documents supporting this information.

Details of this due diligence depend on the specific Internet number resources that are requested. These details can be found in the Request Forms and Supporting Notes and for IPv4 addresses in the IPv4 Registration Procedures.

2. After the registration or distribution of Internet number resources

After the agreement has been signed and the Internet number resources have been registered, the RIPE NCC must ensure that relevant registration data are maintained up-to-date and correct. To this end, the RIPE NCC performs audits (please see Audit activity) and has procedures to ensure that (legal or natural) persons that have registered Internet number resources are aware of the changes that must be communicated to the RIPE NCC (e.g.,see RIPE NCC procedural documents about transfers of Internet number resource records and change of a Member’s official name, Independent resources – contractual changes between sponsoring LIR and End User and Closure of LIR and Deregistration of Internet Number Resources.

Submission of a change

Changes in the registration data must be requested by:

- A registered contact person (somebody that has been delegated the authority to contact the RIPE NCC on behalf of the person that has been registered Internet number resources through the LIR portal); or

- An authorised person (somebody that has the general authority to act on behalf of the person that has been registered Internet number resources).

If there is any doubt about the identity or the authority of the person requesting these changes, the RIPE NCC reserves the right to request additional documentation (e.g., proof of identity, court decisions, etc.) and to request support or information from third parties.

The RIPE NCC will ask the requester to submit all relevant documentation that supports this change. Such documentation may include:

• Registration papers from local authorities of the country the organisation is registered in
• Court decisions establishing, recognising or ordering the change
• Agreements mentioning the change
• Confirmation signed by an authorised person

For more information, please see the procedural document about transfers of Internet number resource records and change of a Member’s official name .

The RIPE NCC reserves the right to check the validity of this documentation by requesting support or information from third parties.

3. Confidentiality and privacy issues

The RIPE NCC maintains a duty of confidentiality towards the legal or natural persons that request Internet number resources. Information passed to the RIPE NCC is securely stored and will not be distributed further than is necessary, within the RIPE NCC and beyond.

Details of the process of handling personal data by the RIPE NCC can be found in the RIPE NCC Privacy Statement.

1. Overview

2. Special Purpose Ranges

2.1. IPv6 PI Address Space

3. Routing Decisions

4. Longest Prefix Tables

1. Overview

This document details the address space managed by the RIPE NCC and the longest prefixes issued from different address ranges.

All IPv4 and IPv6 address space managed by the RIPE NCC and the current status of each address range can be found in the extended statistics file published daily at the URL below:

ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest

2. Special Purpose Ranges

2.1. IPv6 PI Address Space

The RIPE NCC assigns IPv6 Provider Independent (PI) prefixes in accordance with the IPv6 Address Allocation and Assignment Policy. The IPv6 PI assignments smaller than a /32 are taken from 2001:678::/29.

3. Routing Decisions

Routing decisions are the responsibility of network operators.

4. Longest Prefix Tables

The smallest prefix assigned by the RIPE NCC from any IPv4 range is a /29.

The smallest prefix assigned by the RIPE NCC from any IPv6 range is a /48.

1. Introduction

As per Certification Policy (CP) [RFC6484]:

This Public Key Infrastructure (PKI) is designed to support validation of claims by current holders of Internet number resources (INRs), in accordance with the records of the organisations that act as Certification Authorities (CAs) in this PKI. The ability to verify such claims is essential to ensuring the unambiguous distribution of these resources.

The structure of the Resource PKI (RPKI) is congruent with the number resource allocation framework of the Internet. The IANA allocates Internet number resources to Regional Internet Registries (RIRs), among others, as well as for special purposes [RFC5736]. The RIRs, in turn, manage the allocation of number resources to End Users, Internet Service Providers (ISPs) and others.

This PKI encompasses several types of certificates (see IETF document draft-ietf-sidr-arch-xx for more details):

• CA certificates for each organisation distributing INRs and for the INR holder

• End-entity (EE) certificates for organisations to validate digital signatures on RPKI-signed objects

In addition to the CP [RFC6484], relevant information about general PKI concepts may be found in RFC5280, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".

1. 1. Overview

This CPS describes:

• Participants

• Distribution of the certificates and Certificate Revocation Lists (CRLs)

• How certificates are issued, managed and revoked

• Facility management (physical security, personnel, audit, etc.)

• Key management

• Audit procedures

The PKI encompasses several types of certificates:

• CA certificates for each organisation distributing INRs and INR holders

• End entity (EE) certificates for organisations to validate digital signatures on RPKI-signed objects

The Certification Practice Statement is for convenience and informational purposes only. The Terms and Conditions for the RIPE NCC Certification Service can be found at:

http://www.ripe.net/certification/legal/index.html

The RIPE NCC Certification Service Terms and Conditions prevail over the CPS and the CPS does not affect the interpretation of these Terms and Conditions.

1. 2. Document Name and Identification

The name of this document is "RIPE NCC Certification Practice Statement for the Resource PKI".

1. 3. PKI Participants

As per CP [RFC6484]:

Note: In a PKI, the term "subscriber" refers to an individual or organisation that is a Subject of a certificate issued by a CA. The term is used in this fashion throughout this document, without qualification, and should not be confused with the networking use of the term to refer to an individual or organisation that receives service from an ISP. In such cases the term "network subscriber" will be used. Also note that, for brevity, this document always refers to PKI participants as organisations or entities, even though some of them are individuals.

1. 3. 1. Certification Authorities

This CPS covers three types of CAs for the RPKI: one Offline CA for the RIPE NCC, one Online CA for the RIPE NCC, and a number of hosted member CAs, which are all equivalent and may be described as a single CA for the purpose of this document.

The Offline CA is the top level CA allowing the RIPE NCC to act as a Trust Anchor in the RPKI. The Online CA allows the RIPE NCC to act as parent CA to RIPE NCC Members. This two layer approach provides a secure revocation and recovery capability in case the Online CA is compromised or becomes unavailable. The Offline CA issues certificates only to instances of the Online CA. The CRLs issued by the Offline CA are used to revoke only a certificate issued to the Online CA. The Online CA is used to issue RPKI certificates to RIPE NCC Members, to whom Internet number resources have been distributed.

In addition the RIPE NCC offers a hosted CA service to RIPE NCC Members. These CAs are designated "hosted member CAs". The hosted member CAs are highly automated, taking care of the major part of the operational burden for RIPE NCC Members who want to act as CAs in the RPKI.

See also section 1. 6 for definitions and acronyms used in this document.

1. 3. 2. Registration Authorities

There is no distinct Registration Authority (RA) for either the Offline CA or the Online CA operating under this CPS. The former needs no distinct RA capability because it issues certificates only to the Online CA. The Online CA depends on the sign-on mechanism used by the LIR Portal to identify individuals authorised to make requests. One of the possible sign-on mechanisms is by using an X.509 client certificate issued by the RIPE NCC Business PKI (see section 3. 2. 6 for more details). The RIPE NCC already establishes a contractual relationship with each subscriber (RIPE NCC Member) and assumes responsibility for distributing and tracking the current allocation of address space and AS Numbers. Since the RIPE NCC operates the LIR Portal sign-on service and BPKI CA, no distinct RA is used.

1. 3. 3. Subscribers

All RIPE NCC Members can receive distributions of IP addresses and AS Numbers from the RIPE NCC Online CA and thus are subscribers in the PKI sense.

1. 3. 4. Relying parties

As per CP [RFC6484]:

Entities or individuals that act in reliance on certificates or RPKI-signed objects issued under this PKI are relying parties. Relying parties may or may not be subscribers within this PKI. See section 1. 6 for the definition of an RPKI-signed object.

1. 3. 5. Other participants

The RIPE NCC operates a repository that holds certificates, CRLs and other RPKI-signed objects, such as Route Origin Authorisation (ROA) objects.

1. 4. Certificate Usage

1. 4. 1. Appropriate certificate uses

The certificates issued under this hierarchy are for authorisation in support of validation of claims of current holdings of address space and/or AS Numbers. With regard to routing security, an initial goal of this PKI is to allow the holder of a set of address blocks to be able to declare, in a secure fashion, the AS Number of each entity that is authorised to originate a route to these addresses, including the context of ISP proxy aggregation. Additional uses of the PKI, consistent with the basic goal cited above, are also permitted under this policy.

1. 4. 2. Prohibited certificate uses

Any uses other than those described in section 1. 4. 1 are prohibited.

1. 5. CPS Administration

1. 5. 1. Organisation administering the document

Since this CPS describes the implementation of the Offline CA, Online CA and hosted member CAs maintained by the RIPE NCC, this CPS is also administered by the RIPE NCC. However, it should be noted that approval procedures described in section 1. 5. 3-4 apply.

Whenever the implementation is changed, this CPS will be modified and republished as a RIPE Document. When this happens this will be announced through the appropriate communication channels (such as the RIPE NCC's ncc-announce mailing list).

1. 5. 2. Contact person

The RPKI CPS point of contact is the RIPE NCC, Singel 258, 1016AB, Amsterdam, Netherlands.

1. 5. 3. Person determining CPS suitability for the policy

This document is reviewed on behalf of the RIPE community by the Certification Authority Task Force (CA-TF). It is expected that the role of the CA-TF will be transferred to an appropriate RIPE Working Group when the RPKI becomes established as a RIPE NCC service.

1. 5. 4. CPS approval procedures

A RIPE certification policy dealing with issues such as validity times, revocation, re-issuance and access to the services involved is currently being developed by the RIPE community. The implementation of the various CAs (Offline, Online and hosted member CAs) will reflect this policy.

This CPS is not subject to the RIPE Policy Development Process. It provides a detailed outline of the implementation of the RPKI by the RIPE NCC. The CPS is publicly available and when necessary, additional reporting mechanisms, such as mailing lists or presentations at RIPE Meetings, are used to communicate the contents. When the RIPE NCC RPKI implementation is found to be inconsistent with applicable policies the RIPE NCC is committed to update the implementation and this CPS.

1. 6. Definitions and Acronyms

BPKI Business PKI: A BPKI is used by the RIPE NCC to identify RIPE NCC Members to whom RPKI certificates can be issued.

CA Certificate Authority. A CA is an entity that issues digital certificates for use by other parties. A CA may issue CA certificates to subordinate CAs. Thus a tree structure of CAs can be created, often dubbed Public Key Infrastructure (PKI). The RIPE NCC operates three levels of CAs in the PKI hierarchy, covered in this CPS:

Offline CA The RIPE NCC Offline CA. This CA is kept offline when not in use for security reasons, and acts as the top level in the hierarchy. For the moment this CA is making itself available as a Trust Anchor as described in [draft-TA-version4]. In the future this CA may become subordinate to a top level single Trust Anchor CA that will issue certificates to all RIRs.

Online CA The RIPE NCC Online CA. This CA is used on a daily basis to issue certificates to subordinate hosted member CAs.

Hosted member CA A hosted member CA that is technically hosted by the RIPE NCC as a RIPE NCC service in the LIR Portal.

CP Certificate Policy for the Resource PKI (RPKI). See [RFC6484].

CPS Certification Practice Statement. A CPS is a document that specifies the practices that a Certification Authority employs in issuing certificates.

ISP Internet Service Provider. An ISP is an organisation managing and selling Internet services to other organisations.

LIR Local Internet Registry. This is an organisation, typically a network service provider, that distributes IP addresses and AS Numbers to End Users and/or uses them in its own infrastructure. RIPE NCC Members are usually referred to as "LIRs".

LIR Portal The public portal provided by the RIPE NCC to its members (LIRs) that allows them access to various RIPE NCC services, including the hosted member CA service. The portal is also used to access the RIPE NCC Online CA by specific users, as described later in this CPS.

RIPE NCC Member A natural person or legal entity that has entered into the RIPE NCC Standard Service Agreement with the RIPE NCC.

RIR Regional Internet Registry. An RIR is an organisation that manages the distribution and registration of IP address and AS Numbers within a particular region of the world. At present, there are five RIRs: ARIN (North America), RIPE NCC (Europe, the Middle East and parts of Central Asia), APNIC (Asia-Pacific), LACNIC (Latin America and Caribbean) and AfriNIC (Africa).

RP Relying Party as defined in section 1. 3. 4.

TA Trust Anchor. The top CA certificate in the chain used for validation. Relying Parties choose which CA certificate they trust as being the top of the validation tree. Relying Parties may choose to trust more than one TA.

RPKI Objects and Certificates:

Certificate An X.509 PKIX Resource Certificate as described in [res-certificate-profile].

Certificates come in two flavors:

Certificate Authority (CA) Certificates are used by Certificate Authorities to issue subordinate certificates and EE certificates.

End Entity (EE) Certificates are embedded in RPKI-signed objects such as Manifests and ROAs and are used to sign these objects (see [RFC6488]). Note the CAs described in this CPS do not currently issue any multi-use End Entity Certificates as described in [res-certificate-profile].

ROA Route Origin Authorisation. This is a digitally signed object that identifies a network operator, identified by an AS Number, that is authorised to originate routes to a specified set of address blocks. See [RFC6482].

CRL Certificate Revocation List as described in [res-certificate-profile].

Manifest A signed object under the RPKI listing all subordinate signed objects and certificates for a CA certificate. See [RFC6486].

2. Publication And Repository Responsibilities

2. 1. Repositories

As per the CP [RFC6484], certificates, CRLs and RPKI-signed objects are made available to all network operators to download, to enable them to validate this data.

2. 2. Publication of Certification Information

RIPE NCC uploads the certificates, CRLs and RPKI-signed objects that it issues to a local repository system that operates as part of a world-wide distributed system of repositories.

Offline CA

The CA certificate for the RIPE NCC Offline CA is intended to be used as a Trust Anchor by relying parties. The Trust Anchor Locator, as per [RFC6490], follows:

rsync://rpki.ripe.net/ta/ripe-ncc-ta.cer

MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0URYSGqU

z2myBsOzeW1jQ6NsxNvlLMyhWknvnl8NiBCs/T/S2XuNKQNZ+wBZ

xIgPPV2pFBFeQAvoH/WK83HwA26V2siwm/MY2nKZ+Olw+wlpzlZ1

p3Ipj2eNcKrmit8BwBC8xImzuCGaV0jkRB0GZ0hoH6Ml03umLprR

sn6v0xOP0+l6Qc1ZHMFVFb385IQ7FQQTcVIxrdeMsoyJq9eMkE6D

oclHhF/NlSllXubASQ9KUWqJ0+Ot3QCXr4LXECMfkpkVR2TZT+v5

v658bHVs6ZxRD1b6Uk1uQKAyHUbn/tXvP8lrjAibGzVsXDT2L0x4

Edx+QdixPgOji3gBMyL2VwIDAQAB

Online CA

The Online CA publishes subordinate certificates, CRLs and RPKI-signed objects under:

rsync://rpki.ripe.net/repository/33/36711f-25e1-4b5c-9748-e6c58bef82a5/1/

Hosted member CAs

The hosted member CAs publish subordinate signed objects in the repository that is hosted by the RIPE NCC:

rsync://rpki.ripe.net/repository

The exact URI of the publication point is unique per hosted member CA and can be found in the hosted member CA certificate as described in [res-certificate-profile].

Note the repository structure is defined in [RFC6481].

2. 3. Time or Frequency of Publication

A certificate will be published within 24 hours after issuance.

2. 4. Access Controls on Repositories

Write access to the repositories is limited to the systems running the Offline CA, Online CA and hosted member CAs.

3. Identification And Authentication

3. 1. Naming

3. 1. 1. Types of names

The Subject of each certificate issued by the RIPE NCC is identified by an X.500 Distinguished Name (DN).

For the Offline CA the self-signed CA certificate is published as a Trust Anchor, as described in section 2. 2. The subject is ‘CN=ripe-ncc-ta’.

For all other certificates controlled by the Offline CA, Online CA and hosted member CAs the subject has the format CN=<pub key hash>, where the public key hash is a Base64 encoded form of the public key SHA-1 hash, as described in section 2.1 of [RFC4387].

3. 1. 2. Need for names to be meaningful

The Subject name in each subscriber certificate will be unique to the public key found on the certificates.

Note: The name of the holder of an address block or AS Number is intended to not be "meaningful" in the conventional, human-readable sense, since certificates issued under this PKI are used for authorisation in support of applications that make use of attestations regarding INR holdings, not for identification.

3. 1. 3. Anonymity or pseudonymity of subscribers

Although subject names in certificates issued by this registry are not meaningful, and may appear "random,", anonymity is not a function of this PKI, and thus no explicit support for this feature is provided.

3. 1. 4. Rules for interpreting various name forms

None.

3. 1. 5. Uniqueness of names

The generated subject based on the public key hash, as described in 3.1.1, reduces the likelihood of accidental collisions to a negligible minimum.

3. 1. 6. Recognition, authentication, and role of trademarks

Because the subject names are not intended to be meaningful, there is no provision to recognise or authenticate trademarks, service marks, etc.

3. 2. Initial Identity Validation

3. 2. 1. Method to prove possession of private key

For the Offline CA, proof of possession of the private keys used for the self-signed certificate can be determined internally.

For the Online CA that acts as subscriber to the Offline CA, possession of the private keys is effected via the procedures used to generate and manage these keys. Specifically, the RIPE NCC uses a hardware security module (HSM) to generate the key pairs for each of these CAs and thus assures that the private key is appropriately associated with the public key in the certificates issued by each of these CAs

For the hosted member CAs that act as subscribers to the Online CA, possession of the private keys is effected by the system. Note that the hosted member CAs are managed systems and operators do not access the keys directly. These CAs will contact the Online CA as needed via protocols internal to the RIPE NCC. These protocols also cover proof of possession of the private keys.

3. 2. 2. Authentication of organisation identity

The hosted Member CA is available only to RIPE NCC Members. The RIPE NCC has already established procedures to verify the identity of the RIPE NCC Members. These procedures are explained here:

http://www.ripe.net/info/faq/membership/newlir-setup.html#1

However it should be noted that certificates issued under this PKI do not attest to the identity of certificate holders. This is also reflected by the seemingly random subject names as described in 3.1.3.

For hosted member CAs the RIPE NCC is able to map a logged in user to a specific organisation, and the organisation can be mapped to a specific public key. Thus the RIPE NCC is able to map these public keys to a specific set of resources as represented in the RIPE NCC records.

3. 2. 3. Authentication of individual identity

The individuals who are authorised to operate the Offline CA are authenticated by possession of the necessary HSM key cards and via physical and procedural security access controls.

For hosted member CAs, individual identity is delegated to the RIPE NCC Member’s LIR Portal "admin" user. Admin users must set up users for their LIR and associate them with the ‘certification‘ role in order to grant individuals access to the certification section.

The admin user’s identity can be (re-)established using the admin password reset procedure:

https://lirportal.ripe.net/lirportal/activation/activation_request.html

The reset procedure involves two halves of a code that are sent via two separate paths, email and fax, that need to be combined in order to reset the "admin" account’s password.

For the Online CA, the same mechanism is used as described for hosted member CA users. It should be noted, however, that these users require an additional role that can not be set through the public user management interface.

3. 2. 4. Non-verified subscriber information

No non-verified subscriber data is included in certificates issued under this certificate policy.

3. 2. 5. Validation of authority

Access to the Offline CA is restricted to a Developer that has access to the Unix account on the server. In addition, the HSM key cards are protected by pass phrases known only to the individual CA Operators (see section 5. 2. 3 for a description of the CA Operator role).

Access to the Online CA is restricted to CA Operators using the LIR Portal to log in and having an additional role enabled by the administrators of the single sign-on system (this role can not be set by others).

Access to the hosted member CA is restricted to users of the LIR Portal that have the "certification" role enabled by the "admin" user for their registry.

3. 2. 6. Criteria for interoperation

The RPKI is not intended to interoperate with any other PKI at this stage.

The function of the Online CA will be extended in the future to interoperate with the other four RIRs and RIPE NCC Members operating their own CAs.

3. 3. Identification and Authentication for Re-Key Requests

3. 3. 1. Identification and authentication for routine re-key

For the Offline CA and Online CA the same identification and authentication mechanisms apply as described in section 3. 2. 3.

For hosted member CAs routine re-keys are automated by the software and no explicit authentication is required. A routine re-key is initiated whenever the current key for a hosted member CA is older than five years.

The key roll over algorithm is described in [RFC6489].

3. 3. 2. Identification and authentication for re-key after revocation

The old key can be revoked as the final step in key rollover algorithm [RFC6489], after a new key has been activated.

In our implementation, old keys are not automatically revoked after a routine re-key. Explicit revocation of old keys can be done by CA Operators of the Offline CA and Online CA. CA Operators for the Online CA can also revoke old keys for specific hosted member CAs. Identification and authentication for these roles has been described in section 3. 2. 3.

The RIPE NCC implementation may change following discussion of the key rollover standard, as the standard is currently unclear about whether revocation of the old key should be done immediately. Current belief is that there is no reason (security or operational) why old keys should not be automatically revoked after a successful re-key, so that may well be implemented in the near future.

3. 4. Identification and Authentication for Revocation Request

For hosted member CAs it should be noted that user actions in the interface may result in revocation of EE certificates used for objects (such as ROAs) that should be invalidated.

4. Certificate Life-Cycle Operational Requirements

4. 1. Certificate Application

4. 1. 1. Who can submit a certificate application

Any RIPE NCC Member may request a certificate.

4. 1. 2. Enrolment process and responsibilities

For the Offline CA a Developer can configure and initialise the CA on a server controlled by the RIPE NCC (see section 5. 2. 1 for a description of the Developer role).

For the Online CA a Developer can install and initialise the application. When this has been done a CA Operator can log in and initialise the Online CA.

For hosted member CAs: RIPE NCC Members may use a hosted member CA hosted by the RIPE NCC as part of the RIPE NCC LIR portal. In order to activate the hosted member CA an "admin" user must log in and grant the "certification" role to a normal user. This user must then log in and ensure that a client certificate has been generated for them (or generate one if this is missing). The user that has the "certification" role will then be able to click through on a link labeled "Certification". This link will take the user to a page where they must explicitly opt in to the hosted member CA service - they do this by clicking "Yes, I want to activate my hosted member CA". After activation, a mostly automated hosted member CA will be created. Authentication and authorisation for further automated processes should be considered transitive from the moment that user opted-in and activated the hosted member CA, as described here.

4. 2. Certificate Application Processing

For hosted member CAs an initial CA certificate is requested automatically by the system when the authorised user chooses to opt in to the service.

4. 2. 1. Performing identification and authentication functions

See section 3. 2. 3.

4. 2. 2. Approval of certificate applications

The online CA will issue certificates to hosted member CAs with a validity time to the end of the calendar year, plus a six months grace period to allow for renewal before the certificate expires.

All Provider Aggregatable (PA) resources registered to the RIPE NCC Member at the time of issuance will be included in the certificate.

For hosted member CAs, the system will automatically request renewal of the CA certificate that lists all eligible resources when new resources are received by the RIPE NCC Member and/or a new validity time is applicable.

4. 2. 3. Time to process certificate applications

The RIPE NCC will issue a certificate attesting to resource allocations within one business day of approval of the certificate application.

4. 3. Certificate Issuance

4. 3. 1. CA actions during certificate issuance

The Offline CA will produce a response message that includes all publishable certificates and other objects after the certificate has been issued. This message can be physically transferred to the Online CA, where it is published.

The Online CA and hosted member CAs make all subordinate certificates and objects available for publication. In practice, the system will make a best effort to publish these materials as soon as possible, but as described in section 2. 3, publication should happen within no more than 24 hours of issuance.

4. 3. 2. Notification to subscriber by the CA of issuance of certificate

Publication of a certificate in the repository operated by RIPE NCC is the means by which a subscriber is notified of certificate issuance. This procedure is employed by all CAs covered by this CPS.

4. 3. 3. Notification of certificate issuance by the CA to other entities

Publication of a certificate in the repository operated by RIPE NCC is the means by which other entities are notified of certificate issuance.

4. 4. Certificate Acceptance

4. 4. 1. Conduct constituting certificate acceptance

A subscriber is presumed to have accepted a certificate issued by any of the Certificate Authorities covered by this CPS and published in the RIPE NCC repository unless the subscriber contacts the RIPE NCC.

4. 4. 2. Publication of the certificate by the CA

Certificates will be published in the repository system within one business day of being issued by any of the CAs covered by this CPS.

4. 5. Key Pair and Certificate Usage

A summary of the use model for the IP Address and AS Number PKI is provided below.

4. 5. 1. Subscriber private key and certificate usage

The hosted member CAs receive CA certificates from the Online CA. This means that these certificates could in principal be used to issue subordinate CA certificates. However, the hosted system does not provide this functionality. The hosted member CA certificates will only be used (by the system) to issue EE certificates used for RPKI-signed objects (such as ROAs) and manifests.

4. 5. 2. Relying party public key and certificate usage

Reliance on a certificate must be reasonable under the circumstances. If the circumstances indicate a need for additional assurances, the relying party must obtain such assurances in order for such reliance to be deemed reasonable.

Before any act of reliance, relying parties MUST independently (1) verify that the certificate will be used for an appropriate purpose that is not prohibited or otherwise restricted by this CPS (see section 1. 5), and (2) assess the status of the certificate and all the CAs in the chain (terminating at the RIPE NCC Trust Anchor) that issued the certificates relevant to the certificate in question. If any of the certificates in the certificate chain have been revoked, the relying party is solely responsible for determining whether reliance on a digital signature to be verified by the certificate in question is acceptable. Any such reliance is made solely at the risk of the relying party.

If a relying party determines that use of the certificate is appropriate, the relying party must utilise appropriate software and/or hardware to perform digital signature verification as a condition of relying on the certificate. Moreover the relying party MUST validate the certificate in a manner consistent with the RPKI certificate profile [RFC6487], which specifies the extended validation algorithm for RPKI certificates.

4. 6. Certificate Renewal

Note that the hosted member CAs do not issue CA certificates to subordinate CAs and there is no need for certificate renewal for EE certificates used for signed objects. However, hosted member CAs are mentioned a few times in this section as children of the Online CA.

4. 6. 1. Circumstance for certificate renewal

For hosted member CAs: When new Internet number resources are associated with a RIPE NCC Member or a new validity time is applicable (see section 4. 2. 2) a certificate will be renewed.

Note that in case Internet number resources are no longer associated with a RIPE NCC Member the Online CA will re-issue a new certificate, minus those Internet number resources, and revoke overclaiming certificates, as described in section 4. 9.

4. 6. 2. Who may request renewal

For hosted member CAs, requests for renewal are fully automated.

For the Online CA, RIPE NCC staff with the Online CA Administrator role can request renewal from the Offline CA.

For the Offline CA, Internet number resources may have to be added to the self-signed certificate. RIPE NCC staff with the appropriate role may perform this action.

4. 6. 3. Processing certificate renewal requests

The same stipulations listed in section 4. 2. 2 apply here.

4. 6. 4. Notification of new certificate issuance to subscriber

See section 4. 3. 2.

4. 6. 5. Conduct constituting acceptance of a renewal certificate

See section 4. 4. 1.

4. 6. 6. Publication of the renewal certificate by the CA

Both the Offline CA and Online CA will publish renewed subordinate CA certificates within one business day of issuance.

4. 6. 7. Notification of certificate issuance by the CA to other entities

See section 4. 3. 2.

4. 7. Certificate Re-Key

Note that the hosted member CAs do not issue CA certificates to subordinate CAs and there is no need for certificate re-key for EE certificates used for signed objects. However hosted member CAs are mentioned a few times in this section as children of the Online CA.

4. 7. 1. Circumstance for certificate re-key

As per the RPKI CP, re-key of a certificate will be performed only when requested, based on:

1. Knowledge or suspicion of compromise or loss of the associated private key, or

2. Expiration of the cryptographic lifetime of the associated key pair

If a certificate is revoked to replace the resource extensions (see [res-certificate-profile], the replacement certificate will incorporate the same public key, not a new key, unless the subscriber requests a re-key at the same time. If the re-key is based on a suspected compromise, then the previous certificate will be revoked.

Section 5.6 of the Certificate Policy notes that when a CA signs a certificate, the signing key should have a validity period that exceeds the validity period of the certificate. This places additional constraints on when a CA should request a re-key.

4. 7. 2. Who may request certification of a new public key

For hosted member CAs, an automated key roll over is performed when the key has been in use for five years. Authentication and authorisation for this is considered transitive from opt in (see section 4. 1. 2).

For the RIPE NCC Online CA, a manual key rollover is planned to be performed every five years. This manual rollover can be initiated by RIPE NCC staff in the Online CA Administrator role.

4. 7. 3. Processing certificate re-keying requests

The same stipulations listed in section 4. 2. 2 apply here.

4. 7. 4. Notification of new certificate issuance to subscriber

See section 4. 3. 2.

4. 7. 5. Conduct constituting acceptance of a re-keyed certificate

See section 4. 4. 1.

4. 7. 6. Publication of the re-keyed certificate by the CA

For all Certificate Authorities covered by this CPS, a re-keyed certificate will be published in the repository system within one business day of being issued by this CA.

4. 7. 7. Notification of certificate issuance by the CA to other entities

See section 4. 3. 3.

4. 8. Certificate Modification

4. 8. 1. Circumstance for certificate modification

Certificate modification is not applicable to the CAs described here. Renewal is used when new resources are to be certified, or a new validity time is applicable, as described in section 4. 6. Re-issuance and revocation is used when resources are no longer held by an entity, as described in section 4. 9.

4. 9. Certificate Revocation and Suspension

4. 9. 1. Circumstances for revocation

Certificates can be revoked for several reasons:

• A signed object needs to be invalidated

• One or more listed Internet number resources are no longer associated with the RIPE NCC Member

• As the last steps when doing a planned re-key (clean up)

• As the last steps when doing an unplanned re-key because a loss or compromise of the old key has come to light

4. 9. 2. Who can request revocation

For the hosted member CAs, revocation of their CA certificate can be performed by RIPE NCC staff on request or when RIPE NCC staff have reason to believe the keys are compromised. In the latter case this will always be performed as the final step of an emergency key rollover for the hosted member CA. The other circumstances for revocation, most notably when ROA objects need to be invalidated because a user of the hosted member CA changes the specification, are managed automatically by the system.

For the Online CA, the RIPE NCC may manually request revocation of the old CA certificate as soon as a key rollover has been performed. Related events, most notably the revocation of the EE certificates used for manifests, are managed by the system.

4. 9. 3. Procedure for revocation request

When one or more of the Internet number resources listed in a certificate are no longer associated with a RIPE NCC Member, the Online CA will:

• Re-issue a new certificate, minus the lost Internet number resources, but maintaining all other properties

• Publish the new certificate using the same publication point as before, thus replacing the old certificate

• Revoke any non-expired certificates held by the hosted member CA that list the lost Internet number resources, thus invalidating any signed objects (such as ROAs) that refer to these Internet number resources.

4. 9. 4. Revocation request grace period

Any party that is able to identify the need for revocation that is not already handled by the system and operators is expected to notify the RIPE NCC within one business day.

4. 9. 5. Time within which CA must process the revocation request

The RIPE NCC will process a revocation request within one business day of receipt and validation of the request.

4. 9. 6. Revocation checking requirement for relying parties

As per the CP, a relying party is responsible for acquiring and checking the most recent, scheduled CRL from the issuer of the certificate, whenever that relying party validates a certificate.

4. 9. 7. CRL issuance frequency

Each CRL will carry a nextScheduledUpdate value and a new CRL will be published at or before that time. The RIPE NCC will set the nextScheduledUpdate value when it issues a CRL to signal when the next scheduled CRL will be issued. The CAs covered by this CPS use different values:

Offline CA: 3 months from the moment of issuance

Online CA: 24 hours from the moment of issuance

Hosted member CAs: 24 hours from the moment of issuance

As a matter of good operational sense, all CAs covered by this CPS will strive to republish and re-issue a new CRL before the next scheduled update value in time to deal with any operational problems.

It should be noted that the values listed here may be used by relying parties to determine the need to fetch an updated CRL. In particular this means that a possible revocation by the Offline CA may go unnoticed for three months - this should not be a problem since the production keys are protected by an HSM. A revoked ROA for a hosted member CA may not be noticed for 24 hours. The values here should be regarded as a compromise between various aspects, including the operational burden of re-signing (for Offline CA), time needed to be able to do an emergency restore, efficiency of caching in the global RPKI, propagation time of revocation in the global RPKI.

4. 9. 8. Maximum latency for CRLs

A CRL will be posted to the repository system within one hour of issuance.

4. 9. 9. On-line revocation/status checking availability [OMITTED]

4. 9. 10. On-line revocation checking requirements [OMITTED]

4. 9. 11. Other forms of revocation advertisements available [OMITTED]

4. 9. 12. Special requirements re key compromise [OMITTED]

4. 9. 13. Circumstances for suspension [OMITTED]

4. 9. 14. Who can request suspension [OMITTED]

4. 9. 15. Procedure for suspension request [OMITTED]

4. 9. 16. Limits on suspension period [OMITTED]

4. 10. Certificate Status Services

These CAs do not support Online Certificate Status Protocol (OCSP), but rather use Certificate Revocation Lists (CRLs).

4. 10. 1. Operational characteristics [OMITTED]

4. 10. 2. Service availability [OMITTED]

4. 10. 3. Optional features [OMITTED]

4. 11. End of Subscription [OMITTED]

4. 12. Key Escrow and Recovery [OMITTED]

4. 12. 1. Key escrow and recovery policy and practices [OMITTED]

4. 12. 2. Session key encapsulation and recovery policy and practices [OMITTED]

5. Facility, Management and Operational Controls

5. 1. Physical Controls

5. 1. 1. Site location and construction

For the Offline CA, operations are conducted within a physically protected area of an office building in which the RIPE NCC is a tenant. This building is located at:

Singel 258

1016AB Amsterdam

The Netherlands

The RIPE NCC space within this facility includes offices and meeting spaces and two machine rooms.

For the Production CA and hosted member CAs, core cryptographic operations are performed by two machines physically located in two different data centers in a load balanced (and fail over) set up.

The two data centers are:

Nikhef:

Science Park 105

1098XG Amsterdam

The Netherlands

Telecity 2:

Kuiperbergweg 13

1101AE Amsterdam

The Netherlands

5. 1. 2. Physical access

For the Offline CA, physical access is restricted to the RIPE NCC's IT staff and senior managers. The access system relies on personal smart cards. Access to areas is logged every moment of the day on our access system, this data is mirrored at the same moment to another server, located in another building. CCTV is in operation and recordings are kept for one week.

For Nikhef, physical IT staff may request access for themselves. IT management may request access for others. Access is logged by the reception and the electronic access system. The server is physically located in one of five racks rented by the RIPE NCC. The racks are kept locked and have their own key set. They are located in a machine room that includes rack space rented by third parties.

For Telecity2, IT staff may request access for themselves. IT management may request access for others. The server is physically located in one of four racks rented by the RIPE NCC. The racks are housed in a special suite, dedicated to the RIPE NCC only. Only Telecity2 staff can open the suite for us and access is logged by the reception.

5. 1. 3. Power and air conditioning

The offline CA server is located in an air conditioned server room in the RIPE NCC office building. At the moment of writing we do not monitor power, but we are running a project to overcome this. It should be noted that power outages are not expected to have an impact on this CA since it is kept offline when not in use.

For Nikhef, power consumption and air conditioning are monitored by the provider. Should power consumption exceed the maximum allowance, the RIPE NCC will receive an invoice, but power will not be cut. Nikhef has an uninterruptible power supply (UPS) to overcome immediate power failures, and a generator with enough fuel to cover for arrival of more fuel and/or fixing the power failure.

For Telecity2, power consumption and air conditioning are monitored by the provider. Should power consumption exceed the maximum allowance, the RIPE NCC will receive an invoice, but power will not be cut. Telecity2 has a UPS to overcome immediate power failures, and a generator with enough fuel to cover for arrival of more fuel and/or fixing the power failure.

5. 1. 4. Water exposures

The RIPE NCC server room used by the Offline CA is located on the second floor of the office building. This is above sea level.

The server room located at Nikhef is located on the first floor of their building. This is above sea level.

The server room located at Telecity2 is located on the first floor of their building.

5. 1. 5. Fire prevention and protection

The RIPE NCC server room used by the Offline CA has fire extinguishing equipment that is sufficient for any fire in the server rooms. The server rooms are monitored by our security company, and in case of fire they will contact the fire brigade of Amsterdam.

5. 1. 6. Media storage

Whenever the Offline CA is operated, all data is backed up (encrypted where needed) to a network filesystem that is mirrored between the Nikhef and Telecity2 datacenters. In addition this data is backed up off-site nightly (see section 5. 1. 8).

For the Online CA and hosted member CAs all data is stored (encrypted where needed) on a network filesystem that is mirrored between the Nikhef and Telecity2 datacenters. In addition this data is backed-up off-site nightly (see section 5. 1. 8).

5. 1. 7. Waste disposal

When servers reach their end of life, the hard disks are physically destroyed by RIPE NCC staff.

Key cards will be destroyed if they are found to be broken. If a key card is lost a new card set will be generated and all HSM keys will be migrated to the new card set in order to ensure that the lost card is rendered useless.

There is no other waste that may contain sensitive data.

5. 1. 8. Off-site backup

The network filesystem, used to store the data from the CAs, is backed up every night to another fileserver. This second fileserver is also backed up every night to another backup server, located in Ede, the Netherlands. The distance between this site and Amsterdam is approximately 70km. Ede is above sea level.

5. 2. Procedural Controls

5. 2. 1. Trusted roles

For the Offline CA:

System Operator Has access to the server. Ensures system is set up correctly. Can perform restore using quorum of Administrative Card Set used to protect the keys. See section 6 for more details on card set controls used for the HSM.

CA Operator Has access to one out of ten key cards from the Operator Card Set (OCS) needed to operate the Offline CA. Three out of ten key operators must be present to provide a quorum for operations involving the offline CA.

There are ten CA Operators.

Five of the CA operators also have access to one of five cards from the Administrative Card Set (ACS) that initialised the HSM. Three of these cards are needed for a restore operation (see section 6).

Developer Has access to the source code used to run the Offline CA. Is responsible for developing, testing and deploying new releases.

In addition, the Developer has de-facto technical knowledge of the set-up and will therefore facilitate specific Offline CA operations, including:

• Transferring outstanding request (certificate and/or revocation) from the Online CA to the Offline CA

• Providing technical knowledge for operating the Offline CA

• Transferring the response to the Online CA and making sure the response is properly processed

For the Online CA:

System Operator Same as for Offline CA.

Developer Has access to the source code used to run the Online CA. Is responsible for developing, testing and deploying new releases.

In addition the Developer can configure values used by the software, such as publication frequency.

CA Operator Has access to the user interface. Can perform key re-key operations, revoke old keys, and has access to the system status page that allows switching on/off of the background services for the Online CA.

ACS Card holder The ACS Card Holder receives one of five cards making up the ACS for the HSMs used for the Online CA and hosted member CAs. Three of these five cards are needed to perform a restore.

There are five ACS Card Holders.

For the hosted member CAs:

System Operator Same as for Offline CA.

Developer Same as for Online CA.

CA Operator Has access to the user interface. The system automates all cryptographic operations such as creating and revoking EE certificates, publication etc.

The CA Operator can perform the following actions only:

• Activate the hosted member CA

• Create/update/delete ROA configurations (the objects themselves are managed by the system)

RIPE NCC Operator This role is available to all CA Operators for the Online CA. It allows access to all actions that a member CA Operator could perform. In addition it allows re-key operations and revocation of old keys. The role also has access to the system status page that allows switching on/off of the background services for hosted member CAs.

5. 2. 2. Number of persons required per task

For all roles and CAs listed in the above section only one person is required per task, except for CA operations for the Offline CA; here three out of ten persons are required.

5. 2. 3. Identification and authentication for each role

For the Offline CA:

System Operator Root access to the server running the Offline CA is limited to RIPE NCC IT staff. Since the system does not accept any incoming network traffic this requires that the IT staff have access to the server room (see section 5. 1. 2) in order to log in.

CA Operator Has no account on the server, but will be asked by the Developer to present their key card and enter their passphrase for authentication and authorisation of the operation.

Developer The Developers can login to the Unix account that is used to run the Offline CA software.

For the Production CA:

System Operator Same as for Offline CA.

Developer The Developers have access to the Unix account that is used to run the software.

CA Operator The CA operator uses the RIPE NCC single sign-on system to log in to the user interface. The login process requires that a username, password and client certificate are presented. In addition, the CA Operator must be a member of a specific group that is not available to public users of the LIR Portal.

For the hosted member CAs:

System Operator Same as for Online CA.

Developer Same as for Online CA.

CA Operator The CA operator uses the RIPE NCC single sign-on system to log in to the user interface. The login process requires that a username, password and client certificate are presented. In addition the CA Operator must be made a member of the "certification" group by the "admin" user for their LIR in the LIR Portal.

5. 2. 4. Roles requiring separation of duties

The CA Operator role for the Offline CA is performed by RIPE NCC staff from various departments. The people fulfilling these roles have no other roles in the CAs operated by the RIPE NCC.

5. 3. Personnel Controls

5. 3. 1. Qualifications, experience and clearance requirements

Staff members are assigned to the roles mentioned in section 5. 2. 1 only if supervisory personnel deem them to be sufficiently trustworthy and only after they have undergone in-house training for the role.

5. 3. 2. Background check procedures

All RIPE NCC staff undergo normal employment reference checks.

5. 3. 3. Training requirements

The RIPE NCC provides its CA staff with training upon assignment to a CA role as well as on-the-job training as needed to perform their job responsibilities competently.

5. 3. 4. Retraining frequency and requirements

The RIPE NCC provides its CA staff with re-training as needed to continue performing their job responsibilities competently.

5. 3. 5. Job rotation frequency and sequence

There are no requirements for enforced job rotation among staff fulfilling trusted CA roles.

5. 3. 6. Sanctions for unauthorised actions

If RIPE NCC staff are determined to have performed activities inconsistent with RIPE NCC RPKI policies and procedures, appropriate disciplinary action will be taken.

5. 3. 7. Independent contractor requirements

No independent contractor or consultant is used to perform any of the roles for the CAs covered by this document. Contractors who are required to perform any maintenance functions on CA severs or cryptographic modules must be escorted and directly supervised by RIPE NCC staff at all times when in sensitive areas.

Independent contractors and consultants may be part of the development team, but never constituting more than 50% of the total team.

5. 3. 8. Documentation supplied to personnel

Training for staff assigned to a trusted CA role is primarily via mentoring. An internal wiki is maintained by RIPE NCC staff as a further training aid.

5. 4. Audit Logging Procedures

5. 4. 1. Types of events recorded

For the Offline CA no audit logging is implemented.

Audit records are generated for operations performed by the CA operators for the Online CA and hosted member CAs. Audit records include the date, time, responsible user and summary content data relating to the event. Records are stored in a database and are visible through the user interface.

The physical access control system separately maintains logs for access to the areas housing sensitive CA equipment.

5. 4. 2. Frequency of processing log

Logs will be analysed during general audits or after a suspected incident.

5. 4. 3. Retention period for audit log

Audit records for the Online CA and hosted member CAs are included in the nightly database back-up and retained off-site for a minimum of two years.

5. 4. 4. Protection of audit log

At the moment, no additional measures are taken to protect the audit logs, as compared to normal back-up procedures. This process is currently under review, and may change in the near future.

5. 4. 5. Audit log backup procedures

See section 5. 4. 3.

5. 4. 6. Audit collection system (internal vs. external) [OMITTED]

5. 4. 7. Notification to event-causing subject [OMITTED]

5. 4. 8. Vulnerability assessments

The RIPE NCC employs an outside firm to perform periodic vulnerability assessments for computer and network systems and the software that was developed in house to operate the CAs covered by this CPS. These reports are provided to the RIPE NCC Security Officer and the RIPE NCC Managing Director.

5. 5. Key Changeover

The Offline CA currently acts as a Trust Anchor. An emergency key rollover has been practiced for the current set-up.

The Online CA key pair changes on a scheduled basis. The algorithm used is described in [RFC6489]. Initiating the re-key is a manual action initiated by a Online CA Operator via the user interface.

The hosted member CAs perform an automated re-key using the algorithm described in [RFC6489].This happens whenever a key has been in use for five years.

5. 6. CA or RA Termination

The RIPE NCC has been granted sole authority by the Internet Assigned Numbers Authority (IANA) to manage allocation of IP address space and AS Number resources in the RIPE NCC service region, which includes Europe, the Middle East and parts of Central Asia. The RIPE NCC has established the RPKI for its region consistent with this authority. There are no provisions for termination and transition of the CA function to another entity.

6. Technical Security Controls

This section describes the security controls used by the RIPE NCC.

6. 1. Key Pair Generation and Installation

6. 1. 1. Key pair generation

For the RIPE NCC RPKI and hosted member CAs operated by RIPE NCC, key pairs are generated using a hardware cryptographic module. The module used for this purpose is certified as complying with FIPS 140-2 level 3. The hardware cryptographic module employed for this process is the nCipher nShield9000e.

6. 1. 2. Private key delivery to subscriber

Private keys can not be extracted from the HSM in unencrypted form. The Offline CA and Online CA only require the public key from their subscribers. The hosted member CAs have no subscribers.

6. 1. 3. Public key delivery to certificate issuer

For the Offline CA, a custom mechanism has been developed to transfer certificate sign requests and/or revocation requests that include the Online CA public key hash. Since the Offline CA server is not connected to a network, the transfer is done using XML files on a USB stick (a.k.a. sneaker net).

The hosted member CAs and Online CA are managed by the same software. Therefore the Online CA has direct access to the member public keys and no key delivery is involved.

6. 1. 4. CA public key delivery to relying parties

For the Online CA and hosted member CAs, public keys are included in CA and EE certificates issued by these CAs. The keys are delivered to relying parties by publication of the CA certificates and signed objects that include EE certificates (ROAs and manifests) to the repository.

The Offline CA is intended to be used as a Trust Anchor by relying parties. Its Trust Anchor Locator [RFC6490] is described in section 2. 2. The RIPE NCC will publish this Trust Anchor Locator at:

http://www.ripe.net/certification/validation

It may also publish this via other mechanisms, such as printed material, RIPE Meeting presentations or in Member Updates.

6. 1. 5. Key sizes

As per [RFC6485], the CAs covered by this CPS use a 2048-bit RSA key for all keys, including the keys used for EE certificates.

6. 1. 6. Public key parameters generation and quality checking

The nCipher HSMs used by the CAs covered by this CPS were certified as complying with FIPS 140-2 level 3. Though the details of the key generation implementation used by these modules are not known by the RIPE NCC, the RIPE NCC trusts that this certification implies that key generation and quality checking by the modules is sufficiently safe.

6. 1. 7. Key usage purposes (as per X.509 v3 key usage field)

The key usage extension bit values are consistent with [RFC5280]. For the RIPE NCC RPKI CA certificates, the keyCertSign and cRLSign bits are set TRUE. All other bits (including digitalSignature) are set FALSE, and the extension is marked critical.

6. 2. Private Key Protection and Cryptographic Module Engineering Controls

6. 2. 1. Cryptographic module standards and controls

The Offline CA is operated under FIPS 140-2 level 3, requiring three out of ten operator keys to be presented for key pair generation and signing operations.

The Online CA and hosted member CAs employ a cryptographic module evaluated under FIPS 140-2 level 3 [FIPS]. However, because these systems need to be running 24/7 and need to be able to perform key generation and signing operations without human intervention, they are operated under FIPS 140-2 level 2 to allow unattended operation.

6. 2. 2. Private key (n out of m) multi-person control

As described in section 6. 2. 1, three out of ten CA Operators are required to operate the Offline CA.

For the Online CA and hosted member CAs no multi-person control is used during normal operation.

6. 2. 3. Private key escrow

No private key escrow procedures are required for this PKI.

6. 2. 4. Private key backup

For all CAs covered by this CPS, the private keys are stored on disk by the HSM using Advanced Encryption Standard (AES) encryption with a key that is protected by a 3-out-of-5 Administrative Card Set.

For the Offline CA, the files containing the encrypted private key and other necessary information are copied to fileshare that is duplicated between the Nikhef and Telecity2 data centres after every operation. These files are backed up off-site on a nightly basis to a remote site located in Ede, the Netherlands, 70 km from Amsterdam.

For the Online CA and hosted member CAs, all encrypted private keys and other necessary information are stored on a fileshare that is duplicated between the Nikhef and Telecity2 data centers after every operation. These files are backed up off-site on a nightly basis to a remote site located in Ede, the Netherlands, 70 km from Amsterdam.

6. 2. 5. Private key archival

There will be no archive of private keys by this CA.

6. 2. 6. Private key transfer into or from a cryptographic module

The encrypted private keys and other information described in section 6. 2. 4 may be restored to another HSM. In order to do this, a system administrator must have access to a quorum of the Administrative Card Set (ACS); in this case three out of five cards are needed.

Also note that this mechanism allows multiple HSMs to share the same internal key and encrypted managed keys stored on a network file system. This allows for the load balancing and fail-over set-up that is used for the Online CA and member CAs.

6. 2. 7. Private key storage on cryptographic module

The private keys for all CAs covered by this CPS may be temporarily stored inside the cryptographic module and will be protected from unauthorised use in accordance with the FIPS 140-2 requirements applicable to the module.

Long term storage is done by storing the keys to disk in encrypted form, as described above.

6. 2. 8. Method of activating private key

For the Offline CA, activating the keys requires that three out of five Operator cards are presented by individual senior staff, as described in section 6. 2. 1.

For the Online CA and hosted member CAs, the private keys can be used by all processes that run on the physical servers that host the nCipher nShield9000e PCI cards.

6. 2. 9. Method of deactivating private key

The Offline CA keys are de-activated as soon as processing is finished. Subsequent operation will require re-activation as described above. In addition the server is physically turned off when not in use. As soon as processing is done, the server is backed up and is shut down again.

The cryptographic modules for the RIPE NCC RPKI CA and hosted member CAs will operate in an unattended mode, on a 24/7 basis.

6. 2. 10. Method of destroying private key

Keys are not stored long-term inside the hardware security modules used by the CAs covered by this CPS. The HSMs store the keys on disk in encrypted form. When keys are no longer in use they are deleted from disk. Since they were encrypted in the first place, no additional action is taken to zero the bytes or purge them from long term back-up.

6. 2. 11. Cryptographic Module Rating

The cryptographic module(s) used by all CAs covered by this CPS are certified under FIPS 140-2, at level 3 [FIPS].

For the Online CA and hosted member CAs, these modules are operated at FIPS-140-2 level 2 to allow for automatic processing.

6. 3. Other Aspects of Key Pair Management

6. 3. 1. Public key archival

Because this PKI does not support non-repudiation, there is no need to archive public keys.

6. 3. 2. Certificate operational periods and key pair usage periods

For the Offline CA that is intended to be used as a Trust Anchor by relying parties, the RIPE NCC is committed to support the same key pair for at least five years after 1 Jan 2011.

For the Online CA and hosted member CAs, key pairs have an intended validity interval of five years.

6. 4. Activation Data

6. 4. 1. Activation data generation and installation

For the Offline CAs, the 3/5 Administrative Card Set (ACS) and the 3/10 Operator Card Set (OCS) were generated following the procedures described in the HSM manual. The cards were distributed among five of the ten Offline CA Operators described in section 5. 1. 2.

For the Online CA and the hosted member CAs, the 3/5 Administrative Card Set was generated following the procedures described in the HSM manual. The cards were distributed between the five Offline CA Operators described in section 5. 1. 2.

6. 4. 2. Activation data protection

See section 6. 2. 8.

6. 4. 3. Other aspects of activation data

None.

6. 5. Computer Security Controls

6. 5. 1. Specific computer security technical requirement

The Offline CA is kept offline when not in use. It is only switched on when in use and is never connected to any network. All data (requests, responses, backups) are transferred using otherwise empty USB sticks.

The Online CA and hosted member CAs are operated on machines in the RIPE NCC internal service VLAN. The user interface is made available through a firewall that load balances requests to two different back-end proxy servers. These will delegate requests for the "certification" section only to the back-end machines.

6. 5. 2. Computer security rating [OMITTED]

6. 6. Life Cycle Technical Controls

6. 6. 1. System development controls

The software for all CAs covered by this CPS was developed in-house by the RIPE NCC, working together with external consultants. The RIPE NCC software development follows an "agile" methodology that includes test-driven development. Unit test coverage of at least 75% and succeeding functional tests were required for all components. All software is developed and maintained under a revision control system (subversion) and releases are tagged. Continuous integration is triggered for each commit and each release and ensures that any possible broken tests come to light before a release is made final. Code is subject to a code review during development. The RIPE NCC software development uses bug and issue tracking software for all software development. Prior to deployment to the production service, code is versioned and deployed to a standalone platform for integration tests. The same packages used for these integration tests are deployed to the production service, provided that no problems were found.

6. 6. 2. Security management controls

The RIPE NCC uses the same access policy for the servers used to run the Offline CA and the Online and member CAs: only staff from the responsible departments have SSH access. SSH access is limited to the RIPE NCC office and VPN networks. Access to the systems is logged.

It should be noted that in addition, the Offline CA server is physically switched off when not in use.

6. 6. 3. Life cycle security controls

See section 6. 6. 1 for a description of the software life cycle, including testing prior to release. Deployment of new software releases is scheduled, with planned back-out, and post-deployment testing of service.

Host operating systems are maintained to current patch levels, and CERT and other security advisories are tracked for relevant vulnerabilities.

Hosts and network infrastructure are physically maintained and replaced in a duty cycle averaging four years. Onsite maintenance contracts cover normal business hours support for this hardware.

6. 7. Network Security Controls

The vLAN used for the servers that host the CAs covered by this CPS is protected by router Access Control Lists (ACLs) and/or by firewall rules. This applies both to incoming and outgoing traffic from/to other vLANs, and the same applies for the Internet at large. We do not currently have a dedicated vLAN for these servers, though we plan to look into this in the near future.

Sensitive data is protected by at least one of TLS or SSL with client and server certificates, and with SSH version 2 with 1024-bit keys, or better. Extra care is taken for private data: PGP encryption is mandatory.

6. 8. Time-Stamping

The RPKI operated by the RIPE NCC does not make use of or provide a Time Stamping Authority as defined by RFC3161.

7. Certificate and CRL Profiles [OMITTED]

Please refer to the Certificate and CRL Profile [RFC6487].

8. Compliance Audit and Other Assessments

The RIPE NCC employs an outside firm to perform periodic vulnerability assessments for computer and network systems, including those that are part of the RPKI CA.

8. 1. Frequency or Circumstances of Assessment

Assessments are initiated at the behest of the Information Security Officer, Business Owner (Service Manager) or RIPE NCC Senior Management.

8. 2. Identity/Qualifications of Assessor

The outside firm engaged to perform the assessment is a commercial entity specialising in IT security assessment.

8. 3. Assessor's Relationship to Assessed Entity

The outside firm engaged to perform the assessment is a paid contractor with no other relationships to the RIPE NCC.

8. 4. Topics Covered by Assessment

The external vulnerability assessment performed on RIPE NCC IT systems covers a variety of topics including (but not limited to) network port scanning, testing of web application interfaces, review of user authentication and authorisation mechanisms, logging and auditing, network security, and configuration management.

8. 5. Actions Taken as a Result of Deficiency

The RIPE NCC Security Officer reviews all recommendations made by the external assessor and will advise on remedial actions as appropriate.

8. 6. Communication of Results

The external vulnerability reports are provided to all relevant stakeholders within the RIPE NCC including, but not limited to the Business Owner, Information Security Officer and Senior Management.

9. References

[RFC5280] D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", May 2008.

[RFC6484] Seo, K., Watro, R., Kong, D., and Kent, S. , "Certificate Policy for the Internet IP Address and AS Number PKI", work in progress, July 2007.

[RFC6487] Huston, G., Loomans, R., Michaelson, G., "A Profile for X.509 PKIX Resource Certificates", work in progress, June 2007.

[RFC6481] Huston, G., Loomans, R., Michaelson, G., "A Profile for Resource Certificate Repository Structure", work in progress, May 2010.

[RFC6482] Lepinski, M., Kent, S., Kong, D., "A Profile for Route Origin Authorizations (ROAs)", work in progress, November 2010.

[RFC6488] Lepinski, M., Chi, A., Kent, S., "Signed Object Template for the Resource Public Key Infrastructure", work in progress, October, 2010

[RFC6486] Austein, R., Huston, G., Kent, S., Lipinski, M., "Manifests for the Resource Public Key Infrastructure", work in progress, November 2010

[RFC6489] Huston, G., Michealson, G., Kent, S., "CA Key Rollover in the RPKI", December 2010

[RFC6490] Huston, G., Weiler, S., Michealson, G., Kent, S., "Resource Certificate PKI (RPKI) Trust Anchor Locator", work in progress, November 2010

[RFC6485] Huston, G., "A Profile for Algorithms and Key Sizes for use in the Resource Public Key Infrastructure", work in progress, November 2010

[RFC4387] P. Gutmann, Ed., "Internet X.509 Public Key Infrastructure - Operational Protocols: Certificate Store Access via HTTP", Feb 2006.

[res-certificate-profile] Huston, G., Loomans, R., Michaelson, G., "A Profile for X.509 PKIX Resource Certificates".

[up/down] G. Houston, R. Loomis, B. Ellacott, R. Austien, "A Protocol for Provisioning Resource Certificates,"

[BGP4] Y. Rekhter, T. Li (editors), A Border Gateway Protocol 4 (BGP-4). IETF RFC 1771, March 1995.

[FIPS] Federal Information Processing Standards Publication 140-2 (FIPS PUB 140-2), "Security Requirements for Cryptographic Modules", Information Technology Laboratory, National Institute of Standards and Technology, May 25, 2001.

[RSA] Rivest, R., Shamir, A., and Adelman, L. M. 1978. A method for obtaining digital signatures and public-key cryptosystems. Commun. ACM 21, 2 (Feb.), 120-126.

In the near future, the RIPE NCC will deplete its free IPv4 address pool. This will have a substantial effect on the RIPE NCC budget and its cost development over the coming period. Generally speaking, the RIPE NCC budget will increase because of the IPv4 depletion. This is a result of the increased work on ensuring accuracy of registration, including additional audits, thorough review of IPv4 requests and the impact of the "Run Out Fairly" policy.

The budgeted costs for 2012 are 7% higher than the budgeted costs for 2011. This is caused by increased outreach and training activities to support IPv6 adoption, increased costs to cater for IPv4 depletion and the enhancement of Information Services and Measurement activities. For the particulars, please see: "RIPE NCC Activity Plan 2012".

RIPE NCC Budgeted Statement of Income & Expenditure 2012

Expenses per Activity

Below is an overview of the full-time equivalents (FTEs), operational expenses and capital expenses per activity. FTEs are rounded to absolute numbers. All amounts are in kEUR. The overview is presented on two levels.

Development of the RIPE NCC Reserves

The table below summarises the RIPE NCC’s capital development. The capital consists of the RIPE NCC reserves, including the surplus/deficit for the year at issue.

Note: *The capital in 2007 includes the member rebate of EUR 2.5 million.

**The expenses 2008 include a payback from the Personnel Fund of EUR 1.5 million

Income and Fees per Billing Category

Table of Contents

1. Introduction

2. Clearing House – General Information

3. Clearing House Procedure

   1. Redistribution from Clearing House

   2. Timeline of Clearing House Procedure

4. Changes in Member Status

   1. Closing and/or Default of a Member

   2. Merging of Two Members

   3. Changes in Billing Size

1. Introduction

This document provides additional information on the RIPE NCC Clearing House and should be read in conjunction with the RIPE NCC Standard Service Agreement. The RIPE NCC Standard Service Agreement will be authoritative over this document.

The RIPE NCC is a not-for-profit organisation. Nevertheless, a positive or negative result can be achieved in a particular year. In principle, this would be subject to Corporate Income tax. However, the RIPE NCC has set up special arrangements with the Dutch tax authorities to move any surplus or deficit to accumulate in a “special” reserve. This “special” reserve, known as the Clearing House, gives the RIPE NCC a stable financial position to operate soundly and continuously.

The Dutch tax authorities have set a maximum to this reserve. To avoid any taxation or payout from the Clearing House, the RIPE NCC Board and the RIPE NCC Management aim to stay within this set boundary.

The Clearing House procedure was approved by the Dutch tax authorities in 1998 and has been amended in 2003 and updated in 2011. The Clearing House procedure started with the 1998 financial year.

The RIPE NCC Executive Board reserve the right to make changes, in accordance with Dutch tax law, to this procedure as necessary.

2. Clearing House – General Information

The Clearing House procedure has been developed to comply with the Dutch tax ruling describing how to redistribute an excess amount to the RIPE NCC Members. A RIPE NCC Member is defined as a natural person or legal entity that receives services from the RIPE NCC and has been invoiced a service fee for the year at issue. The Clearing House may equal a maximum of three times the total amount of RIPE NCC service fees in the relevant financial year as stated in the audited financial report. This income excludes the sign-up fee and any other Service fees or payments made to the RIPE NCC that are not stipulated by the RIPE NCC Standard Service Agreement.

Only Members that have fulfilled their financial obligations towards the RIPE NCC in the relevant financial year can participate in the Clearing House procedure. If during the year the RIPE NCC Standard Service Agreement has been terminated by either party no participation in the Clearing House procedure will take place.

3. Clearing House Procedure

The surplus or deficit that results from the audited financial statements of the financial year will be transferred to the Clearing House. The accumulated amounts will be reserved in the Clearing House. In case this total amount exceeds a total of three times the income from the Members Service fees of the financial year at issue, the RIPE NCC will redistribute the excess amount from the Clearing House to the Members.

3.1 Redistribution from the Clearing House

The Member's share of the excess amount will be equal to the percentage of its fee contribution to the service fees paid to the RIPE NCC over the past 3 years, including the relevant financial year in which the Clearing House exceeded the maximum.

A Member's percent share of the total paid fees is calculated by dividing that Member's paid fee by the total of all other Members' paid fees for the past 3 years.

This excess amount will not actually be paid out but will be credited to the Member’s account and will be deducted from the Service fee for the year after the Clearing House procedure has taken place. In case of termination of the RIPE NCC Standard Service Agreement the excess amount payable will not be redistributed.

3.2 Timeline of Clearing House Procedure

The Clearing House procedure will take place within 90 days of receipt of the audited financial statements. The settlement for the excess amount will be done with the invoices for the year following the year in which the Clearing House procedure has taken place.

4 Changes in Member Status

4.1 Closing and/or Default of a Member

If during the year the RIPE NCC Standard Service Agreement has been terminated by either party, any excess amounts payable to the Member will remain in the Clearing House.

4.2 Merging of Two Members

In case of a merger between two Members, the fee will be the total amount paid by the two registries for the year at issue. In case of Clearing House redistribution they will then receive a percentage reflecting the total amount paid.

4.3 Changes in Billing Size

Changes in billing size during the year at issue have no impact on the Clearing House redistribution of the excess amount as the fee paid by the Member determines the amount that will be settled.

Translation

In this translation, an attempt has been made to be as literal as possible without jeopardising the overall continuity. To guarantee a high quality translation with as little room as possible for differences in interpretation a District Court sworn translator has executed the translation. Inevitably, differences may occur in translation, and if so the Dutch text will by law govern.

Article 1 – Definitions

In these Articles of Association the following capitalised terms shall have the following meanings. Wherever reference is made to documents drafted in the English language only the English title of these documents has been used:

- Activity Plan – the annual plan stating the Vision and Focus of the association as well as its current activities and the new activities for the coming year.

- Annual Meeting – the annual General Meeting as referred to in paragraph 14.2 of these Articles of Association.

- Annual Report – the report as stated in section 2:391 of the Dutch Civil Code (“DCC”; jaarverslag), including the Financial Report.

- Audit Report - the certificate in respect of the correctness of the Financial Report as referred to in section 2:393(5) DCC issued by an accountant as referred to in section 2:393(1) DCC.

- Charging Scheme – the document stating the annual contribution (service fee) to be paid by the Members.

- Financial Report – the report as stated in section 2:361 DCC (jaarrekening), including the balance sheet, statement of income and expenditure and the (explanatory) notes.

- General Meeting – the meeting of the Members of the Association as referred to in article 14 of these Articles of Association.

- In Writing – any textual message transmitted by current means of (electronic) communication, including (postal) mail and e-mail, but not including verbal communication and Short Messaging Service (SMS).

- Members – candidate or full members of the association as referred to in article 4 of these Articles of Association.

- Standard Service Agreement (SSA) – the agreement entered into between the association and a Member

- Supporter – the legal entity or natural person who has entered into an agreement with association to make annual donations to support the association (supporter agreement).

Article 2 – The Association: Name and Seat

2.1 The name of the Association is:

Réseaux IP Européens Network Coordination Centre (RIPE NCC).

The name of the Association may be abbreviated to RIPE NCC.

2.2 The official seat of the Association is in Amsterdam, the Netherlands.

Article 3 – The Association: Objective

The objective of the Association is to perform activities for the benefit of the Members, primarily activities that the Members need to organize as a group. This object can be sub-divided into the following activities:

- Registration Activities related to the role of the Association as Regional Internet Registry;

- Co-ordination Activities, including the support of the stable operation of the Internet;

- Administration Activities, including all regular reports and administrative support as well as all other general administrative tasks which cannot be attributed to a specific activity;

- New Activities, including all activities which are necessary to react to the rapidly changing world of the Internet; and to do all that is connected therewith or may be conducive thereto, all this in the widest sense of the word. Making profit is not an object of the Association.

Article 4 – Membership: candidate and full members

4.1 Legal entities or natural persons who have entered into the Standard Service Agreement with the association shall become candidate members of the Association. Employees of the Association are not allowed to be a member of the Association or to enter into the Standard Service Agreement with the Association.

4.2 After a period of six (6) months the candidate membership of the Association shall be converted into full membership.

4.3 If in these Articles of Association the terms Membership and Members are used, they shall also be understood to mean candidate membership and candidate members, unless otherwise stated.

Article 5 – Membership: Register

5.1 The Executive Board shall keep a Register in which the names and addresses of all Members are recorded, stating the date on which the Standard Service Agreement was signed, on which date their Membership started.

5.2 The Register as mentioned in paragraph 5.1 will record which natural person/persons is/are duly authorised to:

a. represent the Member at the General Meeting;

b. serve as the Member’s Administrative Contact;

c. serve as the Member’s Technical Contact.

5.3 Members shall notify the Executive Board of the authorised person(s) as referred to in paragraph 5.2 and of any changes therein. Without such notification, the person identified as the authorised person in the Standard Service Agreement and the designated Administrative Contact and Technical Contact shall be recorded in the Register as persons authorised to represent the Member at the General Meeting.

5.4 Every Member shall notify the Executive Board of the address, including an e-mail address, to be used by the Association to give that Member notice of the General Meeting. Without such notification, the postal address stated in the Standard Service Agreement and the last designated e-mail address of the Administrative Contact of that Member shall be recorded in the Register as the address(es) to be used by the Executive Board for sending convocations for a General Meeting.

5.5 The Register will record which members have agreed to the procedure of electronic Participation and voting. For each of these members the Register will record which natural persons are authorised to cast votes electronically.

Article 6 – Membership: End of Membership

6.1 Membership shall end:

a. on the death (natural person) or the dissolution (legal entity) of a Member;

b. by notice of termination by the Association in accordance with this article;

c. by notice of termination by the Member in accordance with this article;

d. by notice of termination upon termination of the Standard Service Agreement with the Association;

e. by notice of termination if the Membership is no longer possible due to legal or statutory restrictions; or

f. if the Member is a natural person: by notice of termination upon the person becoming an employee of the Association.

6.2 The Association may give notice of termination of Membership if the Association cannot reasonably be required to continue the Membership.

Notice of termination by the Association shall be given by the Executive Board, which must observe a reasonable period of notice. The length of such notice shall be dependent on the severity of the reason for termination.

In the event the Membership is terminated pursuant to paragraph 6.1 e or 6.1f, notice of termination may be given with immediate effect.

6.3 Notice of termination of Membership by a Member may only be given with three months' notice. However, said Member can terminate his Membership with immediate effect (by notice of termination) if the Member cannot reasonably be required to continue the Membership.

6.4 If the applicable notice period as referred to in the provisions of the preceding paragraphs is not observed, the Membership shall terminate at the earliest time possible after the date on which notice was given.

6.5 A Member may immediately terminate his Membership without observing any period of notice within one month after having become aware or after having been notified of a resolution restricting his rights or increasing his obligations, in which case the resolution shall not apply to him. However, the Members shall not have such right to immediately terminate their Membership within one month if it concerns a resolution which alters the rights and obligations relating to the annual contribution (service fee).

6.6 If Membership ends in the course of a financial year of the Association, the annual contribution shall nevertheless remain due by the Member in full.

Article 7 – Membership: Contribution and Obligations

7.1 The Members shall be obliged to pay an annual contribution pursuant to the Charging Scheme as referred to in the Standard Service Agreement. Each Charging Scheme adopted by the General Meeting shall continue to apply until a new Charging Scheme has been adopted.

7.2 Failure to pay (part of) the annual contribution will automatically result in suspension of the Member, during which period the Member cannot attend the General Meeting nor exercise his voting rights.

7.3 The Executive Board may attach obligations to the Membership of the Association, provided that these obligations contribute to the realisation of the objects of the Association.

Article 8 – Executive Board: General

8.1 Subject to the restrictions under the Articles of Association the Executive Board shall be charged with the management of the Association, including, but not limited to, the adoption and, where necessary, amendment of the budget and Activity Plan.

8.2 The Executive Board of the Association shall consist of at least three and at most five natural persons. They shall be members of the Board in a personal capacity and do not have to be Members of the Association. Employees of the Association cannot be appointed members of the Executive Board.

8.3 The Executive Board shall designate from its midst a chair, a secretary and a treasurer.

8.4 The secretary shall keep minutes of the proceedings at all meetings of the Executive Board. The minutes shall be sent to the Executive Board members and shall be adopted by them In Writing as soon as possible after the meeting.

Within two weeks of adoption the minutes of an Executive Board meeting shall be published on the website of the Association.

Article 9 – Executive Board: Appointment, Suspension and Dismissal

9.1 The members of the Executive Board shall be appointed by the General Meeting from a list of nominees to be drawn up by the Members.

A nomination for the appointment of a member of the Executive Board shall need the written support of at least five Members and shall be submitted no later than three weeks before the General Meeting. If three weeks before the General Meeting the number of candidates nominated for appointment as referred to above does not exceed the number of vacancies, the Executive Board shall have to nominate one or more candidates for appointment so that the total number of proposed candidates shall exceed the number of Executive Board members to be appointed by the General Meeting.

9.2 If the members or the Executive Board should fail to draw up a list of nominees within three months after the vacancy has occurred, the General Meeting may appoint a member of the Executive Board at its own discretion.

9.3 The Executive Board may decide to appoint natural persons as advisers to the Executive Board. An adviser to the Executive Board can attend all Executive Board meetings. He/she can advise the Executive Board on all subjects. An adviser to the Executive Board is not an Executive Board member and therefore does not have the right to vote at meetings of the Executive Board.

9.4 A member of the Executive Board may be suspended or dismissed by the General Meeting at any time. A resolution to suspend or dismiss a member of the Executive Board shall require a majority of at least two thirds of the votes cast.

9.5 Any suspension may be extended one or more times, but may not last longer than three months in total. If at the end of that period no decision has been taken on termination of the suspension or on dismissal, the suspension shall end.

9.6 The membership in the Executive Board shall become effective at the end of the General Meeting at which the member was appointed and shall automatically terminate at the end of the Annual Meeting in the third calendar year after the year in which the Executive Board member was appointed. An Executive Board member shall be eligible for immediate re-appointment.

9.7 If a member of the Executive Board is appointed to an interim vacancy, then in derogation of paragraph 9.6 membership shall terminate at the end of the Annual Meeting in the third calendar year after the year in which his/her predecessor was appointed.

9.8 If a member of the Executive Board is appointed to a vacancy which was not filled prior to his/her appointment, then in derogation of paragraph 9.6 membership shall terminate at the end of the Annual Meeting in the calendar year as determined by the Executive Board in accordance with a schedule of appointment and termination to be drawn up by the Executive Board.

9.9 Furthermore, membership in the Executive Board shall end by a three months notice of termination by this Executive Board member or by his/her death.

Article 10 – Executive Board: Authority and Representation

10.1 The Executive Board shall have full authority provided there are at least two members of the Executive Board left. If there are fewer than three members left, the Executive Board shall as soon as possible convene a General Meeting at which one or more new Executive Board members shall be appointed.

10.2 The Executive Board may, at its own discretion, consult the Members about any decisions it plans to take.

10.3 Subject to the prior approval of the General Meeting the Executive Board has authority to enter into agreements to purchase, dispose of or encumber registered property or to enter into agreements whereby the Association commits itself as guarantor or joint and several debtor, warrants performance by a third party or undertakes to provide security for a debt of a third party. The said approval shall also apply to the authority to represent the Association in respect of such acts.

10.4 The authority to represent the Association shall be vested in the Executive Board. Two members of the Executive Board, acting jointly, shall also be authorised to represent the Association.

However, in all matters in which the Association has a conflict of interest with one or more members of the Executive Board, the General Meeting may designate one or more persons in order to represent the Association.

10.5 Acts by the Association intended to have legal effect against a Member of the Association or a member of the Executive Board shall be put In Writing.

Article 11 – Approval of Resolutions of the Executive Board

11.1 The General Meeting shall be authorised to subject resolutions of the Executive Board other than those mentioned in paragraph 10.3 - to its approval. These resolutions shall be clearly specified and notified to the Executive Board In Writing.

11.2 The lack of approval as referred to in paragraph 11.1 does not affect the representative authority of the Executive Board or its members.

Article 12 – Management Team

12.1 The Executive Board shall appoint a Management Team consisting of one or more Managing Directors who shall be employed by the Association.

12.2 The Executive Board shall delegate to the Management Team all operational decisions with respect to the Standard Service Agreements.

12.3 The Executive Board may delegate other powers to the Management Team and give a limited power to one or more members of the Management Team to represent the Association.

12.4 There is an arbitration procedure in place for the settlement of disputes between Members of the Association on the one hand and the Management Team on the other regarding decisions of the Management Team with respect to the Standard Service Agreements.

The Executive Board may appoint new arbiters to the arbitration pool, propose the dismissal of current arbiters and propose changes the arbitration procedure. The authority to approve new arbiters, to dismiss current arbiters or to change the arbitration procedure is vested in the General Meeting.

12.5 The Management Team will be invited to attend the meetings of the Executive Board.

12.6 The remuneration and further conditions of employment for each member of the Management Team shall be determined by the Executive Board.

12.7 The Executive board may lay down regulations regarding the duties of the Management Team or the individual members of the Management Team.

Article 13 – Financial Year. Financial Report. Annual Report

13.1 The financial year of the Association shall coincide with the calendar year.

13.2 The Executive Board shall keep notes in respect of the financial position of the Association in such a manner that the rights and obligations of the Association can be ascertained at any time.

13.3 At the Annual Meeting the Executive Board shall submit an Annual Report on the course of business of the Association and on the policy conducted.

13.4 The Executive Board shall submit the Financial Report and Audit Report for the approval of the Annual Meeting. These documents shall be signed by the members of the Executive Board; if one or more signatures are missing, this shall be stated giving the reason(s).

13.5 After expiration of the period as referred to in paragraph 14.2, any Member of the Association may commence legal proceedings against all the members of the Executive Board in order to enforce the obligations as stated in paragraph 13.3 and 13.4.

13.6 The Executive Board shall keep the records referred to in this article for the legally
required period.

Article 14 – General Meeting: General Meetings. Annual Meetings. Extraordinary General Meetings

14.1 All powers of the Association not conferred in other constituent bodies by law or by these Articles of Association shall be vested in the General Meeting.

14.2 The Annual Meeting shall be held within six months after the end of the financial year. If the General Meeting has decided to extend this period pursuant to the provisions of paragraph 15.5(a), the Annual Meeting shall be held no later than on the day on which the period of extension ends.

14.3 Extraordinary General Meetings shall be held as often as the Executive Board deems necessary.

Article 15 – General Meeting: Convocations. Agenda. Resolutions

15.1 The Executive Board shall send the convocations for the General Meeting, including the agenda containing the subjects for the General Meeting, a URL to the verbatim text of the proposed resolutions and, if applicable, the draft Activity Plan and draft budget, to the Members at least four weeks before the Meeting. In the event the Executive Board does not have full authority under paragraph 10.1 of these Articles of Association, the authority to convoke a meeting shall be vested in the Management Team.

15.2 General Meetings shall be convened by the Executive Board by e-mails sent to the e-mail addresses as recorded in the Register (see article 5).

15.3 The agenda for the Annual Meeting shall include the following subjects:

a. the adoption of the Financial Report;

b. the discharge of the Executive Board with regard to its actions as they appear from the Annual Report;

c. the filling of any vacancies in the Executive Board.

15.4 The following subjects shall be placed on the agenda for the Annual Meeting or on the agenda for another General Meeting to be held in the same calendar year:

a. a discussion of the draft Activity Plan and draft budget after a presentation by the Executive Board;

b. the adoption of the Charging Scheme with respect to the coming financial year upon proposal of the Executive Board;

c. a discussion of the policy and the quality of services (to be) rendered by the Association.

15.5 If applicable, the agenda for the Annual Meeting or another General Meeting shall also include the following subjects:

a. the extension of the period within which the Executive Board shall submit the Annual Report (as referred to in paragraph 14.2), which shall also constitute an extension of the period within which the Annual Meeting - at which the Annual Report is to be submitted - shall be held;

b. the filling of any vacancies in the Executive Board;

c. upon proposal by the Executive Board: adoption of amendments to the Standard Service Agreement;

d. upon proposal by the Executive Board: approval of new arbiters and/or dismissal of current arbiters and/or adoption of amendments to the arbitration
procedure;

e. other proposals and/or discussion points put forward by the Executive Board or (a group of) Members of the Association (pursuant to paragraph 15.6) and announced in the convocation for the Meeting.

15.6 On the written application of a group of Members who are jointly entitled to cast at least two percent (2%) of the total number of possible votes, other subjects will be added to the agenda. Such an application, accompanied by the verbatim text of the resolutions proposed by the said Members, shall have to be sent to the Executive Board at least two weeks before the Meeting.

The Executive Board shall immediately send the verbatim text of the resolutions proposed by the said Members to all the Members of the Association.

15.7 The General Meeting may only vote on resolutions with respect to subjects for which the verbatim text of the related proposed resolutions has been sent to the Members in the manner set out above.

15.8 On the written application of a group of Members who are jointly entitled to cast at least one-tenth (10%) of the total number of possible votes, the Executive Board shall convene a General Meeting within a period of four weeks. If the application has not been complied with within fourteen days, the applicants may then proceed to convene the Meeting themselves in the manner in which the General Meeting is convened by the Executive Board.

15.9 As long as all the Members of the Association are present or represented at a General Meeting, (legally) valid resolutions can be passed on all subjects brought up for discussion, even if the formalities prescribed by law or by these Articles of Association for the convocation and holding of Meetings have not been complied with, provided such resolutions are passed unanimously.

Article 16 – General Meeting: Location. Admittance. Voting rights

16.1 All General Meetings (including the Annual Meetings) shall be held in the place where the Association has its official seat, unless the Executive Board decides otherwise and states the place where the General Meeting is to be held in the convocation letter/e-mail.

16.2 Each Member of the Association, provided he/she has not been suspended, and each member of the Executive Board, whether or not Member of the Association, shall be entitled to attend the General Meeting. Members may be represented by the persons referred to in paragraph 16.4. Supporters as defined in Article 1 shall be entitled to attend the General Meeting as observers, without voting rights.

The chair of the General Meeting shall decide on the admittance of other persons.

16.3 Members and Supporters who wish to attend the Meeting shall notify the Executive Board hereof.

If the Member at this Meeting:

- is to be represented by one or more employees or directors, the notification shall state the name(s) of the employee(s) or director(s) and specify who is allowed to exercise the voting right on behalf of that Member;

- is to be represented by a proxy, the notification has to be submitted no later than two weeks before the Meeting and shall state the name and address of the proxy. An employee of the Association cannot be a proxy.

16.4 The right to attend a General Meeting is limited to:

a. in the case of a Member/natural person: the Member;

b. in the case of a Member/legal entity: the natural person recorded as representative of said Member in the Register of the Association (see article 5);

c. the employee(s) of the Member as stated in the notification referred to in article 16.3;

d. an employee or director of the Member who submits proof before the commencement of the General Meeting that he/she is duly authorised to attend the General Meeting on behalf of the Member;

e. a proxy as stated in the notification referred to in paragraph 16.3;

f. in the case of a Supporter/natural person: the Supporter;

g. an employee or director of the Supporter who submits proof before the commencement of the General Meeting that he/she is duly authorised to attend the General Meeting on behalf of the Supporter;

h. other persons admitted by the chair of the General Meeting.

16.5 The right to exercise voting rights at a General Meeting is limited to:

a. in the case of a Member/natural person: the Member;

b. in the case of a Member/legal entity: the natural person recorded as representative of said Member in the Register of the Association (see article 5);

c. an employee or director of a Member who is authorised to exercise the voting right pursuant to the statement in the notification referred to in paragraph 16.3;

d. an employee or director who submits proof before the commencement of the General Meeting that he/she is duly authorised to exercise the voting rights for said Member;

e. a proxy as stated in the notification referred to in paragraph 16.3 and who physically attends the General Meeting.

If there are two or more persons entitled to vote present for one Member at a General Meeting, the person first registered for voting at the General Meeting shall be deemed to have the right to vote for that Member.

16.6 All natural persons who wish to attend the General Meeting and/or to exercise the right to vote at the General Meeting may be required to submit proof of their identity. All natural persons who wish to exercise the right to vote via electronic means will be required to submit proof of their identity, no later than 24 hours before the General Meeting.

16.7 Each Member of the Association who has not been suspended shall have one vote. Candidate Members shall not have the right to vote.

16.8 A proxy (as referred to in paragraph 16.5 (e)) may not cast more than one percent (1%) of the total number of possible votes of all Members of the Association, regardless of whether or not they are present or represented at the Meeting.

16.9 A member of the Executive Board who is not a Member of the Association or a representative of a Member of the Association shall have the right to advise the General Meeting.

Article 17 – General Meeting: Electronic participation and voting

17.1 In addition to the possibility of the members to physically attend the meeting, the Executive Board may decide to open the possibility for the Members to attend the General Meeting through electronic means at a remote location and to vote through electronic means from a remote location for resolutions as specified by the Executive Board. Also, the Executive Board may decide to allow the Members in physical attendance at the General Meeting to cast their votes through electronic means. In addition the Executive Board may decide to open the possibility for the Members to electronically participate in deliberation at the General Meeting. The Executive Board shall regulate the (technical) procedure and the requirements for electronic attendance, voting and/or deliberation.

17.2 Members who are not yet registered as such in the register of members of the association (see paragraph 5.5) who wish to use the possibility to participate through electronic means in the General Meeting and vote electronically must express their agreement with the procedure and the requirements prior to the vote being cast and no later than 24 hours before the General Meeting. Such agreement will be recorded in the register of members of the association (see paragraph 5.5).

17.3 The possibility to electronically participate, vote and/or deliberate in the General Meeting is without prejudice to the right of said member to (always) physically attend or to be represented by proxy at the General Meeting, subject to the conditions as stated in Article 16. If a Member physically attends or is represented by proxy at the General Meeting, the right to vote for that Member will be with that natural person that physically attends the General Meeting or by the proxy holder representing him, respectively.

Article 18 – General Meeting: Voting

18.1 Except where otherwise stipulated by these Articles of Association or by law, all resolutions shall be adopted by an absolute majority of the votes cast, i.e. greater than fifty percent (50%) of the votes cast.

18.2 The chair's verdict on the result of a vote as pronounced at the General Meeting shall be final and binding. The same shall apply to the chair's verdict as pronounced at the General Meeting on the content of an adopted resolution insofar as the Meeting voted on a proposal not recorded In Writing in a General Meeting at which all the Members of the Association are present or represented, as meant in paragraph 15.9.

18.3 If, however, the correctness of that verdict as mentioned in paragraph 18.2 is challenged immediately after its pronouncement, a new vote shall be taken if so desired by the absolute majority at the Meeting or, if the original vote was not taken per capita or by ballot, by someone present who was entitled to vote. As a result of such a new vote the original vote shall be void.

18.4 If it is an election of persons the following method is used. The voter ranks the candidate(s) in order of preference (first choice, second choice, etc.). If, after the first round of voting, no candidate has an absolute majority, the candidate with the least number of votes is dropped and all ballots assigned to that candidate are recounted. The next preference of each of those voters is used to reassign their vote to one of the remaining candidates. This process is repeated until a candidate achieves an absolute majority vote (Instant Runoff Voting).

If more than one person received the smallest number of votes in a voting round, it shall be decided by drawing lots which of these persons shall not participate in the following round. If the votes tie in an election between two persons, it shall be decided by drawing lots who is elected.

In the case of multiple seat elections there will be a separate election process for each seat on the basis of only one election round in which (1) all the votes for all seats are being cast and (2) the ranking by the voter of the candidate(s) in order of preference will be the same for each seat. The winner of a seat will not be eligible for another seat.