Attributes
The lay-out of this document is:
<attribute> == {basic}
or else the attribute is defined in this document.
If
<attribute> == {basic}
look for {basic} in the "Basics" file.
address
-------
Full postal address of a person.
<address> == {free text}
admin-c
-------
An on-site contact (person)
<admin-c> == {auto-nic-assign} | {nic-handle} | {name}
advisory
--------
Advises a specific `target' autonomous system (AS)
to use the information that is defined in this
attribute.
<ASnnnn> <AS specific information>
<ASnnnn> == <aut-num> == {aut-num}
<AS specific information> == not defined in code; see ripe-131.
<AS specific information> == defined by the operator of ASnnnn
<AS specific information> == <1 or more of any type of character>
as-exclude
----------
A list of transit ASes from which all routes will be
ignored.
exclude <aut-num> to <exclude-route-keyword>
exclude == `exclude'
<aut-num> == {aut-num}
to == `to'
<exclude-route-keyword> == [ <aut-num> | <as-macro> | <community> | ANY ]
ANY == `ANY'
as-in
-----
Description of policy for route acceptance.
from <aut-num> <cost> accept <routing policy expres-
sion>
from == `from'
<aut-num> == <aut-num>
<cost> == {cost}
accept == `accept'
<routing policy expression> == ({askeyword} | <netlist>) <brackets> | <braces>
<netlist> == {netlist}
<brackets> == {brackets}
<braces> == {braces}
as-list
-------
The list of ASes or other AS macros that make up an
AS Macro.
<aut-num> <as-macro> ...
<aut-num> == {aut-num}
<as-macro> == {as-macro}
as-macro
--------
The identifier of a macro containing at least two
Autonomous Systems.
AS-<string> where <string> consists of uppercase
leters only.
<as-macro> == `AS-'(1 or more `A'...`Z')
as-name
-------
A descriptive name associated with an AS.
Uppercase letters, dashes ("-") and digits, no
spaces. Must start with a letter. "." and "_"
will be converted into "-".
<as-name> == {netname}
as-out
------
Description of policy for route announcement.
to <aut-num> announce <routing policy expression>
to == `to'
<aut-num> == {aut-num}
announce == `announce'
<routing policy expression> == ({brackets}|{braces}) (`{' {netlist} `}') | \
{askeyword}
as-transit
----------
The transit preferences of an AS.
transit <ASpath> to <destination>
transit == `transit'
<ASpath> == <ASpath> # not defined in the code
to == `to'
<destination> == <destination> # not defined in the code
aut-num
-------
The autonomous system number. This must be a
uniquely allocated autonomous system number from an
AS registry (e.g.RIPE NCC, the Inter-NIC, etc).
"AS"<positive integer between 1 and 65535>
<aut-num> == {aut-num}
aut-sys
-------
This attribute is OBSOLETE.
auth
----
Scheme to be used to authenticate update requests.
<auth> == ({auth_NONE} | {auth_MAIL-FROM} | {auth_CRYPT-PW})
author
------
Limerick author (i.e. author of a Limerick, not an
author from Limerick :-D )
<author> == ({auto-nic-assign} | {nic-handle} | {name})
authority
---------
The formal authority for a community. This could be
an organisation, institute, committee, etc.
<authority> == (1 or more [`a'..`z', `A'..`Z', 0..9, `-', ` ', `,',
`\', `(', `)', `/'])
bdry-gw
-------
This attribute is OBSOLETE.
bdrygw-l
--------
List of boundary gateways.
Obsolete in the inetnum object.
bis
---
This is the `boundary intermediate system'
attribute.
<bis> == {CLNS prefix} or {CLNS prefix} {CLNS prefix}
changed
-------
Who previously changed this object and when this
change was made.
<RFC822 e-mail address> <DATE> E-mail address of
person updating the object. DATE in YYYYMMDD or
YYMMDD format.
<changed> == {RFC-822 address} {DATE}
comm-list
---------
A list or 1 or more communities of which a route is
part.
<community object> <community object> ...
<community object> == <community>
community
Name of a community.
Uppercase text which cannot start with a routing
policy expression keyword.
<community> == {community}
connect
This attribute is OBSOLETE
country
--------
Name of the country of the admin-c.
2 letter uppercase ISO 3166 country code.
<country> == <member of the country code list>
<member of the country code list> == <[`A'..`Z'][`A'..`Z']>
default
-------
There are two uses of this attribute; (a) with the
dom-prefix (CLNS) object; (b) with the aut-num (AS)
object:
dom-prefix (CLNS) object:
------------------------
<CLNS prefix>
aut-num (AS) object:
-------------------
<aut-num> <relative cost> <default-expression>
<default-expression> is optional.
<aut-num> == {aut-num}
<relative cost> == <cost> == {cost} == <positive, non-zero integer>
<default-expression> == (`static' | `default' |{netlist})
descr
-----
A short description of this object.
All characters possible.
<descr> == {free text}
dom-in
------
<boundary intermediate system> <preference cost>
<CLNS keyword>
<boundary intermediate system> == {CLNS prefix}
<preference cost> == {cost} == (positive, non-zero integer)
<CLNS keyword> == ({CLNS prefix} |ANY|AND|OR|NOT| `(' | `)'
dom-name
--------
The IP domain name for a ConnectionLess Network Ser-
vice object.
Fully qualified domain name without trailing "."
<dom-name> == <domain name>
dom-net
-------
List of IP networks in a domain.
Dotted quad including trailing 0's.
<dom-net> == {net number}
dom-out
-------
dom-out attribute
<boundary intermediate system> <routing policy
expression>
<boundary intermediate system> == <CLNS prefix>
<routing policy expression> ==
< <aut-num> | <KEYWORD> | <community> | <as-macro> | <netlist> >
dom-prefix
----------
<CLNS prefix>
domain
------
IP domain name.
Full qualified domain name without trailing ".".
<domain> == {domain name}
e-mail
------
The e-mail address of a person or role.
RFC-822 address.
<e-mail> == {RFC-822 address}
fax-no
------
The fax number of a person or role
+ <Country Code> <Area Code> <Fax Number>
+ <Country Code><Area Code & Number><extension>
<fax-no> == {phone number}
gateway
-------
This attribute is OBSOLETED
guardian
--------
This attribute functions as a "notify" attribute.
<guardian> == {RFC-822 address}
hole
----
Indicates the parts of the address space covered to
which the originator does not provide connectivity.
Classless prefix length representation. <IP num-
ber>/<prefix length>
<hole> == {IP number}/{prefix length}
<IP number> == <quad>.<quad>.<quad>.<quad>
<quad> == 0 <= X <= 255
<prefix length> == 0 <= X <= 32
ias-int
-------
OBSOLOETED
NONE
ifaddr
------
An interface address within an internet router.
<Interface Address> <Interface Subnet Mask>
<ifaddr> == {Interface Address} {Interface Subnet Mask}
<Interface Address> == {IP address}
inet-rtr
--------
Fully qualified domain name of an internet router.
Fully qualified domain name without trailing "."
<inet-rtr> == <domain name>
inet6num
--------
Full IP version 6 address.
<ip6num>/<prefix length>
inetnum
-------
A range of IP address space.
x.x.x.x - x.x.x.x, where 0 =< x =< 255
<inetnum> == {inetnum range} or {inetnum prefix}/{inetnum length}
interas-in
----------
Incoming local preferences on an inter-AS connec-
tion.
from <aut-num> <local-rid> <neighbour-rid> <prefer-
ence> accept <routing policy expression>
<interas-in> == from <aut-num> <local-rid> <neighbour-rid> \
<preference> accept <routing policy expression>
from == `from'
<aut-num> == <aut-num>
accept == `accept'
<local-rid> == <IP address>
<neighbour-rid> == <IP address>
<preference> == <cost> == <positive, non-zero integer>
accept == `accept'
<routing policy expression> ==
< <aut-num> | <KEYWORD> | <community> | <as-macro> | <netlist> >
interas-out
Outgoing local preferences on an inter-AS connec-
tion.
to <aut-num> <local-rid> <neighbour-rid> [<metric>]
announce <routing policy expression> <metric> is
optional and is defined as: (<metric-type>=<value>)
to == `to'
<aut-num> == <aut-num>
<local-rid> == <IP address>
<neighbour-rid> == <IP address>
[<metric>] == optional <metric>
<metric> == `(metric-out=)'<metric value>
<metric value> == [`IGP'| 1 or more dec dgt]
announce == `announce'
<routing policy expression> == <routing policy expression>
limerick
--------
Title of a limerick.
LIM-<string>, where string can include alphanumeric
characters, "-" character.
<limerick> == `LIM-'(0 or more [a..z,A..Z,0..9,`-'])
localas
-------
The autonomous system in which a router belongs.
AS<positive integer between 1 and 65535>.
<localas> == <aut-num>
location
--------
This attribute is OBSOLETE
maintainer
----------
This attribute is OBSOLETE.
mnt-by
------
The identifier of a registered mntner object used
for authorization and authentication.
<mntner>
<mnt-by> == (1 or more [`A'..`Z', 0..9, `-'])
mnt-lower
---------
<mnt-lower> == (1 or more [`A'..`Z', 0..9, `-'])
The identifier of a registered mntner object used
for hierarchical authorization and authentication.
<mntner>
mnt-nfy
-------
The e-mail address to be notified when an object
protected by a mntner is successfully updated.
RFC-822 address.
<mnt-nfy> == {RFC-822 address}
mntner
------
The name of a mntner object. Must be an unique mnt-
ner name, but can be identical to AS names, nic-han-
dles.
<uppercase letter><uppercase alphanumeric, "-">
<mntner> == ([`A'..`Z'])(0 or more [`A'..'Z', 0..9, `-'])
netname
-------
The name of a range of IP address space.
<netname> == {netname}
nic-hdl
-------
The NIC handle of a role or person object. This can
be a RIPE NIC-handle or a NIC-handle assigned by
other regional registries.
RIPE NIC-handle: <Initials><0-999>-RIPE
<nic-hdl> == {NIC-handle}
notify
------
The e-mail address to which notifications of changes
to an object should be sent.
<RFC-822 address>
<notify> == {RFC-822 address}
nserver
------
List of nameservers for a domain object; a minimum
of two is mandatory .
<Fully qualified domain name(s) without trailing
"."> OR <IP Address(es) of the nameserver(s)>
<nserver> == {domain-name} OR <nservIP-addr>
<nservIP-addr> ==
( <nservIP-element>.<nservIP-element>.<nservIP-element>.<nservIP-element> )
<nservIP-element> == ([0..9] 0 or more [0..9])
#
# N.B. this definition of an IP address is not as strict as other definitions
nsf-in
------
This attribute is OBSOLETE
nsf-out
-------
This attribute is not used.
Obsolete
op-fax
------
Fax Number
+ <Country Code><Area Code><Fax Number> Optional:
spaces may be used to split up the number into its
constituent components. "." characters can also be
used to separate the digits.
<op-fax> == {phone number}
op-mail
-------
E-mail address of a person or role object
<RFC-822 address>
<op-mail> == <RFC-822 address>
op-phone
--------
Telephone number
+ <Country Code><Area Code><Phone Number> + <Country
Code><Area Code><Phone Number> <ext.> <number>
Optional: spaces may be used to split up the number
into its constituent components. "." characters can
also be used to separate the digits.
<op-phone> == <phone number>
origin
------
The autonomous system announcing a route.
AS<positive integer between 1 and 65535>
<origin> == <aut-num>
peer
----
Details of any (interior or exterior) router peer-
ings.
<Peer address> <Peer AS> <Routing Protocol> [Local
AS] [Local AS] is optional.
<peer> == <Peer address> <Peer AS> <Routing Protocol> [<Local AS>]
<Peer address> == <IP address>
<Peer AS> == <aut-num>
#
# Code is strange; if it finds "pe", it checks for the optional
# `localas' string. If it finds `localas', it only checks the
# optional part, and does not do a syntax check on <Peer address>,
# <Peer AS> etc.
#
person
------
The full name of an adminstrative, technical or zone
contact person specified in another object. Do not
use titles such as "Dr.", "Prof.", "Mv.", "Ms.",
"Mr.", etc.
<Personal Name> <Family Name> where each name is
composed of alphabetic characters.
<person> != {nic-handle}
<person> == {Name}{Name} ... {Name}
#
# Number of <Name> is defined in the configuration file;
# now, it is 2
#
<Name> != `AUTO-'
<Name> cannot include <Titles>
<Titles> == ([mr|ms|mrs|dr|drs||ir|ing|sign|herr|hr|frau|prof]`.')
<Name> == (At least two characters, neither can be the `.' character)
<Name> == !(`AUTO-') && <Name-part-1><Name-part-2>
<Name-part-1> == ([`a'..`z', `A'..`Z'])
<Name-part-2> == (0 or more [alphanumeric, `-', `.', `|', "`", "'" ])
phone
-----
Telephone number
+ <Country Code><Area Code><Phone Number> + <Country
Code><Area Code><Phone Number> ext. <number>
Optional: spaces may be used to split up the phone
number into its constituent components. "." charac-
ters can also be used between to separate the dig-
its.
<phone> == <phone number>
remarks
-------
General remarks. Can include an URL or RFC822
address (if preceeded by mailto:).
<remarks> == {free text}
rev-srv
-------
Domain name server for a range of IP addresses.
Fully qualified name without trailing "."
<rev-srv> == {domain name}
role
----
The full name of a role entity e.g. RIPE DBM.
Two components, each consisting of alphabetic char-
acters. Note: there is no "-" character between the
two components of the the name.
<role> != `AUTO-'
<role> cannot be a NIC-handle
<role> != <NIC-handle>
<role> == {person}
rout-pr
-------
Routing privilages attribute.
Uppercase letters, digits or "-" characters.
<rout-pr> == ( 1 or more [`A'..`Z', 0..9, `-'] )
route
-----
A route being anounced.
Classless prefix length representation. <IP num-
ber>/<prefix length>
<route> == (1 or more [0..9, `.']) or
<route> == {inetnum prefix}/{inetnum length}
<route> == {inetnum range}
routpr-l
--------
This attribute is OBSOLETE
source
------
Identifier of the database containing authoritative
data for this object. Use RIPE for objects in the
RIPE Database.
Uppercase Text.
<source> == defined in configuration file as DBFILE and CANUPD
status
------
Type of allocated or assigned address space.
Uppercase Text.
<status> == ([`D'(`ELEGATED')|`ASSIGNED '(`PA'|`PI') |
`ALLOCATED '(`PI'|`PA'|`UNSPECIFIED')] )
sub-dom
-------
List of the sub-domains of a domain
<Relative domain name to the domain>
<sub-dom> == <domain name>
tech-c
------
A technical contact.
<NIC-handle>
<tech-c> == <NIC-handle> or <person> or <role>
text
---
Must be humourous, but not malicious or insulting.
:-)
<text> == {free text}
trouble
-------
Information on who to contact when there are prob-
lems.
<text> == {free text}
upd-to
------
The e-mail address to be notified when an object
protected by a mntner is unsuccessfully updated.
RFC-822 address
<upd-to> == {RFC-822 address}
withdrawn
---------
Indicates who withdrew a route and the date.
<RFC822 e-mail address> <DATE> E-mail address of
person withdrawing the route. DATE in YYYYMMDD or
YYMMDD format.
<withdrawn> == {RFC-822 address} {DATE}
zone-c
------
NIC-handle of the person with authority over a zone.
<NIC-handle>
<zone-c> == <NIC-handle> or <person> or <role>