- members-discuss - mailman.ripe.net

Consultation on RIPE NCC Charging Scheme 2025
by Fergal Cunningham 18 Mar '24

18 Mar '24

Dear RIPE NCC members, I want to remind you that this Wednesday, 20 March, from 10:00-11:30 UTC (11:00-12:30 CET) we will have an Open House where members can give their input on the RIPE NCC Charging Scheme 2025. You can register to attend now at: https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-schem… This open house will kick off discussion on the charging scheme and will give the Executive Board valuable input ahead of its meeting on 25 March, where it will decide on the draft charging proposal it will present to the members. All those who register to attend will receive a Meetecho link to participate in the open house on Wednesday morning. This year, we want to receive input from members before publishing any draft charging scheme. We believe this will help to arrive at a good proposal well in advance of the General Meeting. To help with discussions, we also provide a consultation page where members can see relevant facts and documentation about the charging scheme as well as the financial landscape the RIPE NCC is operating in. We will develop this page with further information as the consultation progresses: https://www.ripe.net/membership/mail/member-and-community-consultations/cha… We look forward to your involvement in this important process for RIPE NCC members. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC Key Dates 20 March - Consultation with members begins at Charging Scheme 2025 Open House 25 March - RIPE NCC Executive Board discusses charging scheme proposal to put forward to members 27 March - Registration for RIPE NCC General Meeting opens 10 April - Draft charging scheme proposal published for members to discuss 24 April - Final charging scheme proposal published for members to vote on 22-24 May - RIPE NCC membership votes on charging scheme options for 2025

1 0

RIPE NCC Charging Scheme 2025: Open House on 20 March 11:00-12:30 UTC+1
by Fergal Cunningham 05 Mar '24

05 Mar '24

Dear members, We invite you to take part in an Open House on 20 March to discuss the RIPE NCC Charging Scheme 2025. This year, we would like to get input from the members before the Executive Board proposes one or more charging schemes to be discussed and voted on by members. You can register to attend now at: https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-schem… The RIPE NCC will give a presentation at the Open House that explains the current outlook and financial considerations, and then take input and guidance from the members on this important topic. The Open House will be recorded for those who can not attend on the day. The following Monday, 25 March, a RIPE NCC Executive Board Meeting will take place where the Board and Management will discuss the input from members and decide on one or more draft charging schemes to propose to the membership to be voted on at the May General Meeting. We will provide background information and data that can help guide discussions ahead of the Open House. And of course we encourage members to continue to discuss the 2025 charging scheme on this list after the Open House takes place. We look forward to your participation. Kind regards, Fergal Cunningham Head of Membership Engagement RIPE NCC

1 0

[GM] Call for Volunteers for Executive Board Election Code of Conduct Team
by Ondrej Filip 14 Feb '24

14 Feb '24

Dear members, This is a call for volunteers from the membership to join the Executive Board Election Code of Conduct Team for the May 2024 General Meeting elections. The Executive Board election of 2024 will be the fourth to have a Code of Conduct (CoC) for Executive Board Election candidates. I should make it clear that this is a separate Code of Conduct to the RIPE NCC and RIPE community CoCs. This code has been established and is only in effect for confirmed candidates during the election process. An Executive Board Election Code of Conduct Team was also established to evaluate reports of violations of the Code of Conduct. The team for 2023 was made up of six volunteers and the Executive Board would like to express its gratitude to Cynthia Revström, Arnold Nipper, Annie Yanyan Yang, Kris Edgar, Nat Morris and Sebastian Becker who carried out this important work. The Executive Board would now like to ask for volunteers from the membership to be on the Executive Board Election Code of Conduct Team for the May 2024 election. The task of this team will be to evaluate any reports of violations of the election Code of Conduct by candidates. If the team confirms that a violation of the election Code of Conduct has taken place, disqualification of the candidate in question can take place. If you are willing to participate in this role, please send a mail to <agm(a)ripe.net> by *6 March 2024*. The Board will appoint members of the team from the list of those that volunteer. Members should not volunteer if they expect to become candidates in the election. The Executive Board Election Code of Conduct can be found at: https://www.ripe.net/membership/meetings/gm/meetings/may-2024/executive-boa… Kind regards, Ondřej Filip Chair, RIPE NCC Executive Board

