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/members-discuss@ripe.net/
[members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers
- Previous message (by thread): [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers
- Next message (by thread): [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nipuna Ruhunage
n.ruhunage at ism-apac.com
Thu Nov 28 10:03:16 CET 2019
Aggerd Stuart, With the rapid growth of internet devices, it’s senseless we fighting over IPV4. Nipuna Ruhunage | System Engineer Address: 3rd Floor, Alnitak Building, No. 752, Dr. Danister De Silva Mw, Colombo 09. Email: n.ruhunage at ism-apac.com<mailto:n.ruhunage at ism-apac.com> Telephone: +94 11 511 5588 Mobile: +94 76 8386848 Website: www.ism-apac.com<https://www.ism-apac.com> [cid:image001.jpg at 01D5A5F8.C1E5C130] Follow us on [cid:image002.png at 01D5A5F8.C1E5C130]<https://www.facebook.com/ISMAPAC/> [cid:image003.png at 01D5A5F8.C1E5C130]<https://www.instagram.com/ism_apac/> [cid:image004.png at 01D5A5F8.C1E5C130]<https://www.linkedin.com/company/ism-apac-pvt-ltd/> [cid:image005.png at 01D5A5F8.C1E5C130]<https://www.youtube.com/channel/UCMiAQiEm3cXMNk_SdnLGZTQ> From: members-discuss <members-discuss-bounces at ripe.net> On Behalf Of Stuart Gilbertson | Consider IT Limited Sent: Thursday, November 28, 2019 2:22 PM To: Dave Benwell <dave at it-communicationsltd.co.uk> Cc: members-discuss at ripe.net Subject: Re: [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers Perhaps we should be focussing our efforts on IPv6? All the best, Stuart Stuart Gilbertson Consider IT Limited Superior IT Support www.considerit.co.uk<http://www.considerit.co.uk/> 0131 510 0110 Please Note: This e-mail and any files that may be attached to it are for the named person's use only. It may contain confidential, proprietary or legally privileged information and is strictly confidential. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender by replying to this message. In the event that you are not the intended recipient, you must not directly or indirectly copy, print, or otherwise disseminate this message in full or in part. Consider IT Ltd takes reasonable steps to ensure that our e-mails are virus-free, and in any event, accept no liability, either for any alterations made to this e-mail by third parties, or any viruses that it may contain, howsoever arising. Consider IT Ltd reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. On Thu, 28 Nov 2019 at 08:47, Dave Benwell via members-discuss <members-discuss at ripe.net<mailto:members-discuss at ripe.net>> wrote: My stance on this is below. Why should a private company be allowed to make profit on public IP Space. Even the UK Government sells its IP Space to private companies for Profit (Public selling Public IP Space to private companies is a JOKE Remember, IP Space is not owned by the LIR but allocated by Ripe. So how and why is it allowed by a LIR to sell something that is not owned by them? If a LIR no longer needs IP Space then return it to RIPE. This is why IPV4 ran out due to RIPEs poor management policy. IF I could vote no confidence in the ripe board for allowing such business to take place, I would vote now. I'll go rent a car park space shall I, be allocated a space and then go sell it for 500x the rent price. Members need to step up here and instead of saying this has been discussed before, get on and make this change or the same will happen with IPv6 in years to come. -----Original Message----- From: members-discuss [mailto:members-discuss-bounces at ripe.net<mailto:members-discuss-bounces at ripe.net>] On Behalf Of Carlos Friaças via members-discuss Sent: 27 November 2019 23:44 To: Patrick Velder <lists at velder.li<mailto:lists at velder.li>> Cc: members-discuss at ripe.net<mailto:members-discuss at ripe.net> Subject: Re: [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers Hi, I don't understand RIPE NCC's actions as "support", instead i see it as simple "acknowledgement". And in case you haven't noticed, "They" are also RIPE NCC members, some even several times... :-) Cheers, Carlos On Wed, 27 Nov 2019, Patrick Velder wrote: > Hi, > > I see no reasons why there should be "RIPE certified brokers" or similar. > They are making profit with "selling" public resources. That's a > business which should not be supported by RIPE. > > Best regards > > On 27.11.19 14:45, Maxemilian Hilbrand wrote: >> Me too. >> >> I got some similar emails within the last few weeks, and I have no >> idea if this is fraud or not. >> >> To avoid fraud, it might be a good idea to have an official auction >> of IP addresses on the RIPE website as trusted source. >> >> Max >> >> >> Maxemilian Hilbrand (Software & Systeme) >> >> CH: +41 71 511 722 0 >> AT (mobile): +43 660 703 92 54 >> maxemilian.hilbrand at isicore.com<mailto:maxemilian.hilbrand at isicore.com> >> >> isicore AG ? Unterlettenstrasse 14 ? CH-9443 Widnau Gerichtsstandort >> CH-9450 Altstätten, UID CHE-110.354.078 >> Verwaltungsratspräsident: Maxemilian Hilbrand >> >> www.isicore.com<http://www.isicore.com> I info at isicore.com<mailto:info at isicore.com> >> >> -----Ursprüngliche Nachricht----- >> Von: members-discuss <members-discuss-bounces at ripe.net<mailto:members-discuss-bounces at ripe.net>> Im Auftrag >> von Netmaster >> Gesendet: Mittwoch, 27. November 2019 14:03 >> An: members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> Betreff: Re: [members-discuss] Fwd: Re: RIPE DB T&C violation by >> brokers >> >> Hi all, >> >> we also received the same mail today. >> >> Regards >> Stefan >> >> >> >> >> -- >> >> Zentrale >> T +49 731 92013 - 0 >> F +49 731 92013 - 290 >> E info at scanplus.de<mailto:info at scanplus.de> >> >> scanplus GmbH, sp systemhaus GmbH, >> Lise-Meitner-Str. 5-7, 89081 Ulm >> Geschäftsführung: Jürgen Hörmann, Andreas Werther >> Datenschutzbeauftragter: Thomas Dietrich scanplus GmbH, sp systemhaus >> GmbH sind zertifiziert nach DIN EN ISO 9001:2015, ISO/IEC 27001:2013, >> Data Center Category TIER 3, scanplus GmbH Amtsgericht Ulm HRB >> 3220,www.scanplus.de<http://www.scanplus.de> -----Ursprüngliche Nachricht----- >> Von: members-discuss <members-discuss-bounces at ripe.net<mailto:members-discuss-bounces at ripe.net>> Im Auftrag >> von ds at schallert.com<mailto:ds at schallert.com> >> Gesendet: Mittwoch, 27. November 2019 12:55 >> An: members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> Betreff: [members-discuss] Fwd: Re: RIPE DB T&C violation by brokers >> >> Received this one below today. I'm pretty certain that they're also >> pulling contact data from >> https://www.ripe.net/membership/indices/data/cc.xxxx.html >> >> Regards >> >> >> >> ### BEGIN ### >> >> -------- Forwarded Message ------- >> From: "Schurr Networks" <contact at jerseypride.org<mailto:contact at jerseypride.org>> >> To: xxxx >> Date: 27. November 2019 11:13 >> Subject: Acquire IPv4 >> >> Greetings, >> >> >> Hope this email finds you well. >> >> We will gladly assist if you are interested to Buy / Sell / Lease >> IPv4 addresses. >> >> Please feel free to contact me if you have any questions. >> >> >> -- >> >> Kind regards, >> >> Alexandra Schurr >> >> >> You received this email because you subscribed at RIPE Database >> Webinar >> >> Unsubscribe >> >> >> ### END ### >> >> >> >> -------- Weitergeleitete Nachricht ------- >> Von: "Alexander Zubkov" <green at msu.ru<mailto:green at msu.ru>> >> An: "Carlos Friaças" <cfriacas at fccn.pt<mailto:cfriacas at fccn.pt>>, members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> CC: exec-board at ripe.net<mailto:exec-board at ripe.net> >> Gesendet: 27. November 2019 00:37 >> Betreff: Re: [members-discuss] RIPE DB T&C violation by brokers >> 26.11.2019, 20:16, "Carlos Friaças via members-discuss" <members-discuss at ripe.net<mailto:members-discuss at ripe.net>>: >> >>> On Tue, 26 Nov 2019, Sander Steffann wrote: >>> >>>> Hi, >>> The page should reflect this: *these* are the brokers that have >>> signed a contract with the NCC, and whoever is not on this page is >>> inherently less trustworthy. Or at least, not backed by a NCC contract. >>>> +1 >>>> >>>> Currently the list of brokers is of value to the brokers because it >>>> gives them credibility. Let's turn that around and make sure the >>>> list is of value to the community instead, with very strict rules >>>> and penalties for breaking the rules. >> There are rules already. See "Recognised IPv4 Transfer Broker Agreement" >> link to it is available on the brokers list page: >> https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-merge >> rs/brokers >> https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-merge >> rs/brokers/RecognisedIPv4Broker >> greement.doc >> But the Supplity is still there, despite: >> 2. The Broker shall adhere to the relevant RIPE Policies and RIPE NCC >> procedural documents ... >> 4. The Broker does not represent the RIPE NCC and shall not imply or >> create the impression to third parties that they represent the RIPE NCC. >> 6. This agreement shall be terminated: >> * By the RIPE NCC with immediate effect if the Broker violates any of >> their obligations as outlined in this agreement ... >> >> And it is known for sure, that Supplity impersonates RIPE NCC on its >> Facebook page (still), they were lying in their spam about getting >> e-mail on RIPE NCC's training courses. They are obviously using RIPE >> DB to collect e-mails to send their spam messages. >> >> PS. I reported their page to Facebook several days ago, but looks >> like they are not going to do anything with it or may be waiting for >> zillions of reports. So who can - please make more reports about >> their page: (...) -> Find Support or Report Page -> Scams and Fake >> Pages -> Pretending to be Another Business (or another report reason >> you find suitable). May be it will help. >> >>> Hi, >>> >>> Are there any strict rules *today*? >>> >>> Are there any penalties for breaking the rules (if there are any) *today*? >>> >>> Cheers, >>> Carlos >>> >>>> Cheers, >>>> Sander >>> _______________________________________________ >>> members-discuss mailing list >>> members-discuss at ripe.net<mailto:members-discuss at ripe.net> >>> https://mailman.ripe.net/ >>> Unsubscribe: >>> https://lists.ripe.net/mailman/options/members-discuss/green@msu.ru >> _______________________________________________ >> members-discuss mailing list >> members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> https://mailman.ripe.net/ >> Unsubscribe: >> https://lists.ripe.net/mailman/options/members-discuss/ds@schallert.c >> om >> >> _______________________________________________ >> members-discuss mailing list >> members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> https://mailman.ripe.net/ >> Unsubscribe: >> https://lists.ripe.net/mailman/options/members-discuss/netmaster%40sc >> anplus.de<http://anplus.de> _______________________________________________ >> members-discuss mailing list >> members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> https://mailman.ripe.net/ >> Unsubscribe: >> https://lists.ripe.net/mailman/options/members-discuss/max%40isicore. >> com >> >> >> _______________________________________________ >> members-discuss mailing list >> members-discuss at ripe.net<mailto:members-discuss at ripe.net> >> https://mailman.ripe.net/ >> Unsubscribe: >> https://lists.ripe.net/mailman/options/members-discuss/lists%40velder >> .li > > _______________________________________________ > members-discuss mailing list > members-discuss at ripe.net<mailto:members-discuss at ripe.net> > https://mailman.ripe.net/ > Unsubscribe: > https://lists.ripe.net/mailman/options/members-discuss/lir%40fccn.pt > _______________________________________________ members-discuss mailing list members-discuss at ripe.net<mailto:members-discuss at ripe.net> https://mailman.ripe.net/ Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/stuart.gilbertson%40considerit.co.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 12824 bytes Desc: image001.jpg URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1215 bytes Desc: image002.png URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1462 bytes Desc: image003.png URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1370 bytes Desc: image004.png URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 1552 bytes Desc: image005.png URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20191128/715701ce/attachment-0003.png>
- Previous message (by thread): [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers
- Next message (by thread): [members-discuss] [LIR] Re: Fwd: Re: RIPE DB T&C violation by brokers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]