From ripencc-management at ripe.net Mon Oct 2 18:04:07 2017 From: ripencc-management at ripe.net (Axel Pawlik) Date: Mon, 2 Oct 2017 18:04:07 +0200 Subject: [ncc-services-wg] RIPE NCC Community Projects Fund Selection Committee Chosen Message-ID: 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: Regards, Axel Pawlik Managing Director RIPE NCC From job at ntt.net Sat Oct 28 12:49:55 2017 From: job at ntt.net (Job Snijders) Date: Sat, 28 Oct 2017 12:49:55 +0200 Subject: [ncc-services-wg] RIPE NCC hosted RPKI Validator instance? Message-ID: <20171028104955.GB44257@Vurt.local> 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 From tim at ripe.net Sat Oct 28 21:15:21 2017 From: tim at ripe.net (Tim Bruijnzeels) Date: Sat, 28 Oct 2017 21:15:21 +0200 Subject: [ncc-services-wg] RIPE NCC hosted RPKI Validator instance? In-Reply-To: <20171028104955.GB44257@Vurt.local> References: <20171028104955.GB44257@Vurt.local> Message-ID: <4B7C2627-5A11-451B-B968-A32021132A56@ripe.net> Dear Job, We recommend that people run a local validator instance for production purposes. The instance on http://localcert.ripe.net:8088/ is our bleeding edge code, but we are more than happy to look into hosting a stable release on a stable httpS url. Kind regards Tim Bruijnzeels RIPE NCC > On 28 Oct 2017, at 12:49, Job Snijders wrote: > > 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 > >