Download RIPE Database Reference Manual

2.5.5 Protection of Route Object Space
2.5.6 Protection of Objects with Hierarchical Names
2.5.7 Protection of Domain Object Space
2.5.8 Protecting Membership of a Set
2.5.9 Referencing an irt Object
2.5.10 Referencing an Organisation Object
3.0 Mirroring of the RIPE Database
4.0 Using the RIPE Database Efficiently
4.1 Using the Role Object
4.2 Using the Organisation Object
4.3 Abuse Handling
Appendices
A1. Object Attributes
A2. Copyright Information
A2.1 RIPE Database Copyright
A2.2 RIPE NCC Copyright
Acknowledgements
References
Introduction
The RIPE Network Management Database (often called the "RIPE Database") contains
information about IP address space allocations and assignments, routing policies and
reverse delegations in the RIPE NCC service region:
http://www.ripe.net/membership/maps/index.html
It also contains some information about forward domain names. However, this
information about domain names is for reference only. The RIPE Database is not the
same as a domain name registry, which are run by the country code Top-Level Domain
(ccTLD) administrators of Europe and surrounding areas. If this is what you need, you
should use the IANA ccTLD Database for a full list of the ccTLD administrators [17].
While the information in the RIPE Database is made freely available to the public for
Internet operational purposes, it is subject to copyright restrictions. See Appendix A2,
'Copyright information'.
This document describes how to update series 3.x of the RIPE Database. This series uses
the Routing Policy Specification Language (RPSL) [1] to represent all database objects.
It uses the Routing Policy System Security (RPSS) [2] for authorisation. This provides
better security for Internet Routing Registries (IRR). The RIPE Database includes an IRR
as well as an Internet Number Registry (INR). It makes use of RPSL next generation
specifications [14]. This allows for registering of multicast and IPv6 routing policies.
3