RIPE Terms of Reference
Charter of the European IP networks coordination body
Blokzijl, R., "RIPE Terms of Reference", RFC 1181, DOI 10.17487/RFC1181, September 1990, <https://www.rfc-editor.org/info/rfc1181>.
@misc{rfc1181,
series = {Request for Comments},
number = 1181,
howpublished = {RFC 1181},
publisher = {RFC Editor},
doi = {10.17487/RFC1181},
url = {https://www.rfc-editor.org/info/rfc1181},
author = {R. Blokzijl},
title = {{RIPE Terms of Reference}},
pagetotal = 2,
year = 1990,
month = sep,
} RFC text
Contents
Network Working Group R. Blokzijl
Request for Comments: 1181 RIPE/NIKHEF
September 1990
RIPE Terms of Reference
Status of this Memo
This RFC describes the Terms of Reference of RIPE (Reseaux IP
Europeens), the cooperation of European IP networks. This memo
provides information for the Internet community. It does not specify
any standard.
Distribution of this memo is unlimited.
1. Terms of Reference of RIPE
Recognising that IP networks are growing beyond the LAN's in Europe,
and are extending over national and international WAN's in Europe,
the RIPE coordinating body has been created. RIPE stands for the
"Reseaux IP Europeens".
The objective of RIPE is to ensure the necessary administrative and
technical coordination to allow the operation and expansion of a
pan-European IP network.
o RIPE acts as a forum for the exchange of technical information
and the creation of expertise on IP networking.
o The area of relevance for RIPE is Europe.
o All parties operating wide area IP networks are encouraged to
participate.
o RIPE promotes and coordinates interconnection of IP networks
within Europe and to other continents.
o RIPE establishes agreement on common network management
practices and the operational management of the interconnected
networks.
o RIPE serves as a focal point for other common activities of the
participants related to IP networking.
o All documents produced by RIPE will be publicly available.
o RIPE is not a network service provider. IP networks
collaborating in RIPE remain under the executive authority of
their respective organisations.
Security Considerations
Security issues are not discussed in this memo.
Author's Address
Rob Blokzijl
RIPE
c/o NIKHEF
P.O.B. 41882
NL-1009 DB Amsterdam
the Netherlands
Phone: +31 20 5920413
EMail: k13@nikhef.nl
AI ELI5
On this page
§1Recognizing the Need
As IP networks grew beyond local area networks and extended over national and international wide-area networks across Europe, the need became clear for a body to coordinate their operation and expansion.
RIPE (Reseaux IP Europeens, or IP Networks Europe) was created to fill this role. The RFC outlines RIPE's Terms of Reference, which describe its objectives, scope and relationship to the networks it serves.
Many companies and universities had networks. They needed to agree on how to connect them together.
§2RIPE's Objectives and Role
RIPE serves several purposes. It acts as a forum for exchanging technical information and building expertise on IP networking. It promotes and coordinates interconnection of IP networks within Europe and to other continents. It establishes agreement on common network management practices and operational management of interconnected networks. It also serves as a focal point for other common activities of its participants related to IP networking.
Importantly, RIPE is not a network service provider itself. The networks remain under the authority of their respective organizations; RIPE coordinates but does not control.
RIPE is a meeting place where network operators talk about how to connect fairly and agree on rules everyone can follow.
§3Participation and Operations
All parties operating wide-area IP networks in Europe are encouraged to participate. RIPE operates as a collaborative body where member networks retain their independence. All documents produced by RIPE are made publicly available, reflecting the open nature of the Internet.
The RFC states that RIPE's area of relevance is Europe, distinguishing it from other regional coordinating bodies elsewhere in the world.
Any European network can join. They keep their own independence but work together and share what they learn.