RIPE NCC: Difference between revisions
No edit summary |
updates: Executive Board, Senior Management, reference material |
||
| Line 10: | Line 10: | ||
| businesses = | | businesses = | ||
| products = | | products = | ||
| employees = | | employees = 137 (2014)<ref name="report">[https://www.ripe.net/publications/docs/ripe-646]</ref> | ||
| revenue = | | revenue = | ||
| website = [http://ripe.net ripe.net] | | website = [http://ripe.net ripe.net] | ||
| Line 17: | Line 17: | ||
| linkedin = | | linkedin = | ||
| twitter = | | twitter = | ||
| keypeople = [[Axel Pawlik]], Managing Director<br/>[[Paul Rendek]], | | keypeople = [[Axel Pawlik]], Managing Director<br/>[[Paul Rendek]], Director of External Relations<br/>[[Daniel Karrenberg]], Chief Scientist (Advisor)<br/>[[Andrew de la Haye]], Chief Operations Officer<br/>[[Jochem de Ruig]], Chief Financial Officer<br/>[[Serge Radovcic]], Chief Communications Officer<br/>[[Kaveh Ranjbar]], Chief Information Officer<br/> | ||
}} | }} | ||
The '''Réseaux IP Européens Network Coordination Centre''' ('''RIPE NCC''') is the [[RIR]] for Europe, the Middle East, and parts of Central Asia. The main focus of RIPE NCC is | The '''Réseaux IP Européens Network Coordination Centre''' ('''RIPE NCC''') is the [[RIR]] for Europe, the Middle East, and parts of Central Asia. The main focus of the RIPE NCC is the allocation of Internet number resources (INRs) and the maintenance of a registry of all allocated INRs in its service region.<ref>[http://www.ripe.net/ ripe.net]</ref> | ||
The organization's most important tasks include: | The organization's most important tasks include: | ||
| Line 26: | Line 26: | ||
* Operating the RIPE Database | * Operating the RIPE Database | ||
* Operating the K-root server cluster, one of the world’s 13 root name servers | * Operating the K-root server cluster, one of the world’s 13 root name servers | ||
* | * Facilitating RIPE community activities | ||
* Developing the RIPE Atlas network | |||
* Providing high-quality measurement information services<ref>[https://www.ripe.net/publications/docs/ripe-646 2014 RIPE NCC Annual Report], ripe.net.</ref> | |||
RIPE NCC is not to be confused with [[RIPE]], a related but independent collaborative forum. | The RIPE NCC is not to be confused with [[RIPE]], a related but independent collaborative forum. | ||
==History== | ==History== | ||
RIPE NCC was established on September 16th, 1990, to deal with administrative tasks for RIPE, although it was not formally established and recognized until 1992. RIPE NCC did not become a separate legal entity until 1998. Although the two organizations are legally independent today, they remain highly interdependent. RIPE NCC supports RIPE by facilitating RIPE meetings and providing support for RIPE working groups. RIPE NCC maintains the RIPE | The RIPE NCC was established on September 16th, 1990, to deal with administrative tasks for RIPE, although it was not formally established and recognized until 1992. The RIPE NCC did not become a separate legal entity until 1998. Although the two organizations are legally independent today, they remain highly interdependent. The RIPE NCC supports RIPE by facilitating RIPE meetings and providing support for RIPE working groups. The RIPE NCC maintains the RIPE Database, a public database containing registration details of the IP addresses and AS numbers originally allocated to members by the RIPE NCC.<ref>[http://www.ripe.net/ripe/about/the-history-of-ripe RIPE History], ripe.net.</ref> | ||
In November 2011, RIPE NCC received a temporary order from Dutch police that prevented any changes from being made to a registration of four specific blocks of [[IPv4]] address space in the RIPE Registry. The injunction was ordered the 8th of November and was in effect through March 22, 2012.<ref>[http://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-blocks-registration-in-ripe-registry-following-order-from-dutch-police NCC Blocks Registration, ripe.net]</ref> In return, the organization intended to settle the matter further in Dutch court. It did not withdraw, remove, or reclaim the address blocks but temporary locked registration for them.<ref>[https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-to-seek-clarification-from-dutch-court-on-police-order-to-temporarily-lock-registration RIPE NCC Intends to Seek Clarification from Dutch Court on Police Order to Temporarily Lock Registration], | In November 2011, the RIPE NCC received a temporary order from Dutch police that prevented any changes from being made to a registration of four specific blocks of [[IPv4]] address space in the RIPE Registry. The injunction was ordered the 8th of November and was in effect through March 22, 2012.<ref>[http://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-blocks-registration-in-ripe-registry-following-order-from-dutch-police NCC Blocks Registration, ripe.net]</ref> In return, the organization intended to settle the matter further in Dutch court. It did not withdraw, remove, or reclaim the address blocks but temporary locked registration for them.<ref>[https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-to-seek-clarification-from-dutch-court-on-police-order-to-temporarily-lock-registration RIPE NCC Intends to Seek Clarification from Dutch Court on Police Order to Temporarily Lock Registration], ripe.net. Published 18 November 2011.</ref> In January 2012, the locks were removed under the RIPE community's opinion that legal grounding to execute the order was insufficient.<ref>[https://www.ripe.net/internet-coordination/news/about-ripe-ncc-and-ripe/ripe-ncc-unlocks-registration-in-ripe-registry RIPE NCC Unlocks Registration in RIPE Registry], ripe.net. Published 10 January 2012.</ref> | ||
On September 14, 2012, RIPE NCC distributed the last blocks of | On September 14, 2012, the RIPE NCC distributed the last blocks of IPv4 address space that it had available. As a result, the RIPE NCC is now distributing IPv4 address space to Local Internet Registries (LIRs) from the last /8 according to section 5.6 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”.<ref>[http://www.circleid.com/posts/20120914_ripe_ncc_distributed_last_ipv4_address_space_from_available_pool/ Ripe NCC Distributed Last IPv4 Address Space From Available Pool, CircleID.com]</ref> | ||
==RIPE NCC Structure== | ==RIPE NCC Structure== | ||
RIPE NCC is made up of its members, an Executive Board, and its staff, led by a management team. | The RIPE NCC is made up of its members, an Executive Board, and its staff, led by a management team. | ||
===Membership=== | ===Membership=== | ||
Organizations and individuals must | Organizations and individuals must be registered as members of an RIR in order to request [https://en.wikipedia.org/wiki/Provider-aggregatable_address_space provider-aggregatable] (PA) [[IP]] addresses and AS Numbers, or when they plan to assign them to End Users or customers. Those who wish to request a small amount of [https://en.wikipedia.org/wiki/Provider-independent_address_space provider-independent] (PI) [[IP]] addresses and AS numbers for personal use may do so via the Request of Independent Resources process.<ref name="member">[http://www.ripe.net/lir-services/member-support/become-a-member Becoming a Member], ripe.net.</ref> Most of the RIPE NCC’s members are [[ISP]]s and telecommunications organizations, but other members include corporations, academic institutions and government bodies. At the end of 2014, the RIPE NCC had 11,115 members in 76 countries. | ||
RIPE NCC membership is not required to attend RIPE meetings, to take part in the RIPE Policy Development Process (PDP), or use some RIPE NCC Services. Membership is required, however, to request IPv4 and IPv6 address space, AS Numbers and related services, to attend the RIPE NCC General Meetings, to provide feedback on the RIPE NCC Activity Plan, to accept the RIPE NCC Charging Scheme or Financial Report, and to vote candidates onto the RIPE NCC Executive Board. Member benefits include the ability to attend RIPE NCC Training Courses, the use of an LIR Portal account to manage registry data and make Internet number requests, and the receipt of two free tickets to RIPE Meetings.<ref name="member"></ref> | RIPE NCC membership is not required to attend RIPE meetings, to take part in the RIPE Policy Development Process (PDP), or use some RIPE NCC Services. Membership is required, however, to request IPv4 and IPv6 address space, AS Numbers and related services, to attend the RIPE NCC General Meetings, to provide feedback on the RIPE NCC Activity Plan, to accept the RIPE NCC Charging Scheme or Financial Report, and to vote candidates onto the RIPE NCC Executive Board. Member benefits include the ability to attend RIPE NCC Training Courses, the use of an LIR Portal account to manage registry data and make Internet number requests, and the receipt of two free tickets to RIPE Meetings.<ref name="member"></ref> | ||
There is a sign-up fee for joining RIPE NCC, after which members must pay an annual fee | There is a sign-up fee for joining the RIPE NCC, after which members must pay an annual fee.<ref name="charging scheme">[https://www.ripe.net/publications/docs/ripe-620 RIPE NCC Charging Scheme 2015], ripe.net.</ref> | ||
===The Executive Board=== | ===The Executive Board=== | ||
The | The Executive Board, which consists of seven people, is elected by the members of the RIPE NCC. Their duties are to represent the membership and provide guidance to the RIPE NCC's senior management team, approve the RIPE NCC's Activity Plan and Budget, appoint the RIPE NCC management, and call General Meetings. They are responsible for the overall financial position of the organization, and are to keep up-to-date records of the RIPE NCC's financial situation. The Executive Board delegates all operational decisions relating to the Standard Service Agreements to the management staff.<ref name="report"></ref> | ||
[[Image:ripenccstaffchart.png|thumb|right|RIPE NCC staff chain of command.<ref name="report"></ref>]] | [[Image:ripenccstaffchart.png|thumb|right|RIPE NCC staff chain of command.<ref name="report"></ref>]] | ||
The current Executive Board members are: | The current Executive Board members are: | ||
* [[Nigel Titley]], Chairman (May | * [[Nigel Titley]], Chairman (May 2013 - May 2016) | ||
* [[Remco van Mook]], Treasurer (May | * [[Remco van Mook]], Treasurer (May 2013 - May 2016) | ||
* [[Christian Kaufmann]], Secretary (May | * [[Christian Kaufmann]], Secretary (May 2014 - May 2017) | ||
* [[Dmitry Burkov]], [[ICANN]] Liaison (May | * [[Dmitry Burkov]], [[ICANN]] Liaison (May 2015 - May 2018) | ||
* [[ | * [[Maria Häll]], Member (May 2014 - May 2017) | ||
* [[Salam Yamout]], Member (May 2014 - May 2017) | |||
* [[János Zsakó]], Member (May 2015 - May 2018) | |||
Members of the Executive Board serve a 3-year term.<ref>[http://www.ripe.net/lir-services/ncc/executive-board RIPE NCC Executive Board]</ref> | Members of the Executive Board serve a 3-year term.<ref>[http://www.ripe.net/lir-services/ncc/executive-board RIPE NCC Executive Board]</ref> | ||
| Line 63: | Line 67: | ||
===Staff=== | ===Staff=== | ||
The duties of the staff overall are to: | The duties of the staff overall are to: | ||
# Perform the operations and facilitate the services of RIPE NCC. | # Perform the operations and facilitate the services of the RIPE NCC. | ||
# Provide administrative support for RIPE and RIPE NCC members. | # Provide administrative support for RIPE and RIPE NCC members. | ||
# Cooperate with the other four RIRs and industry partners like [[ISOC]] and [[ICANN]]. | # Cooperate with the other four RIRs and industry partners like [[ISOC]] and [[ICANN]]. | ||
# Implement policies proposed and accepted by | # Implement policies proposed and accepted by the Internet community.<ref name="report"></ref> | ||
The management staff | The management staff comprises the RIPE NCC Managing Director supported by a Senior Management Team of six members: | ||
* The Director of External Relations oversees community outreach activities and government liaison | |||
* The Chief Communications Officer oversees the Communications Department, which includes the Web Services and RIPE Labs teams | |||
* The Chief Operations Officer manages the RIPE NCC’s core operations (Member Services) | |||
* The Chief Information Officer is responsible for the RIPE NCC's global infrastructures, such as the provision of reverse DNS in the RIPE NCC service region and the operation of the global K-root server cluster | |||
* The Chief Financial Officer is responsible for the RIPE NCC’s financial activities and also oversees its legal activities | |||
* The Chief Scientist advises the Managing Director and the Senior Management team, particularly on new activities<ref name="senior management">[https://www.ripe.net/about-us/staff]</ref> | |||
==Services== | ==Services== | ||
In addition to | In addition to distributing IPv4 and IPv6 addresses and AS Numbers, the RIPE NCC provides the following services to its members: | ||
'''Database Services''': | '''Database Services''': | ||
| Line 86: | Line 96: | ||
* Facilitation of RIPE NCC Regional Meetings | * Facilitation of RIPE NCC Regional Meetings | ||
* Roundtable Meetings for governments, regulators and law enforcement agencies | * Roundtable Meetings for governments, regulators and law enforcement agencies | ||
* Public representation the RIPE NCC, its members and the RIPE community | * Public representation of the RIPE NCC, its members and the RIPE community | ||
* Support for the Middle East Network Operators Group’s ([[MENOG]]) activities | * Support for the Middle East Network Operators Group’s ([[MENOG]]) activities | ||
'''Training''': | '''Training''': | ||
| Line 97: | Line 107: | ||
* Routing Information Service | * Routing Information Service | ||
* Hostcount++<ref name="report"></ref> | * Hostcount++<ref name="report"></ref> | ||
'''Measurements and Innovation Support''': | |||
* RIPE Atlas | |||
* RIPEstat | |||
* RIPE Labs | |||
==References== | ==References== | ||
| Line 102: | Line 116: | ||
==External Links== | ==External Links== | ||
* [https://www.ripe.net/membership/indices/ Countries Served by | * [https://www.ripe.net/membership/indices/ Countries Served by the RIPE NCC] | ||
Revision as of 09:24, 3 August 2015
 | |
| Type: | Independent, Non-Profit |
| Headquarters: | Singel 258 1016 AB Amsterdam |
| Country: | Netherlands |
| Employees: | 137 (2014)[1] |
| Website: | ripe.net |
| Key People | |
| Axel Pawlik, Managing Director Paul Rendek, Director of External Relations Daniel Karrenberg, Chief Scientist (Advisor) Andrew de la Haye, Chief Operations Officer Jochem de Ruig, Chief Financial Officer Serge Radovcic, Chief Communications Officer Kaveh Ranjbar, Chief Information Officer | |
The Réseaux IP Européens Network Coordination Centre (RIPE NCC) is the RIR for Europe, the Middle East, and parts of Central Asia. The main focus of the RIPE NCC is the allocation of Internet number resources (INRs) and the maintenance of a registry of all allocated INRs in its service region.[2]
The organization's most important tasks include:
- Distribution and registration of IPv4 and IPv6 addresses and Autonomous System (AS) Numbers
- Operating the RIPE Database
- Operating the K-root server cluster, one of the world’s 13 root name servers
- Facilitating RIPE community activities
- Developing the RIPE Atlas network
- Providing high-quality measurement information services[3]
The RIPE NCC is not to be confused with RIPE, a related but independent collaborative forum.
History[edit | edit source]
The RIPE NCC was established on September 16th, 1990, to deal with administrative tasks for RIPE, although it was not formally established and recognized until 1992. The RIPE NCC did not become a separate legal entity until 1998. Although the two organizations are legally independent today, they remain highly interdependent. The RIPE NCC supports RIPE by facilitating RIPE meetings and providing support for RIPE working groups. The RIPE NCC maintains the RIPE Database, a public database containing registration details of the IP addresses and AS numbers originally allocated to members by the RIPE NCC.[4]
In November 2011, the RIPE NCC received a temporary order from Dutch police that prevented any changes from being made to a registration of four specific blocks of IPv4 address space in the RIPE Registry. The injunction was ordered the 8th of November and was in effect through March 22, 2012.[5] In return, the organization intended to settle the matter further in Dutch court. It did not withdraw, remove, or reclaim the address blocks but temporary locked registration for them.[6] In January 2012, the locks were removed under the RIPE community's opinion that legal grounding to execute the order was insufficient.[7]
On September 14, 2012, the RIPE NCC distributed the last blocks of IPv4 address space that it had available. As a result, the RIPE NCC is now distributing IPv4 address space to Local Internet Registries (LIRs) from the last /8 according to section 5.6 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”.[8]
RIPE NCC Structure[edit | edit source]
The RIPE NCC is made up of its members, an Executive Board, and its staff, led by a management team.
Membership[edit | edit source]
Organizations and individuals must be registered as members of an RIR in order to request provider-aggregatable (PA) IP addresses and AS Numbers, or when they plan to assign them to End Users or customers. Those who wish to request a small amount of provider-independent (PI) IP addresses and AS numbers for personal use may do so via the Request of Independent Resources process.[9] Most of the RIPE NCC’s members are ISPs and telecommunications organizations, but other members include corporations, academic institutions and government bodies. At the end of 2014, the RIPE NCC had 11,115 members in 76 countries.
RIPE NCC membership is not required to attend RIPE meetings, to take part in the RIPE Policy Development Process (PDP), or use some RIPE NCC Services. Membership is required, however, to request IPv4 and IPv6 address space, AS Numbers and related services, to attend the RIPE NCC General Meetings, to provide feedback on the RIPE NCC Activity Plan, to accept the RIPE NCC Charging Scheme or Financial Report, and to vote candidates onto the RIPE NCC Executive Board. Member benefits include the ability to attend RIPE NCC Training Courses, the use of an LIR Portal account to manage registry data and make Internet number requests, and the receipt of two free tickets to RIPE Meetings.[9]
There is a sign-up fee for joining the RIPE NCC, after which members must pay an annual fee.[10]
The Executive Board[edit | edit source]
The Executive Board, which consists of seven people, is elected by the members of the RIPE NCC. Their duties are to represent the membership and provide guidance to the RIPE NCC's senior management team, approve the RIPE NCC's Activity Plan and Budget, appoint the RIPE NCC management, and call General Meetings. They are responsible for the overall financial position of the organization, and are to keep up-to-date records of the RIPE NCC's financial situation. The Executive Board delegates all operational decisions relating to the Standard Service Agreements to the management staff.[1]
The current Executive Board members are:
- Nigel Titley, Chairman (May 2013 - May 2016)
- Remco van Mook, Treasurer (May 2013 - May 2016)
- Christian Kaufmann, Secretary (May 2014 - May 2017)
- Dmitry Burkov, ICANN Liaison (May 2015 - May 2018)
- Maria Häll, Member (May 2014 - May 2017)
- Salam Yamout, Member (May 2014 - May 2017)
- János Zsakó, Member (May 2015 - May 2018)
Members of the Executive Board serve a 3-year term.[11]
Staff[edit | edit source]
The duties of the staff overall are to:
- Perform the operations and facilitate the services of the RIPE NCC.
- Provide administrative support for RIPE and RIPE NCC members.
- Cooperate with the other four RIRs and industry partners like ISOC and ICANN.
- Implement policies proposed and accepted by the Internet community.[1]
The management staff comprises the RIPE NCC Managing Director supported by a Senior Management Team of six members:
- The Director of External Relations oversees community outreach activities and government liaison
- The Chief Communications Officer oversees the Communications Department, which includes the Web Services and RIPE Labs teams
- The Chief Operations Officer manages the RIPE NCC’s core operations (Member Services)
- The Chief Information Officer is responsible for the RIPE NCC's global infrastructures, such as the provision of reverse DNS in the RIPE NCC service region and the operation of the global K-root server cluster
- The Chief Financial Officer is responsible for the RIPE NCC’s financial activities and also oversees its legal activities
- The Chief Scientist advises the Managing Director and the Senior Management team, particularly on new activities[12]
Services[edit | edit source]
In addition to distributing IPv4 and IPv6 addresses and AS Numbers, the RIPE NCC provides the following services to its members:
Database Services:
- Development, operation and maintenance of the RIPE Database
- Operation of a Routing Registry
Technical Services:
- Operation of K-root, one of 13 root name server clusters
- rDNS delegations
- Technical administration of Tier-0 ENUM
Community Support and Outreach:
- Administrative support for RIPE
- Maintenance and development of RIPE community mailing lists
- Facilitation of RIPE Meetings
- Facilitation of RIPE NCC Regional Meetings
- Roundtable Meetings for governments, regulators and law enforcement agencies
- Public representation of the RIPE NCC, its members and the RIPE community
- Support for the Middle East Network Operators Group’s (MENOG) activities
Training:
- Provision of RIPE NCC Training Courses for members and stakeholders
- Provision of an E-Learning Centre freely available to members and non-members
Information Services:
Measurements and Innovation Support:
- RIPE Atlas
- RIPEstat
- RIPE Labs
References[edit | edit source]
- ↑ 1.0 1.1 1.2 1.3 1.4 [1]
- ↑ ripe.net
- ↑ 2014 RIPE NCC Annual Report, ripe.net.
- ↑ RIPE History, ripe.net.
- ↑ NCC Blocks Registration, ripe.net
- ↑ RIPE NCC Intends to Seek Clarification from Dutch Court on Police Order to Temporarily Lock Registration, ripe.net. Published 18 November 2011.
- ↑ RIPE NCC Unlocks Registration in RIPE Registry, ripe.net. Published 10 January 2012.
- ↑ Ripe NCC Distributed Last IPv4 Address Space From Available Pool, CircleID.com
- ↑ 9.0 9.1 Becoming a Member, ripe.net.
- ↑ RIPE NCC Charging Scheme 2015, ripe.net.
- ↑ RIPE NCC Executive Board
- ↑ [2]