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

Re: [ncc-services-wg] [address-policy-wg] Crimea papers
by Michiel Klaver 29 Jul '14

29 Jul '14

it concerns everyone, but the question asked can only be answered by RIPE NCC legal desk. When they answer and it is not satisfying, you should contact your ambassy and take it to the political level. We as LIR members cannot change politics. ksyu(a)netassist.ua wrote at 29-07-2014 10:53: > Because it concern to everyone. > Today you accept russian aggression. Tomorrow will die more than 298 YOUR > people from their arms. > > 29.07.2014 11:43, Michiel Klaver пишет: >> Hi Max, >> >> Please tell us why you choose to spam thousands of subscribers of public >> mailinglists, while your question should have been addressed directly to NCC >> legal desk? >> >> http://www.ripe.net/lir-services/ncc/contact >> > >

1 0

Re: [ncc-services-wg] [address-policy-wg] Crimea papers
by Sander Steffann 29 Jul '14

29 Jul '14

Hi Max, I understand your frustration, but this is not the place to fight this fight. The RIPE NCC has both Russian and Ukrainian members. A member can be an existing entity under either Russian or Ukrainian law. The location of the entity doesn't matter in this case. A company can have its office in Crimea, independent of whether it is registered as a Russian or a Ukrainian company and independent of which country Crimea belongs to. The RIPE NCC can only deal with if an entity exists. Compare it to this: if I would go and live in Belgium I can be a member as a Dutch personal entity while having a Belgian address. But this is getting severely off-topic for this mailing list, so let's stop this discussion here and focus on address policy again :) Cheers, Sander

3 2

Planning for RIPE69
by Lindqvist Kurt Erik 22 Jul '14

22 Jul '14

Dear WG Members, me and Bijal are trying to do some time planning for RIPE69. If you know/think/plan/dream of submitting a policy proposal, or otherwise would like to have time on the agenda, could you please let us know by emailing ncc-services-wg-chairs(a)ripe.net ? This will help us to not run (so much) into the AGM as we usually do... Kurtis & Bijal NCC Services chairs

1 0

Closure of Test Traffic Measurements Service and Changes to the DNS Monitoring Service
by Romeo Zwart 07 Jul '14

07 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear colleagues, As of 1 July 2014, the old DNS Monitoring Service (DNSMON), based on the Test Traffic Measurements Service (TTM), has stopped receiving updates to its data. The new DNSMON interface is available at: https://atlas.ripe.net/dnsmon All historic DNSMON visualisations will remain available at: http://dnsmon-old.ripe.net We will keep these visualisations of the historic data available until at least the end of 2014. Existing URLs that point to specific periods or zones in the old DNSMON (for example http://dnsmon.ripe.net/dns-servmon/server/) will be redirected and will continue to work for as long as the old DNSMON visualisation servers are maintained. As discussed at the RIPE 68 DNS Working Group session in Warsaw, the RIPE NCC will provide some statistics on usage of the old visualisations at RIPE 69 in London. The DNS Working Group will be consulted regarding the further maintenance or possible decommissioning of these visualisations. Background The RIPE NCC announced a new version of DNSMON in March 2014 and informed the community that the old DNSMON would be phased out. The old DNSMON was dependent upon measurements run as part of TTM, which was in the last phase of its existence. TTM has been decommissioned, as announced previously, on 1 July 2014. In line with the closure of TTM, data collection in the old DNSMON has also been terminated from that same date. These changes are in line with our previous communications, notably the RIPE Labs article "Timeline for Phasing Out the Old TTM-Based DNSMON": https://labs.ripe.net/Members/romeo_zwart/copy_of_proposed-time-lines-for-p… Romeo Zwart RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO6fx4ACgkQGRL9suBV+eos8ACfUMImGvgAV9rJ1bxzLbt4hLmv HewAni2DYCGSLAWOAhYREtCsprGj8jKR =gI+O -----END PGP SIGNATURE-----

1 0

New on RIPE Labs: RIPE NCC Training Survey Results
by Mirjam Kuehne 01 Jul '14

01 Jul '14

Dear colleagues, At the beginning of each year and after each course we send a survey to the RIPE NCC members who participated in our training courses. We published a summary of the results on RIPE Labs: https://labs.ripe.net/Members/sandra_bras/ripe-ncc-training-survey-results Kind regards, Mirjam Kuehne RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 24 Jun '14