1 0

The redesigned www.ripe.net is now live
by Phillip Oldham 26 Jan '24

26 Jan '24

Dear colleagues, If you visit www.ripe.net today, you might notice some changes. For the past few months, we’ve been working on redesigning ripe.net, and we released the new version yesterday at approximately 18:00 UTC+1. Here are some of the major changes: • The design of the website has changed • The content management system has been changed from Plone to Wagtail • We migrated servers to make this switch • The website is now significantly more mobile and tablet friendly • We are using a new search engine on the website, so search results should be more relevant, and we will be investing time to make this experience even better • Accessibility has been improved, and we aim to align with WCAG 2.1 standards as soon as possible • Visitors should see some performance improvements, and we aim to continue adding improvements for usability and energy efficiency • The RIPE community is more prominent and easy to access from the top-level navigation under “community”, and we are applying a new community design to community-related pages: https://www.ripe.net/community/ The overall navigation of the website has not been significantly altered to ensure a smooth transition. We will be making more changes to the navigation to improve readability and discoverability. Many of you shared input in a survey and some of you joined us for user interviews at RIPE 86 and for conversations following my presentation at RIPE 87. Thank you for helping us through this process. While we have launched the newly redesigned website, with over 8,000 web pages migrated to the new platform, we know there will be fixes and tweaks needed in the weeks to come. If you notice any issues or have feedback, please let us know on the forum: https://forum.ripe.net/t/www-ripe-net-redesign-is-live/820 For anything urgent, please email us at webmaster(a)ripe.net Kind regards, Phillip Oldham (he/him) <poldham(a)ripe.net> Manager, Web Services RIPE NCC Stationsplein 11, 1012 AB Amsterdam

5 6

Re: [members-discuss] The redesigned www.ripe.net is now live
by Phillip Oldham 24 Jan '24

24 Jan '24

