RIPE

Réseaux IP Européens (RIPE, French for "European IP Networks") is a forum open to all parties with an interest in the technical development of the Internet. The RIPE community’s objective is to ensure that the administrative and technical coordination necessary to maintain and develop the Internet continues. It is not a standards body like the Internet Engineering Task Force (IETF) and does not deal with domain names like ICANN.

For the regional Internet registry, see Réseaux IP Européens Network Coordination Centre. For other uses, see Ripe.
Réseaux IP Européens
(RIPE)
FormationMay 22, 1989 (1989-05-22)
TypeINGO
PurposeTo maintain and develop the Internet and its unique characteristics. RIPE's activities in Internet governance are based on a commitment to enhance the cooperation between the public and private sectors.
Location
  • Amsterdam, Netherlands
Chair
Hans Petter Holen
Websitewww.ripe.net

RIPE is not a legal entity and has no formal membership. This means that anybody who is interested in the work of RIPE can participate through mailing lists and by attending meetings. RIPE has a chair to keep an eye on work between RIPE meetings and to act as its external liaison. Rob Blokzijl, who was instrumental in the formation of RIPE, was the initial chair and remained in that position until 2014, when he appointed Hans Petter Holen as his successor. The RIPE community interacts via RIPE Mailing Lists,[1][2] RIPE Working Groups,[3] and RIPE Meetings.[4]

Although similar in name, the RIPE NCC and RIPE are separate entities. The RIPE NCC provides administrative support to RIPE, such as the facilitation of RIPE meetings[4] and providing administrative support to RIPE Working Groups.[3] It was established in 1992 by the RIPE community to serve as an administrative body.

History

The name is a translation of the English title of a diagram to French by John Quarterman.[5] This was presented in Special Session of RIPE 58.[6]

The first RIPE meeting was held on 22 May 1989 in Amsterdam, Netherlands. It brought together 14 representatives of 6 countries and 11 networks[7] At the time European governments, standardisation bodies and telecommunications companies were pushing for the OSI standard and IP-based networks were seen as the wrong way to go. In the academic community (mostly nuclear and particle physics) there was a strong need to work together with colleagues across Europe and the United States. IP provided a standard to allow interconnection and cooperation, whereas the networks offered by the European telecommunications companies often completely lacked that.

Former RIPE NCC offices at 258 Singel, Amsterdam

RIPE as an organisation was established by the RIPE terms of reference, which were agreed on 29 November 1989.[8] There were ten organisations intending to participate in the RIPE Coordinating Committee, along the lines defined by the RIPE Terms of Reference, though some still needed to make a formal decision. These organisations were: BelWue, CERN, EASInet, EUnet, GARR, HEPnet, NORDUnet, SURFnet, SWITCH and XLINK.[9] At the same time task forces were established to facilitate the interconnection of European IP-networks in the following weeks and months.[10] The four task forces were:

  1. Connectivity and Routing
  2. Network Management and Operations
  3. Domain Name System
  4. Formal Coordination

One of the results was a proposal on 16 September 1990 to establish the RIPE Network Coordination Centre (NCC) to support the administrative tasks in the RIPE community[11] and the first RIPE NCC Activity Plan was published in May 1991.[12]

RIPE asked RARE (one of the predecessors of TERENA) if they would provide the legal framework for the RIPE NCC. After a solicitation procedure, the RIPE NCC began in April 1992 with its headquarters in Amsterdam, Daniel Karrenberg as manager and only two other staff members. Initial funding was provided by the academic networks (RARE members), EARN and EUnet. The RIPE NCC was formally established when the Dutch version of the articles of association was deposited with the Amsterdam Chamber of Commerce on 12 November 1997.[13]

Function

Any document, proposal, procedure or policy that has been proposed and accepted by the RIPE community is published online in the RIPE Document Store.[14]

The RIPE community develops and sets policies for the technical coordination of the Internet and the management and distribution of Internet resources (IP addresses and Autonomous System Numbers (ASNs)) through an established, open, bottom-up process of discussion and consensus-based decision-making. The RIPE Policy Development Process (PDP) formally tracks input into and discussion on any policy proposed. The RIPE PDP is transparent and consensus-based. Anyone may suggest a new policy or a change to an existing one. Proposals are then discussed and accepted or rejected by the RIPE community according to the RIPE PDP guidelines.[15]

RIPE meetings happen twice a year in different locations throughout the RIPE NCC service region.[16] The meetings are five-day events in which Internet service providers (ISPs), network operators, government representatives, regulators and other interested parties gather to discuss relevant issues, developments and policies. RIPE Meetings are open to anyone, although registration is required.

The RIPE community has formed a number of RIPE Working Groups to deal with various issues and topics related to the work of RIPE NCC members and the general Internet community.[3] Each of the RIPE Working Groups has a mailing list where topics or questions related to the working group can be discussed. The RIPE Working Groups[3] meet twice a year in dedicated sessions at RIPE Meetings.[4]

The RIPE community refers collectively to the individuals or organisations, whether members of the RIPE NCC or not, that have an interest in the way the Internet is managed, structured or governed.

RIPE NCC
Main article: RIPE NCC

The regional Internet registry for Europe, the Middle East and parts of Central Asia. It also serves as the secretariat for RIPE.

See also

References
  1. "Mailing Lists — RIPE Network Coordination Centre". ripe.net. Retrieved 2013-06-20.
  2. "RIPE Mailing Lists — RIPE Network Coordination Centre". ripe.net. Retrieved 2013-06-20.
  3. "Active Working Groups — RIPE Network Coordination Centre". ripe.net. Retrieved 2013-06-21.
  4. "FAQ: RIPE Meetings — RIPE Network Coordination Centre". ripe.net. Archived from the original on 2013-05-15. Retrieved 2013-06-21.
  5. Karrenberg, Daniel (2009-05-07). "How the Name RIPE Came About" (PDF). ripe.net. Retrieved 2017-07-09.
  6. "RIPE 58 - Amsterdam, the Netherlands | 4-8 May 2009". ripe.net. Retrieved 2013-06-21.
  7. "Participants of first RIPE meeting". ripe.net. Archived from the original on 2008-04-11. Retrieved 2008-07-31.
  8. "RIPE terms of reference". ripe.net. Retrieved 2008-07-31.
  9. "RIPE: Statement of cooperation". ripe.net. Retrieved 2008-07-31.
  10. "RIPE Task forces". ripe.net. Retrieved 2008-07-31.
  11. "RIPE network coordination centre". ripe.net. Retrieved 2008-07-31.
  12. "First RIPE NCC Activity Plan". ripe.net. Retrieved 2008-07-31.
  13. "NCC history". ripe.net. Archived from the original on 2007-06-15. Retrieved 2008-07-31.
  14. "RIPE Document Store — RIPE Network Coordination Centre". ripe.net. Retrieved 2013-06-21.
  15. "RIPE Policy Development — RIPE Network Coordination Centre". ripe.net. Retrieved 2013-06-21.
  16. RIPE.net Archived February 3, 2011, at the Wayback Machine
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.