Broadband One currently does not use aut-num objects as a basis for routing policy. A sample Aut-Num object (preferred format):
aut-num: AS12345
as-name: ACME-AS
descr: ACME Widgets of America
import: from A56789
action pref=100;
accept ANY
export: to AS56789
announce AS12345
admin-c: ZA1
tech-c: ZA1
notify: zacme@acme.com
mnt-by: MAINT-AS12345
changed: zacme@acme.com 19960626
source: BBOI
aut-num: [mandatory] [single] [primary/look-up key] as-name: [mandatory] [single] [ ] descr: [mandatory] [multiple] [ ] member-of: [optional] [multiple] [inverse key] import: [optional] [multiple] [ ] export: [optional] [multiple] [ ] default: [optional] [multiple] [ ] remarks: [optional] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] cross-mnt: [optional] [multiple] [inverse key] cross-nfy: [optional] [multiple] [inverse key] notify: [optional] [multiple] [inverse key] mnt-lower: [optional] [multiple] [inverse key] mnt-routes: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]
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), or one uniquely generated for the Broadband One routing registry. "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 description of this object. All characters are possible. The description field may span multiple lines, either with or without labels.
member-of: A reverse-key reference to an as-set object. This does not have to be present even if the aut-num is a member of an as-set.
import: A set of statements describing the import policy of that aut-num object. Each policy statement may be on a single or multiple lines, but an individual statement should only contain a single import: label. For example, the following policies may be written in either of the following ways:
import: from AS2 action pref = 1; accept { 128.9.1.0/24 }
import: from AS3 action pref = 1; accept { 128.9.2.0/24 }
OR:
import: from AS2
action pref = 1;
accept { 128.9.1.0/24 }
import: from AS3
action pref = 1;
accept { 128.9.2.0/24 }
export: A set of statements describing the export policy of that aut-num object. Each policy statement may be on a single or multiple lines, but an individual statement should only contain a single export: label. For example the following policies may be written in either of the following ways:
export: to AS4 announce AS1
export: to AS5 announce AS1
OR:
export: to AS4
announce AS1
export: to AS5
announce AS1
default: Default routing policies are specified using the default attribute. Each statement may be on a single or multiple lines, but an individual statement should only contain a single default: label. For example:
default: to AS2 action pref = 1;
default: to AS3 action pref = 2;
OR:
default: to AS2
action pref = 1;
default: to AS3
action pref = 2;
remarks: General remarks. Can include an URL or RFC822 email address (preceded by mailto:) - may span multiple lines, either with or without multiple remarks: labels.
admin-c: An on-site contact (person) represented by (NIC-handle ), which links to a person object.
tech-c: A technical contact, represented by (NIC-handle ), which links to a person object.
notify: The e-mail address to which notifications of changes to an object should be sent (RFC-822 format).
mnt-by: The identifier of a registered maintainer object used for and authentication. changed: Who previously changed this object. (RFC822 e-mail address) E-mail address of person updating the object.
source: The identifier of the database containing authoritative data for this object. This should be BBOI (in upper case) for all Broadband One maintainers.