- members-discuss - mailman.ripe.net

LIR contact spam
by Cynthia Revström 11 Mar '21

11 Mar '21

Hi, I just received an email from a @gmail.com address to my LIR contact address that is not used for anything else except maybe some other related object in the RIPE DB. In the email it appears they just want to buy a /22 and a /23, and how they say what method they want to use for payment, and that they can use whatsapp. My question is, has anyone else received this same email or was it just a one-off? And also, this is not the first email of this kind that I have received but I assume there is nothing much you can do other than to just mark them as spam? I am just asking as ARIN wanted to collect the Cogent spam emails I think, but I assume RIPE NCC has nothing similar for LIR contact spam in general (such as a "whois spammer list")? -Cynthia

6 7

Re: [members-discuss] autoresponders/tickets subscribed to this list (was: Re: [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by Elvis Daniel Velea 04 Mar '21

04 Mar '21

Hi, On 2/19/21 5:57 AM, Pavel Polyakov wrote: > Elvis Daniel Velea <elvis(a)v4escrow.net> wrote: > >> I would be embarrassed to have members continue to ask for years for >> a fix to this problem. When will you fix this issue? It keeps coming >> back again and again. >> >> I sent an e-mail to this mailing list and got several automatic >> responses again... > > There is nothing the RIPE can do about it because those messages are > sent to you and not the mailing list. Anybody who has read access to > the list can fetch your email address and send those. RIPE NCC can do things to verify who has setup auto-responders to the mailing list and contact those users or unsubscribe them. Actually, they have said numerous times that they have or are working on a solution for this.. > > And where is the problem really? Is it so hard to instruct your MUA to > filter them? Yes, the e-mail addresses auto responding keep changing all the time. Every time I send an e-mail to this mailing list I get between 3-4 and a dozen e-mails. If they can not maintain a clean mailing list for the members, they should move this to a forum or something that can be kept clean. @RIPE NCC... do you plan to answer to any of my e-mails? As a member I demand an answer. Elvis

2 1

Removal of Belastingdienst from the mailing list
by Matthias Merkel 02 Mar '21

02 Mar '21

Hi all, There have been many complaints about this on the list already, but Belastingdienst is still sending automated ticket responses to the mailing list. The emails don't even just go to the sender of the email, but to the entire mailing list. Can we give them an official deadline for until when they have to fix this or be removed from the mailing list? Matthias Merkel

4 5

ONTVANGSTBEVESTIGING VAN: Re: LIR contact spam
by hostmaster＠belastingdienst.nl 01 Mar '21

01 Mar '21

Geachte heer, mevrouw, U hebt een e-mail gestuurd naar de technische beheerder van het domein m.b.t. domein en/of dns issues. Hartelijk dank daarvoor. De Belastingdienst zal uw mail analyseren, beoordelen en zo nodig passend reageren. Met vriendelijke groet, De Belastingdienst (Opmerking: De Belastingdienst zal niet reageren op andere berichten dan waarvoor het e-mail adres is bedoeld. Voor alle andere vragen, verzoeken en opmerkingen moet u contact opnemen met de Belastingtelefoon: 0800 - 0543) ------------------------------------------------------------------------ De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten. Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren. The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email. This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.

1 0

ONTVANGSTBEVESTIGING van het bericht dat is verzonden op: 01/03/2021 13:20:41
by noc＠belastingdienst.nl 01 Mar '21

01 Mar '21

Dear sender, We have received your mail and will get back to you as soon as possible. Best regards, Network Operations Centre Belastingdienst / DataCentre ServicesYep, that is my point :) These addresses are either scraped from WHOIS or from the list of members. The list of members has this on every member page: > Apart from agreed Internet operational purposes, no part of this information may be reproduced, stored in a retrieval system or transmitted, in any form or by any means (electronic, mechanical, recorded or otherwise), without prior permission of the RIPE NCC. Any use of this information to target advertising, or similar activities, is explicitly forbidden and may be prosecuted. The RIPE NCC requests notification of any such activities or suspicions thereof. And this kind of spam quite obviously is not "agreed internet operational purposes". Example: https://www.ripe.net/membership/indices/data/nl.ripencc-cs.html -Cynthia On Mon, Mar 1, 2021 at 1:03 PM Pavel Polyakov <p.polyakov+ripe(a)urdn.com.ua> wrote: Cynthia Revström via members-discuss <members-discuss(a)ripe.net> wrote: > My question is, has anyone else received this same email or was it > just a one-off? I did too. But I think this happens because your LIR email address is published in the whois of your organization object. At least, this is why it happened in my case. -- PP _______________________________________________ members-discuss mailing list members-discuss(a)ripe.net https://lists.ripe.net/mailman/listinfo/members-discuss Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/noc%40belastingdiens… ------------------------------------------------------------------------ De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten. Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren. The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email. This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.

1 0

ONTVANGSTBEVESTIGING VAN: Re: LIR contact spam
by hostmaster＠belastingdienst.nl 01 Mar '21

01 Mar '21

Geachte heer, mevrouw, U hebt een e-mail gestuurd naar de technische beheerder van het domein m.b.t. domein en/of dns issues. Hartelijk dank daarvoor. De Belastingdienst zal uw mail analyseren, beoordelen en zo nodig passend reageren. Met vriendelijke groet, De Belastingdienst (Opmerking: De Belastingdienst zal niet reageren op andere berichten dan waarvoor het e-mail adres is bedoeld. Voor alle andere vragen, verzoeken en opmerkingen moet u contact opnemen met de Belastingtelefoon: 0800 - 0543) ------------------------------------------------------------------------ De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten. Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren. The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email. This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.

1 0

ONTVANGSTBEVESTIGING van het bericht dat is verzonden op: 01/03/2021 13:03:46
by noc＠belastingdienst.nl 01 Mar '21

01 Mar '21

Dear sender, We have received your mail and will get back to you as soon as possible. Best regards, Network Operations Centre Belastingdienst / DataCentre ServicesCynthia Revström via members-discuss <members-discuss(a)ripe.net> wrote: > My question is, has anyone else received this same email or was it > just a one-off? I did too. But I think this happens because your LIR email address is published in the whois of your organization object. At least, this is why it happened in my case. -- PP _______________________________________________ members-discuss mailing list members-discuss(a)ripe.net https://lists.ripe.net/mailman/listinfo/members-discuss Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/noc%40belastingdiens… ------------------------------------------------------------------------ De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten. Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren. The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email. This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.

1 0

Re: [members-discuss] [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by Steffen Weinreich 19 Feb '21

19 Feb '21

Hi Ivo, Thanks for the heads up. It would be usefull if a LIR Admin user in the portal could see if "his" users have the 2FA enabled. That way I could encourage my colleagues without 2FA to enable. CC: to the members-discuss for feedback on the suggestion. mit freundlichen Grüßen Steffen Weinreich -- Wireless Logic mdex GmbH Bäckerbarg 6, 22889 Tangstedt, Germany Am 18.02.21 um 16:49 schrieb Ivo Dijkhuis: > Dear colleagues, > > Last weekend, RIPE NCC Access, our single sign-on (SSO) service was > affected by what appears to be a deliberate ‘credential-stuffing’ > attack, which caused some downtime. We mitigated the attack, and we are > now taking steps to ensure that our services are better protected > against such threats in the future. > > Our preliminary investigations do not indicate that any SSO accounts > have been compromised. If we do find that an account has been affected > in the course of our investigations, we will contact the account holder > individually to inform them. > > We would like to ask you to enable two-factor authentication on your > RIPE NCC Access account if you have not already done so to ensure that > your account is secure. In general, using two-factor authentication > across all your accounts can help limit your exposure to such attacks. > > If you notice any suspicious activity in your RIPE NCC Access account, > please contact us immediately at <security(a)ripe.net>. > > Best regards, > > Ivo Dijkhuis > Senior Information Security Officer, > RIPE NCC >

6 5

Abwesenheitsmeldung: Re: [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by p.glauber＠stadtwerke-forchheim.de 19 Feb '21

19 Feb '21

Sehr geehrte Damen und Herren, vielen Dank für Ihre E-Mail. Ich werde am 22.02.2021 wieder im Hause sein. Beachten Sie bitte, dass Ihre E-Mail nicht weitergeleitet wird. In dringenden Fällen wenden Sie sich bitte per Mail an die Abteilung Telekommunikation oder rufen Sie uns an. Die Mail-Adresse lautet foone(a)stadtwerke-forchheim.de Nach meiner Rückkehr werde ich Ihre E-Mail bearbeiten. Freundliche Grüße Patrick Glauber Stadtwerke Forchheim GmbH Haidfeldstraße 8 91301 Forchheim Telefon: 09191 613 218 E-Mail: p.glauber(a)stadtwerke-forchheim.de Internet: www.stadtwerke-forchheim.de

1 0

Re: [members-discuss] [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by Jan-Henning Plassmann 19 Feb '21

19 Feb '21

Hi to all! +1 to Steffen’s idea. +1 to Elvis‘s idea. Mit freundlichen Grüßen p.p.a. Jan Plassmann JHP-IT.net UG & Co. KG Mail: <mailto:jan.plassmann@jhp-it.net> jan.plassmann(a)jhp-it.net Telefon: +49 30 120 85 58 - 23 Mobil: +49 1522 865 32 81 ----------------------------------------------------------------------------- JHP-IT.net UG & Co. KG Just Handle IT Professionally Schillerstrasse 10 10625 Berlin Mail: <mailto:office@jhp-it.net> office(a)jhp-it.net Telefon: +49 30 120 85 58 - 20 Telefax: +49 30 120 85 58 - 21 Geschäftsstelle Hamburg: Am Wasserberg 11b 22869 Schenefeld Telefon: 040 – 84 60 25 37 Telefax: 040 – 18 11 65 83 Geschäftsführerin und Inhaberin: Anna Bisping Einzelprokura: Jan-Henning Plassmann Sitz der Gesellschaft: Berlin Handelsregister: Berlin Charlottenburg HRA 50707 B, USt.-Id.-Nr: DE 301 403 084 Bankverbindung: Berliner Volksbank, IBAN: DE05 1009 0000 2557 4290 02, BIC: BEVODEBB This message and any attachments are confidential as a business secret and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please telephone or e-mail the sender and delete this message and any attachment from your system. Also, if you are not the intended recipient you should not disclose the content or take / retain / distribute any copies. Diese von Ihnen erhaltene E-Mail und die anliegenden Dateien sind das Geheimnis des Unternehmens und sind ausschließlich für die angeführten Adressaten bestimmt. Sollten Sie nicht der richtige Empfänger sein, informieren Sie bitte umgehend den Absender und vernichten Sie diese E-Mail. Unbefugte Weitergabe der erhaltenen Informationen sowie das unerlaubte Kopieren / Speichern / Verbreiten der erhaltenen Informationen ist nicht gestattet Von: members-discuss <members-discuss-bounces(a)ripe.net> Im Auftrag von Elvis Daniel Velea Gesendet: Freitag, 19. Februar 2021 09:48 An: Steffen Weinreich <steffen.weinreich(a)mdex.de> Cc: Ivo Dijkhuis <ivo.dijkhuis(a)ripe.net>; members-discuss(a)ripe.net Betreff: Re: [members-discuss] [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication Hi, +1 to Steffen’s idea. Also, a couple of questions... how can I find out if someone (attempts to) login with my SSO? Can the RIPE NCC provide a page showing a list of last 5-10-100 (un)successful logins? How about e-mail notifications (with the IP address of the attacker) when a failed login attempt is made? Can I get an e-mail notification that someone has logged in, every time a successful login happens? - I’d like these to be opt-in Elvis On Fri, Feb 19, 2021 at 00:40 Steffen Weinreich <steffen.weinreich(a)mdex.de <mailto:steffen.weinreich@mdex.de> > wrote: Hi Ivo, Thanks for the heads up. It would be usefull if a LIR Admin user in the portal could see if "his" users have the 2FA enabled. That way I could encourage my colleagues without 2FA to enable. CC: to the members-discuss for feedback on the suggestion. mit freundlichen Grüßen Steffen Weinreich -- Wireless Logic mdex GmbH Bäckerbarg 6, 22889 Tangstedt, Germany <https://www.google.com/maps/search/B%C3%A4ckerbarg+6,+22889+Tangstedt,+Germ…> Am 18.02.21 um 16:49 schrieb Ivo Dijkhuis: > Dear colleagues, > > Last weekend, RIPE NCC Access, our single sign-on (SSO) service was > affected by what appears to be a deliberate ‘credential-stuffing’ > attack, which caused some downtime. We mitigated the attack, and we are > now taking steps to ensure that our services are better protected > against such threats in the future. > > Our preliminary investigations do not indicate that any SSO accounts > have been compromised. If we do find that an account has been affected > in the course of our investigations, we will contact the account holder > individually to inform them. > > We would like to ask you to enable two-factor authentication on your > RIPE NCC Access account if you have not already done so to ensure that > your account is secure. In general, using two-factor authentication > across all your accounts can help limit your exposure to such attacks. > > If you notice any suspicious activity in your RIPE NCC Access account, > please contact us immediately at <security(a)ripe.net <mailto:security@ripe.net> >. > > Best regards, > > Ivo Dijkhuis > Senior Information Security Officer, > RIPE NCC > _______________________________________________ members-discuss mailing list members-discuss(a)ripe.net <mailto:members-discuss@ripe.net> https://lists.ripe.net/mailman/listinfo/members-discuss Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/elvis%40v4escrow.net -- This message was sent from a mobile device. Some typos may be possible.

1 0

autoresponders/tickets subscribed to this list (was: Re: [ncc-announce] Attack on RIPE NCC Access - Please Enable Two-Factor Authentication
by Elvis Daniel Velea 19 Feb '21

19 Feb '21

Dear RIPE NCC, I would be embarrassed to have members continue to ask for years for a fix to this problem. When will you fix this issue? It keeps coming back again and again. I sent an e-mail to this mailing list and got several automatic responses again... 1. Dear belastingdienst, can you unsubscribe your ticketing system de.belastingdienst(a)belastingdienst.nl from this mailing list? I got two emails from you... 2. Dear cpro(a)mib.cpro.fr, please stop asking me to click on links for my e-mails to be delivered to your inbox. If you don’t want my e-mails, just unsubscribe, please. 3. Dear info(a)parsnafe.com, I have no idea what your e-mail written in Persian (?) means. Please unsubscribe auto-responders from this mailing list. ... and the list can continue. I really hope the RIPE NCC will come up with a solution to this, it’s not like we haven’t asked for it for decades... /elvis On Fri, Feb 19, 2021 at 00:47 Elvis Daniel Velea <elvis(a)v4escrow.net> wrote: > Hi, > > +1 to Steffen’s idea. > > Also, a couple of questions... how can I find out if someone (attempts to) > login with my SSO? > > Can the RIPE NCC provide a page showing a list of last 5-10-100 > (un)successful logins? > > How about e-mail notifications (with the IP address of the attacker) when > a failed login attempt is made? > Can I get an e-mail notification that someone has logged in, every time a > successful login happens? > - I’d like these to be opt-in > > Elvis > > On Fri, Feb 19, 2021 at 00:40 Steffen Weinreich <steffen.weinreich(a)mdex.de> > wrote: > >> Hi Ivo, >> >> Thanks for the heads up. >> >> It would be usefull if a LIR Admin user in the portal could see if "his" >> users have the 2FA enabled. That way I could encourage my colleagues >> without 2FA to enable. >> >> CC: to the members-discuss for feedback on the suggestion. >> >> mit freundlichen Grüßen >> >> Steffen Weinreich >> >> -- >> Wireless Logic mdex GmbH >> Bäckerbarg 6, 22889 Tangstedt, Germany >> <https://www.google.com/maps/search/B%C3%A4ckerbarg+6,+22889+Tangstedt,+Germ…> >> >> Am 18.02.21 um 16:49 schrieb Ivo Dijkhuis: >> >> > Dear colleagues, >> > >> > Last weekend, RIPE NCC Access, our single sign-on (SSO) service was >> > affected by what appears to be a deliberate ‘credential-stuffing’ >> > attack, which caused some downtime. We mitigated the attack, and we are >> > now taking steps to ensure that our services are better protected >> > against such threats in the future. >> > >> > Our preliminary investigations do not indicate that any SSO accounts >> > have been compromised. If we do find that an account has been affected >> > in the course of our investigations, we will contact the account holder >> > individually to inform them. >> > >> > We would like to ask you to enable two-factor authentication on your >> > RIPE NCC Access account if you have not already done so to ensure that >> > your account is secure. In general, using two-factor authentication >> > across all your accounts can help limit your exposure to such attacks. >> > >> > If you notice any suspicious activity in your RIPE NCC Access account, >> > please contact us immediately at <security(a)ripe.net>. >> > >> > Best regards, >> > >> > Ivo Dijkhuis >> > Senior Information Security Officer, >> > RIPE NCC >> > >> >> _______________________________________________ >> members-discuss mailing list >> members-discuss(a)ripe.net >> https://lists.ripe.net/mailman/listinfo/members-discuss >> Unsubscribe: >> https://lists.ripe.net/mailman/options/members-discuss/elvis%40v4escrow.net > > >> -- > This message was sent from a mobile device. Some typos may be possible. > -- This message was sent from a mobile device. Some typos may be possible.

1 0

Re: [members-discuss] alireza gholamshahi
by alireza gholamshahi 15 Jan '21

15 Jan '21

https://bit.ly/3ooq1sN ⚡ alireza gholamshahi ____________________________________________________________________ Trump Administration Moves To Brand Houthis In Yemen A Terrorist Group The designation has broad implications — not just for the Iran-backed group, which controls Yemen's capital, but also for international organizations trying to help residents badly in need of aid. 2020 and me: 'I know the value of family more' Despite the many challenges, Rula in Istanbul believes 2020 will benefit us in the future. Ireland has the world's highest Covid-19 rate. How did it go so wrong? The seasonality of the virus, the presence of the more transmissible UK variant and households mixing over Christmas all contributed to the surge, according to a government spokesperson from the office of Prime Minister Micheál Martin. Trump calls for 'no violence' ahead of planned 'armed protests' - as removal vans arrive at White House Donald Trump has called for "no violence" ahead of what the FBI has warned are "armed protests" being planned at all 50 state capitals ahead of Joe Biden's inauguration - as removal vans were spotted outside the White House. 100-Year-Old Indian Princess' Wish to Save Her Palaces Comes True as Gov't Buys It for Tourism The princess inherited the royal residence from her husband, but since his death it has fallen into disrepair – however, her resilience and close friends have ensured that her new life will be breathed into her beloved palace. High Demand For COVID-19 Vaccine Strains Health Departments In South An uneven vaccine rollout across Southern states is causing frustration. Health departments are overwhelmed with people seeking shots as phone lines and websites are unable to keep up with the demand. Speaker Nancy Pelosi walks through Capitol riots damage The House leader said her staff hid under a table and barricaded the door for two hours. While Brazilians wait for a vaccine, Bolsonaro plays politics Many countries are getting a shot of hope this month as they vaccinate health workers against the coronavirus, but Brazil seems stuck in limbo, despite its own vaunted national vaccination program. Servant, Stardust and Blithe Spirit This week on Backstage - Bethany Minelle, Stevie Wong and Amy Hitchcock unpack Netflix's ambitious new slate for programming in 2021. Trump's Two Favoured Banks Distance Themselves From President Over Capitol Mayhem The banks' decision comes hot on the heels of social networks and other companies suspending ties with the president after he was widely accused of inciting his supporters to storm the Capitol building to "stop the steal".

1 0

Re: [members-discuss] [ncc-announce] [news] LIR Account closure? Notify us by 1 December
by Sergey Myasoedov 20 Nov '20

20 Nov '20

Dear Henriette, Thank you for this timely notification. I got a question from our community. If an LIR (or multi-LIR) has received their IPv4 network in December 2018 and would like to make a transfer in 2020, they should submit a request with the MyLIR portal no earlier than 731 day after initial allocation, otherwise the system will not allow the transfer request. And this mean an invoice for 2021 will be received by the LIR and no transfer will be possible until full payment. Does this situation reflect the reality? Will the LIR carry extra expenses? -- Kind regards, Sergey Myasoedov You wrote Monday, November 16, 2020, 1:38:00 PM: > Dear RIPE NCC members, > We would like to inform you that a request to close an LIR account > or any request that will result in the closure of an LIR account > should be submitted in full before 1 December 2020. This includes > closures that result from policy transfers and changes in business > structures. Any requests submitted after this date mean that you could be invoiced for 2021. > The request should contain all the requested information and > documents in order for the RIPE NCC to process it before the end of > the year. An overview of the required documents can be found at: > https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/req… > For requests resulting in the closure of an LIR account that are > submitted later than 1 December 2020, or requests that are > incomplete, we can not guarantee that the LIR account will be closed > before 31 December 2020. Invoices for 2021 will be issued for LIR > accounts still open on 1 January 2021. > Best Regards, > Henriette van Ingen > Registry Services Assistant Manager > RIPE NCC

4 3

External thoughts on the Executive Board Election TF
by Harry Cross 11 Nov '20

11 Nov '20

Hi all, I've just had a cursory glance through the report and the mailing list minutes. I'd like to ask why the mailing list was not open to all please, I saw the minutes mentioned this but there was no explanation of why? Surely if the membership had requested for this to happen, it makes sense to allow them to be involved in the discussion. Some people may not want to commit to a full task force membership, but still give their view. I also tried to get to the Doodles and they don't work. Are they public at all please? Thanks Harry >

13 28

Re: [members-discuss] Moderation Please
by Sascha Growe 07 Nov '20

07 Nov '20

Could some setup moderation again, please? Regards -- Sascha Growe Network Architect Tel: +49 40 771 75 6 81 E-Mail: sascha.growe(a)plusserver.com PlusServer GmbH Verlerstr. 6 33332 Gütersloh HRB 84977 / Amtsgericht Köln Geschäftsführer: Dr. Oliver Mauss, Jürgen Metko, Holger Müller, Dr. Frank Nellissen Von: members-discuss <members-discuss-bounces(a)ripe.net> im Auftrag von Elad Cohen <elad(a)netstyle.io> Datum: Samstag, 7. November 2020 um 15:10 An: Töma Gavrichenkov <ximaera(a)gmail.com>, Elvis Daniel Velea <elvis(a)v4escrow.net> Cc: Members Discuss <members-discuss(a)ripe.net> Betreff: Re: [members-discuss] External thoughts on the Executive Board Election TF Toma, can you confirm or deny that you are part of the mob-like Ops-Trust community ? (https://portal.ops-trust.net/) From: members-discuss <members-discuss-bounces(a)ripe.net> on behalf of Töma Gavrichenkov <ximaera(a)gmail.com> Sent: Saturday, November 7, 2020 4:00 PM To: Elvis Daniel Velea <elvis(a)v4escrow.net> Cc: Members Discuss <members-discuss(a)ripe.net> Subject: Re: [members-discuss] External thoughts on the Executive Board Election TF Peace, On Sat, Nov 7, 2020, 4:40 PM Elvis Daniel Velea <elvis(a)v4escrow.net> wrote: my understanding is that the tf was formed of the full set of those who volunteered. a person was kicked out. just for the record. The person was kicked after their non constructive criticism and code of conduct violations led to I think two other people announcing their intention to abandon their participation and contribution, at which point it was clear that it's impossible to preserve the original task force size anyway. The goal was to maximise the number of people involved, i.e. having one task force member leaving was considered better than having two. -- Töma

1 0

Lifting Moderation of Membership Discussion List
by Remco van Mook 31 Oct '20

31 Oct '20

Dear members, The Executive Board met today and decided to remove moderation of the members-discuss mailing list. Instead, if a subscriber sends emails that are not in accordance with the purpose of the mailing list or with the principles of the RIPE Code of Conduct, this individual subscriber will be under moderation from that point on. This evaluation and moderation will be conducted by the Executive Board Secretary and a RIPE NCC staff member. All emails, accepted or rejected, will be archived on the RIPE NCC website. I urge all members to take note of the Code of Conduct that should be adhered to when mailing to the list: https://www.ripe.net/participate/mail/ripe-mailing-list-ripe-forum-code-of-… If you suspect someone is violating the purpose of the list or there is a breach of the Code of Conduct, please notify the RIPE NCC at <ncc(a)ripe.net> rather than responding to the email in question. Regards, Remco van Mook RIPE NCC Executive Board

2 1

Resolution 3 Recommendation
by Antonios Chariton (daknob) 28 Oct '20

28 Oct '20

Dear Members, Since voting has started, I will do my best to avoid siding with either the Yes or the No side, while at the same time bring up a suggestion for this resolution, should it be rejected and can be reworked into the future. Moderators, if you think this should be released after the poll closes, feel free to do that. The document I read, for Resolution 3, contains the wording "a certified copy of his/her official identification document”. I would simply like to point out, again, without getting into politics, that there exist people in disputed territories (or equivalent status), who may not have an official identification document that is considered valid by the Netherlands. There are different kinds of such territories and accepted documents. For example, some of them are recognized by a single country, while some others are not recognized as a country, because possibly of political pressure, but there exist processes of handling official documents, as an exception, and they are referred to as “areas”. A person can travel to the Netherlands with this passport, although the issuing country is not recognized as a country. A person can get a visa there to stay, and it’s mostly considered equivalent, at least to me. I do not say that this should or should not be included, and maybe the decision has already been made (to not), and possibly the Legal team understands the situation better (there may be requirements by Dutch law), I just want to bring this into attention in case it was overlooked, in order to avoid future issues. Best regards, Antonis

2 1

Re: [members-discuss] [exec-board] ripe-ncc-executive-board-election-task-force-report
by Alex de Joode 28 Oct '20

28 Oct '20

Thanks Christian, I missed those. "(b) a signed statement in which he/she declares that he/she shall adhere to the Code of Conduct for candidates for the Executive Board as adopted by the Executive Board and published on the Association’s website, and that he/she has never committed any fraud or other financial misconduct in any jurisdiction" This is extremely broad. It also opens the possibility that RIPE NCC has to become an arbiter wether or not a certain action of a nominee constitutes fraud (with all the possible liabilities for RIPE NCC in civil court). Legally it would be preferable to just focus on 'outcomes': has there been any verdict against a nominee. Court cases can be won by nominees .. Is the wording deliberate (ie as broad as possible) Ifso have you thought about the above scenario ? -- IDGARA | Alex de Joode | alex(a)idgara.nl | +31651108221 On Tue, 27-10-2020 16h 36min, "Kaufmann, Christian" <ckaufman(a)akamai.com> wrote: > Dear Alex, Dear Members, Here you can find the exact wordings and details: https://www.ripe.net/participate/meetings/gm/meetings/october-2020/proposed… and here is the rest of the supporting documents we have sent out before. https://www.ripe.net/participate/meetings/gm/meetings/october-2020/supporti… Hope this helps, Best, Christian Kaufmann RIPE NCC Executive Board From: Alex de Joode <adejoode(a)idgara.nl> > Reply to: Alex de Joode <adejoode(a)idgara.nl> > Date: Tuesday, 27. October 2020 at 14:31 > To: "members-discuss(a)ripe.net" <members-discuss(a)ripe.net>, "exec-board(a)ripe.net" <exec-board(a)ripe.net> > Subject: [exec-board] ripe-ncc-executive-board-election-task-force-report The report states: 7. Other requirements of nominees Recommendation It was agreed that the candidates must agree to follow the code of conduct at all times (see point 6 above). The nominee should also sign a statement certifying that they have not committed fraud or other financial misconduct in any jurisdiction. This requirement should be added to the Articles of Association. This is very broad as it pertains to behaviour. Normally this is stated as "not being convicted for fraud or other financial misconduct in any jurisdiction". So in order to know what we are voting on tomorrow, can the Board show us the exact textual changes we are voting on? Thanks. Alex/(as-spectre) -- IDGARA | Alex de Joode | alex(a)idgara.nl | +31651108221

4 6

Injection of false RPKI ROAs
by Maxi 28 Oct '20

28 Oct '20

Dear fellow Members, Dear RIPE Team, We currently discuss a somehow strange thing. Could the RIPE NCC be forced to inject false ROAs (e.g. for censorship)? If so, is there any legal framework for it? Does the RIPE NCC have any information on attempts? Best, Maxi Impressum: Zeug e.K. Hochstraße 15 92637 Theisseil Inhaber: Maximilian Schieder Telefon: 015678 572314 E-Mail: maxi(a)zeug.co Registergericht: Amtsgericht Weiden in der Oberpfalz Registernummer: HRA 2907

4 4

ripe-ncc-executive-board-election-task-force-report
by Alex de Joode 27 Oct '20

27 Oct '20

The report states:> > 7. Other requirements of nominees Recommendation It was agreed that the candidates must agree to follow the code of conduct at all times (see point 6 above). The nominee should also sign a statement certifying that they have not committed fraud or other financial misconduct in any jurisdiction. This requirement should be added to the Articles of Association. > > This is very broad as it pertains to behaviour. Normally this is stated as "not being convicted for fraud or other financial misconduct in any jurisdiction". > So in order to know what we are voting on tomorrow, can the Board show us the exact textual changes we are voting on? > Thanks, Alex -- SPECTRE/AS47482 | Alex de Joode | alex(a)idgara.nl | +31651108221

1 0

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
by Hans Petter Holen 21 Oct '20

21 Oct '20

Hi Nick, > On 29 Sep 2020, at 17:06, Nick Hilliard (Network Ability Ltd) <nick(a)netability.ie <mailto:nick@netability.ie>> wrote: >> > > Hi Hans Petter, > > couple of queries here. > > 1. RIPE atlas measurements are growing much faster than ripe probe / anchor deployment. In addition, some of the older deployed probe stock is decaying. Is the capex allocation of €130k enough expenditure as part of the long term funding plan for Atlas to ensure that the current rate of increase of measurements can be sustained in the long term? Yes. In terms of measurements data storage and processing, we are aiming to migrate live storage and processing of the ever-growing dataset to the cloud (with proper in-house, offline backup plans). That significantly reduces the investments required for that part. Next to introduction of Software Probes and on replenishing the hardware probe network and keeping up and growing with new or uncovered ASes, so far we have generally relied on contributions from our sponsors. We are currently developing mid- and long-term plans for the supply of hardware probes, and we will inform the community and our membership as soon as we complete our proposal. > > 2. IT security: presumably this encompasses RPKI TA and hosted CA security management too? No. The security budget is not fully centralised. The costs for RPKI TA and hosted CA security management is budgeted as part of the RPKI budget. > 3. RIPE Chair Team: the allocation of €205k for Chair, Vice Chair and travel + subsistence looks surprisingly low given that the average personnel cost per FTE is listed as €102k. Separately, the board committed to ensuring independence of the RIPE Chair Team from the NCC. Can you provide information on how this independence will be maintained, and also reassurance that the RIPE Chair Team remuneration package has been designed or at least reviewed by an independent third party to ensure that it's appropriate for the positions? The remuneration component of the package covers the RIPE Chair but not the Vice Chair. Travel and expenses for both are covered, however. The travel expense budget is based on the travel expense budget for the previous RIPE Chair. For 2021 we have only budgeted for travel 75% of the previous years. The contract between the RIPE Chair and the RIPE NCC has been negotiated between the RIPE Chair and the RIPE NCC Executive board represented by the Chair and Treasurer. The contract includes multiple clauses that enforce the separation of the Chair position from influence by the RIPE NCC and its board. This contract has been reviewed by external legal experts for compliance with Dutch labour laws. The remuneration package is aligned with the RIPE NCC salaries which have been benchmarked by an external party. > 4. Software development: there's been some discussion about the RPKI validator. One issue that hasn't been touched on is the RIPE NCC's general involvement with software development where there are other third party packages available on a commercial or commercially-supported basis. This is an issue that was raised before (many years ago), specifically in the context of development of DNS software. Can you provide some info on what the RIPE NCC's governing policies are in this area? In this case, we follow the RIPE NCC’s roles and responsibilities as laid out here: https://www.ripe.net/about-us/what-we-do/ripe-ncc-association-roles-and-res… <https://www.ripe.net/about-us/what-we-do/ripe-ncc-association-roles-and-res…> We do not have specific policies for software development. Such decisions are made in consultation with the board and community. From what I recall there was no other viable RPKI validator when we started this development work, so an investment to bootstrap the whole system was needed. > 5. E-voting: as there are no alternatives in the short-term future, has the RIPE NCC confirmed that the E-voting platform will be fully GDPR compliant for the upcoming GM and also on Jan 1, 2021? I.e both in terms of potential brexit outcomes and also in terms of transatlantic data transfer following the Schrems 2 ruling. The e-voting platform for the upcoming GM is GDPR compliant. Our third-party platform provider has confirmed that no personal data is transferred to the USA, therefore the recent Schrems II ruling does not have an impact in our relationship. Regarding the legal implications due to Brexit, we are following the relevant developments. When the data protection legal framework is clarified, we will make sure that all amendments necessary are performed in order to comply with the law. I hope this answers your questions, but are happy to further clarify if needed. Hans Petter Holen Managing Director, RIPE NCC

1 0

Webauthn
by Bogdan I. 14 Oct '20

14 Oct '20

Hello What would be your opinion of implementing Webauthn / U2F by security keys for the RIPE NCC website's two factor authentication, in addition to the current TOTP system? The current TOTP based system works fine, but i find using a physical security key to be more convenient and more secure. -- Bogdan Ionescu Redcluster LTD

5 5

Draft Activity Plan 2021 - RPKI development
by Erik Bais 01 Oct '20

01 Oct '20

Dear Hans Petter and fellow members, In the draft activity plan, there is a page about the current RPKI cost and plans of the further development. The plans state on Page 14 - 1.6 RPKI: 6 FTE and a 963.000 euro budget ... <begin quote> Activities in 2021 Our priority over the coming period will be ensuring a stable and resilient RPKI Trust Anchor and Certificate Authority. In 2020, we carried out a third-party security and risk assessment of our RPKI platform. We are now working to define a complete audit framework for RPKI, with the aim of having the audit performed early next year by a third party. Next year we will implement changes to our internal processes and documented procedures on the basis of this audit, as well as things like more granular monitoring and small technical changes that ensure compliance with the relevant RFCs. Aside from that, we are planning significant improvements in our infrastructure to allow high availability and resiliency for the RPKI repositories. In last year’s Activity Plan, we said we would consider whether we should continue to support our RPKI Validator, as it needed further development to match the quality of alternative tools that were now available. Because our RPKI Validator remains the second most widely used tool (with 32% “market share”), we decided that we will continue to support it in 2021 and we aim to make a longer-term decision soon. Finally, we will continue to build awareness of RPKI through training, outreach and promotion efforts. </end quote> I would like to argue that further development of Proof of Concept software (the RPKI validator) isn't required anymore now that there are multiple open source tools available on the market. The RIPE NCC isn't a software development house .. and I don't recall the RIPE NCC has the planning to become one ... I would like to see further development of the RIPE NCC RPKI Validator discontinued as of Jan. 1st 2021. The backend software / infra for the signing of the RPKI environment still needs a lot of work and so does the training (awareness) about RPKI .. so I don't think that the resources or budgeted cost should be reduced, but is needs to be revised... I think that the efforts should be put somewhere else on RPKI. That the RIPE NCC RPKI Validator is widely used, is because of the training efforts from the RIPE NCC.. and I think the community is better served with a more open approach about the usage of other validators, instead of trying to keep members to use a Java based software package. When the RIPE NCC started with the development of the RPKI Validator, there was a lack of other software ... but as things stand today, there are multiple open source implementations and this is a nice moment to go back to the core activity of the RIPE NCC. I know that with the above, I would probably not give the internal development team enough credits for their work and effort in the past years. I do value their work to where they brought this, but it is time to put the focus on the core activities like the signing side of the RPKI and a more robust RPKI infra instead of the validation software. Regards, Erik Bais

12 12

Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Activity Plan and Budget 2021
by Nick Hilliard (Network Ability Ltd) 29 Sep '20

29 Sep '20

Hans Petter Holen wrote on 16/09/2020 15:27: > Dear members, > > The Draft RIPE NCC Activity Plan and Budget 2021 is now available for > your review: > https://www.ripe.net/participate/meetings/gm/meetings/october-2020/draft-ri… > > This document is the clearest way you can learn about our plans for > next year and shape the direction we take as an organisation. We ask > that you read it and share any feedback on <members-discuss(a)ripe.net>. Hi Hans Petter, couple of queries here. 1. RIPE atlas measurements are growing much faster than ripe probe / anchor deployment. In addition, some of the older deployed probe stock is decaying. Is the capex allocation of €130k enough expenditure as part of the long term funding plan for Atlas to ensure that the current rate of increase of measurements can be sustained in the long term? 2. IT security: presumably this encompasses RPKI TA and hosted CA security management too? 3. RIPE Chair Team: the allocation of €205k for Chair, Vice Chair and travel + subsistence looks surprisingly low given that the average personnel cost per FTE is listed as €102k. Separately, the board committed to ensuring independence of the RIPE Chair Team from the NCC. Can you provide information on how this independence will be maintained, and also reassurance that the RIPE Chair Team remuneration package has been designed or at least reviewed by an independent third party to ensure that it's appropriate for the positions? 4. Software development: there's been some discussion about the RPKI validator. One issue that hasn't been touched on is the RIPE NCC's general involvement with software development where there are other third party packages available on a commercial or commercially-supported basis. This is an issue that was raised before (many years ago), specifically in the context of development of DNS software. Can you provide some info on what the RIPE NCC's governing policies are in this area? 5. E-voting: as there are no alternatives in the short-term future, has the RIPE NCC confirmed that the E-voting platform will be fully GDPR compliant for the upcoming GM and also on Jan 1, 2021? I.e both in terms of potential brexit outcomes and also in terms of transatlantic data transfer following the Schrems 2 ruling. Nick

1 0

RIPE NCC Executive Board Election Task Force Report Now Available
by Christian Kaufmann 18 Sep '20

18 Sep '20

Dear members, The RIPE NCC Executive Board Election Task Force assembled in July in order to carry out a full evaluation of our Executive Board nomination and election process. The task force has since shared its report with my fellow board members and I, and we are glad to announce that we fully support all nine of the recommendations they have made for improving the existing processes. The final report is now available on the RIPE NCC website as a supporting document for our October GM, which will take place from 28-30 October adjacent to the RIPE 81 meeting. There will be a presentation on the report during the GM, and members will also have a chance to vote on changes to the RIPE NCC Articles of Association that are necessary if the recommendations are to be implemented. https://www.ripe.net/participate/meetings/gm/meetings/october-2020/supporti… The task force has carried out its objective swiftly and diligently. On behalf of the board, I would like to express our sincere appreciation for the work done by each of the eight members of the task force in such a short amount of time: Erik Bais Randy Bush Carlos Friaças Töma Gavrichenkov Sergey Myasoedov (Task Force Chair) Arnold Nipper Cynthia Revström Jan Žorž We look forward to discussing this topic further with all RIPE NCC members at the October GM. Kind regards, Christian Kaufmann RIPE NCC Executive Board Chairman

1 0