Glossary

 Legacy Resource
Internet number resources that were distributed before (or outside of) the current system of hierarchical distribution by the Regional Internet Registries (RIRs).
 Less Specific
Both IPv4 and IPv6 addresses are structured in hierarchies with 0/0 and ::/0 as the roots of the structures. The root objects have child objects forming the next layer in the hierarchical structure. The root objects are therefore the parents of the child objects. This is repeated throughout the structure as more layers are added. Parent objects are considered to be less specific than the child objects. Child objects are considered to be more specific to the parent objects.
 Maintainer
Any Registrant or person to whom the authority to Update has been delegated by a Registrant either directly or indirectly, and who holds an identifier that allows updates to be authenticated and authorised.
 MD5 Password Hash
MD5 is an algorithm for converting a password or passphrase into a hash of characters.
 Nested
A series of objects are nested when one references the next, that references the next, and so on.
 Network Information Centre (NIC) handle
A sequence of characters that form a unique identifying string used to identify contacts in the RIPE Database (people and business roles).
 Object Template
A pattern or guide describing the characteristics of a specific object type.
 Object Type
There are many different RIPE Database objects representing different pieces of information. They are grouped by type, for example a person object type holds contact information for a person.
 Overlap
One address range crosses the boundary of another address range. For example:
inetnum: 10.240.89.60 - 10.240.89.67
inetnum: 10.240.89.64 - 10.240.89.79
 Parent Object
This object is one level up (less specific) in a hierarchy of INETNUM or INET6NUM objects.
 Parse / Parsing
Analyse (a string or text) into logical syntactic components, typically in order to test conformability to a logical grammar.
 Personally Identifiable Information
A legal phrase that means information that can be used to identify a person.
 Prefix
IP address prefixes are patterns which match the first n binary bits of an IP address where n is the prefix.
 Prefix Notification
Specifies ranges using two parts: the starting address and its length (or prefix).
 Primary Key
A unique identifier in the RIPE Database within a set of objects of the same type.
 Primary Objects
The set of objects that contain all the operational data in the RIPE Database. All other (secondary) objects are there to support the primary objects.
 Pseudo-attribute
An attribute added to an object, or an update message, that is not part of the RPSL object structure. It is needed for the management of the object(s) in the update message. For example supplying a password for an update using the “password:” pseudo attribute.
 Query the RIPE Database
To request information from the RIPE Database.
 Range Notation
Specifies ranges using two parts: the starting address and the end address separated by a hyphen and space character s (‘ - ‘)
 Registrant
A natural person or legal entity to whom an Internet number resource has been registered or who has registered any other primary object in the RIPE Database by specific or general agreement with the RIPE NCC.
 Required attribute
The syntax rules define this attribute as optional. However, additional business rules require this attribute to be present under some circumstances.
 Resource Holder
A person or organisation to which an Internet resource has been registered.
 Reverse Delegation
Allows mapping to a domain name from an IP address.
 RIPE Community
RIPE (Réseaux IP Européens) is a collaborative forum open to all parties interested in wide area IP networks in Europe and beyond. The objective of RIPE is to ensure the administrative and technical coordination necessary to enable the operation of a pan-European IP network
 RIPE Database
The publicly available data collection of Internet Number Registry (INR) data, Internet Routing Registry (IRR) data and Reverse Delegation data published by the RIPE NCC. It contains all the primary and secondary objects. There is also some non-public data required for the operation of the RIPE Database and the registries. Its full title is the RIPE Network Management Database. Or sometime it is referred to as the RIPE Whois Database. But for simplicity it is mostly referred to as the RIPE Database. These names are interchangeable and all mean the same thing.
 RIPE Database Attribute
The key name for a formatted element of data in a RIPE Database object.  The format may be well defined or free format.  An attribute must always have a value associated with it. Unless it is free format, the value cannot be blank. Attributes are sometimes referred to as keys.
 RIPE Database Object
A record in the RIPE Database containing information about an Internet resource or some supporting or administrative details.
 RIPE Internet Number Registry (RIPE INR)
A registry managed by the RIPE NCC that allocates Internet number resources and holds and publishes details of RIPE resources.
 RIPE Internet Routing Registry (RIPE IRR)
A registry managed by the RIPE NCC that holds and publishes details of Internet routing information.
 RIPE NCC Service Region
This defines the geographical area in which the RIPE NCC provides services as an RIR. This includes Europe, the Middle East and parts of Central Asia.