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

Phasing out the LIR Portal object editors
by Alex Band 22 Apr '16

22 Apr '16

Dear colleagues, Over the last year the RIPE NCC has been making a considerable amount of incremental changes to the RIPE Database user interface. Especially the implementation of streamlined authentication using RIPE NCC Access has put us in a position where we can further improve the user experience in other areas. As the next step in this process, we intend to phase out the so-called LIR Portal object editors. Currently, the object editors are necessary to allow you to make changes to particular attributes of RIPE Database objects that are maintained by the RIPE NCC. For example, you can use them to change the tech-c and admin-c in the inetnum object for the allocation that you hold. This system has always been the cause of much confusion. User data that you expect to be able to change in the RIPE Database can only be changed through the LIR Portal, whereas other information can be edited in the RIPE Database itself. Our plan is to bring all of this to the place where it belongs and where users expect it, the RIPE Database. The way we intend to do this involves a couple of steps. The first step is to use business rules to determine which attributes you can change, and which ones can only be changed by the RIPE NCC. For example, in an inetnum for an allocation only the RIPE NCC can change the range, but you can change the admin-c and tech-c. The second step is setting the authorisation for the attributes that you control. The RIPE NCC already has a maintainer on the allocation, RIPE-NCC-HM-MNT. In the system we envision, we would allow you to select an additional maintainer, to authorise changes over the attributes that you are authoritative for. You will be able to select this maintainer in the LIR Portal. We will place this maintainer on all existing and new objects that have joint responsibility: allocations for IP resources and the Organisation object. It is important to note that none of these changes have a fundamental impact on the RIPE Database itself. We are only making changes to the business rules and the way you determine authorisation. We look forward to your feedback! Kind regards, Alex Band Product Manager RIPE NCC

2 1

Call for agenda items
by Kurt Erik Lindqvist 20 Apr '16

20 Apr '16

Dear WG, we are closing in on RIPE72 in Copenhagen. If you have any agenda items for the NCC-Services WG please email ncc-services-wg-chairs(a)ripe.net! The WG will meet on Wednesday the 25 May 2016 at 16:00. Kurtis , WG-Chair

1 0

[training] Training Course: Exploring RIPE Database API
by Training Services 31 Mar '16

31 Mar '16

Dear colleagues, We are happy to announce that a RIPE NCC training course will take place on Sunday 22 May, before RIPE 72 begins on Monday 23 May, in Copenhagen. This course will focus on using RIPE Database RESTful API to programmatically manipulate RIPE Database objects. The course is free of charge and is open to anyone interested. ---------------- Course details ---------------- Exploring RIPE Database API ---------------- Course goals ---------------- By the end of this course, you will be able to perform operations on object in the RIPE Database using RESTful API. ---------------------------------------- Who will benefit from this course? ---------------------------------------- Anyone managing objects in the RIPE Database and considers automating this process or integrating with other software will find this course useful. --------------- Prerequisites: --------------- - Basic programming experience - Basic knowledge of the RIPE Database ------------------------- Course outline: ------------------------- - RIPE Database Overview - Exploring RESTful API - Using RESTful API - Building simple IPAM ---------------------------- Additional information ---------------------------- - Free of charge - Coffee and lunch will be provided - Delivered by the RIPE NCC’s Training Services ----------------------------------------- Registration for RIPE NCC members ----------------------------------------- Please register via the following page: https://lirportal.ripe.net/training/register/courseCode/LIR20160008 ------------------------------------ Registration for non-members ------------------------------------- Please fill out the following information email it to: <training(a)ripe.net>: - Email: - Course name: - Full name : - Vegetarian: yes/no Be quick - we only have 45 seats available on a first-come, first-served basis! If there is enough interest, we will continue to offer courses on different topics of interest alongside future RIPE Meetings. Kind regards, RIPE NCC Training Services

1 0

Updated 5th Draft SLA for the IANA Numbering Services
by Athina Fragkouli 18 Mar '16

18 Mar '16

