4.2.6 Description of the ROUTE6 Object

Below is the object template for the route6 object. It lists all possible attributes that are allowed in this object type.

Attribute Name  Presence   Repeat     Indexed
route6: mandatory single primary/lookup key
descr: mandatory multiple
origin: mandatory single primary/inverse key
pingable: optional multiple
ping-hdl: optional multiple inverse key
holes: optional multiple
org: optional multiple inverse key
member-of: optional multiple inverse key
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: optional multiple
created: generated single
last-modified: generated single
source: mandatory single

A route6 object contains routing information for IPv6 address space resources. This is one of the main elements of the RIPE Internet Routing Registry.

Each interAS route (also known as an interdomain route) originated by an Autonomous System can be specified by using a route6 object for IPv6 addresses.

Authorisation for creating route6 objects is quite complex. There are four scenarios depending on who administers the address space and the AS Number. Because the RIPE INR and IRR are part of the same logical database, they can both be used for authorisation if the address space and/or AS Number are RIPE NCC administered resources. Where one or both are not administered by the RIPE NCC authorisation is bypassed but with the illusion of being genuine authorisation. For more details see the section 'Authorisation'.

As the RIPE IRR is part of a global routing registry, it is possible to create route6 objects in the RIPE Database for address space or AS Numbers registered in other RIR regions.

Example ROUTE6 object including all optional attributes:

route6:        fc00:600::/32
descr: Route
origin: AS3333
mnt-by: CHILD-MB-MNT
components: protocol BGP4 { 0:0:0:0:1:1:1:1/10^+}
protocol OSPF { 0:0:0:0:1:1:1:1/12^+}
inject: at action pref=100; upon HAVE-COMPONENTS { 0:0:0:0:1:1:1:1/0, 0:0:0:0:1:1:1:1/0 }
inject: at rtrs-myset:AS2:rtrs-test:AS777234
inject: at AS777234:rtrs-myset:AS2:rtrs-test:AS7777234
inject: action community = {65535:295};
inject: action community = {65535:20};
inject: upon HAVE-COMPONENTS {::/8}
export-comps: { fc00:600::/48 }
holes: fc00:600::/48, fc00:600::/56, fc00:600::/64
aggr-bndry: AS771234:AS-mytest:AS3:AS-test:AS775234
aggr-mtd: outbound AS771234:AS-mytest:AS3:AS-test:AS775234
member-of: AS200200:rs-test
member-of: AS3333:rs-test
mnt-routes: LIR-MNT { fc00:600::/36^+, fc00:600::/36^-, fc00:600::/16^36-48, fc00:600::/16^42, fc00:600::/56}
mnt-routes: LIR2-MNT anY
changed: noreply _at_ ripe _dot_ net 20120101
created: 1970-01-01T00:00:00Z
last-modified: 2012-01-01T15:30:45Z
source: TEST

Please refer to RFC 2622 for more information on the specific routing information attributes in the route6 object. Description of Attributes Specific to the ROUTE6 Object

  • “route6:” – This specifies the IPv6 address prefix of the route. Together with the "origin:" attribute, these constitute a combined primary key of the route6 object.
    The address can only be specified as a prefix. It can be one or more addresses.
  • “descr:” - A short description related to the object.
  • “origin:” - AS Number of the Autonomous System that originates the route into the interAS routing system. The corresponding aut-num object for this AS must already exist in the RIPE Database.
  • “pingable:” - Allows a network operator to advertise an IP address of a node that should be reachable from outside networks. This node can be used as a destination address for diagnostic tests. The IP address must be within the address range of the route6 object containing this attribute.
  • “ping-hdl:” - References a person or role capable of responding to queries concerning the IP address(es) specified in the 'pingable' attribute.
  • “holes:” – These attributes form a list of the component address prefixes that are not reachable through the aggregate route (that part of the address space is possibly unallocated).
  • “member-of:” – This attribute identifies a set object that this route6 object wants to be a member of. This membership claim, however, should be acknowledged by a corresponding "mbrs-by-ref:" attribute in the referenced set object.
  • “inject:” – These attributes specify which routers perform the aggregation and when they perform it.
  • “aggr-mtd:” – This attribute specifies how the aggregate is generated.
  • “aggr-bndry:” – This attribute defines a set of Autonomous Systems, which form the aggregation boundary.
  • “export-comps:” – This attribute defines the set's policy filter, a logical expression which when applied to a set of routes returns a subset of these routes.
  • “components:” – This attribute defines the component routes used to form the aggregate.
  • “mnt-lower:” - Provides a set of authorisation tokens used for hierarchical object creation. These tokens are used to authorise the creation of the one level more specific (child) objects to the route6 with the “mnt-lower:” attribute. This is only used if the parent route6 object does not contain an “mnt-routes:” attribute. If there is no “mnt-routes:” or “mnt-lower:” attribute, the “mnt-by:” authorises the creation of the child objects. For more details see the section 'Authorisation'.
  • “mnt-routes:” - Provides a set of authorisation tokens that may be used for exact match or more specific route6 object creation. For an exact match route6 object- if there is no “mnt-routes:” attribute, the “mnt-by:” is used. For a more specific route6 object- the “mnt-lower may also be used, if present.
    The "mnt-routes:" attribute can include an optional list of prefix ranges inside curly backets ("{}") or the keyword "ANY". This should follow the reference to the maintainer. The default, when no additional set items are specified, is "ANY" or all more specifics.