24 Jun '14

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 <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

New on RIPE Labs: The IPv6 Analyser
by Mirjam Kuehne 20 Jun '14

20 Jun '14

Dear colleagues, The IPv6 Analyser is a toolset that offers our members a visual insight into all the allocations, aggregations and assignments they have made. This toolset seamlessly integrates with the RIPE Database, allowing you to create new objects with an easy-to-use wizard. It was announced before the RIPE 68 meeting, and we're now seeing LIRs starting to use it. Please find some more details in this RIPE Labs article: https://labs.ripe.net/Members/AlexBand/the-ipv6-analyser Please let us know if you have any comments or questions. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Planned Test Traffic Measurements Service Closure
by Romeo Zwart 05 Jun '14

05 Jun '14

Dear colleagues, The RIPE NCC’s Test Traffic Measurements (TTM) Service will be decommissioned at the end of June 2014. Most of the functionality offered by TTM is available as part of RIPE Atlas and we encourage you to take advantage of this service: https://atlas.ripe.net Handover of Responsibility of TTM Machines We will contact the individual TTM hosts during June to arrange the handover of responsibility for the remaining TTM systems. Many hosts asked us about the possibilities to keep the old hardware around as a stand-alone NTP server. We have a RIPE Labs article detailing the options to transition your TTM system to a dedicated NTP server. The article is available here: https://labs.ripe.net/Members/colin_petrie/how-to-convert-your-ttm-box-to-a… Availability of TTM Data - No new data will be collected via TTM once decommissioned - Current interface for TTM data visualisations will be available until at least the end of 2014 - Raw data from TTM measurements will be downloadable indefinitely Background For more information about the end of TTM, please read this RIPE Labs article by Kaveh Ranjbar posted last year: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services We delayed the decommissioning date mentioned in the article by six months to provide a smooth transition for the DNSMON service from TTM to RIPE Atlas. We also wanted to allow TTM users adequate time to start using RIPE Atlas or other tools. We invite your feedback regarding the above planning. Please send your comments directly to me (<romeo.zwart(a)ripe.net>) or to the MAT Working Group mailing list (<mat-wg(a)ripe.net>). Regards, Romeo Zwart RIPE NCC

1 0

Blocking Access to Personal Data Objects in the RIPE Database
by Denis Walker 28 May '14

28 May '14

Dear colleagues, At RIPE 68, we again raised the issue of how the blocking mechanism works in the RIPE Database. Currently it is all or nothing — if a user queries for too much personal data, we block their access to everything. We often find that this causes issues for legitimate users of the database. This is a recent example of the requests our Customer Services department receives: "This is the outgoing NAT IP for a vast shared hosting cluster. We can't control the type of queries our customers run, there are over 250,000 websites, a tiny fraction might use RIPE but those customers are using RIPE database for a good reason and need to be able to query it. This is why I'm asking for a blanket allow.” Clearly we cannot whitelist any IP address for unlimited access to personal data. However, the option to only block access to personal data objects when the limit is reached would be a great help in these situations. No decision has been made on this issue. We are hoping that it can be further discussed by the community to see if a consensus can be reached. Regards Denis Walker Business Analyst RIPE NCC Database Team

8 7

RIPE Database Release 1.73.1 Available in the Release Candidate Environment
by Johan Åhlén 27 May '14

27 May '14

Dear colleagues, Based on feedback from users testing RIPE Database release 1.73 in the Release Candidate (RC) environment, the RIPE NCC Database Group have made some software improvements that we’ve decided to incorporate into the next deployment. We will not deploy version 1.73 to production. Instead, we will deploy the improved version, 1.73.1, to the RC environment today, 19 May, and to production on 27 May 2014. The main concern with RIPE Database release 1.73 was related to user-automated assignment generation in the RIPE Database for legacy address space. With release 1.73, if a legacy object was updated with an incorrect "status:" attribute value, then the update would fail. With version 1.73.1, the database software will accept the update, regardless of any value supplied by the user, but will show a warning if the “status:” attribute value is incorrect. For more information about this release and how it might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73… We look forward to any questions or comments you might have. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

4 3