- ncc-services-wg - mailman.ripe.net

Re: [ncc-services-wg] ripe-694
by Athina Fragkouli 23 Jan '18

23 Jan '18

Dear Nick, The document ripe-694, "RIPE NCC Audit Activity" is a RIPE NCC organisational document that was updated to accurately reflect how we currently deal with this activity. The document is not a policy document but was drafted by the RIPE NCC and approved by the Executive Board. All documents of this type are published in the RIPE Document Store for transparency and clarity. They are all listed at: https://www.ripe.net/publications/docs/ripe-documents/ripe-ncc-organisation… We outline the process for adopting these RIPE NCC organisational documents at: https://www.ripe.net/about-us/legal/corporate-governance/adoption-process-f… The relevant Executive Board minutes noting the proposal to update the RIPE NCC Audit Activity and the Board's approval of the document are also published: https://www.ripe.net/about-us/executive-board/minutes/2017/minutes-113th-ex… https://www.ripe.net/about-us/executive-board/minutes/2017/minutes-115th-ex… If you have further questions on this process, please let me know. Best regards, Athina Fragkouli Head of Legal RIPE NCC ------ Subject: [ncc-services-wg] ripe-694 Date: Mon, 22 Jan 2018 21:56:11 +0000 From: Nick Hilliard <nick(a)netability.ie> Organisation: Island Bridge Networks To: ncc-services-wg(a)ripe.net <ncc-services-wg(a)ripe.net> Was there any discussion in the ripe community about ripe-694 before it became a ripe document? Nick

1 0

ripe-694
by Nick Hilliard 22 Jan '18

22 Jan '18

Was there any discussion in the ripe community about ripe-694 before it became a ripe document? Nick

1 0

Re: [ncc-services-wg] invoice for NCC services
by Sonia Garbi Gomez 19 Jan '18

19 Jan '18

Dear Sergey, Thank you for your email. With over 17,500 invoices to send, the RIPE NCC has to work hard to ensure everything is ready to go at the same time. Despite our best intentions, a software bug meant that LIRs that require a special Russian invoice were sent their invoices four days early. While the invoices were available in the LIR Portal on 15 January, the intention was to distribute them to members on 19 January 2018, as stated in the RIPE NCC Billing Procedure 2018: <https://www.ripe.net/participate/member-support/payment/billing-procedure-a…> But rest assured, the 30-day payment term is from the date stated on the invoice - 19 January 2018. We apologise for any confusion this may have caused but hope that the unintended bonus of an extra four days to pay is a silver lining. Warm regards and have a lovely weekend, Sonia Garbi Gomez Finance Manager RIPE NCC >>> *From:* Sergey Myasoedov via ncc-services-wg >>> <ncc-services-wg(a)ripe.net <mailto:ncc-services-wg@ripe.net>> >>> *Date:* 18 January 2018 at 16:31:21 CET >>> *To:* ncc-services-wg(a)ripe.net <mailto:ncc-services-wg@ripe.net> >>> *Subject:* *[ncc-services-wg] invoice for NCC services* >>> *Reply-To:* Sergey Myasoedov <sergey(a)devnull.ru >>> <mailto:sergey@devnull.ru>> >>> >>> >>> >>> It was very nice to receive the invoice for membership/services of >>> the NCC on Monday, 15th >>> January. >>> >>> But why the date of the invoice is set to Friday, 19.1.2018? >>> >>> >>> -- >>> Kind regards, >>> Sergey Myasoedov >>> >>>

1 0

invoice for NCC services
by Sergey Myasoedov 18 Jan '18

18 Jan '18

(previous mail to members-discuss list probably was moderated) It was very nice to receive the invoice for membership/services of the NCC on Monday, 15th January. But why the date of the invoice is set to Friday, 19.1.2018? -- Kind regards, Sergey Myasoedov

1 0

DMARC Solution Applied to this Mailing List
by Adam Castle 18 Dec '17

18 Dec '17

Dear Working Group, As more email providers enable Domain Message Authentication Reporting & Conformance (DMARC), some people find they can no longer receive emails from the mailing lists they are subscribed to. We have deployed a Mailman setting change to address this problem. After consultation with the RIPE Working Group Chairs, we have enabled the DMARC "Munge From" setting on all RIPE mailing lists. This means that if your email service provider has DMARC enabled, you will continue to receive all emails sent to this mailing list, but the "From" part of the header will change. If you don't have DMARC enabled, you won't see any change to the emails you receive from this mailing list. You can find more information about how we have been handling DMARC in the following RIPE Labs articles: https://labs.ripe.net/Members/adam_castle/dmarc-and-the-ripe-ncc https://labs.ripe.net/Members/adam_castle/ripe-mailing-lists-and-dmarc To ensure all working group participants are aware of the changes, I am sending this mail to all working groups. If you have any questions or encounter any issues on this mailing list, please let me know. Many thanks. Adam Castle Web Services Manager RIPE NCC

1 0