Hi Luca The LIR Portal is managed by a different team within the RIPE NCC, however I do know that there is an ongoing effort across teams to align the designs of our various applications with the refreshed www.ripe.net <http://www.ripe.net/> website design. Unfortunately I don’t have any further information at this time. I’ll forward your question to that team so they can reach out with further details. Best regards, Phillip Oldham (he/him) <poldham(a)ripe.net> Manager, Web Services RIPE NCC Stationsplein 11, 1012 AB Amsterdam > On 19 Jan 2024, at 14:55, Luca Marini <marini.luca(a)c1vhosting.it> wrote: > > Thanks for the new design, it looks cool! > > Do you plan to update the UI of the LIR portal too? > > > Luca Marini > Chief Commercial Officer > C1V Hosting > Direct: +39 324 6939 048 | Email: marini.luca(a)c1vhosting.it <mailto:marini.luca@c1vhosting.it> > Website: www.c1vhosting.it <http://www.c1vhosting.it/> | Telegram: t.me/c1vhosting <http://t.me/c1vhosting> > Empowering your digital world with sustainability and innovation: > 🌿 Sustainable Solutions: Committed to net zero with renewable energy. > 🌐 Broadband Services: Local and international connectivity. > 🔗 Data Services: WDM paths, Dark Fiber, IP transit. > ☁️ Cloud & Datacenter: Robust, eco-friendly infrastructure. > 🛡️ Cybersecurity: Advanced D/DoS defense and system integration. > > C1V Hosting: Pioneering sustainable digital connectivity. > > Confidentiality Notice: This email may contain confidential information for the sole use of the intended recipient. If you are not the intended recipient, please notify the sender and delete this email. Unauthorized use is prohibited. > > Thank you for choosing C1V Hosting, your partner for sustainable and innovative digital solutions. > > Warm regards, > > Luca Marini > > >> On 19 Jan 2024, at 14:51, Michele Neylon - Blacknight via members-discuss <members-discuss(a)ripe.net> wrote: >> >> >> This is great. Well done to all involved! >> >> >> >> -- >> Mr Michele Neylon >> Blacknight Solutions >> Hosting, Colocation & Domains >> https://www.blacknight.com/ >> https://blacknight.blog/ >> Intl. +353 (0) 59 9183072 >> Direct Dial: +353 (0)59 9183090 >> Personal blog: https://michele.blog/ >> Some thoughts: https://ceo.hosting/ >> ------------------------------- >> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 >> >> I have sent this email at a time that is convenient for me. I do not expect you to respond to it outside of your usual working hours. >> >> >> From: members-discuss <members-discuss-bounces(a)ripe.net> on behalf of Phillip Oldham <poldham(a)ripe.net> >> Date: Friday, 19 January 2024 at 12:18 >> To: members-discuss(a)ripe.net <members-discuss(a)ripe.net> >> Subject: [members-discuss] The redesigned www.ripe.net is now live >> >> [EXTERNAL EMAIL] Please use caution when opening attachments from unrecognised sources. >> >> Dear colleagues, >> >> If you visit www.ripe.net <http://www.ripe.net/> today, you might notice some changes. For the past few months, we’ve been working on redesigning ripe.net, and we released the new version yesterday at approximately 18:00 UTC+1. >> >> Here are some of the major changes: >> • The design of the website has changed >> • The content management system has been changed from Plone to Wagtail >> • We migrated servers to make this switch >> • The website is now significantly more mobile and tablet friendly >> • We are using a new search engine on the website, so search results should be more relevant, and we will be investing time to make this experience even better >> • Accessibility has been improved, and we aim to align with WCAG 2.1 standards as soon as possible >> • Visitors should see some performance improvements, and we aim to continue adding improvements for usability and energy efficiency >> • The RIPE community is more prominent and easy to access from the top-level navigation under “community”, and we are applying a new community design to community-related pages: >> https://www.ripe.net/community/ >> >> The overall navigation of the website has not been significantly altered to ensure a smooth transition. We will be making more changes to the navigation to improve readability and discoverability. >> >> Many of you shared input in a survey and some of you joined us for user interviews at RIPE 86 and for conversations following my presentation at RIPE 87. Thank you for helping us through this process. >> >> While we have launched the newly redesigned website, with over 8,000 web pages migrated to the new platform, we know there will be fixes and tweaks needed in the weeks to come. If you notice any issues or have feedback, please let us know on the forum: >> https://forum.ripe.net/t/www-ripe-net-redesign-is-live/820 >> >> For anything urgent, please email us at webmaster(a)ripe.net >> >> Kind regards, >> >> Phillip Oldham (he/him) <poldham(a)ripe.net> >> Manager, Web Services >> RIPE NCC >> Stationsplein 11, 1012 AB Amsterdam >> >> >> _______________________________________________ >> 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/michele%40blacknight… >> _______________________________________________ >> 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/support%40c1vhosting…

5 4

Re: [members-discuss] [ncc-services-wg] The redesigned www.ripe.net is now live
by Petrit Hasani 22 Jan '24

22 Jan '24

Dear Randy, Thank you for your report. We have investigated the reported issue. The issue is not as a result of the recent work carried out on the new ripe.net <http://ripe.net/> website. Your AS number submission receives an error due to the “AS-“ prefix which is not allowed to be used in an as-name. The “AS-“ prefix is is a reserved prefix for AS SET in accordance with RFC 2622: Routing Policy Specification Language (RPSL): https://datatracker.ietf.org/doc/html/rfc2622#section-2 RFC 2622: Routing Policy Specification Language (RPSL) datatracker.ietf.org The error message received in the request form does not properly clarify it, creating confusion, so we will look to fix it as soon as possible. Please do not hesitate to contact us if you have any questions or concerns. Kind regards, Petrit Hasani RIPE NCC > On 22 Jan 2024, at 16:12, Petrit Hasani <phasani(a)ripe.net> wrote: > > Dear Randy, > > Thank you for reporting the bug. > > We will look into it and hope to resolve it as soon as possible. > > I will contact you once a fix has been deployed. > > Please do not hesitate to contact us if you have any other questions or concerns. > > Kind regards, > > Petrit Hasani > RIPE NCC > >> On 20 Jan 2024, at 21:28, Randy Bush <randy(a)psg.com <mailto:randy@psg.com>> wrote: >> >>> Date: Fri, 19 Jan 2024 13:16:42 +0100 >>> If you visit www.ripe.net today, you might notice some changes. >> >> deploy on friday afternoon and go home for the weekend. i think that is >> covered pretty early in the textbook. >> >> <ripe-asn.jpg> >> which i can fudge past by skipping the hyphens, but then i submit the AS >> allocation form and get >> >> <ripe-ouch.jpg> >> was a show stopper. and it reproduces. with safari and firefox. and >> when i go to re-do, it has not saved the data i entered. >> >> randy-- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ncc-services-wg