Dear Colleagues Please find below the latest NRO announcement regarding the Fifth version of the draft SLA. https://www.nro.net/news/updated-5th-draft-sla-for-the-iana-numbering-servi… Kind regards, Athina Fragkouli Head of Legal RIPE NCC ===== UPDATED FIFTH DRAFT SERVICE LEVEL AGREEMENT FOR THE IANA NUMBERING SERVICES (SLAv5) AND CALL FOR PUBLIC COMMENTS 17 March 2016 Background On 15 January 2015, the Consolidated RIR IANA Stewardship Proposal (CRISP) Team submitted the Internet Number Community Proposal to the request for proposals issued by the IANA Stewardship Coordination Group (ICG). One of the key elements of the Internet Number Community proposal is to replace the current NTIA IANA agreement with a new contract, a Service Level Agreement (SLA), between the IANA Numbering Services Operator and the five RIRs. A first draft of the SLA was published on 1 May 2015 and opened for public comments until 14 June 2015. The first draft of the SLA is available at: https://www.nro.net/sla-v1 A second draft of the SLA was published on 6 August 2015 and opened for public comments until 31 August 2015. The second draft of the SLA is available at: https://www.nro.net/sla-v2 A third draft of the SLA was published on 30 October 2015 and invited ICANN legal staff to provide comments by November 30th 2015. The third draft of the SLA is available at: https://www.nro.net/sla-v3 A fourth draft of the SLA was published on 25 February and invited ICANN to move forward to signing the SLA. The fourth draft of the SLA is available at: https://www.nro.net/sla-v4 Fifth Draft SLA As a result of ICANN comments on the fourth draft and additional feedback received at meetings during ICANN 55 in Marrakech, a fifth draft of the SLA has been produced and is available at: https://www.nro.net/sla The SLAv5 is open for public comments. Comments can be sent to IANAXFER mailing list at https://www.nro.net/mailman/listinfo/ianaxfer. The deadline for comments is April 15th 2016. For the sake of clarity, you can find a track changes version of SLAv5 against the fourth draft at: https://www.nro.net/sla-track-changes Additionally, a document with the comments on SLAv5 and the legal team responses is available at: https://www.nro.net/slav4-comments In accordance with the transparency commitment to our the community, we share the exchange of a clear track of comments between ICANN and RIR staff working towards a final SLA document. About the Fifth Draft SLA The fifth draft of the SLA has been developed by a team consisting of individuals from different RIRs. It responds to the principles included in the Internet Number Community proposal and is based on the already existing provisions of the NTIA IANA agreement. The content of SLAv5 is the result of consideration of public comments received during the public comment period on the second draft SLA,informational meetings with ICANN staff regarding the operational provisions of the SLA, and ICANN’s written comments regarding the third and fourth draft SLA. It is written in such a way that it can be signed as part of the implementation of the IANA transition when this occurs or before, without pre-judging the outcome of the ICG coordinated proposal. The SLA includes legally important provisions, such as those that regulate the five RIRs collective actions and responsibilities in its dealings with ICANN under the SLA. It also includes background and definitions. The SLA also includes explanatory footnotes that reference the source of each article according to the Internet Number Community proposal principles or the NTIA IANA agreement. Next Steps The RIRs thank the community and ICANN staff for its thoughtful comments and now publish this SLAv5 in the interest of transparency and keeping the community apprised of progress being made on the SLA. We trust that all comments and concerns have been addressed and that the current draft, SLAv5, represents a mutually acceptable SLA that is consistent with the principles found within the Internet Number Community proposal. We invite public comments as we approach the final version, which will be signed with ICANN/IANA as part of the IANA Transition planning process and will take effect upon release of their existing agreement with NTIA. _______________________________________________

1 0

How to change the geolocation of my IP's?
by Dmitry Vorozhtsov 17 Mar '16

17 Mar '16

Hello! I’ve got an address block using transfer a few weeks ago. So I tried to change geoloc info and sent a request to MaxMind. Unfortunately, I’ve got a message - «Sorry, we can not accept your request, because location you specified, does not match the data, that we received from this network» I asked once more, but received no answer. I have a record in RIPE DB for this address block. How can I change the geoloc info? Best regards, Dmitry Vorozhtsov

1 0

[training] RIPE NCC Training Courses April-June 2016
by Training Services 29 Feb '16

29 Feb '16

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Budapest, Tirana, Manchester, Lisbon, Bologna, Munich, Tallinn, Moscow, Vienna, Valletta, Reykjavik. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - RIPE Database Training Course - Basic IPv6 Training Course - DNSSEC Training Course - 2 days Advanced IPv6 Training Course - 2 days BGP Operations and Security Training Course For more information visit: https://www.ripe.net/support/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

