[DBWG] mnt-by attribute on autnums

Sander Steffann sander at steffann.nl
Sat Aug 25 16:54:48 UTC 2018

Hi Madhvi,

>> Member owned mntner objects are only allowed in:
>> - "mnt-lower" (allowing creation of AS6500:AS-FOO style objects)
>> - "mnt-routes" (allowing creation of route[6] objects that have matching origin - a control which is going away as a result of the discussion on https://lists.afrinic.net/pipermail/dbwg/2018-May/000035.html)
>> This restriction means that a member cannot update the attributes (including things like [mp-]import/export) of the autnum without the manual assistance of the hostmaster. This restriction doesn't appear to be present (as far as I can tell without being a user of those DBs) at any other RIR.
> AFRINIC is aware that its members need to autonomously update their
> routing policy on their ASNs.
> The mnt-routes allows a member to update its import/export attribute. We
> have tested this previously and it worked. May we please ask you to test
> as well(update your ASN with the attributes) and share with us the error
> messages that you receive. We will test it again as well.

Ah, if that is the case then it just seems to be a documentation problem. The current database documentations states:

"As AFRINIC is not running a routing registry yet, the import, export and default attribute (routing policies) are removed in AFRINIC database and should be provided as remarks only."

Field like import/export/mp-import/mp-export are not documented in the manual at https://www.afrinic.net/library/membership-documents/219-objects-template#23 at all.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.afrinic.net/pipermail/dbwg/attachments/20180825/082696e5/attachment.sig>

More information about the DBWG mailing list