Re: [db-wg] DMARC issue

--- Begin Message --- Thanks for that suggestion. I will ask the NCC if this update is possible. cheersdenisco-chair DB-WG From: Andreas Schulze To: denis walker ; Database WG Sent: Thursday, 23 March 2017, 13:44

[db-wg] DMARC issue

--- Begin Message --- Colleagues The RIPE NCC has applied a mailman work around for DMARC to the DB-WG mailing list. This effectively wraps the sender inside the list address. The only real significance of this is that if you hit Reply the mail goes to the list and not the original sender. So

Re: [db-wg] DMARC issue

because of DMARC policies. cheersdenisco-chair DB-WG From: denis walker via db-wg <db-wg@ripe.net> To: Database WG <db-wg@ripe.net> Sent: Thursday, 23 March 2017, 12:58 Subject: [db-wg] DMARC issue Colleagues The RIPE NCC has applied a mailman work around for DMARC to the D

Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems

e.net" <db-wg@ripe.net> Sent: Friday, 21 April 2017, 6:12 Subject: Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems Hi Denis, On Thursday, April 20, 2017, 7:34:50 PM GMT+8, denis walker via db-wg <db-wg@ripe.net> wrote: > I think you misunderstood

Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems

--- Begin Message --- Hi Gert I do listen to your one voice Gert. Now with Sebastian at least we have two voices. Unfortunately, the way this community works that is probably the only consensus we will get to move forward. It is by no means representative, but it is a consensus. cheers denis

Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems

t; To: db-wg@ripe.net Sent: Thursday, 20 April 2017, 11:47 Subject: Re: [db-wg] NWI-7 proposal for fixing "abuse-c:" problems * denis walker via db-wg <db-wg@ripe.net> [2017-04-18 16:11]: > Colleagues Below is a proposal for fixing the problems with > "abuse-c:

[db-wg] NWI-7 proposal for fixing "abuse-c:" problems

--- Begin Message --- Colleagues Below is a proposal for fixing the problems with "abuse-c:" as shown in the problem statement for NWI-7https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items I look forward to comments. cheers denis co-chair DB-WG Proposal for improving "abuse-c:"

[db-wg] Fw: NWI-7 proposal for fixing "abuse-c:" problems

--- Begin Message --- - Forwarded Message - From: denis walker To: Havard Eidnes Cc: "db-wg@ripe.net" Sent: Thursday, 20 April 2017, 0:51 Subject: Re: NWI-7 proposal for fixing "abuse-c:" problems Hi Havard Thanks

Re: [db-wg] org field in the organisation object

--- Begin Message --- Hi Sergey The original design of the ORGANISATION object was to allow for them to be used hierarchically. So there could be a chain of trust between organisations. But nothing was ever implemented in that way. cheersdenisco-chair DB-WG From: Sergey Myasoedov via

Re: [db-wg] NWI-7: abuse-c implementation plan

--- Begin Message --- Colleagues It is almost two weeks since Tim sent out a proposed implementation plan and timeline. Can we assume no comments mean acceptance? If anyone has any specific comments can we here them please. Regardsdenisco-chair DB-WG From: Tim Bruijnzeels via db-wg

[db-wg] out of region routing in the RIPE Database

--- Begin Message --- Colleagues The DB-WG co-chairs would like to try to resolve (or close and document that as a consensus) another long standing issue, out of region ROUTE(6) and AUT-NUM objects in the RIPE Database (NWI-5). We would like to start off the (final?) round of discussions on

[db-wg] out of region routing in the RIPE Database

--- Begin Message --- Hi Daniel and others Just for the record I have followed all previous discussions on this issue over many years within the RIPE community. There have been many (opposing) views expressed. I don't recall any consensus within the RIPE community to expel all, or even just

Re: [db-wg] Whois release 1.90 in Release Candidate environment, production release planned for 16 October

--- Begin Message --- Hi Tim Thanks for working through this in time for the RIPE Meeting. It may not be the last word on "abuse-c:" but it will please a lot of people. cheersdenisco-chair DB WG From: Tim Bruijnzeels via db-wg To: Database WG Sent:

