October 2013 - ncc-services-wg

policy proposal 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders"
by Dimitri I Sidelnikov 23 Oct '13

23 Oct '13

Hi. Let me express my support for policy proposal 2012-07. -- Kind regards, --- D.Sidelnikov

2 1

Re: [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
by Carsten Schiefner 23 Oct '13

23 Oct '13

Dear colleagues - On 10.10.2013 16:07, Marco Schmidt wrote: > - An amendment to the existing policy document ripe-592 ...which is the following: Replace section 5.5 of ripe-592, currently: "Any LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by either the RIPE NCC or the IANA." with "Any LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that were previously allocated to them by the RIPE NCC or otherwise through the Regional Internet Registry System." Shall my understanding be that the rationale for replacing "the IANA" by "otherwise through the Regional Internet Registry System" is that the former - implying Legacy Internet Resources - would be in contradiction with the second paragraph: "Any existing or future RIPE policy referring to resources shall not apply to legacy resources unless the policy explicitly includes legacy resources in its scope." of section 1.2 "Scope" of the proposal? If not, what else is the rationale for this side effect on ripe-592 then? Anhow: the proposal gets my support - I'd like to see it becoming policy. Best, -C.

1 0

RIPE Policy Proposal 2012-07 "RIPE NCC Services to Legacy Internet Resource Holders"
by herve.clement＠orange.com 23 Oct '13

23 Oct '13

As this policy proposal brings clarification on management of Legacy Internet Resources, Orange supports its adoption as RIPE policy. Best regards [cid:image001.gif@01CECFE1.24CB7D70]<http://www.orange.com/> Hervé CLEMENT Naming, Addressing and Numbering Project Manager Orange/IMT/OLN/AQS/NAN tél. +33 (0)1 57 36 17 97 mob. +33 (0)6 78 91 39 38 herve.clement(a)orange.com<mailto:herve.clement@orange.com> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Re: [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
by Wilfried Woeber 22 Oct '13

22 Oct '13

Marco Schmidt wrote: > Dear colleagues, > > The draft document for version 4.0 of the policy proposal 2012-07, > "RIPE NCC Services to Legacy Internet Resource Holders" has now been > published, along with an impact analysis conducted by the RIPE NCC. While working through the Impact Analysis I am somewhat at a loss how Option 1 and Option 3 are to be handled. In particular, going for Option 1: would the Legacy Resource lose its status: LEGACY and be relabelled to PI or PA? If this is the case, I do not see the rationale for the text in Option 3: In the latter case, however, it should be made clear that the RIPE NCC will not allow the Legacy Resource Holder to become the sponsoring LIR for its own Legacy Internet Resources. In case the status: LEGACY for Option 1 is preserved, then I can agree to the restriction as quoted. Any clarification would be appreciated. Thanks, Wilfried

2 2

2012-08 Publication of Sponsoring LIR for Independent Number Resources Moved to Last Call
by Lindqvist Kurt Erik 17 Oct '13

17 Oct '13

All, following the discussions regarding policy proposal 2012-08 in the NCC-Services WG the chairs have decided a consensus for moving forward exists and thus the proposal is moved to Last Call. Kurtis & Bijal NCC Services WG chairs

8 15

2013-04 Proposal Accepted (Resource Certification for non-RIPE NCC Members)
by Marco Schmidt 16 Oct '13

16 Oct '13

Dear colleagues, Consensus has been reached, and the proposal described in 2013-04 has been accepted by the RIPE community. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2013-04/ The new RIPE document is ripe-596 and it is available at: https://www.ripe.net/ripe/docs/ripe-596 An announcement regarding the implementation will follow. Thank you for your input. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

2013-04 Resource Certification for non-RIPE NCC Members has concluded
by Lindqvist Kurt Erik 16 Oct '13

16 Oct '13

The policy proposal 2013-04 has concluded and the WG Chairs collective have declared that the PDP process has been followed. Announcement to follow from the RIPE NCC. Kurtis & Bijal

1 0

2012-08 Last Call for Comments (Publication of Sponsoring LIR for Independent Number Resources)
by Marco Schmidt 16 Oct '13

16 Oct '13

Dear colleagues, The proposal described in 2012-08, Publication of Sponsoring LIR for Independent Number Resources, is now in its Concluding Phase. The RIPE NCC Services Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 14 November 2013 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the co-Chairs of all RIPE Working Groups for consensus. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 Please e-mail any final comments about this proposal to ncc-services-wg(a)ripe.net before 14 November 2013. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Team 15 Oct '13

15 Oct '13

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://lirportal.ripe.net/training/courses 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

Fwd: [db-wg] Improvements to RIPE Database Software Release Management
by Wilfried Woeber 14 Oct '13

14 Oct '13

Dear Services and Routing folks, please see below fyi. My apologies for the short notice and/or duplicate messages. Regards, Wilfried -------- Original Message -------- Subject: [db-wg] Improvements to RIPE Database Software Release Management Date: Mon, 7 Oct 2013 13:31:06 +0200 From: Johan Åhlén <jahlen(a)ripe.net> To: db-wg(a)ripe.net <db-wg(a)ripe.net> Dear colleagues, Following recent discussion regarding the release management of the RIPE Database software, we looked closely at our procedures and would like to propose some improvements. Together with the Database Working Group chairs, we've scheduled an informal meeting during RIPE 67, open for anyone that is interested in this topic, to discuss the proposals and talk about how we can improve our procedures. The meeting will take place on Monday, 14 October from 18:00-19:00 in room Sigma + Theta. We hope you will join us. Of course, you can also send your feedback and suggestions to this list. This is what we propose: - Split the RIPE Database software into smaller modules. Modularisation would minimise the release frequency for our services. For instance, with a modern API like RDAP we might have bi-weekly major releases and weekly minor releases to quickly respond to changes in the specification. With the NRTM feed, there might be just one major release per year or even less. - Replace the "emergency release" with a "minor release" that only contains patches for operational purposes and bug fixes. No new functionality would be introduced and no feature changes. We would also have "major releases" where functionality is added, changed or removed. With major releases we would keep the minimum two-week user test period leading up to the production release as stated in the previously proposed release procedure. With any minor release, we would put it in production as soon as it's available. Most bugs affect some users. Rather than trying to determine urgency based on numbers of users, size of users, number of networks affected, importance of functionality affected, etc., we would treat all bugs the same. In short, if someone reports an issue to us, we fix it right away. This process has generally worked well over recent years. - Improve the test environment. We know that users would like to have their real data to do proper testing. To solve this issue, we propose to use snapshots of the current database for this purpose. - Improve communication surrounding new releases. This covers all documentation and how we inform users about changes. We hope that you find this way forward beneficial. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0