New on RIPE Labs: How We're Implementing the GDPR
by Mirjam Kuehne 21 Nov '17

21 Nov '17

Dear colleagues, This is the first in a series of articles we plan to publish on RIPE Labs over the coming weeks and months, each of which will provide details of any legal analysis we perform in the implementation of the GDPR in the RIPE Database, and any other RIPE NCC services: https://labs.ripe.net/Members/Athina/how-we-re-implementing-the-gdpr Kind regards, Mirjam Kühne RIPE NCC

1 0

RIPE NCC hosted RPKI Validator instance?
by Job Snijders 02 Nov '17

02 Nov '17

Dear RIPE community, NCC, Oftentimes I use the RIPE NCC RPKI Validator instance hosted at http://localcert.ripe.net:8088/ for doing simple analysis and debugging. Often it is too much work to spin up a dedicated RPKI Validator instance. For this type of work all I usually need is the JSON dump which I fetch at http://localcert.ripe.net:8088/export.json Questions: a) can RIPE NCC commit to keeping an RPKI Validator instance up and running and relatively stable at a stable URL? b) Can the service be made available _only_ over HTTPS? Kind regards, Job

2 2

RIPE NCC Community Projects Fund Selection Committee Chosen
by Axel Pawlik 02 Oct '17

02 Oct '17

Dear colleagues, We are pleased to announce the names of the first RIPE NCC Community Projects Fund Selection Committee. Chosen from a list of submitted nominations by the RIPE NCC Executive Board, the community members are: Nuno Garcia Mieke van Heesewijk Andreas Larson They will join Salam Yamout from the RIPE NCC Executive Board to complete the selection committee. The Executive Board sincerely thanks all those who put themselves forward to be on the committee and warmly welcome the new committee members. The committee is responsible for reviewing applications for projects supporting Internet resilience and operations from late November until late December 2017. These members have committed to serving a minimum term of one year (and a maximum of three) to ensure continuity. The call for funding applications opens on Sunday, 22 October and the Fund will be formally introduced in the RIPE NCC Services Working Group session at RIPE 75 in Dubai. More information on the Fund can be found at: <https://www.ripe.net/support/cpf/ripe-ncc-community-projects-fund> Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Draft Agenda RIPE75 - NCC Services Working Group
by Bijal Sanghani 11 Sep '17

11 Sep '17

Dear all, Below and shortly online you can find the NCC Services working group draft agenda, any additions or comments please let me know. Best regards, NCC Services working group chairs === Date: Tuesday 24 October 2017 Time: 16:00 - 17:45 local time Chair: Kurtis Lindqvist co-Chair: Bijal Sanghani A. Administrative Matters (5 minutes) Welcome Select a scribe Finalise agenda Approve minutes from RIPE 74 B. NCC Services Working Group Elections - Bijal Sanghani, NCC Services working group co-chair (5 minutes) C. RIPE NCC Outlook 2017-2018 - Axel Pawlik, RIPE NCC (15 minutes) D. RIPE NCC Operational Update - Andrew de la Haye, RIPE NCC (15 minutes) E. RIPE NCC Training Developments - Rumy Kanis, RIPE NCC (15 minutes) F. RIPE NCC Community Projects Fund - Paul Rendek, RIPE NCC (15 minutes) G. RIPE Atlas Update - Kaveh Ranjbar, RIPE NCC (15 minutes) H. Open Microphone Session Z. AOB

1 0

Members-discuss complaints
by Sander Steffann 06 Sep '17

06 Sep '17

Hi all, The amount of people complaining on the members-discuss list that they never signed up for it makes me wonder how they ended up here. You'd expect that if an organisation became a RIPE NCC member and provided an email address to add to the members-discuss list that the person using that address would know about it. But I get the feeling that most of the people complaining have no idea what the RIPE NCC is, so why would someone at their company sign them up for the members-discuss list?!? From what I can see in the LIR portal there is no confirmation of the email address when adding someone to the list. Just log in to the LIR portal, add an address and "Members discussion subscription added successfully". Could it be that some malignant LIRs are adding random addresses to the list? You'd hope that all LIRs behave responsibly, but I guess that might be too optimistic. In any case, I'd like the RIPE NCC to check the email addresses of those who complain that they never wanted to be on this list. Check which LIR added them, when they were added, whether there seems to be some relationship between the LIR and the email address etc. Either those people should have a discussion inside their own organisation on signing up unwitting colleagues to mailing lists, or there are actually malignant LIRs that the RIPE NCC seriously needs to talk to. See what we can learn from this. I do hope that Hanlon's razor still applies :) In either case: may I suggest the NCC implements a confirm system where people are only added to the members-discuss list after confirming that they actually want to be on it? The current implementation of trusting that what is entered in the LIR portal interface is with consent of the user of the email address apparently is too surprising for some of the users (and yes, I do realise that the number of intentional users is much higher than the number of complainers, but lets try to minimise the latter category) Cheers! Sander

8 11