January 2014 - ncc-services-wg

comments on proposal 2012-07
by Nick Hilliard 05 Feb '14

05 Feb '14

Hello, I thought I'd chip in on 2012-07. The current version of the proposal is a huge improvement on v1.0 and thanks / kudos need to go to the authors for what was obviously a huge amount of work. I still have issues with a number of areas. Serious issues: Section 3.0 needs to include a term in the contract to state that the services provided by the RIPE NCC to the legacy resource holder are defined by RIPE community policy and may be amended from time to time, according to ripe community policy. Section 2.6 still provides carte blanche for legacy resource holders to freeload services off the RIPE NCC with no consequences. As a RIPE NCC member, I am not at all happy about this. The amount of work that the RIPE NCC is going to have to undertake to handle the legacy resource holder community is very large indeed, and it is not reasonable to expect the RIPE membership to foot the bill for those legacy resource holders who aren't members and who feel un-inclined to contribute towards registration services just because they couldn't be bothered to pay. Section 2.5: I see where this is coming from, namely there will probably be situations where the users of the address space will be unable to identify themselves adequately as having any claim to their assignment. However, this section is open to abuse and it concerns me that it's still there. I concede that there is a requirement to have some type of arrangement like this, but the wording of the current section needs to be tightened up considerably. Less serious issues: Section 2.4 is redundant. We have a well established precedent under the terms of 2007-01 for engaging with sponsoring LIRs and this seems to work well in practice. Creating this policy option merely adds cost to the RIPE NCC's bottom line for no gain. Nits: Section 3.0: "a statement that the RIPE NCC is not entitled to deregister the resources for whatever purpose unless so instructed by the resource holder". This statement is advisory only and it needs to be made clear that the sponsoring LIR does not have power to make a legally binding statement of this form. This actually applies to all four statements in section 3.0. Nick

7 25

Proposed Implementation Plan for 2012-08, "Publication of Sponsoring LIR for Independent Number Resources"
by Johan Åhlén 03 Feb '14

03 Feb '14

Dear colleagues, Last week, the RIPE community reached consensus on the policy proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources”. The RIPE NCC’s proposed implementation plan of the policy can be found here: https://labs.ripe.net/Members/johan_ahlen/policy-2012-08-proposed-plan-for-… You can find the full policy proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 The corresponding RIPE Document is ripe-603, which is available at: https://www.ripe.net/ripe/docs/ripe-603 If you have any comments or concerns, please let us know. Note: this email has been sent to both the RIPE NCC Services WG and the RIPE Database WG mailing lists. We would like to ask you to keep the discussion on the RIPE NCC Services WG mailing list to better facilitate participation. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

Proposed Implementation for 2012-08
by Henrik Lund Kramshøj 31 Jan '14

31 Jan '14

Hi WG members I read the "Proposed Implementation for 2012-08" listed at: https://labs.ripe.net/Members/johan_ahlen/policy-2012-08-proposed-plan-for-… "We propose to add a new optional attribute called "sponsoring-org:" to the object types INETNUM, INET6NUM and AUT-NUM. " - and asking for feedback and thoughts I am a LIR with multiple independent resources for my customers and I think the suggested implementation is reasonable. The proposal is easy to understand, aligns well with the current usage of the whois database and will allow me and colleagues to lookup the link. So from LIR dk.solidonetworks this is a +1 go ahead with the proposed implementation. Best regards Henrik PS not on the list, so please include me in responses if you need further information -- Henrik Lund Kramshøj, Follower of the Great Way of Unix internet samurai cand.scient CISSP hlk(a)kramse.org hlk(a)solidonetworks.com +45 2026 6000 http://solidonetworks.com/ Network Security is a business enabler

1 0

Re: [ncc-services-wg] 2012-08 Proposal Accepted (Publication of Sponsoring LIR for Independent Number Resources)
by Bengt Gördén 22 Jan '14

22 Jan '14

2014-01-22 11:57, Marco Schmidt skrev: > Dear colleagues, > > > Consensus has been reached, and the proposal described in 2012-08, > "Publication of Sponsoring LIR for Independent Number Resources", has > been accepted by the RIPE community. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2012-08 > > > The new RIPE document is ripe-603 and it is available at: > > https://www.ripe.net/ripe/docs/ripe-603 > > > An announcement regarding the implementation will follow. > > > Thank you for your input. Thank you. When will we see an implementation of this in the database? regards, -- Bengt Gördén Resilans AB

