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

2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
by Marco Schmidt 25 Apr '13

25 Apr '13

Dear Colleagues, The draft document for the proposal described in 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders" has been published. The impact analysis that was conducted for this proposal has also been published You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2012-07 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2012-07/draft We encourage you to read the draft document text and send any comments to ncc-services-wg(a)ripe.net before 23 May 2013. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

Re: [ncc-services-wg] 2012-08 New Draft Document and Impact Analysis Published (Publication of Sponsoring LIR for Independent Number Resources)
by Sascha Luck 23 Apr '13

23 Apr '13

On Mon, Apr 22, 2013 at 02:33:08PM +0200, Marco Schmidt wrote: >You can find the full proposal and the impact analysis at: > > https://www.ripe.net/ripe/policies/proposals/2012-08 To recap: my main point of contention with this proposal is that it creates a perception of responsibility of the sponsoring LIR for the actions of the end user - which does not exist beyond keeping the ripedb updated. Thus it creates an attack surface for those who see it as their duty to keep the internet free of <insert agenda here>. Which will make it hard to impossible for a controversial or otherwise inconvenient independent resource holder (or applicant) to find or keep a sponsoring LIR. Impact Statement: "During implementation of this policy, the RIPE NCC will contact those organisations acting as sponsoring LIRs to notify them of this change and allow them time to react appropriately, by reviewing their sponsoring LIR agreements and terminating any they do not want to be associated with (or even all of them)." The wording is ambiguous and may refer to resources "brought in" under 2007-01/Phase III, but it can be read as if a sponsoring LIR will get an opportunity to break a sponsorship contract with an inconvenient end-user, thus orphaning them before an attack even happens. I would ask the NCC to please clarify the intention of this sentence, and note that https://www.ripe.net/lir-services/resource-management/independent-resources… does specify a notice period of 3 months for termination of the IR contract, otherwise we're looking at a case of Breach of Contract. For the record and the avoidance of doubt: I still oppose this proposal for the above mentioned reason. Kind Regards, Sascha Luck > >We encourage you to read the draft document text and send any comments >to ncc-services-wg(a)ripe.net before 20 May 2013. > >Regards > >Marco Schmidt >Policy Development Office >RIPE NCC > >

2 1

New on RIPE Labs: Introducing the RIPE NCC Roadmap
by Mirjam Kuehne 22 Apr '13

22 Apr '13

Dear colleagues, We often get asked about the status of our different services and projects, and while we frequently publish updates on RIPE Labs, we now have a new tool that makes it easier to stay informed. We're happy to announce the RIPE NCC Roadmap, where you can get an overview of all the latest developments and future plans for these services in one place. https://labs.ripe.net/Members/mirjam/introducing-ripe-ncc-roadmap This prototype, which is hosted on RIPE Labs, will be further developed as we receive your feedback, so please let us know what you think. Kind regards, Mirjam Kuehne RIPE NCC

1 0

2012-08 New Draft Document and Impact Analysis Published (Publication of Sponsoring LIR for Independent Number Resources)
by Marco Schmidt 22 Apr '13

22 Apr '13

Dear Colleagues, The draft document for the proposal described in 2012-08, "Publication of Sponsoring LIR for Independent Number Resources" has been published. The impact analysis that was conducted for this proposal has also been published. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2012-08 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2012-08/draft We encourage you to read the draft document text and send any comments to ncc-services-wg(a)ripe.net before 20 May 2013. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

Certifying of PI End User Address Space
by de Brün, Markus 12 Apr '13

12 Apr '13

Hey Andrew, I was hoping PI-space would eventually be coverd by RPKI. As a PI-space holder, who is not a RIPE NCC member, I would prefer option 2. Since the sponsoring LIR (in our case Deutsche Telekom) already has a contractual relationship with the RIPE NCC, this seems to be the straightforward approach. Option 3 is also okay although I understand the issue of non-members benefiting of RIPE-NCC services. If it comes to that, I am prepared to pay a fee as well ;-) Regards, Markus de Brün

4 4

RPKI Validator 2.8 released
by Alex Band 11 Apr '13

11 Apr '13

For those of you who use the 5.5 /8s worth of certified address space in the RPKI repository, we just released a new version of the Validator toolset: https://www.ripe.net/certification/tools-and-resources This version now properly handles other types of RPKI objects, such as Ghostbuster records (rfc6493). Cheers, Alex P.S. You can watch it in action here: http://rpki01.fra2.de.euro-transit.net:8080/roas

1 0

Plan to discontinue email signing from certain addresses
by Alex Band 09 Apr '13

09 Apr '13

