September 2017 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

violation of DB T&C by DB-WG co-chair, is it acceptable?
by Elvis Daniel Velea 14 Oct '17

14 Oct '17

Dear RIPE NCC, can you please present a report showing how many LIRs have reported RIPE DB T&C violations? How many were resolved and what was the outcome? - Specifically, how many times has the RIPE NCC taken any action other than a warning message. Dear DB-WG, should we accept that one of the chairs of this WG is purposely violating the T&Cs of the RIPE DB? Please see below one of the e-mails received from David, the RIPE DB-WG co-chair, by a RIPE NCC member named /<company>/. (I'd like to mention that /<company>/ has never had a business relationship with Larus Cloud Service Limited, has never subscribed to any mailing list and has never requested the message below - which I find to be spam as it was never solicited). regards, elvis From: Larus Team <vendors(a)laruscloudservice.net> Subject: Unused IPv4 space of /<company>/ Dear Colleagues, We are contacting you regarding potential unused IPv4 address currently registered to your organisation /<company>/. Organisations like yours have in the past received address IPv4 space, it sometimes remains unused after changes to networks. Based on the available information it appears that your organisation is currently holding IPv4 space that appears unused or underutilised. We would like to offer you the possibility to capitalise on these addresses, we can assist you in either finding organisation to permanently transfer (sell) towards, or assist you in finding and forging long term relationships with some of our clients by leasing the unused space to them, generating a long-term income. We are a company based in Hong Kong, our CEO Heng Lu, has over ten years’ experience in managing Internet resources across the globe. Our IP manager David Hilario previously worked for the RIPE NCC one of the five RIR and as such has an intricate knowledge of the policies in the RIR policies especially when it comes to transfers and leasing the address space. We have clients lined up waiting for permanent transfers or long-term lease, so we can fulfil any of your requirements. We offer clients with available IP space a 3 months exclusivity contract. based on your requirements, we will match our waiting list clients with your criteria so that your IP space can be capitalise as soon as possible at the best possible rate. Please note that if you are leasing out your address space, we will offer it on a minimum of yearly basis with advance payment from our clients. Please find attached to this email our NDA to be filled in from your side and returned to us before we can proceed any further in our cooperation in regard to these transfers or long-term lease. We can lease and sell IP space to and from ARIN (North America) APNIC (Asia Pacific) and RIPE NCC (Europe, Middle East and parts of Central Asia). Kind Regards, David Hilario IP Manager Larus Cloud Service Limited p: +852 29888918 m: +359 89 764 1784 f: +852 29888068 a: Flat B5, 11/F, TML Tower, No.3 Hoi Shing Road, Tsuen Wan, HKSAR w: laruscloudservice.net e: d.hilario(a)outsideheaven.com Larus Team www.laruscloudservice.net <http://sctrack.mail.laruscloudservice.net/track/click/eyJ1c2VyX2lkIjogNDE4M…>

4 3

Fw: [db-wg] Fw: NWI-7: abuse-c implementation plan modification
by denis walker 03 Oct '17

03 Oct '17

Hi Tim, colleagues No one has expressed any serious concerns over this small change. I think we can safely go ahead and only send the one email notification in these cases when you change the objects. cheersdenisco-chair DB-WG ----- Forwarded Message ----- From: denis walker via db-wg <db-wg(a)ripe.net> To: Database WG <db-wg(a)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 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. Otherwise we can give Tim the go ahead to this modification to the implementation plan. cheersdenisco-chair DB-WG From: Tim Bruijnzeels via db-wg <db-wg(a)ripe.net> To: "db-wg(a)ripe.net" <db-wg(a)ripe.net> Sent: Wednesday, 30 August 2017, 21:32 Subject: Re: [db-wg] NWI-7: abuse-c implementation plan Dear working group, We have a proposed timeline for the implementation. Let me quote the proposal sent out on 28 June here, and comment in-line: > 3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases) > > In these cases we propose to send a warning email to the holders of these objects with the following main message: > > “The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects." > > And then 4 weeks later we will preform the clean-up and refer back to this communication. On further reflection we would prefer to alter the plan, and just a single clean-up of these objects on Monday 30 October as well. This way the clean-up process will be consistent across all object types. Furthermore, there is no action to be taken on these objects and “abuse-mailbox:” on these objects is ignored in the Abuse Finder. In short there does not seem to be a strong motivation for bothering the holders of these objects twice.

2 1

Re: [db-wg] Fw: NWI-7: abuse-c implementation plan modification
by Peter Hessler 27 Sep '17

27 Sep '17

