The as-macro object:
An `AS Macro' is a group of autonomous systems with
the same routing policies. See ripe-181 for details.
[primary/
as-macro: [mandatory] [single] look-up key]
descr: [mandatory] [multiple] [ ]
as-list: [mandatory] [multiple] [ ]
guardian: [optional] [single] [ ]
tech-c: [mandatory] [multiple] [inverse key]
admin-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 as-macro object are
defined below:
as-macro
The identifier of a macro containing at
least two Autonomous Systems.
AS-string where string consists of uppercase
leters only.
descr
A short decription of this object.
All characters possible.
as-list
The list of ASes or other AS macros that
make up an AS Macro.
aut-num as-macro ...
guardian
This attribute functions as a "notify" attribute.
RFC-822 address.
tech-c
A technical contact.
NIC-handle
admin-c
An on-site contact (person)
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.
| 
