Download RIPE Database Reference Manual

Specifies multiprotocol import policy expression. Please refer to RPSLng
[14] for more information.
mp-members:
afi <afi-list> list of <address-prefix-
range> or
<route-set-name> or
<route-set-name><range-operator>
Lists the multiprotocol members of the set. Refer to RPSLng [14] for more
information.
mp-peer: <protocol> afi <afi> <ipv4- or ipv6- address> <options>
| <protocol> <inet-rtr-name> <options>
| <protocol> <rtr-set-name> <options>
| <protocol> <peering-set-name> <options>
Specifies the details of any (interior or exterior) multiprotocol router
peerings. Please refer to RPSLng [14] for more information.
mp-peering: afi <afi> <peering>
Defines a multiprotocol peering that can be used for importing or
exporting routes. Please see RPSLng [14] for more information.
netname:
<netname>
Specifies the name of a range of IP address space. The syntax of the
<netname> attribute is the same as the syntax of the <object-name>
attribute, but it does not have a restriction on RPSL reserved prefixes.
nic-hdl:
<nic-handle>
Specifies the NIC handle of a role or person object. When creating an
object, one can also specify an "AUTO" NIC handle by setting the value
of the attribute to "AUTO-1" or AUTO-1 <Initials>. In such case the
database will assign the NIC handle automatically.
notify:
<e-mail>
Specifies the e-mail address to which notifications of changes to an object
should be sent.
62