The object template includes information on how to complete the attribute values.
Status Instance Search Status route6: [mandatory] [single] [primary/look-up key] descr: [mandatory] [multiple] [ ] origin: [mandatory] [single] [primary/inverse key] holes: [optional] [multiple] [ ] org: [optional] [multiple] [inverse key] member-of: [optional] [multiple] [ ] inject: [optional] [multiple] [ ] aggr-mtd: [optional] [single] [ ] aggr-bndry: [optional] [single] [ ] export-comps: [optional] [single] [ ] components: [optional] [single] [ ] remarks: [optional] [multiple] [ ] 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] [ ]
route6: 2001:0DB8::/32 descr: route object for 2001:0DB8::/32 origin: AS1234 mnt-lower: MAINT-EXAMPLENET-AP mnt-routes: MAINT-EXAMPLENET-AP mnt-by: MAINT-EXAMPLENET-AP changed: firstname.lastname@example.org 20101231 source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|route6||The IPv6 address prefix to be routed.
|descr||A short description related to the object, including the organization responsible for the route6 object.|
|origin||The AS number used to route the address prefix described in the route6 attribute.
Note: if the same address prefix is routed by more than one AS, that is, the network is multihomed, the origin attribute distinguishes between route6 objects with the same prefix in the route attribute.
|mnt-by||Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.
EXAMPLE mnt-by: MAINT-SPARKY-WF
|changed||The email address of who last updated the database object and the date it occurred.
changed: email@example.com 20010921
IMPORTANT! This is NOT to be used as a contact address.
|source||The database where the object is registered.
Attribute may be deleted from the object. To delete an optional attribute you must also remove the attribute from the object template. Failure to do so will result in errors.
|country||Two letter ISO 3166 code of the country or economy where the admin-c is based. Please use UPPERCASE letters.
EXAMPLE country: WF
|holes||Lists address prefixes that are not reachable through the IPv6 route.
|member of||Identifies a route-set object of which you wish this route6 to be a member.
Note: to be included as a member of the route-set, the route-set object must specify the maintainer of the route object in the route-set object’s mbrs-by-ref attribute. For more information, see RFC 2622 – Routing Policy Specification Language (RPSL), section
|inject||Specifies which routers perform the aggregation and when the routers should perform the aggregation.|
|aggr-mtd||Specifies how the route aggregate is generated.|
|aggr-bndry||TA set of Autonomous Systems which form the aggregation boundary.
|export-comps||Specifies an RPSL filter that matches the more specific routes that need to be exported outside the aggregation boundary.|
|components||The component routes used to form the aggregate.|
|remarks||General remarks related to the role object. Remarks can include a URL or RFC 822 address (if preceded by
|cross-mnt||A mntner object to be notified of any overlaps with the prefix specified in the ‘route’ object. When an overlapping ‘route’ is added or removed, a notification will be sent to the email addresses
listed in the email attribute of the specified mntner object.
|notify||The email address to which notifications of changes to this object should be sent.
|mnt-lower||If no ‘mnt-routes’ attribute is included, the registered ‘mntner’ object specified in the mnt-lower attribute is used to control the creation of more specific route objects
within the prefix covered by this route object.
|mnt-routes||The identifier of a registered mntner object used to control the creation of route6 objects more specific than this route6 object.|
Attribute value is generated by the database.
You will soon be able to updated this object in MyAPNIC.
Instances of attribute allowed
|Attribute must appear only once in the object.|
|Attribute may appear multiple times in the object. For example, you may wish to include more than one admin-c attribute.|
Attribute search status
|Primary keys distinguish an object from all other objects in the database. To update a primary key, you must delete the entire object and them create a new object with the updated information.|
|Attribute can be queried in the database to return the object. Please note, however, that a lookup key does not uniquely identify an object.|
|Attribute can be used when performing an inverse query using the -i flag. For example, the query
-i mntner <MNTNER-NAME>
will return all objects with the specified maintainer in the mnt-by attribute.
Using route6 objects
Use route6 objects to help configure your network’s routers. Route6 objects, in combination with the aut-num and other related
objects, can be used to describe your IPv6 routing policy in a compact form. This can help your network identify routing policy errors and omissions more easily than by reading long configuration files.
- Use automated tools, such as IRRToolset, to retrieve information from the route objects to create router configuration files for different architectures.
- Configuration files produced this way are less prone to errors than manually configured routers.
- If your network needs are complex, there are optional advanced technical attributes that allow you to specify route aggregation.