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/[email protected]/

[db-wg] NWI-3 - AFRINIC IRR Homing

Previous message (by thread): [db-wg] NWI-1 - staying on top of abuse contact changes
Next message (by thread): [db-wg] NWI-4 - role of status: field in multivalued status context

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Piotr Strzyzewski Piotr.Strzyzewski at polsl.pl
Mon Jun 27 19:26:05 CEST 2016

On Thu, May 26, 2016 at 02:57:25PM +0200, Job Snijders wrote:
> On Wed, May 25, 2016 at 04:44:03PM +0200, Gert Doering wrote:
> > On Wed, May 25, 2016 at 03:11:38PM +0200, Job Snijders wrote:
> > > NWI-3 - Afrinic IRR Homing
> > > --------
> > [..]
> > >     And while the general problem of out-of-region ROUTE(6) and AUT-NUM
> > >     objects in the RIPE Database IRR, and the problem where the prefix
> > >     and the ASN belong to different regions is not trivial to resolve,
> > >     there seems to be a general consensus that simple cases where
> > >     ROUTE(6) objects have both an ASN and prefix in Afrinic (~34k
> > >     objects), should appear in the Afrinic IRR where authorisation can
> > >     be done and not in the RIPE DB.
> > 
> > Support, as written.
> 
> I too agree with it.

+1

Piotr

-- 
gucio -> Piotr Strzyżewski
E-mail: Piotr.Strzyzewski at polsl.pl

Previous message (by thread): [db-wg] NWI-1 - staying on top of abuse contact changes
Next message (by thread): [db-wg] NWI-4 - role of status: field in multivalued status context

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]