From denis at ripe.net Thu Mar 6 17:15:16 2014 From: denis at ripe.net (Denis Walker) Date: Thu, 06 Mar 2014 17:15:16 +0100 Subject: [ncc-services-wg] RIPE Database Release 1.72 - including SSO Integration Message-ID: <53189F14.5030902@ripe.net> Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team From training at ripe.net Tue Mar 11 13:01:50 2014 From: training at ripe.net (Training Services) Date: Tue, 11 Mar 2014 13:01:50 +0100 Subject: [ncc-services-wg] [training] RIPE NCC Webinars - new dates Message-ID: <531EFB2E.2030402@ripe.net> Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email . We look forward to seeing you online. Kind regards, RIPE NCC Training Services From npediaditi at ripe.net Wed Mar 12 16:52:09 2014 From: npediaditi at ripe.net (Nikolas Pediaditis) Date: Wed, 12 Mar 2014 16:52:09 +0100 Subject: [ncc-services-wg] Implementation plan for 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders" Message-ID: Dear colleagues, The RIPE NCC has published the proposed implementation plan for ripe-605 "RIPE NCC Services to Legacy Internet Resource Holders" (accepted policy proposal 2012-07): The overall implementation: https://labs.ripe.net/Members/nikolas_pediaditis/policy-proposal-2012-07-ripe-ncc-services-to-legacy-internet-resource-holders-proposed-implementation-plan The implementation that specifically relates to the RIPE Database: https://labs.ripe.net/Members/xavier/policy-proposal-2012-07-db-proposed-implementation-plan We are sending this email to three working groups because the implementation is related to anyone holding AUT-NUM or legacy INETNUM objects in the RIPE Database but we ask that comments be made on the RIPE NCC Services Working Group mailing list only. We aim to begin implementation the week of 25 March. Please do not hesitate to contact us if you have any comments or questions. Kind regards, Nikolas Pediaditis IP Resource Analyst RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: From training at ripe.net Fri Mar 14 15:46:10 2014 From: training at ripe.net (Training Services) Date: Fri, 14 Mar 2014 15:46:10 +0100 Subject: [ncc-services-wg] [training] RIPE NCC Courses in Sofia, Bulgaria 16-17 April 2014 Message-ID: <53231632.4030504@ripe.net> Dear Colleagues, The RIPE NCC Training Services Department invites you to register for our upcoming Training Courses in Sofia, Bulgaria: Course type: RIPE Database Training Course Date: Wednesday, 16 April 2014 Time: 09:00-17:30 Course type: IPv6 for LIRs Training Course Date: Thursday, 17 April 2014 Time: 09:00-17:30 How to register: ---------------- You can register up to two people from your LIR for each course by using the LIR Portal at: https://lirportal.ripe.net/training/courses Registration will close when maximum capacity is reached, so please register soon to ensure your attendance. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. RIPE Database Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region. You can find more information about the course at: https://www.ripe.net/lir-services/training/courses/rdb IPv6 for LIRs Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region and if you: * Are thinking about deploying IPv6 in your organisation * Have been told you need to deploy IPv6 * Need to convince your manager that IPv6 needs to be deployed * Looked at an IPv6 address and thought it was too complicated to deploy in your network You can find more information about the course at: http://www.ripe.net/lir-services/training/courses/ipv6 If you have any questions, send an e-mail to . Kind regards, RIPE NCC Training Services From BECHA at ripe.net Tue Mar 18 13:58:03 2014 From: BECHA at ripe.net (Vesna Manojlovic) Date: Tue, 18 Mar 2014 13:58:03 +0100 Subject: [ncc-services-wg] The Beta Version of the New DNSMON is Now Available In-Reply-To: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> Message-ID: <532842DB.7000306@ripe.net> Dear colleagues, The DNS Monitoring Service (DNSMON) has been providing a comprehensive, objective and up-to-date overview of the quality of various global and regional DNS operators' services since 2003. We are in the process of integrating DNSMON within RIPE Atlas and the beta version of the new DNSMON is now publicly available: https://atlas.ripe.net/dnsmon We have also published a RIPE Labs article detailing what?s changed in the new DNSMON: https://labs.ripe.net/Members/fatemah_mafi/an-updated-dns-monitoring-service We invite you all to try the new service and provide your feedback. We?re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. Please send your comments and questions to the DNS Working Group Mailing List at dns-wg at ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC From jaap at NLnetLabs.nl Wed Mar 19 11:49:57 2014 From: jaap at NLnetLabs.nl (Jaap Akkerhuis) Date: Wed, 19 Mar 2014 11:49:57 +0100 Subject: [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available In-Reply-To: <532842DB.7000306@ripe.net> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> Message-ID: <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> We invite you all to try the new service and provide your feedback. We?re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. It doesn't come anywhere close to the old service. E.g., the functionality of is missing. The UI page is garbled. All in all this is pretty bad. jaap From robert at ripe.net Wed Mar 19 12:11:39 2014 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 19 Mar 2014 12:11:39 +0100 Subject: [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available In-Reply-To: <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> Message-ID: <53297B6B.7010500@ripe.net> Dear Jaap, On 2014.03.19. 11:49, Jaap Akkerhuis wrote: > > We invite you all to try the new service and provide your feedback. > We?re confident that the new DNSMON will continue to meet your needs and > hope that you'll be happy with the new features. > > It doesn't come anywhere close to the old service. E.g., the functionality > of is missing. This server view exists in the new implementation too. One can reach it from the zone view, by clicking on the name on a particular server. We prepared for this use case since people are mostly interested in the servers of a (their) particular zone, not an alphabetical list. That said, we can make such a listing page if there's a need for it. > The UI page is garbled. That was an oops, but it is fixed already. Regards, Robert > All in all this is pretty bad. > > > jaap > > From Brett.Carr at nominet.org.uk Wed Mar 19 11:57:51 2014 From: Brett.Carr at nominet.org.uk (Brett Carr) Date: Wed, 19 Mar 2014 10:57:51 +0000 Subject: [ncc-services-wg] [dnsmon-contact] [dnsmon-user] The Beta Version of the New DNSMON is Now Available In-Reply-To: <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> Message-ID: <2485CD86D7C59E4C99BA16B2B5754E2024E6DF@wds-exc2.okna.nominet.org.uk> Jaap, > -----Original Message----- > From: dnsmon-contact-bounces at ripe.net [mailto:dnsmon-contact- > bounces at ripe.net] On Behalf Of Jaap Akkerhuis > Sent: Wednesday, March 19, 2014 10:50 AM > To: Vesna Manojlovic > Cc: ncc-services-wg at ripe.net; dns-wg at ripe.net; RIPE Atlas People; > dnsmon-contact at ripe.net; dnsmon-user at ripe.net; Measurement Analysis and > Tools Working Group > Subject: Re: [dnsmon-contact] [dnsmon-user] The Beta Version of the New > DNSMON is Now Available > > > > We invite you all to try the new service and provide your feedback. > We're confident that the new DNSMON will continue to meet your > needs and > hope that you'll be happy with the new features. > > It doesn't come anywhere close to the old service. E.g., the > functionality of is > missing. > That's what I thought at first but actually it is there it just takes a little finding. Click on the TLD and you will get a list of servers down the left, if you then click on a server you will get something that looks very similar to the old server view. There are two things that I would really like to see: 1. The ability to pull some data out and pull it in to my own monitoring system for a familiar view for our operations engineers. 2. An ability to provide sms/e-mail alerting depending on certain (user definable) conditions. Brett Nominet UK. From Brett.Carr at nominet.org.uk Wed Mar 19 12:02:03 2014 From: Brett.Carr at nominet.org.uk (Brett Carr) Date: Wed, 19 Mar 2014 11:02:03 +0000 Subject: [ncc-services-wg] [dns-wg] [dnsmon-contact] [dnsmon-user] The Beta Version of the New DNSMON is Now Available {Sender Address Possibly Forged} In-Reply-To: <2485CD86D7C59E4C99BA16B2B5754E2024E6DF@wds-exc2.okna.nominet.org.uk> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> <2485CD86D7C59E4C99BA16B2B5754E2024E6DF@wds-exc2.okna.nominet.org.uk> Message-ID: <2485CD86D7C59E4C99BA16B2B5754E2024E8FF@wds-exc2.okna.nominet.org.uk> > -----Original Message----- > From: dns-wg-bounces at ripe.net [mailto:dns-wg-bounces at ripe.net] On > Behalf Of Brett Carr > Sent: Wednesday, March 19, 2014 10:58 AM > To: Jaap Akkerhuis; Vesna Manojlovic > Cc: ncc-services-wg at ripe.net; dns-wg at ripe.net; RIPE Atlas People; > dnsmon-contact at ripe.net; dnsmon-user at ripe.net; Measurement Analysis and > Tools Working Group > Subject: Re: [dns-wg] [dnsmon-contact] [dnsmon-user] The Beta Version > of the New DNSMON is Now Available {Sender Address Possibly Forged} > 2. An ability to provide sms/e-mail alerting depending on certain (user > definable) conditions. To be slightly more specific, https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atlas-status-checks Something more DNS specific but similar to the above would be very useful. Brett From denis at ripe.net Mon Mar 24 14:27:39 2014 From: denis at ripe.net (Denis Walker) Date: Mon, 24 Mar 2014 14:27:39 +0100 Subject: [ncc-services-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <53189F14.5030902@ripe.net> References: <53189F14.5030902@ripe.net> Message-ID: <533032CB.2060005@ripe.net> Dear Colleagues The RIPE Database release 1.72 has now been fully deployed to production. We would like to point out that, with this release, Webupdates and Syncupdates can only be accessed with HTTPS and not with HTTP. This is to conform to the requirements of using RIPE ACCESS now as an authentication method for updating the RIPE Database. Any update using HTTP will be automatically redirected to HTTPS. Regards Denis Walker Business Analyst RIPE NCC Database Team -------- Original Message -------- Subject: RIPE Database Release 1.72 - including SSO Integration Date: Thu, 06 Mar 2014 17:15:16 +0100 From: Denis Walker Organization: RIPE NCC To: Database WG , NCC Services WG Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From gert at space.net Mon Mar 24 21:56:19 2014 From: gert at space.net (Gert Doering) Date: Mon, 24 Mar 2014 21:56:19 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <533032CB.2060005@ripe.net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> Message-ID: <20140324205619.GG43641@Space.Net> Hi, On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote: > The RIPE Database release 1.72 has now been fully deployed to production. > > We would like to point out that, with this release, Webupdates and > Syncupdates can only be accessed with HTTPS and not with HTTP. This is > to conform to the requirements of using RIPE ACCESS now as an > authentication method for updating the RIPE Database. Any update using > HTTP will be automatically redirected to HTTPS. Uh, what? This does not *exactly* meet POLA, and that part of the change was not announced as such - and as it's quite likely that this breaks someone's syncupdate script (why would a syncupdate client be written to handle http->https redirects if all it wants is a single POST?) this really should have been announced before. ... and I'm less than convinced that wanting to have HTTPS *for RIPE ACCESS* is a good reason to force it by surprise on everyone else. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From sander at steffann.nl Mon Mar 24 23:26:14 2014 From: sander at steffann.nl (Sander Steffann) Date: Mon, 24 Mar 2014 23:26:14 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <20140324205619.GG43641@Space.Net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140324205619.GG43641@Space.Net> Message-ID: Hi, > This does not *exactly* meet POLA, and that part of the change was not > announced as such - and as it's quite likely that this breaks someone's > syncupdate script (why would a syncupdate client be written to handle > http->https redirects if all it wants is a single POST?) this really should > have been announced before. I fully agree. Making https mandatory for updates is a change in the public interface to the DB and it should have been announced. Denis: can you gather some stats on how many POSTs are sent over http, get a redirect, and then don't retry over https? It would give a rough estimate of how many scripts can't handle the redirect. Cheers, Sander From Piotr.Strzyzewski at polsl.pl Tue Mar 25 08:26:29 2014 From: Piotr.Strzyzewski at polsl.pl (Piotr Strzyzewski) Date: Tue, 25 Mar 2014 08:26:29 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <533032CB.2060005@ripe.net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> Message-ID: <20140325072629.GA19555@hydra.ck.polsl.pl> On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote: Dear Denis > The RIPE Database release 1.72 has now been fully deployed to production. Could you please specify, when the new version of RIPE Database Update Reference Manual will be available online? > We would like to point out that, with this release, Webupdates and > Syncupdates can only be accessed with HTTPS and not with HTTP. This is to > conform to the requirements of using RIPE ACCESS now as an authentication > method for updating the RIPE Database. Any update using HTTP will be > automatically redirected to HTTPS. And this is good example of what I was trying to avoid when we were discussing being over cautious with changing something just a week ago. Piotr -- gucio -> Piotr Strzy?ewski E-mail: Piotr.Strzyzewski at polsl.pl From agoston at ripe.net Tue Mar 25 09:43:21 2014 From: agoston at ripe.net (Agoston Horvath) Date: Tue, 25 Mar 2014 09:43:21 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <20140324205619.GG43641@Space.Net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140324205619.GG43641@Space.Net> Message-ID: <533141A9.4060206@ripe.net> Dear colleagues, Let me clarify. Denis was referring to the web forms, that are also named 'syncupdates' and 'webupdates'. The actual syncupdates service did not change. Furthermore, the syncupdates and webupdates web forms were already enforcing https because of sensitive authentication data (e.g. passwords). The only change that happened yesterday was that now we also enforce https on the query form, so that the RIPE Access session token is secured. Sorry for the misunderstanding. Kind regards, Agoston Horvath Senior Software Engineer RIPE NCC On 03/24/2014 09:56 PM, Gert Doering wrote: > Hi, > > On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote: >> The RIPE Database release 1.72 has now been fully deployed to production. >> >> We would like to point out that, with this release, Webupdates and >> Syncupdates can only be accessed with HTTPS and not with HTTP. This is >> to conform to the requirements of using RIPE ACCESS now as an >> authentication method for updating the RIPE Database. Any update using >> HTTP will be automatically redirected to HTTPS. > > Uh, what? > > This does not *exactly* meet POLA, and that part of the change was not > announced as such - and as it's quite likely that this breaks someone's > syncupdate script (why would a syncupdate client be written to handle > http->https redirects if all it wants is a single POST?) this really should > have been announced before. > > ... and I'm less than convinced that wanting to have HTTPS *for RIPE > ACCESS* is a good reason to force it by surprise on everyone else. > > Gert Doering > -- NetMaster > From gert at space.net Tue Mar 25 09:55:23 2014 From: gert at space.net (Gert Doering) Date: Tue, 25 Mar 2014 09:55:23 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <533141A9.4060206@ripe.net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140324205619.GG43641@Space.Net> <533141A9.4060206@ripe.net> Message-ID: <20140325085523.GL43641@Space.Net> Hi, On Tue, Mar 25, 2014 at 09:43:21AM +0100, Agoston Horvath wrote: > Denis was referring to the web forms, that are also named 'syncupdates' and 'webupdates'. > The actual syncupdates service did not change. > > Furthermore, the syncupdates and webupdates web forms were already enforcing https because of sensitive authentication data (e.g. passwords). The only change > that happened yesterday was that now we also enforce https on the query form, so that the RIPE Access session token is secured. Thanks for the clarification. This is far less intrusive than the original mail made me believe, and I think it's a reasonable change which should not have any adverse effects. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: From sander at steffann.nl Tue Mar 25 10:23:28 2014 From: sander at steffann.nl (Sander Steffann) Date: Tue, 25 Mar 2014 10:23:28 +0100 Subject: [ncc-services-wg] [db-wg] RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <20140325085523.GL43641@Space.Net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140324205619.GG43641@Space.Net> <533141A9.4060206@ripe.net> <20140325085523.GL43641@Space.Net> Message-ID: <0DD9F1F1-BDD1-4493-8D1B-5D9762AAD615@steffann.nl> Hi, Op 25 mrt. 2014, om 09:55 heeft Gert Doering het volgende geschreven: > Hi, > > On Tue, Mar 25, 2014 at 09:43:21AM +0100, Agoston Horvath wrote: >> Denis was referring to the web forms, that are also named 'syncupdates' and 'webupdates'. >> The actual syncupdates service did not change. >> >> Furthermore, the syncupdates and webupdates web forms were already enforcing https because of sensitive authentication data (e.g. passwords). The only change >> that happened yesterday was that now we also enforce https on the query form, so that the RIPE Access session token is secured. > > Thanks for the clarification. This is far less intrusive than the original > mail made me believe, and I think it's a reasonable change which should > not have any adverse effects. I fully agree. Thanks for the clarification! Sander From denis at ripe.net Tue Mar 25 16:26:35 2014 From: denis at ripe.net (Denis Walker) Date: Tue, 25 Mar 2014 16:26:35 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <20140325072629.GA19555@hydra.ck.polsl.pl> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140325072629.GA19555@hydra.ck.polsl.pl> Message-ID: <5331A02B.8080304@ripe.net> Dear Piotr The new versions of both the Update and Query Reference Manuals in PDF format were available on the www.ripe.net website yesterday. The html version of the new Query Reference Manual is now also available. They both include details of the new SSO auth option. Regards Denis Walker Business Analyst RIPE NCC Database Team On 25/03/2014 08:26, Piotr Strzyzewski wrote: > On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote: > > Dear Denis > >> The RIPE Database release 1.72 has now been fully deployed to production. > Could you please specify, when the new version of RIPE Database Update > Reference Manual will be available online? > >> We would like to point out that, with this release, Webupdates and >> Syncupdates can only be accessed with HTTPS and not with HTTP. This is to >> conform to the requirements of using RIPE ACCESS now as an authentication >> method for updating the RIPE Database. Any update using HTTP will be >> automatically redirected to HTTPS. > And this is good example of what I was trying to avoid when we were > discussing being over cautious with changing something just a week ago. > > Piotr > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Piotr.Strzyzewski at polsl.pl Tue Mar 25 21:32:40 2014 From: Piotr.Strzyzewski at polsl.pl (Piotr Strzyzewski) Date: Tue, 25 Mar 2014 21:32:40 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <5331A02B.8080304@ripe.net> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140325072629.GA19555@hydra.ck.polsl.pl> <5331A02B.8080304@ripe.net> Message-ID: <20140325203240.GB9452@hydra.ck.polsl.pl> On Tue, Mar 25, 2014 at 04:26:35PM +0100, Denis Walker wrote: Dear Denis > The new versions of both the Update and Query Reference Manuals in PDF > format were available on the www.ripe.net website yesterday. The html > version of the new Query Reference Manual is now also available. They both > include details of the new SSO auth option. Just to excuse myself - the very first sentence in RIPE Database Update Reference Manual (http://www.ripe.net/data-tools/support/documentation/upd-ref-manual) is: "This document describes how to update version 1.71 of the RIPE Database.". I didn't checked the rest of the document. ;-) However, the footers on every page states it is from the version 1.72. Honestly speaking, if this PDF is somehow autogenerated, isn't that obvious to define the version number and then use it everywhere? This is just a rhetorical question. Just to note: The Query Reference Manual (both html and PDF) last updated (according to the webpage and your statement above) on 25 Mar 2014 says: "This document describes how queries work in version 1.68 of the RIPE Database." Piotr -- gucio -> Piotr Strzy?ewski E-mail: Piotr.Strzyzewski at polsl.pl From jahlen at ripe.net Wed Mar 26 09:26:29 2014 From: jahlen at ripe.net (=?utf-8?Q?Johan_=C3=85hl=C3=A9n?=) Date: Wed, 26 Mar 2014 09:26:29 +0100 Subject: [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration In-Reply-To: <20140325203240.GB9452@hydra.ck.polsl.pl> References: <53189F14.5030902@ripe.net> <533032CB.2060005@ripe.net> <20140325072629.GA19555@hydra.ck.polsl.pl> <5331A02B.8080304@ripe.net> <20140325203240.GB9452@hydra.ck.polsl.pl> Message-ID: <1745190A-1126-4828-925D-920D796C4D4A@ripe.net> Dear Piotr, Thanks for pointing out the version mismatches, we?ll update the manuals ASAP. As mentioned earlier we?re currently in the process of improving the documentation. We?re doing this in two phases, first we'll improve our procedures and apply the best practices for documenting software. Once we have the new procedure in place we'll do a major review of the manuals, section by section. Please bear with us until then as this is quite a big project. Kind regards, Johan ?hl?n Asst. Manager Database RIPE NCC On 25 Mar 2014, at 21:32, Piotr Strzyzewski wrote: > On Tue, Mar 25, 2014 at 04:26:35PM +0100, Denis Walker wrote: > > Dear Denis > >> The new versions of both the Update and Query Reference Manuals in PDF >> format were available on the www.ripe.net website yesterday. The html >> version of the new Query Reference Manual is now also available. They both >> include details of the new SSO auth option. > > Just to excuse myself - the very first sentence in RIPE Database Update > Reference Manual > (http://www.ripe.net/data-tools/support/documentation/upd-ref-manual) > is: "This document describes how to update version 1.71 of the RIPE > Database.". I didn't checked the rest of the document. ;-) > However, the footers on every page states it is from the version 1.72. > Honestly speaking, if this PDF is somehow autogenerated, isn't that > obvious to define the version number and then use it everywhere? This is > just a rhetorical question. > > Just to note: The Query Reference Manual (both html and PDF) last > updated (according to the webpage and your statement above) on 25 Mar > 2014 says: "This document describes how queries work in version 1.68 of > the RIPE Database." > > Piotr > > -- > gucio -> Piotr Strzy?ewski > E-mail: Piotr.Strzyzewski at polsl.pl > > From training at ripe.net Tue Mar 25 17:15:34 2014 From: training at ripe.net (Training Services) Date: Tue, 25 Mar 2014 17:15:34 +0100 Subject: [ncc-services-wg] [training] RIPE NCC Webinars - new dates Message-ID: <5331ABA6.2090902@ripe.net> Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email . We look forward to seeing you online. Kind regards, RIPE NCC Training Services