Updated 4th Draft SLA for the IANA Numbering Services
by Athina Fragkouli 25 Feb '16

25 Feb '16

Dear Colleagues Please find below the NRO announcement on the 4th draft Service Level Agreement for the IANA Numbering Services. The announcement is available at: https://www.nro.net/news/updated-4th-draft-sla-for-the-iana-numbering-servi… Athina Fragkouli Head of Legal RIPE NCC ----------- UPDATED FOURTH DRAFT SERVICE LEVEL AGREEMENT FOR THE IANA NUMBERING SERVICES (SLAv4) AND CALL TO ICANN TO MOVE FORWARD WITH SIGNING THE SLA 25 February 2016 Background On 15 January 2015, the Consolidated RIR IANA Stewardship Proposal (CRISP) Team submitted the Internet Number Community Proposal to the request for proposals issued by the IANA Stewardship Coordination Group (ICG). One of the key elements of the Internet Number Community proposal is to replace the current NTIA IANA agreement with a new contract, a Service Level Agreement (SLA), between the IANA Numbering Services Operator and the five RIRs. A first draft of the SLA was published on 1 May 2015 and opened for public comments until 14 June 2015. The first draft of the SLA is available at: https://www.nro.net/sla-v1 A second draft of the SLA was published on 6 August 2015 and opened for public comments until 31 August 2015. The second draft of the SLA is available at: https://www.nro.net/sla-v2 A third draft of the SLA was published on 30 October 2015 and invited ICANN legal staff to provide comments by November 30th 2015. The third draft of the SLA is available at https://www.nro.net/sla-v3 Fourth Draft SLA As a result of ICANN comments on the third draft of the SLA and a clarification call on Tuesday January 26th (https://www.nro.net/pipermail/ianaxfer/2016-February/000725.html) a fourth draft of the SLA has been produced and available at https://www.nro.net/sla For the sake of clarity, you can find a track changes version of SLAv4 against the third draft at: https://www.nro.net/sla-track-changes Additionally, a document with the comments on SLAv3 and the legal team responses is available at: https://www.nro.net/slav3-comments In accordance with the transparency commitment with the community, we share the exchange of a clear track of comments between ICANN and RIR staff working towards a final SLA document. About the Fourth Draft SLA The fourth draft of the SLA has been developed by a team consisting of individuals from different RIRs. It responds to the principles included in the Internet Number Community proposal and is based on the already existing provisions of the NTIA IANA agreement. The content of SLAv4 is the result of consideration of public comments received during the public comment period on the second draft SLA as well as informational meetings with ICANN staff regarding the operational provisions of the SLA and ICANN’s written comments regarding the third draft SLA. It remains written in such a way that it can be signed as part of the implementation of the IANA transition when this occurs or before, without pre-judging the outcome of the ICG coordinated proposal. The SLA includes legally important provisions, such as those that regulate the five RIRs acting together and being responsible collectively in its dealings with ICANN under the SLA. It includes background and definitions. The SLA also includes explanatory footnotes that reference the source of each article according to the Internet Number Community proposal principles or the NTIA IANA agreement. Next Steps The RIRs thank the community and ICANN staff for its thoughtful comments and now publish this SLAv4 in the interest of transparency and keeping the community apprised of progress being made on the SLA. We trust that all comments and concerns have been addressed and that the current draft, SLAv4, represents a mutually acceptable SLA that is consistent with the principles found within the Internet Number Community proposal. We invite ICANN staff to take the appropriate steps so that we can move forward with signing of this SLA as soon as possible, preferably during the ICANN 55 Meeting in Marrakech Morocco.

1 0

Draft NCC Services WG Minutes - RIPE 71
by Amanda Gowland 03 Feb '16

03 Feb '16

