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

Call for Agenda Items RIPE76 - RIPE NCC Services WG
by Bijal Sanghani 11 Apr '18

11 Apr '18

Dear NCC-Services WG, RIPE76 is fast approaching and we have a few spaces free on the agenda. If you would like to suggest a topic for discussion or have a presentation you have or would like to see presented please get in touch with the working group chairs at ncc-services-wg-chairs(a)ripe.net <mailto:ncc-services-wg-chairs@ripe.net>. Remember, this is your opportunity to let the RIPE NCC know what you want from them :) Best regards, RIPE NCC Services WG Chairs

1 0

NCC Services WG - Draft Minutes RIPE 75
by Bijal Sanghani 22 Mar '18

22 Mar '18

Dear All, The draft minutes from the NCC Services WG at RIPE 75 are now available online: https://www.ripe.net/participate/ripe/wg/services/minutes/ripe-75-ripe-ncc-… Please feel free to send comments to either myself, Kurtis or the mailing list. Kind regards, NCC Services WG Chairs

1 0

Update of RIPE NCC Procedural Document
by Athina Fragkouli 08 Feb '18

08 Feb '18

Dear colleagues, The RIPE NCC Procedural document, “Closure of Members, Deregistration of Internet Resources, and Legacy Resources” has recently been reviewed and updated. The document has been updated to ensure it is consistent with changes to the Articles of Association (AoA) that were approved by the RIPE NCC General Meeting (GM) in October 2017. The changes to the procedural document specify that once we have begun the closure procedure for a member, and RIPE NCC services have been suspended, the membership will also be suspended. More information is available in the GM supporting documents here: https://www.ripe.net/participate/meetings/gm/meetings/october-2017/updated-… Please see here the updated document here: https://www.ripe.net/publications/docs/ripe-697/ Kind regards, Athina Fragkouli Head of Legal RIPE NCC

1 0

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