WHOIS (RIPE)

A description of the individual attributes of the RIPE network number and person object in WHOIS information.

Contents

• Format and syntax of the network number object
• • inetnum
  • netname
  • descr
  • country
  • admin-c
  • tech-c
  • rev-srv
  • remarks
  • notify
  • mnt-by
  • changed
  • source
• Format and syntax of the person object
• • person
  • address
  • phone
  • fax-no
  • E-Mail
  • nic-hdl
  • remarks
  • notify
  • mnt-by
  • changed
  • source

Format and syntax of the network number object

The Network Number object is also often referred to as the inetnum object because the row containing the network number information is named "inetnum".

A brief overview of the object:

inetnum

The "inetnum" attribute specifies the address range to which the displayed information refers. This attribute is required, and only one attribute is allowed in the object.

inetnum: 192.87.45.0

This specification represents a Class C network number that includes the IP address range from 192.87.45.0 to 192.87.45.255. The network number can be a Class A, Class B, or Class C network number.

inetnum: 192.87.44.0 - 192.87.45.0

This specification represents a block of two Class C network numbers that include the IP addresses from 192.87.44.0 to 192.87.45.255. The spaces between the IP addresses and the hyphen (-) are required. The range specification can include any block of a Class A, Class B, and Class C network number.

inetnum: 192.87.45.0 > 192.87.45.255

This syntax represents the address range from 192.87.45.0 to 192.87.45.255. Cross-class ranges can also be defined in this syntax (e.g., 192.87.45.0 > 192.87.55.155). This means that this syntax is not bound by the conventions of network classes A, B and C. The spaces between the IP addresses and the greater than sign (>) are required.

netname

The "netname" attribute specifies the name of the specified address range. This attribute may only consist of uppercase letters, numbers, and a hyphen, and must begin with a capital letter. This attribute is required, and only one attribute is allowed in the object.

descr

The "descr" attribute contains a brief description of the organization and its location that uses the specified address range. The descr attribute does not need to contain the full address, as is required for the Contact Person object. Any text can be entered. This attribute is required, and multiple attributes are allowed in the object.

descr: RIPE Network Coordination Centre
descr: Amsterdam, Netherlands

country

The "country" attribute contains the two-letter country code according to ISO 3166 and is based on the location of the organization in question. For international organizations, the country specification should be based on the most significant location or the address of the administrative contact person. This attribute is required, and only one attribute is allowed in the object.

The country code consists of two capital letters, e.g.:

country: NL

or

country: DE

admin-c

The "admin-c" attribute contains the name or NIC handle of the administrative contact person. If possible, this should be a person who works at the organization for which the address range in question is registered. The value of this attribute should be exactly the same as that in the Person object. More than one administrative contact person can be specified in additional admin-c attributes. This attribute is required, and multiple attributes are allowed in the object.

An example of a name and NIC handle:

admin-c: Daniel Karrenberg

and/or

admin-c: DK58

tech-c

The "tech-c" attribute contains the name or NIC handle of the technical contact person. The format and syntax are the same as in the "admin-c" attribute. This attribute is required, and multiple attributes are allowed in the object.

rev-srv

The "rev-srv" attribute contains the full name of the computer that provides a reverse domain name service for this address range. If multiple reverse name servers are present, they must be specified in separate rev-srv attributes. Only one server name may be specified per attribute. This attribute is required, and multiple attributes are allowed in the object.

rev-srv: ns.ripe.net
rev-srv: ns.eu.net

remarks

The "remarks" attribute contains information that cannot be specified in the other attributes. Although multiple lines are permitted for these remarks, only information that is absolutely necessary and relevant to the database users should be entered. This attribute is optional, and multiple attributes are permitted in the object.

remarks: will be returned to NIC 950101

notify

The "notify" attribute contains the e-mail address of the person who should be notified of a change to the object. The e-mail address must be entered in the format for e-mail addresses (RFC822). This attribute is optional, and multiple attributes are permitted in the object.

notify: operations@ripe.net

mnt-by