Hi Kurtis, Bijal, Hope you're having a relaxing holiday (Bijal especially!). Please find below the draft minutes from your last session. Please let me know if there are any corrections and if we can publish on the website. Many thanks, Amanda ---- RIPE NCC Services Working Group RIPE 71 18 November 2015, 16:00 local time WG co-Chairs: Kurtis Lindqvist, Bijal Sanghani (absent) Scribe: Emile Aben A. Administrative Matters Kurtis welcomed the room. B. IANA Update - Elise Gerich (IANA) The presentation is available at: https://ripe71.ripe.net/presentations/58-IANA_RIPE_NOV2015.pptx There were no questions. C. RIPE NCC Outlook - Axel Pawlik (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/121-RIPE-NCC-Outlook-2015-and-2016.pdf There were no questions. D. IETF Endowment Update - Jari Arkko (IETF) and Greg Kapfer (ISOC) The presentation is available at: https://ripe71.ripe.net/presentations/106-ripe_bucharest_ietf_endowment_v3.… Martin Levy (Cloudflare) asked if funding the IETF isn't already done through ISOC. Greg answered that IETF wants diversification in their funding sources. Jari acknowledged that. Martin responded that he doesn't support extra bureaucracy being thrown at anything. Nurani Nimpuno (Netnod) said she thought it to be a good thing to have diversification of funds, and interprets this proposal as a way of diversification, not necessarily increase of funds. Salam Yamout (RIPE NCC Executive Board) asked if the IETF is also looking for independence. Jari stated the goal is to broaden the financial support. The IETF will still need an organisational home. Greg added that there is a very good working relationship between IETF and ISOC, and stated that the proposal is a long-term endeavour. Daniel Karrenberg (as private person) asked about transparency in the proposal. He said he finds the current story to vague, and acknowledges IETF does great work. He mentioned ISOC being well funded so this is about ISOC setting priorities, and said that ISOC could put down the endowment itself. Jari provided details about budget. Regarding ISOC contribution, Jari said that that would likely increase. Greg detailed current ISOC funding, and said ISOC will always be investing in the IETF. Leah Symekher (ISC) asked how to expand participation for IETF and how to diversify the participation. Jari answered that IETF brings in fellows into the IETF meetings for this, and to build on participants who are interested long-term. He said IETF has multiple tools like the mentoring programme at the IETF to bring in new participants. Mirjam Kuehne (RIPE NCC) said the RIRs contribute membership money into ISOC specifically earmarked to support IETF and wondered what will happen with that. Greg said it's for IETF operating expenses, which is a different thing from the endowment proposal. Mohsen Souissi (as private person) asked Greg and Jari to write the proposal up so it's easy to decide on. Jari said that's a fair request, and will get it done. E. RIPE NCC Arbiters Process - Ondrej Sury (CZ.NIC) and Wilfried Woeber (University Vienna/ACOnet/VIX) The presentation is available at: https://ripe71.ripe.net/presentations/57-Presentation-for-Arbiters-Panel-RI… Farzaneh Badii (University of Hamburg) asked if arbitration was not enforceable in court. Wilfried answered that the RIPE NCC doesn't have the mandate to enforce Farzaneh asked if the artiration then is non-binding. Wilfried clarified that it is binding for the RIPE NCC, but its no legal mechanism to enforce it in another party in a dispute. Ondrej thanked the ripe ncc secretariat. Nurani asked if there is a roll-over procedure for arbiters. Wilfried clarified that it is the responsibility of the RIPE NCC management or the general meeting, but there is no fixed mandate. F. RIPE NCC Operational Update - Andrew de la Haye (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/128-COO-Update-final-RIPE71.pdf Radu-Adrian Feurdean (CCS) asked if the issues that were discussing this morning in the address policy working group should be discussed in the services working group or in the general meeting. Andrew responded that the general meeting is the right place. Nigel Titley (RIPE NCC Executive Board) confirmed that. G. RIPE NCC Services Developments - Alex Band (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/113-ServicesWG-RIPE71.pdf There were no questions. H. Open Microphone Session There were no questions.

2 1

Draft Minutes from WG session at RIPE 71
by Kurt Erik Lindqvist 03 Feb '16

03 Feb '16

