This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] A test on AFRINIC range announcing without RIPE route object
- Previous message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
- Next message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Fri Jun 15 14:03:34 CEST 2018
Dear Denis, On Fri, Jun 15, 2018 at 1:58 PM, denis walker via db-wg <db-wg at ripe.net> wrote: > My current understanding is that AFRINIC does not refuse to create a ROUTE > simply because you do not own the foreign ASN. They may do some additional > checks, but if everything is in order they will permit the ROUTE creation. > So this is not a show stopper. It turns out that AfriNIC will allow you to set any African Origin ASN - but only allows foreign ASNs as "Origin ASN" iff the prefix holder and the ASN holder are the same organisation. This is why organisations that lease AfriNIC IP space out to to non-AfriNIC ASNs must use RADB, RIPE, NTTCOM, ALTDB, etc where these restrictions do not apply. This restriction does not apply when creating RPKI ROAs - when creating a ROA the prefix holder can simply input any ASN regardless of whether it is an AfriNIC managed resource or not. Kind regards, Job
- Previous message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
- Next message (by thread): [db-wg] A test on AFRINIC range announcing without RIPE route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]