My traditional response to any modification of the database: As long as a notification that the objects were modified is sent, I have no objections. On 2017 Sep 27 (Wed) at 09:56:09 +0000 (+0000), denis walker via db-wg wrote: :Date: Wed, 27 Sep 2017 09:44:42 +0000 (UTC) :From: denis walker <ripedenis(a)yahoo.co.uk> :To: Database WG <db-wg(a)ripe.net> :Subject: Fw: [db-wg] NWI-7: abuse-c implementation plan modification : :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. Otherwise we can give Tim the go ahead to this modification to the implementation plan. :cheersdenisco-chair DB-WG : : From: Tim Bruijnzeels via db-wg <db-wg(a)ripe.net> : To: "db-wg(a)ripe.net" <db-wg(a)ripe.net> : Sent: Wednesday, 30 August 2017, 21:32 : Subject: Re: [db-wg] NWI-7: abuse-c implementation plan : :Dear working group, : :We have a proposed timeline for the implementation. Let me quote the proposal sent out on 28 June here, and comment in-line: : : :> 3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases) :> :> In these cases we propose to send a warning email to the holders of these objects with the following main message: :> :> “The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects." :> :> And then 4 weeks later we will preform the clean-up and refer back to this communication. : :On further reflection we would prefer to alter the plan, and just a single clean-up of these objects on Monday 30 October as well. This way the clean-up process will be consistent across all object types. Furthermore, there is no action to be taken on these objects and “abuse-mailbox:” on these objects is ignored in the Abuse Finder. In short there does not seem to be a strong motivation for bothering the holders of these objects twice. :

1 0

Fw: [db-wg] NWI-7: abuse-c implementation plan modification
by denis walker 27 Sep '17

27 Sep '17

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. Otherwise we can give Tim the go ahead to this modification to the implementation plan. cheersdenisco-chair DB-WG From: Tim Bruijnzeels via db-wg <db-wg(a)ripe.net> To: "db-wg(a)ripe.net" <db-wg(a)ripe.net> Sent: Wednesday, 30 August 2017, 21:32 Subject: Re: [db-wg] NWI-7: abuse-c implementation plan Dear working group, We have a proposed timeline for the implementation. Let me quote the proposal sent out on 28 June here, and comment in-line: > 3) Clean up of “abuse-mailbox:” on PERSON (89k cases), MNTNER (2500 cases) and IRT (238 cases) > > In these cases we propose to send a warning email to the holders of these objects with the following main message: > > “The “abuse-mailbox:” is deprecated on these object and will be removed in 4 weeks, if you want to set up abuse contact information on your resource objects you can do so by having a default “abuse-c:” on your ORGANISATION referenced by your resource objects, or possibly overriding that default with a specific “abuse-c:” reference on applicable resource objects." > > And then 4 weeks later we will preform the clean-up and refer back to this communication. On further reflection we would prefer to alter the plan, and just a single clean-up of these objects on Monday 30 October as well. This way the clean-up process will be consistent across all object types. Furthermore, there is no action to be taken on these objects and “abuse-mailbox:” on these objects is ignored in the Abuse Finder. In short there does not seem to be a strong motivation for bothering the holders of these objects twice.

1 0

Whois release 1.90 in Release Candidate environment, production release planned for 16 October
by Tim Bruijnzeels 27 Sep '17

27 Sep '17

Dear working group, RIPE Database Release 1.90 was deployed to the Release Candidate Environment, last week on 22 September 2017. If no issues are raised, we plan to deploy this version to production on Monday 16 October 2017 Release 1.90 introduces the following main features in support of NWI-7 (abuse-c implementation): = Allow adding an "abuse-c:" attribute to INET(6)NUM and AUT-NUM objects = Disallow adding "abuse-c:" to object types other than ROLE, INET(6)NUM and AUT-NUM Release 1.90 contains a number of small improvements: = Make org-name validation case-sensitive (no longer consider case changes a no-op) = Support to remove generated AUT-NUM "remarks:" regarding legacy status The complete list of other minor issues solved by this release can be found here: https://github.com/RIPE-NCC/whois/blob/master/changes.txt Please let us know if you see any issues with this release in the RC environment. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering and Senior Technical Officer RIPE NCC

1 0

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by Nick Hilliard 27 Sep '17

27 Sep '17

Clement Cavadore via db-wg wrote: > While there are many examples where spammers uses RIPE DB, more > specifically when it comes to "IPv4 reselling market", I think that it > is unacceptable to tolerate such a behavior from a chair (and/or from > anyone from his company). A (co-)chair should fight against such > practices, especially from his or her co-workers. It would be good if David took the opportunity to explain what he did and how / whether it's compatible with being co-chair of DBWG. Separately, if people have received spam from Larus, they should complain to the RIPE NCC. Nick

2 2

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by ripedenis＠yahoo.co.uk 14 Sep '17

14 Sep '17

Hi Nick Let's not single anyone out here, perhaps people should report spam to the RIPE NCC from 'any' broker offering deals on address space. Cheers Denis Co-chair DB-WG -------------------------------------------- On Thu, 14/9/17, Nick Hilliard via db-wg <db-wg(a)ripe.net> wrote: Separately, if people have received spam from Larus, they should complain to the RIPE NCC. Nick -----Inline Attachment Follows-----

1 0

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by Henriette Van Ingen 14 Sep '17