All, please find the draft minutes of the RIPE71 session below. Please send any comments or corrections! Best regards, Lindqvist Kurt Erik kurtis(a)kurtis.pp.se ---- RIPE NCC Services Working Group RIPE 71 18 November 2015, 16:00 local time WG co-Chairs: Kurtis Lindqvist, Bijal Sanghani (absent) Scribe: Emile Aben A. Administrative Matters Kurtis welcomed the room. B. IANA Update - Elise Gerich (IANA) The presentation is available at: https://ripe71.ripe.net/presentations/58-IANA_RIPE_NOV2015.pptx There were no questions. C. RIPE NCC Outlook - Axel Pawlik (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/121-RIPE-NCC-Outlook-2015-and-2016.pdf There were no questions. D. IETF Endowment Update - Jari Arkko (IETF) and Greg Kapfer (ISOC) The presentation is available at: https://ripe71.ripe.net/presentations/106-ripe_bucharest_ietf_endowment_v3.… Martin Levy (Cloudflare) asked if funding the IETF isn't already done through ISOC. Greg answered that IETF wants diversification in their funding sources. Jari acknowledged that. Martin responded that he doesn't support extra bureaucracy being thrown at anything. Nurani Nimpuno (Netnod) said she thought it to be a good thing to have diversification of funds, and interprets this proposal as a way of diversification, not necessarily increase of funds. Salam Yamout (RIPE NCC Executive Board) asked if the IETF is also looking for independence. Jari stated the goal is to broaden the financial support. The IETF will still need an organisational home. Greg added that there is a very good working relationship between IETF and ISOC, and stated that the proposal is a long-term endeavour. Daniel Karrenberg (as private person) asked about transparency in the proposal. He said he finds the current story to vague, and acknowledges IETF does great work. He mentioned ISOC being well funded so this is about ISOC setting priorities, and said that ISOC could put down the endowment itself. Jari provided details about budget. Regarding ISOC contribution, Jari said that that would likely increase. Greg detailed current ISOC funding, and said ISOC will always be investing in the IETF. Leah Symekher (ISC) asked how to expand participation for IETF and how to diversify the participation. Jari answered that IETF brings in fellows into the IETF meetings for this, and to build on participants who are interested long-term. He said IETF has multiple tools like the mentoring programme at the IETF to bring in new participants. Mirjam Kuehne (RIPE NCC) said the RIRs contribute membership money into ISOC specifically earmarked to support IETF and wondered what will happen with that. Greg said it's for IETF operating expenses, which is a different thing from the endowment proposal. Mohsen Souissi (as private person) asked Greg and Jari to write the proposal up so it's easy to decide on. Jari said that's a fair request, and will get it done. E. RIPE NCC Arbiters Process - Ondrej Sury (CZ.NIC) and Wilfried Woeber (University Vienna/ACOnet/VIX) The presentation is available at: https://ripe71.ripe.net/presentations/57-Presentation-for-Arbiters-Panel-RI… Farzaneh Badii (University of Hamburg) asked if arbitration was not enforceable in court. Wilfried answered that the RIPE NCC doesn't have the mandate to enforce Farzaneh asked if the artiration then is non-binding. Wilfried clarified that it is binding for the RIPE NCC, but its no legal mechanism to enforce it in another party in a dispute. Ondrej thanked the ripe ncc secretariat. Nurani asked if there is a roll-over procedure for arbiters. Wilfried clarified that it is the responsibility of the RIPE NCC management or the general meeting, but there is no fixed mandate. F. RIPE NCC Operational Update - Andrew de la Haye (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/128-COO-Update-final-RIPE71.pdf Radu-Adrian Feurdean (CCS) asked if the issues that were discussing this morning in the address policy working group should be discussed in the services working group or in the general meeting. Andrew responded that the general meeting is the right place. Nigel Titley (RIPE NCC Executive Board) confirmed that. G. RIPE NCC Services Developments - Alex Band (RIPE NCC) The presentation is available at: https://ripe71.ripe.net/presentations/113-ServicesWG-RIPE71.pdf There were no questions. H. Open Microphone Session There were no questions.

1 0

RIPE Policy Proposal 2016-01 Affects Legacy Internet Resource Holders
by Marco Schmidt 28 Jan '16

28 Jan '16

Dear colleagues, We just published RIPE Policy Proposal 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy", to the Anti-Abuse Working Group mailing list. The goal of this proposal is to extend RIPE Document ripe-563, "Abuse Contact Management in the RIPE Database", to Legacy Internet Resource Holders. As this proposal makes reference to the RIPE Policy, "RIPE NCC Services to Legacy Internet Resource Holders", which was developed by the RIPE NCC Services Working Group, we would like to notify you. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-01 We encourage you to review this proposal and send your comments to <anti-abuse-wg(a)ripe.net> before 26 February 2016. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0