person: [mandatory] [single] [primary/look-up key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [optional] [multiple] [look-up key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] Format and syntax of the person object The person object contains details for the technical and administrative contact persons specified in the inetnum object (and in other objects not described in this document). A short form overview of the person object is: Below each of these attributes and their format and syntax are described in more detail, and examples are given. person: Daniel Karrenberg address: RIPE Network Coordination Centre (NCC) address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: Netherlands phone: +31 20 592 5065 fax-no: +31 20 592 5090 e-mail: dfk@ripe.net nic-hdl: DK58 changed: ripe-dbm@ripe.net 920826 source: RIPE person: The person attribute contains the full name as specified as a technical or administrative contact in another object. The name must be written identically to those given in the tech-c and admin-c attribute of for example the inetnum object (but must NOT be the NIC handle). Again here, official titles like 'Dr', 'Prof' or 'Sir' should not be used. Example: person: Daniel Karrenberg Status: mandatory, only one line allowed address: The address attribute contains the full postal address of this person. It should be written down as you would for ordinary postal mail using one line for each part of the address. Example: address: RIPE Network Coordination Centre address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: The Netherlands Status: mandatory, multiple lines allowed phone: The phone attribute contains the telephone number for this person. It has the following format: + . The can be split with spaces to denote exchange and subscriber number. Most countries should drop a leading zero when specifying their area code. Multiple phone numbers should be specified in order of preference on different lines. An extension reachable only through an operator can be specified by adding "ext." and the phone extension to the phone number. Example: phone: +31 20 592 5065 phone: +31 20 592 5000 ext. 5089 Status: mandatory, multiple lines allowed fax-no: The fax-no attribute contains the telefax number for this person. It has the same format as the phone number explained above. Example: fax-no: +31 20 592 5090 e-mail: The e-mail attribute contains the electronic mail address for this person if applicable. This should be a valid RFC 822 electronic mail address, preferably in full domain syntax. Example: e-mail: Daniel.Karrenberg@ripe.net Status: optional, multiple lines allowed nic-hdl: The nic-hdl attribute contains the officially assigned NIC handle for this person, if applicable. NIC handles are unique identifiers assigned and used by the InterNIC to unambiguously refer to Internet people. Example: nic-hdl: DK58 Status: mandatory, only one line allowed The rest of the attributes in the person object have the same syntax and meaning as in the inetnum object, but are repeated for completeness. 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 provides extra information to users of the database, and usage should be kept to a minimum. For format is like the description attribute free text. 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. A more detailed description can be found in [2]. The format is one RFC822 electronic mail address per line. Although multiple lines are allowed, usage should be kept to a minimum. 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 authorisation of database update requests. It is described in more detail in [2]. The format is a registered maintainer name 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. Example: 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. Example: source: RIPE Status: mandatory, only one line allowed, fixed value