[db-wg] Fw: Foreign ROUTE objects in RIPE Database - final decision?

@ripe.net> To: denis walker <ripede...@yahoo.co.uk> Cc: Database WG <db-wg@ripe.net> Sent: Wednesday, 11 October 2017, 16:21 Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? On Mon, Oct 09, 2017 at 02:49:39PM +0100, denis walker via db-wg wrote: > Qu

[db-wg] Fw: Fw: NWI-7: abuse-c implementation plan modification

: denis walker via db-wg <db-wg@ripe.net> To: Database WG <db-wg@ripe.net> Sent: Wednesday, 27 September 2017, 11:55 Subject: [db-wg] Fw: NWI-7: abuse-c implementation plan modification Colleagues I think the suggestion below from Tim is OK. There seems little point sending n

[db-wg] Fw: NWI-7: abuse-c implementation plan modification

--- Begin Message --- Colleagues I think the suggestion below from Tim is OK. There seems little point sending notifications to users about changes they don't need to take action on of data that is redundant. So if anyone has any strong objections please let us know by the end of this week.

Re: [db-wg] Validation on "org-name:" syntax (double spaces and newlines)

Hi Colleagues A few comments expressed a slight preference for option 2 below, rejecting updates with multiple whitespace. So with my devil's advocate hat on let me make a comment. Putting multiple whitespaces in any text string in the database input has no meaning or benefit to anyone (except

Re: [db-wg] Validation on "org-name:" syntax (double spaces and newlines)