14 Sep '17

Dear Elvis, You asked us the following question: “can you please present a report showing how many LIRs have reported RIPE DB T&C violations? How many were resolved and what was the outcome? - Specifically, how many times has the RIPE NCC taken any action other than a warning message.” Since September 2016, the RIPE NCC has received ten reports regarding the abuse of contact data in the RIPE Database, thereby violating the RIPE Database Terms and Conditions. - We sent warning emails to the parties that were reported. - We sent two of these parties a second warning. - One party continued to violate the RIPE Database Terms and Conditions. We ultimately terminated the Broker Agreement between this party and the RIPE NCC on the grounds of multiple violations of the RIPE Database Terms and Conditions. Regards, Henriette van Ingen Assistant Manager Customer Services RIPE NCC > On 12 Sep 2017, at 09:42, Elvis Daniel Velea via db-wg <db-wg(a)ripe.net> wrote: > > > From: Elvis Daniel Velea <elvis(a)velea.eu> > Subject: violation of DB T&C by DB-WG co-chair, is it acceptable? > Date: 12 September 2017 at 00:33:12 GMT+2 > To: db-wg(a)ripe.net > Reply-To: elvis(a)velea.eu > > > Dear RIPE NCC, > > can you please present a report showing how many LIRs have reported RIPE DB T&C violations? How many were resolved and what was the outcome? > > - Specifically, how many times has the RIPE NCC taken any action other than a warning message. > Dear DB-WG, should we accept that one of the chairs of this WG is purposely violating the T&Cs of the RIPE DB? > > Please see below one of the e-mails received from David, the RIPE DB-WG co-chair, by a RIPE NCC member named <company>. > (I'd like to mention that <company> has never had a business relationship with Larus Cloud Service Limited, has never subscribed to any mailing list and has never requested the message below - which I find to be spam as it was never solicited). > > regards, > > elvis > From: Larus Team <vendors(a)laruscloudservice.net> <mailto:vendors@laruscloudservice.net> > Subject: Unused IPv4 space of <company> > Dear Colleagues, > > We are contacting you regarding potential unused IPv4 address currently registered to your organisation <company>. > > Organisations like yours have in the past received address IPv4 space, it sometimes remains unused after changes to networks. Based on the available information it appears that your organisation is currently holding IPv4 space that appears unused or underutilised. > > We would like to offer you the possibility to capitalise on these addresses, we can assist you in either finding organisation to permanently transfer (sell) towards, or assist you in finding and forging long term relationships with some of our clients by leasing the unused space to them, generating a long-term income. We are a company based in Hong Kong, our CEO Heng Lu, has over ten years’ experience in managing Internet resources across the globe. Our IP manager David Hilario previously worked for the RIPE NCC one of the five RIR and as such has an intricate knowledge of the policies in the RIR policies especially when it comes to transfers and leasing the address space. > > We have clients lined up waiting for permanent transfers or long-term lease, so we can fulfil any of your requirements. > > We offer clients with available IP space a 3 months exclusivity contract. based on your requirements, we will match our waiting list clients with your criteria so that your IP space can be capitalise as soon as possible at the best possible rate. Please note that if you are leasing out your address space, we will offer it on a minimum of yearly basis with advance payment from our clients. > > Please find attached to this email our NDA to be filled in from your side and returned to us before we can proceed any further in our cooperation in regard to these transfers or long-term lease. We can lease and sell IP space to and from ARIN (North America) APNIC (Asia Pacific) and RIPE NCC (Europe, Middle East and parts of Central Asia). > > Kind Regards, > David Hilario > > IP Manager > Larus Cloud Service Limited > > p: +852 29888918 m: +359 89 764 1784 > f: +852 29888068 > a: Flat B5, 11/F, TML Tower, No.3 Hoi Shing Road, Tsuen Wan, HKSAR > w: laruscloudservice.net > e: d.hilario(a)outsideheaven.com <mailto:d.hilario@outsideheaven.com> > > Larus Team > www.laruscloudservice.net <http://sctrack.mail.laruscloudservice.net/track/click/eyJ1c2VyX2lkIjogNDE4M…> >

1 0

Re: [db-wg] violation of DB T&C by DB-WG co-chair, is it acceptable?
by Clement Cavadore 14 Sep '17

14 Sep '17

Dear all, On Thu, 2017-09-14 at 04:08 +0200, Elvis Daniel Velea via db-wg wrote: > The questions stand. > I am curious to see what the rest of the wg members think. While there are many examples where spammers uses RIPE DB, more specifically when it comes to "IPv4 reselling market", I think that it is unacceptable to tolerate such a behavior from a chair (and/or from anyone from his company). A (co-)chair should fight against such practices, especially from his or her co-workers. DB is not meant for a marketing and advertising usage. And if any company is caught the hand in the honey pot, it should be publicly shamed/unsubscribed/banned from reading DB contact infos/whatever. -- Clément Cavadore

1 0