The lookup key is simply an attribute that is indexed, meaning that you can search for it. Thus, in this example, searching for "RIPE NCC" might give you multiple results, but searching for "CREW-RIPE" will give you only one. In the case of the role object, the "nic-hdl:" is the only attribute you can be sure won't appear in any other role object (unlike the "role:" attribute with the role's name). The primary key is a unique identifier within a set of objects of the same type. Finally, some attributes are flagged with a search key, which can be: In addition, there is an indication if the attribute can only appear a single time, or if you can use it multiple times in the object. Mnt-by: Įvery attribute is marked as mandatory, optional, or whether the value is generated by the RIPE Database server. Here is the template for the role object. Users have to stick to the template, as well as the syntax rules for each value, when creating an object in the RIPE Database. There is a specific template for each object. The formatted object in this example is created according to a template. role: RIPE NCC Registration Services DepartmentĪddress: RIPE Network Coordination Centre (NCC) Here is an example of a role object, which describes a role performed by one or more people, such as an administrative or technical contact. An object has multiple fields, called attributes or keys, that each have a value. These are blocks of text in a standard notation defined in the Routing Policy Specification Language (RPSL). The RIPE Database stores all information in records known as objects. This document will outline which query method will give you the best results. For example, you can query for a specific record identifier, do a free-text search, or perform a query that includes results from whois databases run by other Regional Internet Registries. There are several ways in which you can influence the scope of your search. People who want to query for this information have several options available to them, varying from a web interface to a command line tool, as well as a RESTful API. Other information is entered by resource holders themselves, such as customer assignments, reverse DNS, routing and contact information. Some of this information is entered by the RIPE NCC, such as the IP address allocations and AS Number assignments that were given to a certain resource holder.
0 kommentar(er)