2 2

two-factor authentication mandatory
by Mike B 22 Jan '24

22 Jan '24

Hello, I agree completely with the use of 2FA and do agree with the spirit of this being mandatory. However the current state of RIPE NCC MFA is not suitable to be made mandatory. Namely the TOTP requires a phone (sms) or TOTP App. I would like to see support for FIDO2 keys, if this is not possible OTP via email would be a compromise. My rational for this is that some organisations do not allow phones within the office, nor have any Apps available to install on their systems. Perhaps a more generic scenario is if a phone is out of battery. I'm sure you can appreciate while I am in favour of MFA I think this must be in a different format. I'm aware this is a feature many have been keen for for a while. I see two ways forward: 1) RIPE supports another method of MFA (FIDO KEYS or emailed OTP). 2) RIPE makes Mandatory MFA the choice of the LIR admin. I would like to hear other views on this request to the RIPE NCC. I am not looking for suggestions for workarounds such as online TOTP or writing my own code for this. Regards, Michael

13 14

[Ticket #675089] Re: The redesigned www.ripe.net is now live
by FlexiScale Flexiscale Support 21 Jan '24

21 Jan '24

Franziska Kunsmann, Thank you for request. We will be in touch shortly. SUBJECT: Re: [members-discuss] The redesigned www.ripe.net is now live STATUS: Open http://myservices.flexiscale.com/?cmd=tickets&action=view&num=675089&hash=s…

1 0

Re: [members-discuss] [ncc-services-wg] The redesigned www.ripe.net is now live
by Randy Bush 20 Jan '24

20 Jan '24

> Date: Fri, 19 Jan 2024 13:16:42 +0100 > If you visit www.ripe.net today, you might notice some changes. deploy on friday afternoon and go home for the weekend. i think that is covered pretty early in the textbook. which i can fudge past by skipping the hyphens, but then i submit the AS allocation form and get was a show stopper. and it reproduces. with safari and firefox. and when i go to re-do, it has not saved the data i entered. randy

1 1

Re: [members-discuss] two-factor authentication mandatory
by Oleksij Samorukov 11 Jan '24

11 Jan '24

On 2024/01/11 14:48, Mark Janssen via members-discuss wrote: > On Thu, 2024-01-11 at 14:35 +0100, Mike B wrote: >> My rational for this is that some organisations do not allow phones >> within the office, nor have any Apps available to install on their >> systems. Perhaps a more generic scenario is if a phone is out of >> battery. I'm sure you can appreciate while I am in favour of MFA I >> think this must be in a different format. > > TOTP can be done without phones or phone apps... it just needs the > shared secret and a HMAC fucntion, this can be done via various > password-managers, simple python-scripts, your Ti-81 calculator or any > number of other methods. > > I would advise against any form of e-mail 2fa, as this really reduces > it to a single-factor (with password-resets via email). BTW, TOTP is supported by a recent Yubi key, so you can use it as a hardware token as well. But +1 for FIDO2 implementation, is a very popular standard with many implementations on the market. And it should be easy to implement on the backend/frondent side, implementation is very straightforward with many examples all-around. -- Oleksij Samorukov

1 0