The "mnt-by" attribute specifies the registered entity responsible for maintaining and updating this object. Requests regarding updates should be directed here. This attribute is optional, and multiple attributes are allowed in the object.

mnt-by: RIPE-DBM

changed

The "changed" attribute specifies who changed this object and when the change was made. The person is specified as an e-mail address, followed by the change date, separated by a space in the format YYMMDD. This attribute is required, and multiple attributes are allowed in the object so that the change history is visible.

changed: marten@ripe.net 940328

source

The "source" attribute specifies the source of the data in question. This will usually be the name of the NIC. If the data originates from another database, the name of that database is specified. This attribute is intended to support the global exchange of information. In the case of RIPE, the value of the "source" attribute is always "RIPE". This attribute is required, and only one attribute is allowed in the object.

source: RIPE

Format and syntax of the person object

The Person object contains detailed information about the technical and administrative contact person specified in the internet numbers object.

A brief overview of the object:

person

The "person" attribute contains the full name of a technical or administrative contact person specified in another object. The content of the person attribute must be spelled exactly like the content of the "tech-c" or "admin-c" attribute. However, it does not have to be the NIC handle. Titles such as "Dr." or "Prof." should not be specified here either. This attribute is required, and only one attribute is allowed in the object.

person: Daniel Karrenberg

address

The "address" attribute contains the person's full address. It should be entered as is usual for mail. One line should be used for each part of the address. This attribute is required, and multiple attributes are allowed in the object.

address: RIPE Network Coordination Centre
address: Kruislaan 409
address: NL-1098 SJ Amsterdam
address: The Netherlands

phone

The "phone" attribute contains the person's complete telephone number. The format for the telephone number is set as "+<Country code> <Area code> <Phone number>". The telephone number can also be split with spaces. Extensions that can only be reached by an operator can be marked with "ext". This attribute is required, and multiple attributes are allowed in the object.

phone: +31 20 592 5065
phone: +31 20 592 5000 ext. 5089

fax-no

The "fax-no" attribute contains the person's fax number. The fax number is specified in the same format as the phone number. This attribute is optional, and multiple attributes are allowed in the object.

fax-no: +31 20 592 5090

e-mail

The "e-mail" attribute contains the person's e-mail address. The e-mail address must be entered in the e-mail address format (RFC822). This attribute is optional, and multiple attributes are allowed in the object.

e-mail: Daniel.Karrenberg@ripe.net

nic-hdl

The "nic-hdl" attribute contains the officially assigned NIC handle for this person. NIC handles are unique identification numbers from InterNIC to refer to a specific person. This attribute is optional, and only one attribute is allowed in the object.

nic-hdl: DK58

remarks

The "remarks" attribute contains information that cannot be specified in the other attributes. While multiple lines are allowed for these remarks, only information that is absolutely necessary and relevant to the database users should be entered. This attribute is optional, and multiple attributes are allowed in the object.

remarks: will be returned to NIC 950101

notify

The "notify" attribute contains the e-mail address of the person who should be notified of a change to the object. The -mail address must be entered in the e-mail address format (RFC822). This attribute is optional, and multiple attributes are allowed in the object.

notify: operations@ripe.net

mnt-by

The "mnt-by" attribute specifies the registered entity responsible for maintaining and updating this object. Requests regarding updates should be directed to this entity. This attribute is optional, and multiple attributes are allowed in the object.

mnt-by: RIPE-DBM

changed

The "changed" attribute specifies who changed this object and when the change was made. The person is specified as an e-mail address, followed by the change date, separated by a space in the format "YYMMDD". This attribute is required, and multiple attributes are allowed in the object so that the change history is visible.

changed: marten@ripe.net 940328

source

The "source" attribute specifies the source of the data in question. This will usually be the name of the NIC. If the data originates from another database, the name of that database is specified. This attribute is intended to support the global exchange of information. In the case of RIPE, the value of the "source" attribute is always "RIPE". This attribute is required, and only one attribute is allowed in the object.

source: RIPE

A detailed description can be found in the documentation from RIPE NCC.