Dear colleagues, One of the goals of the RIPE NCC is to simplify and streamline our infrastructure and internal processes. Over the years, we have taken great strides in making our infrastructure easier to maintain and more cost effective. However, there are a couple of legacy scripts and tools that are entangled deeply in our workflows and are very hard to phase out on the short term. One of these legacy tools is our ticketing system. The infrastructure we need and the resources it costs is disproportionate to the amount of value that it offers. Migrating away from it in one go is proving to be very complicated. This is why we have decided on a phased approach. One element of the ticketing system that will be affected in the first phase is PGP Authentication: https://www.ripe.net/lir-services/resource-management/contact/pgp-authentic… Signing emails from hostmaster(a)ripe.net, lir-help(a)ripe.net, new-lir(a)ripe.net and enum(a)ripe.net is one of the first pieces that we need to remove in order to phase out all the legacy software. While we realise that it is a best practice to sign such emails and are aware of the value it offers, we are planning to discontinue email signing from just these addresses starting 1 January 2014. It will allow us to phase out a part of our infrastructure that makes future migration a lot easier, while saving cost in the mean time. Please note that this change will not affect email interaction with the RIPE Database. As soon as we have replaced our current ticketing system, we will re-evaluate email signing. As we may have overlooked some potential issues that certain members of our Community might have if we discontinue this functionality, naturally we are open to your feedback. Kind regards, Alex Band Product Manager RIPE NCC

10 14

Status of 2012-07
by Lindqvist Kurt Erik 05 Apr '13

05 Apr '13

All, We wanted to provide an update on the next steps for 2012-07. The document will be moved to the next Phase (Review phase), this will be done with a version 3 of the document. The changes between version 2 and version 3 are non-significant, and we believe they do not justify a complete re-run of Phase 2. The changes to the document are in-line with the requests made by the community. Last, the RIPE NCC are working on the Impact study for this proposal and will post this to the list as soon as it's available. Best regards, Kurtis & Bijal

2 1

[news] Phase 1 Update: Abuse Contact Management in the RIPE Database
by Kaveh Ranjbar 03 Apr '13

03 Apr '13

[Apologies for duplicate emails] Dear colleagues, Phase 1 of ripe-563 "Abuse Contact Management in the RIPE Database" is now being implemented, as announced on 19 March 2013. According to ripe-563, all resources allocated or assigned by the RIPE NCC will need to have an abuse contact email address included in their RIPE Database registration. During the first six months of implementation (phase 1), all Local Internet Registries (LIRs) must add an abuse contact attribute ("abuse-c:") to their LIR's ORGANISATION object to provide abuse contact information for all of the allocated address space under their LIR. Since the initial announcement two weeks ago, we are pleased to report that 24.8% of the RIPE NCC's allocated IPv4 address space is already covered with an abuse contact. More statistics will be sent to the RIPE Anti-Abuse Working Group mailing list. In phase 1, we will send notifications to LIRs that haven't added abuse contact information to their LIR's ORGANISATION object. If this information is not added by the LIR by the end of phase 1, we will automatically add the LIR's contact email address (which is already publicly listed at: <https://www.ripe.net/membership/indices/>) as their abuse contact. LIRs can always change this information as needed. More information on the implementation plan, including phase 2 (covering PI space and ASNs) is available on RIPE Labs at: <https://labs.ripe.net/Members/kranjbar/implementation-details-of-policy-201…> ------------------------------- How to add "abuse-c" ------------------------------- An explanation of how to add "abuse-c:" to an LIR's ORGANISATION object as well as how to fine-tune abuse contact information for sub-allocations and assignments is outlined here: <https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-…> Please kindly consider adding abuse contact information as soon as possible to the ORGANISATION object(s) you control or maintain in the RIPE Database. Kind Regards, Kaveh Ranjbar, RIPE NCC Database Group Manager

1 0

Pre-PDP discussion: "Yearly list of services by RIPE"
by Richard Hartmann 02 Apr '13

02 Apr '13

Dear all, this is the fifth suggestion: RIPE will create a yearly list of all services it provides to members or the general public This list will include at least: * Name of the service * Cost in time and money of maintaining and possibly extending this service * Cost in time and money of maintaining the backend needed for this service; this is to catch stuff that relies on old and brittle infra * Number of users if applicable/traceable per year * Number of queries/transactions if applicable/traceable per year * General usefulness of the service from RIPE's POV * Status of service, such as "active, supported", "deprecated", or "scheduled for decommissioning on YYYY-MM-DD" * A suggestion for the future status of the service If in doubt, RIPE will focus less on detailed interpretation and analysis and more on giving out as many hard facts and stats as possible. Interpretation will happen on the mailing lists anyway. RIPE will implement this policy in a light-weight manner that is not a drain on resources in and as of itself.

7 14