In message
denis walker wrote:
>Interesting that you have tried to build a tool to get the correct
>whois data on a resource from any RIR. The RIPE Database already does
>this for you. The RIPE NCC mirrors all the other RIR resource
>databases and some independent IRR databases in a Global
HI Ronald
The process and timelines are explained here
https://labs.ripe.net/author/stefania_fokaeos/our-plan-to-fix-country-codes/
cheers
denis
co-chair DB-WG
On Wed, 12 May 2021 at 22:21, Ronald F. Guilmette via db-wg
wrote:
>
> It is my understanding that it was decided that country: fields
Hi Ronald
Interesting that you have tried to build a tool to get the correct
whois data on a resource from any RIR. The RIPE Database already does
this for you. The RIPE NCC mirrors all the other RIR resource
databases and some independent IRR databases in a Global Resource
Service (GRS) If you
It is my understanding that it was decided that country: fields would be
added into any & all org objects that did not already contain them.
I would just like to inquire about the current status and expected timeline
for this project. Is there an expected completion date? Is RIPE NCC doing
all
In message <77e5d90b-6733-4cf8-8e15-3d984e4fb...@ripe.net>,
Edward Shryane wrote:
>The RIPE-NONAUTH database contains all out of region route(6) objects
>(referencing prefixes not allocated to RIPE).
>
>This database was created by NWI-5:
Dear Working Group Members,
Below is the agenda for the Database Working Group for RIPE82. If you have
any questions, comments, or requested changes please let the chairs know.
Best regards,
William & Denis
DB-WG Chairs
A. Introduction - 5 min
* Welcome
* Scribe
* Jabber
*
Dear Erik,
On Wed, May 12, 2021 at 12:00:52PM +0400, Erik Linder via db-wg wrote:
> is there a need for the ROA object to be identical in length to the route
> object?
>
> take 41.213.128.0/21 is a RIPE-NOAUTH route object and there is a
> valid ROA from AFRINIC for 41.213.128.0/17 max length 24
Hi Erik,
> On 12 May 2021, at 10:00, Erik Linder wrote:
>
> is there a need for the ROA object to be identical in length to the route
> object?
>
> take 41.213.128.0/21 is a RIPE-NOAUTH route object
> and there is a valid ROA from AFRINIC for 41.213.128.0/17 max length 24
>
> regards
> erik
On 12/05/2021 09:35, Edward Shryane wrote:
> The proposed cleanup is to only remove route(6) objects from RIPE-NONAUTH
> which are not registered in *any* region:
> https://www.ripe.net/ripe/mail/archives/db-wg/2021-March/006876.html
>
> The cleanup will not delete the 62.61.192.0/18AS49902
is there a need for the ROA object to be identical in length to the route
object?
take 41.213.128.0/21 is a RIPE-NOAUTH route object
and there is a valid ROA from AFRINIC for 41.213.128.0/17 max length 24
regards
erik
On Wed, 12 May 2021 at 11:46, Edward Shryane wrote:
> Hi Erik,
>
> > On 12
Hi Erik,
> On 12 May 2021, at 09:27, Erik Linder wrote:
>
> > The proposed cleanup is to only remove route(6) objects from RIPE-NONAUTH
> > which are not registered in *any* region:
> too bad, because I have a use case where I have a couple of route objects in
> RIPE-NOAUTH but they are
> The proposed cleanup is to only remove route(6) objects from RIPE-NONAUTH
which are not registered in *any* region:
too bad, because I have a use case where I have a couple of route objects
in RIPE-NOAUTH but they are maintained by an old peering partner which
seems to have no wish to help me
Hello Frank, Ronald,
The RIPE-NONAUTH database contains all out of region route(6) objects
(referencing prefixes not allocated to RIPE).
This database was created by NWI-5:
https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005245.html
The proposed cleanup is to only remove route(6)
13 matches
Mail list logo