Hi Alex I presume 'whitespace' does include them, but to be sure Tim can confirm that. cheersdenisco-chair DB WG From: Alexander Stranzky via db-wg To: db-wg@ripe.net Sent: Monday, 13 November 2017, 9:05 Subject: [db-wg] Validation on "org-name:" syntax (double spaces

[db-wg] Creation of out of region ROUTE(6) objects

Colleagues We are now approaching the implementation stage for managing the existing out of region ROUTE(6) objects in the RIPE Database (NWI-5). A question has been asked about the creation of new ROUTE(6) objects in the RIPE Database relating to non RIPE address space. This will still be

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

Hi all From: Nick Hilliard via db-wg To: Tim Bruijnzeels Cc: Database WG Sent: Tuesday, 12 December 2017, 23:16 Subject: Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request Tim Bruijnzeels via db-wg

Re: [db-wg] Getting fraudulent entries removed

Hi guys Perhaps after the RIPE NCC implements the agreed actions on foreign ROUTE objects, it would be a good idea to do a (one time?) cleanup/review of all foreign ROUTE objects in the RIPE IRR. Find the contact details in the appropriate RIR Database for all non RIPE address space covered by

Re: [db-wg] query related to Open Source wg talk on blockchain

Hi Sandra Sub-allocation is not the same as transfer. At least not in the current understanding of transfers. There is also a difference between resources and objects in the database. If a resource holder ´transfers´ part of an allocation to another organisation, then the original resource

[db-wg] IRRd re-write

Colleagues During the current discussion on out-of-region ROUTE objects, Job announced that IRRd is being re-written and will have some 'potentially' fantastic features including 'possibly' authentication against the RIRs number registries. The alternative/commercial IRRs have also been

Re: [db-wg] A test on AFRINIC range announcing without RIPE route object

Hi Job From: Job Snijders via db-wg To: Lu Heng Cc: Database WG Sent: Wednesday, 13 June 2018, 12:52 Subject: Re: [db-wg] A test on AFRINIC range announcing without RIPE route object >> >> In conclusion, If you employ a non-Afrinic asn for announcements >> (which means a

Re: [db-wg] A test on AFRINIC range announcing without RIPE route object

: 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 wrote: > My current understanding is that AFRINIC does not refuse to create a ROUTE > simply because you do n

Re: [db-wg] A test on AFRINIC range announcing without RIPE route object

Hi Lu 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. As a side note, if you have

Re: [db-wg] A test on AFRINIC range announcing without RIPE route object

Hi All The co-chairs of the DB-WG are talking in the background to the RIRs about how this change will impact the holders of their address space. We are following the points raised here and checking some issues with the appropriate RIRs. The RIPE NCC Database team is also in the loop of these

Re: [db-wg] IRRd re-write

Colleagues My suggestion about the IRR(s) yesterday didn't seem to go down too well, so I will try again. I will start with a question. Why do people believe that having many, many independent/commercial IRRs, mostly containing unverified operational data and lots of personal data, where they

Re: [db-wg] [routing-wg] Last Call - creation of new out of region ROUTE(6) objects

Hi Ronald I understand your viewpoint, but I think it is a bit harsh to criticise the judgement of the early developers of the routing system. As Sandra explained in this posthttps://www.ripe.net/ripe/mail/archives/db-wg/2017-October/005707.html the early model was based on ASs. Then as the

[db-wg] Last Call - creation of new out of region ROUTE(6) objects

Colleagues Plans to implement the solution for NWI-5 by dropping the auth requirement from ASNs in ROUTE(6) object creation and marking existing out of region ROUTE(6) objects in the database with a different source tag are progressing. In December I asked if we should continue to allow the

Re: [db-wg] NWI-5 Out of region ROUTE(6)/AUT-NUM objects implementation request

Hi Tim I just noticed the comment below:"In case of inter-RIR transfers of live networks, ROUTE(6) objects are sometimes preserved for the transferred prefix(es). If so, they will be moved between the ‘RIPE’ and ‘RIPE-NONAUTH’ sections according to the direction of the transfer." Does this mean

[db-wg] Implementation of NWI-5 out of region ROUTE(6) objects

Colleagues Based on the proposal by Tim for NWI-5 and the following discussions, the DB-WG co-chairs would like the RIPE NCC to schedule implementation of the following actions: -Remove the ASN authorisation requirement for ROUTE(6) object creation -Deprecate the "mnt-routes:" attribute in the

Re: [db-wg] Clean up unreferenced maintainers (after 90 days)

Thanks for letting us know Ed cheersdenisco-chair DB-WG From: Edward Shryane via db-wg To: Database WG Sent: Thursday, 15 February 2018, 10:13 Subject: Re: [db-wg] Clean up unreferenced maintainers (after 90 days) Dear Working Group, thank you for

Re: [db-wg] Chair Selection Process Revision Proposal

Hi Erik To be honest I don't think we need to make the rules over complex. If a chair is removed by consensus and they stand again, the remaining chairs can take the same consensus that removed the chair as a consensus against that person being reappointed. I think the logic is their without

Re: [db-wg] Implementation plan and dates for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.

Thanks Ed I think this is a sensible plan. cheersdenisco-chair DB-WG From: Edward Shryane via db-wg To: db-wg Cc: Piotr Strzyzewski ; l...@merit.edu; Job Snijders Sent: Tuesday, 24 July 2018, 12:18 Subject: Re: [db-wg] Implementation plan and dates for NWI5 - Out-of-region ROUTE(6)

Re: [db-wg] Source GRS vs RIPE

Hi Guys I am sure everyone will disagree with me, but this shows (to me) why it would be better to have one authoritative, accurate, trusted, distributed IRR managed by the 5 RIRs than many independent/commercial IRRs with non authenticated data. cheersdenisco-chair DB-WG From: Aftab

Re: [db-wg] Whois Update Server Migration

thanks Ed From: Edward Shryane To: denis walker Cc: Database WG Sent: Tuesday, 20 March 2018, 21:23 Subject: Re: [db-wg] Whois Update Server Migration Hi Denis, we plan to switch from the current Whois update server, to a

Re: [db-wg] remove bogon prefixes in the RIPE IRR NON-AUTH DB?

HI Ed Are there any ROUTE(6) objects with source: RIPE for bogon prefixes or is this one that Job mentioned with source RIPE-NONAUTH the only one in the database (with either source)? cheersdenisco-chair DB-WG From: Edward Shryane via db-wg To: Job Snijders Cc: db-wg Sent: Monday,

Re: [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects

Hi Job Just a couple of points. First is a technical issue with your proposal. In your Rationale you mention ¨creating out of region inetnums¨. It wasn't possible to create such objects. Only out of region aut-nums and route(6)s. You talk about cleaning up garbage in the RIPE-NONAUTH IRR. The

Re: [db-wg] remove bogon prefixes in the RIPE IRR NON-AUTH DB?

Thanks Ed. Perhaps a way forward then would be if you can ask Customer Services to contact the maintainers of this object and ask them to delete it, explaining why. It's always better if people clean up their own objects. cheersdenisco-chair DB-WG From: Edward Shryane To: denis walker

Re: [db-wg] PERSON objects in the RIPE Database

Hi Nick, Athina Perhaps the RIPE NCC legal team can give us some advice on this issue. In your presentation at RIPE 76 you said the justification for personal data in the RIPE Database was for contacting people about operational issues. If many of these 2 million people whose personal data is

Re: [db-wg] PERSON objects in the RIPE Database

From: Nick Hilliard via db-wg To: denis walker Cc: DB-WG Sent: Tuesday, 25 September 2018, 23:46 Subject: Re: [db-wg] PERSON objects in the RIPE Database denis walker via db-wg wrote on 20/09/2018 13:04: > This does raise a number of questions: the requirement for admin-c and

Re: [db-wg] Idea: magic mntner for all LIR contacts

I suspect the RIPE NCC can't give an answer in 5 minutes as to how long it would take to implement such a feature. So I think it is better to decide what people really want and then ask the NCC to estimate the work required as part of the NWI process. Given that you are all managing with the

Re: [db-wg] Sideline --template [was: Certain sponsored? ASNs without sponsoring-org]

Hi Wilfried These are the "org-type:" values according to the -v output org-type    Specifies the type of the organisation. org-type can have one of these values: o 'IANA' for Internet Assigned Numbers Authority o 'RIR' for Regional Internet Registries o 'NIR' for

Re: [db-wg] Idea: magic mntner for all LIR contacts

So maybe we are thinking of something like this: A MNTNER object that is created by the RIPE NCC and perhaps jointly maintained by the RIPE NCC and the LIR, that is created when a new LIR is established and includes the SSO auth of all listed (non-billing) LIR contacts. Each time a (non-billing)

[db-wg] NWI-8 LIR´s SSO Authentication Groups

Hi Tore Sorry for the delay. This was on my ToDo list but just hadn´t got to that point yet. The DB-WG chairs agree this is suitable to be added to the list of Numbered Work Items as ¨NWI-8 LIR´s SSO Authentication Groups¨ I think the discussion we had in January, ending with Nick´s summary,

Re: [db-wg] Proposal for restricting authentication concerning use of revoked and expired GPG ID's in key-cert objects

Hi Ed Thanks for following up on this. Just one question, have you taken into account time zones? If an update is signed now in Dubai it is 19:51. If the update is processed on Amsterdam time, it is 16:51. Will this update fail because it is 3 hours in the future? cheersdenisco-chair DB-WG

[db-wg] NWI reviews: NWI-3, NWI-6 consensus

Colleagues The author of 'NWI-6 Applicable data model not clear from contextless objects' has agreed that it can be cancelled. No one disagreed with that so the chairs agree to cancel NWI-6. It was suggested that 'NWI-3 Afrinic IRR Homing' was partly superseded by 'NWI-5 Out of region ROUTE(6) /

Re: [db-wg] Fwd: proposal: new attribute 'geofeed:

Hi guys GDPR applies to the entire RIPE Database because the RIPE NCC, who operate the database, is based in the EU. It does not matter where the data subject or data maintainer is based. cheers denis co-chair DB-WG On Mon, 11 Jan 2021 at 13:43, Nick Hilliard via db-wg wrote: > > Randy Bush

Re: [db-wg] Fwd: proposal: new attribute 'geofeed:

Hi Randy On Mon, 11 Jan 2021 at 19:07, Randy Bush wrote: > > > Hi guys > > ahem > > > GDPR applies to the entire RIPE Database because the RIPE NCC, who > > operate the database, is based in the EU. > > appreciate the legal opinion. how come person: objects are allowed? > I asked this very

Re: [db-wg] Fwd: proposal: new attribute 'geofeed:

HI Hank, colleagues Whilst I can't answer your basic question, I could say that if the IETF approves a change to RPSL, with the RIPE Database data model based on RPSL, in principle we should implement the RPSL change. Perhaps another question, to the RIPE NCC legal team, if I have a fixed IP

Re: [db-wg] Historical records... what is and isn't available

Hi Ronald True...historical versions of these objects are not available in any form for privacy and security reasons. Personally I don't think MNTNER objects should be visible at all to the public. I don't know of any other service on the internet where details of how you secure your data are

Re: [db-wg] Historical records... what is and isn't available

HI Shane On Fri, 4 Dec 2020 at 09:52, Shane Kerr via db-wg wrote: > > Ronald, > > On 03/12/2020 22.57, Ronald F. Guilmette via db-wg wrote: > > > > Let's cut to the chase here. I'll start the ball rolling, and Denis can > > support or not support the following propoal as he sees fit... > > > >

Re: [db-wg] Historical records... what is and isn't available

HI Shane On Fri, 4 Dec 2020 at 09:39, Shane Kerr via db-wg wrote: > > Denis, > > On 02/12/2020 23.39, denis walker via db-wg wrote: > > Personally I don't think MNTNER objects should be visible at all to > > the public. I don't know of any other service on the internet

[db-wg] NWI-?? Rationalising contact references

Colleagues I would like to propose a new NWI about contact references in the RIPE Database. Something that has needed to be cleaned up for a very long time. I have written a draft Problem Statement and Solution Definition below. Your comments are appreciated. cheers denis co-chair DB-WG

Re: [db-wg] Problem definition for new NWI (12?) - NRTM service

Hi Stavros Thanks for starting this off with a draft problem statement. As there has been a lot of interest in this recently we will initiate "NWI-12 NRTMv4". Ed can you set that up on the NWI web page? We would welcome comments from other community members on this problem statement. cheers

[db-wg] Fwd: Multi tenancy in a LIR?

Hi Hank Your scenario is not clear. When you say "each has their own resources", how did they get those resources? Were they separate LIRs that have received allocations, have there been mergers, were they all allocated to the parent organisation's LIR and distributed to sub organisations? Or do

Re: [db-wg] Fwd: Multi tenancy in a LIR?

bility for their use. They also cut themselves off from using the reclaim functionality as that relies on the "mnt-lower:" in the resource object. cheers denis co-chair DB-WG On Fri, 20 Nov 2020 at 06:27, Hank Nussbacher via db-wg wrote: > > On 19/11/2020 21:41, denis walker via db-wg

Re: [db-wg] Fwd: Multi tenancy in a LIR?

g the reclaim functionality as that relies > on the "mnt-lower:" in the resource object. > > cheers > denis > co-chair DB-WG > > On Fri, 20 Nov 2020 at 06:27, Hank Nussbacher via db-wg > wrote: > > > > On 19/11/2020 21:41, denis walker via db-wg w

Re: [db-wg] Fwd: Multi tenancy in a LIR?

retains any liability for their use. They also > > cut themselves off from using the reclaim functionality as that relies > > on the "mnt-lower:" in the resource object. > > > > cheers > > denis > > co-chair DB-WG > > > > On Fri, 20 Nov

Re: [db-wg] Interest to continue NWI-9

Hi All As Job said it is at an early discussion stage. If we do this using the NWI mechanism then the Problem statement and then a Solution definition will be discussed on the mailing list by anyone with an interest in this issue. Someone has to put forward a first draft for discussion. Once

Re: [db-wg] Interest to continue NWI-9

Hi Job I am certainly available for that. Would you be available then Ed to offer any input from the RIPE NCC? cheers denis co-chair DB-WG On Thu, 29 Oct 2020 at 20:38, Job Snijders wrote: > > On Thu, Oct 29, 2020 at 06:30:28PM +0100, denis walker wrote: > > I would suggest we create NWI-12 to

Re: [db-wg] Interest to continue NWI-9

here in the internet-stack this protocol belongs, but that it is an > improvement over version 3. > > NRTM v4 can easily be something that is finished and deployed in 2021. > What needs to be done is fairly straight-forward, and lots of existing > tools can be used to make the job easier (

Re: [db-wg] Interest to continue NWI-9

Hi Stavros Thanks for the comment. I have let Ed know about your interest. cheers denis co-chair DB-WG On Thu, 29 Oct 2020 at 17:11, Stavros Konstantaras via db-wg wrote: > > Hi WG chairs, > > > I would like to declare that from our side we are still interested to team up > with Ed and RIPE

[db-wg] Fwd: proposal: new attribute 'geofeed:'

Hi Ed Can you do a quick count on INETNUM and INET6NUM objects and see how many currently have a "remarks: Geofeed" attribute and if any have more than one. An interesting question Robert. Perhaps an even more interesting one is, if we implement the "geofeed:" attribute, should we allow anyone

Re: [db-wg] Org-types

Hi Cynthia Capitalisation makes no difference, so they are all 'OtHeR'. RIR and IANA are probably self explanatory. WHITEPAGES should be (or should soon be made) redundant. It was an idea from 10+ years ago to allow 'well known figures' from the IT, Internet, network, operators communities to be

Re: [db-wg] proposal: new attribute 'geofeed:'

Hi Job So if we were to create a new NWI with your suggested Problem statement: Associating an approximate physical location with an IP address has proven to be a challenge to solve within the current constraints of the RIPE database. Over the years the community has chosen to

Re: [db-wg] Fwd: proposal: new attribute 'geofeed:

HI Maria Thanks for the preliminary analysis. I do have a couple of questions below... On Wed, 27 Jan 2021 at 09:21, Maria Stafyla wrote: > > Hi Denis, all, > > Thank you for your patience in this matter. > > We looked into this and the answer varies depending on the situation. > > Allocations

Re: [db-wg] AFRINIC Audit report

Hi All Your post, Ronald, also has nothing to do with the RIPE Database. Please contact the webmas...@ripe.net if you have some issues with the web site. There is no need for either of you to reply to this email. Let's close this discussion on this mailing list. cheers denis co-chair DB-WG On

Re: [db-wg] Deprecation of whitepages

You are right Randy, sometimes you are so subtle I can't figure out which side of the argument you are supporting. Are you saying you think it should be possible to protect contact data from deletion when it is not referenced by any resource objects? So it is there for some reason other than the

Re: [db-wg] AFRINIC Audit report

HI Elad As co-chair of the DB-WG I would like to point out that what you are talking about.has nothing to do with the RIPE Database. Please don't use this mailing list for these discussions. cheers denis co-chair DB-WG On Fri, 29 Jan 2021 at 20:30, Elad Cohen via db-wg wrote: > > Yes Ronald,

Re: [db-wg] Deprecation of whitepages

Hi Ed Well maybe we should start by discussing this exclusion list. It's the first I have heard of it. If such a list exists (as it does) then the reasons for exclusion should be defined. Maybe exclusion is also the wrong term, protected is perhaps more appropriate. Who decides if an object

Re: [db-wg] The DBTF needs your feedback!

Hi Ronald Although I have nothing to do with the questionnaire, I am curious what information you believe 'someone' wants to hide, or maybe you think has already been hidden, that has never before been hidden in this traditionally open whois? btw nothing is decided by voting. Like other working

Re: [db-wg] The DBTF needs your feedback!

HI Ronald As Shane pointed out, the task force will make recommendations. Nothing will change without discussion and consensus or through legal necessity. One of the concerns with the RIPE Database is that it contains far too much 'personal' data. 'Personal' means 'who' the data relates to, not

[db-wg] Deprecation of whitepages

Colleagues Way back in 2008 it was suggested that the RIPE Database could be used for linking people well known within the network operating industry. The concept of 'whitepages' was introduced. This was an ORGANISATION object (ORG-PAGE1-RIPE) with 'org-type: WHITEPAGES' that could be referenced

Re: [db-wg] Deprecation of whitepages

Hi Will I wasn't aware that the RIPE Atlas system/service had any reliance on objects in the RIPE Database. Maybe Robert can elaborate more on this? There are only 4 PERSON objects in the RIPE Database that reference the Whitepages ORGANISATION object. None of these make any reference in remarks

Re: [db-wg] "status:" attribute values in the RIPE database

Hi Ronald It says in the documentation that you cannot split the primary key attribute value over multiple lines. To make sure that is still the case, I just tried to create this object in the test database: INETNUM: 10.0.0.0 - 10.0.0.255 NETNAME: fred

Re: [db-wg] Issue creating new AS-SET

HI Ed Why didn't this report a syntax error in the as-set name rather than a hierarchical part already exists? cheers denis co-chair DB-WG On Wed, 9 Jun 2021 at 16:06, Edward Shryane via db-wg wrote: > > Hi Job, Denis, > > On 9 Jun 2021, at 15:55, Job Snijders via db-wg wrote: > > On Wed, Jun

Re: [db-wg] Issue creating new AS-SET

OK I misread your first email :) cheers denis co-chair DB-WG On Wed, 9 Jun 2021 at 19:20, Denis Fondras via db-wg wrote: > > Le Wed, Jun 09, 2021 at 06:56:18PM +0200, denis walker via db-wg a écrit : > > HI Ed > > > > Why didn't this report a syntax error in the

Re: [db-wg] NWI-4 - role of status: field in multivalued status context - reprise

Hi guys Just out of interest why do people think having a dual attribute primary key pair is better than allowing multiple "status:" attributes in very specific cases? Multiple status attributes is probably far simpler to implement and maybe easier to parse. Changing the pkey affects the way

[db-wg] RIPE Database Task Force minutes

Colleagues The Task Force has published minutes of it's most recent meeting on their mailing list. There are also some interesting comments and observations from Daniel. You can find them here https://www.ripe.net/ripe/mail/archives/ripe-db-requirements-tf/2021-May/date.html cheers denis

[db-wg] What is the RIPE Database in 2021?

Colleagues There was an interesting presentation in the Address Policy session at RIPE 82 this morning by Remco. He raised a number of issues about what exactly is the RIPE Database, what does it do and who does it do it for? The history of the RIPE Database is quite well known (within the

Re: [db-wg] Cleanup of route(6) objects in the RIPE NONAUTH database using unregistered space

ill keep the DB-WG informed. > > Regards > Ed Shryane > RIPE NCC > > On 25 Apr 2021, at 13:03, Cynthia Revström wrote: > > imo an NWI seems unnecessary unless we want it for purposes of referencing > back to in the future. > > -Cynthia > > On

Re: [db-wg] Cleanup of route(6) objects in the RIPE NONAUTH database using unregistered space

ards, > > Arash > > On Fri, 7 May 2021, 22:56 denis walker via db-wg, wrote: >> >> HI Ed >> >> As no one has objected I think we can assume you can go ahead with this plan. >> >> cheers >> denis >> co-chair DB-WG >> >> On Fri, 7

Re: [db-wg] Route objects for space administered by other RIRs

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

Re: [db-wg] country field in ORG objects

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

Re: [db-wg] New NWI for geofeed?

Hi Massimo Does this mean geofeed values are only meaningful when used as a collection and not individually? Take this example with a /16 and a more specific /24 both having a geofeed attribute. If I query for an address within the /16 but outside of the more specific /24 I will get the INETNUM

Re: [db-wg] Restricting WHOIS searches to type: netname

Hi Ronald The query option '--types' or '-T' refers to object types. The list you gave is the list of all object types. The 'netname' is an attribute in the INET(6)NUM object types. It is not, itself, an object type. It is possible to search on netname using the full text search

Re: [db-wg] created: field value

Hi Ronald I don't have answers to all your questions but let me throw a few ideas out. First of all the "created:" attribute reflects the date the object was created in the RIPE Database. This may not be the same as 'registered' date. For legacy space there is no concept of allocations and

[db-wg] DBTF final draft postponed

Colleagues Following the recent Bof the DBTF has postponed publication of it's final draft requirements document. You can see details here https://www.ripe.net/ripe/mail/archives/ripe-list/2021-May/002231.html cheers denis co-chair DB-WG

Re: [db-wg] BOGON => 103.86.68.0/22

Hi Ronald It was agreed that the RIPE BNCC can go ahead with this regular cleanup without an NWI https://www.ripe.net/ripe/mail/archives/db-wg/2021-May/006952.html so it is in progress already. cheers denis co-chair DB-WG On Thu, 27 May 2021 at 18:46, Ronald F. Guilmette via db-wg wrote: > >

Re: [db-wg] Further cleanup (was: RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*)

Hi Niall On Fri, 2 Jul 2021 at 17:21, Niall O'Reilly via db-wg wrote: > > George, Ed, everybody, > > This seems as good a moment as any to wave the POLA, transparency, > and due-process banners. > > On 1 Jul 2021, at 23:46, George Michaelson via db-wg wrote: > > > I don't think this problem has

Re: [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Hi Ed Thanks for the data. This is quite bad. As recently as March this year someone created a ROUTE object referencing an unregistered ASN: 193.110.94.0/24AS16712,20210318 This is not 'accurate data' that resource holders are contracted to enter into the RIPE Database. It could simply be a typo

Re: [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Hi Job I admit to being a 'not well informed' routing person but let me try to interpret what you have just said. The origin ASN may or may not be registered when the ROUTE object is created. The origin ASN can be returned (AUT-NUM deleted) after the ROUTE object is created The ROUTE object may

[db-wg] consensus on AS23456

Colleagues Whilst part of the discussion continues, there does seem to be a consensus on adding AS23456 to the reserved list maintained by the RIPE NCC. This would prevent anyone creating a ROUTE(6) object with AS23456 as the origin. The chairs also recognise the consensus to not delete or

Re: [db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Hi Guys To create a ROUTE(6) object in the RIPE Database, the referenced origin AUT-NUM object doesn't need to exist in the RIPE Database. But should the ASN have been allocated by one of the RIRs? So perhaps the first questions to answer aren't about whether or not we should delete these

Re: [db-wg] Cleanup of route(6) objects in the RIPE NONAUTH database using unregistered space

-chair DB-WG On Sun, 25 Apr 2021 at 13:03, Cynthia Revström wrote: > > imo an NWI seems unnecessary unless we want it for purposes of referencing > back to in the future. > > -Cynthia > > On Wed, Apr 21, 2021, 04:02 denis walker via db-wg wrote: >> >> Colleagues

[db-wg] input from community???

Colleagues Over recent months several important issues have been raised on this mailing list. We have seen comments from maybe 1 or 2 people to some of them. No comments at all to others. We appreciate that covid issues affect many businesses in many ways. So perhaps some of you have far more

[db-wg] Fwd: Reminder, join us today for the RIPE Database Requirements Task Force BoF

Colleagues The current draft document from the DB Task Force can be found here https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/the-ripe-database-requirements-task-force-draft-document.pdf You can discuss any issue in the bof but the TF has asked for specific feedback on three

[db-wg] Comments on RIPE Database requirements progress

Colleagues For the benefit of those who don't often check the mail archives of the RIPE Database Task Force there have been 4 meetings in February and March with 3 sets of minutes published so far on their mail archive which can be found here:

  1   2   3   >