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 ]
Lu Heng
h.lu at anytimechinese.com
Fri Jun 15 14:48:12 CEST 2018
Hi denis: Job already did ask in their mailling and that was the situation. RIR IRR should not work separately, as internet doesn’t distinguish from ripe traffic to Afrinic traffic, we shouldn’t solve one problem here and create another somewhere else. But again, I am asking the community to allow Afrinic some time to fix their IRR, end of the day, we want to a more functional internet not an more broken one. RADB is an alternative we are currently looking into, but then again, it is best to have RIR’ IRR working as expected. With regards. Lu On Fri, Jun 15, 2018 at 21:11 denis walker <ripedenis at yahoo.co.uk> wrote: > Hi Job > > This is not my understanding. But please, someone raise this specific > issue on an AFRINIC mailing list and get an official response from AFRINIC. > It is pointless debating it here. > > cheers > denis > co-chair DB-WG > > ------------------------------ > *From:* Job Snijders <job at instituut.net> > *To:* denis walker <ripedenis at yahoo.co.uk> > *Cc:* Lu Heng <h.lu at anytimechinese.com>; Database WG <db-wg at ripe.net> > *Sent:* Friday, 15 June 2018, 14:03 > *Subject:* Re: [db-wg] A test on AFRINIC range announcing without RIPE > route object > > 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 > > > > -- -- Kind regards. Lu -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20180615/9a87031f/attachment.html>
- 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 ]