inetnum: [mandatory] [single] [primary/look-up key] netname: [mandatory] [single] [look-up key] descr: [mandatory] [multiple] [ ] country: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] rev-srv: [optional] [multiple] [ ] status: [mandatory] [single] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] mnt-lower: [optional] [multiple] [ ] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] Below each of these attributes and their format and syntax are described in more detail, and examples are given. inetnum: 192.87.45.0 netname: RIPE-NCC descr: RIPE Network Coordination Centre descr: Amsterdam, Netherlands country: NL admin-c: DK58 tech-c: DK58 rev-srv: ns.ripe.net rev-srv: ns.eu.net notify: ops@ripe.net changed: tony@ripe.net 940110 source: RIPE inetnum: The inetnum attribute contains the range of IP address space this object gives information on. The syntax of this attribute can be either of the fol- lowing: inetnum: 192.87.45.0 - 192.87.45.255 inetnum: 192.87.45.0/24 Status: mandatory, only one line allowed netname: The netname attribute specifies a name for this range of IP address space. It should be a reason- ably descriptive name, consisting of capitals, dashes ("-") and digits, but must start with a cap- ital. The network name used to be a unique name identifying the address space. Nowadays it is mainly used to guard against errors by requiring both the address and the name for certain opera- tions. You will most likely never find this name anywhere else than in a database like the RIPE database. An example: netname: RIPE-NCC Status: mandatory, only one line allowed descr: The descr attribute consists of a short description of the organisation and location where this address space is used. The description can have multiple lines. It need not contain the full postal address as this is required in the contact person object (see further in this document). Free text is allowed. An example: descr: RIPE Network Coordination Centre descr: Amsterdam, Netherlands Status: mandatory, multiple lines allowed country: The country attribute gives the two letter ISO 3166 country code for the country where the organisation is located. An up-to-date version of ISO 3166 can be obtained using anonymous ftp from ftp.ripe.net:iso3166-codes. In cases where the address space is used across national boundaries, it should contain the most appropriate country, usually based on the address of the administrative contact person. The format is two letter uppercase country code. An example: country: NL Status: mandatory, only one line allowed admin-c: The admin-c attribute contains NIC handle of the administrative contact person. The administrative contact must be someone who is physically located at the site of the network. This value should be exactly the same as the attribute in the person object (see desription of person object). More than one administrative contact person can be specified, by simply repeating the attribute. An example of both the NIC handle and normal name use: admin-c: DK58 Status: mandatory, multiple lines allowed tech-c: The tech-c attribute contains the NIC handle of the technical contact person. The technical contact person does not have to be physically located at the site of the network. The format and syntax is the same as the admin-c attribute above. Status: mandatory, multiple lines allowed rev-srv: The rev-srv attribute contains the fully qualified domain name of the machine that runs a reverse domain name service for the address space. If there are multiple reverse name servers for this address space, they should all be specified on dif- ferent lines. Only one hostname is allowed per line. An example: rev-srv: ns.ripe.net rev-srv: ns.eu.net Status: optional, multiple lines allowed status: Specifies whether the request is provider aggregatable or provider independent. Should be filled in with either "ASSIGNED PA" or "ASSIGNED PI". An example: status: ASSIGNED PA Status: mandatory, single remarks: The remarks attribute contains any remarks about this address space that cannot be expressed in any of the other attributes. Although multiple lines are allowed, it should be only be used if it pro- vides extra information to users of the database, and usage should be kept to a minimum. For format is like the description attribute free text. An example: remarks: will be returned to NIC 950101 Status: optional, multiple lines allowed notify: The notify attribute contains an email address to which notifications of changes to this object should be send. This can be useful if more than one person manage the same object (see description of mntner object). The format is one RFC822 electronic mail address per line. Although multiple lines are allowed, usage should be kept to a minimum. An example: notify: operations@ripe.net Status: optional, multiple lines allowed mnt-by: The maintainer attribute contains a registered maintainer name. This attribute is used for author- isation of database update requests (see. description of mntner object). The format is a registered maintainer name. An example: mnt-by: RIPE-DBM Status: optional, multiple lines allowed changed: The changed field contains information on who last changed this object, and when this change was made. The format is an RFC 822 electronic mail address of the person who made the change, and the date of change in YYMMDD format. Multiple lines are allowed and shows the update history of an object. An exam- ple: changed: marten@ripe.net 940328 Status: mandatory, multiple lines allowed source: The source contains a source of information. For the RIPE database, the value should always be "RIPE". This field is used to combine and exchange information between various database sources around the world. Fixed value: source: RIPE Status: mandatory, only one line allowed, fixed value