2 1

2012-08 Proposal Accepted (Publication of Sponsoring LIR for Independent Number Resources)
by Marco Schmidt 22 Jan '14

22 Jan '14

Dear colleagues, Consensus has been reached, and the proposal described in 2012-08, "Publication of Sponsoring LIR for Independent Number Resources", has been accepted by the RIPE community. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 The new RIPE document is ripe-603 and it is available at: https://www.ripe.net/ripe/docs/ripe-603 An announcement regarding the implementation will follow. Thank you for your input. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 20 Jan '14

20 Jan '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

Proposed Implementation of Resource Certification for non-RIPE NCC Members
by Alex Band 16 Jan '14

16 Jan '14

Dear colleagues, We have been working on the implementation of 2013-04, "Resource Certification for non-RIPE NCC Members", and would like to give you an overview of our proposed plan for certifying address space held by Provider Independent (PI) End Users. You can find the full details below. In summary: 1. We propose to only issue certificates for PI End User resources if an End User Assignment Agreement has been submitted and verified by the RIPE NCC and all internal RIPE Registry records match with the associated information in the RIPE Database 2. Users will no longer be able to update the "org-name:” attribute in the organisation object without RIPE NCC involvement. This attribute will only be locked if the organisation object is referenced from a resource object. With this step we are enforcing an existing business rule. 3. RIPE NCC Access authorisation will be added to the RIPE Database. This will simply be an additional value for the "auth:" attribute, referencing your RIPE NCC Access account. Detailed explanation: Currently, when a PI resource is assigned to an End User, we make a record of the organisation name and the organisation-id in our registry. This information is reflected in the related inetnum object for the resource (the org-id attribute), as well as the organisation object (the org-name attribute). However, it is possible that these informational elements can fall out of sync, as the End User is free to update these objects without involving the RIPE NCC. This can negatively impact the accuracy of the registry. One of the primary goals of issuing resource certificates is to make the RIPE Registry as accurate and robust as possible. Therefore, we propose to only issue certificates for PI End User resources: 1. If an End User Assignment Agreement has been submitted and verified by the RIPE NCC 2. If all internal RIPE Registry records match with the associated information in the RIPE Database During the request procedure, we would perform checks to see if the resources are eligible for certification. If all of the records in the RIPE Registry and RIPE Database match, the PI End User or Sponsoring LIR would be able to request a certificate without interaction with the RIPE NCC. However, if registry and database information are out of sync, we would ask you to first resolve this (with our help) to ensure that all records match correctly. In this implementation, you will no longer be able to update the "org-name:” attribute in the organisation object without RIPE NCC involvement. This attribute will only be locked if the organisation object is referenced from a resource object. This would ensure that our registry records remain accurate at all times. Additionally, the RIPE NCC plans to launch a project where we will proactively match the RIPE Registry and RIPE Database records in cooperation with the resource holder. Another aspect we need to implement is the association of a RIPE NCC Access account with the person who has authoritative control over the resources. In order to achieve this, we will introduce the ability to add a RIPE NCC Access account to a MNTNER object in the RIPE Database. Practically, this will simply be an additional value for the "auth:" attribute, referencing your RIPE NCC Access account. This will immediately fulfil a long-standing user request to be able to update RIPE Database objects with your RIPE NCC Access account, making authentication between different RIPE NCC services more seamless. Please do not hesitate to contact us if you have any questions. Kind regards Alex Band Product Manager RIPE NCC

1 0

[service] Report on Wednesday's Technical Outage
by Brian Riddle 10 Jan '14

10 Jan '14

Dear colleagues, We are currently upgrading our network. On Wednesday, between 15:42 and 17:27 (UTC+1), while performing a clean-up operation on our network equipment, we experienced an outage on our network which affected our virtual environment. This caused a number of our services to be unavailable for a period of time, ranging from 20 minutes to 1 hour and 45 minutes. Major services affected: 15:42 - 16:02 Internal network 15:42 - 16:08 RIPE Database 15:42 - 16:50 LIR Portal 15:42 - 16:55 www.ripe.net 15:42 - 17:27 RIPE Labs Major services not affected: DNS, K-root. As a result, we are reviewing our network maintenance procedures to minimise the risks of this occurring again. We apologise for any inconvenience that this may have caused. Kind regards Brian Riddle IT Manager RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 06 Jan '14

06 Jan '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