RFC 1181 INFORMATIONAL INFRASTRUCTURE · REGIONAL

RIPE Terms of Reference

The stated purpose and working scope of the RIPE coordinating body.

On rfc-editor.org ↗
PUBLISHED
September 1990
AUTHORS
R. Blokzijl
STREAM
Legacy
DOI
10.17487/RFC1181

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
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

ISO Plain Language

On this page
PROBLEMEuropean IP networks were expanding beyond local networks and across national and international wide-area networks, creating a need for coordination.
MECHANISMRIPE provides a forum for technical information, coordinates interconnection and common network-management practices, and supports other shared IP-networking activities.
RIPE'S ROLEThe RFC documents RIPE's terms of reference and says RIPE is not a network service provider; participating networks remain under their organizations' authority.

§1Why RIPE Was Created

RIPE stands for Réseaux IP Européens. The RFC says the coordinating body was created as IP networks expanded beyond local networks and across Europe through national and international wide-area networks.

Its objective is to provide administrative and technical coordination so a pan-European IP network can operate and expand.

RIPE was created to coordinate European IP networks as they connected across wider areas. The RFC sets out the body's objective and scope.

§3RIPE's Responsibilities and Participation

RIPE acts as a forum for exchanging technical information and building expertise in IP networking. It promotes and coordinates interconnection within Europe and with other continents, and works toward agreement on common network-management practices.

Operators of wide-area IP networks are encouraged to participate. RIPE is not a service provider, and participating networks remain under the executive authority of their respective organizations. RIPE documents are publicly available.

RIPE helps network operators share information and coordinate connections and management practices. The operators keep authority over their own networks.

§3Status and Scope

RFC 1181 is an informational document describing RIPE's terms of reference. It does not specify a standard. Its stated area of relevance is Europe.

This RFC is an informational description of RIPE's role in Europe. It does not define a technical standard.