The aut-num object:
The aut-num object describes the details of the
registered owner of an Autonomous System and their
routing policy for that AS. See ripe-181 and
RFC-BGP4 for details.
[primary/
aut-num: [mandatory] [single] look-up key]
as-name: [optional] [single] [ ]
descr: [mandatory] [multiple] [ ]
as-in: [optional] [multiple] [ ]
as-out: [optional] [multiple] [ ]
cross-nfy: [optional] [multiple] [inverse key]
cross-mnt: [optional] [multiple] [inverse key]
interas-in: [optional] [multiple] [ ]
interas-out: [optional] [multiple] [ ]
as-exclude: [optional] [multiple] [ ]
default: [optional] [multiple] [ ]
guardian: [optional] [single] [ ]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [mandatory] [multiple] [inverse key]
remarks: [optional] [multiple] [ ]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]
The content of the attributes of the aut-num object are
defined below:
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
as-name
A descriptive name associated with an AS.
Uppercase letters, dashes ("-") and digits,
no spaces. Must start with a letter.
descr
A short decription of this object.
All characters possible.
as-in
Description of policy for route acceptance.
from aut-num cost accept routing policy
expression
as-out
Description of policy for route announcement.
to aut-num announce routing policy expression
cross-nfy
Name of person or role object fro use in cross
notification
person/role
cross-mnt
Name of a maintainer object for use in cross
notification
mntner
interas-in
Incoming local preferences on an inter-AS
connection.
from aut-num local-rid neighbour-rid preference
accept routing policy expression
interas-out
Outgoing local preferences on an inter-AS
connection.
to aut-num local-rid neighbour-rid [metric]
announce routing policy expression
metric is optional and is defined as:
(metric-type=value)
as-exclude
A list of transit ASes from which all routes
will be ignored.
exclude aut-num to exclude-route-keyword
default
There are two uses of this attribute;
(a) with the dom-prefix (CLNS) object;
(b) with the aut-num (AS) object:
aut-num relative cost default-expression
default-expression is optional.
guardian
This attribute functions as a "notify"
attribute.
RFC-822 address.
admin-c
An on-site contact (person)
NIC-handle
tech-c
A technical contact.
NIC-handle
remarks
General remarks. Can include an URL or RFC822
address (if preceeded by mailto:).
free text
notify
The e-mail address to which notifications
of changes to an object should be sent.
RFC-822 address
mnt-by
The identifier of a registered mntner object
used for authorization and authentication.
mntner
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.
source
Identifier of the database containing
authoritative data for this object.
Use RIPE for objects in the RIPE Database.
Uppercase Text.
|