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

Account/login (Customer number : 112319 , Registry ID : be.zapfinv , Reference : RIPE)
by Sitaula, Dipak 10 Oct '13

10 Oct '13

Dear, We got an e-mail from RIPE to update our contact information of the RIPE account but we have lost our Login (username and password) detail. Technical contact is : KDM Can u provide us our login detail please... Kind regards, -- Dipak Sitaula Network Administrator M: +32 495 267467 E: dipak.sitaula(a)zapfi.com www.zapfi.com Intelligent Mobile Marketing Click<http://content.zapfi.com/disclaimer/ZFDisclaimer.html> to view our disclaimer. We are committed to the preservation of the environment. We encourage you to only print this email if absolutely necessary.

2 1

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

10 Oct '13

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. Some of the main differences from version 3.0 include: - Rewording and new text in section 1.2 (Scope) - Rewording and new text in section 2.6 (No relationship) - New section 2.7 (Lapse of relationship or agreement) - Rewording and new text in section 3.0 (Contractual requirements) - An amendment to the existing policy document ripe-592 You can find the full proposal and 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 8 November 2013. Regards Marco Schmidt Policy Development Office RIPE NCC

1 0

Expansion of eligible address space for Resource Certification (RPKI)
by Alex Band 10 Oct '13

10 Oct '13

Dear colleagues, When the Resource Certification (RPKI) service was launched in 2011, only address space allocated to the RIPE NCC directly by IANA was eligible for certification. Today, we are happy to announce that all address space that was historically transferred to the RIPE NCC from other Regional Internet Registries (RIRs) is also eligible. These ranges are so called "minority" address space, meaning that the full /8 block is managed by one of the four other RIRs, but a subset is managed by the RIPE NCC. LIRs who hold address space in these minority ranges will automatically have those resources added to their certificate, if they already have one. Starting today, they can create Route Origin Authorisations (ROAs) for the BGP announcements that they make with these prefixes. Resource Certification (RPKI) is a free service offered by all RIRs to offer BGP Origin Validation. It allows operators to request a digital certificate containing their Internet number resources and make cryptographically verifiable statements about their intended BGP announcements. These ROAs allow other network operators to make reliable routing decisions. In the RIPE NCC service region, more than 1,600 LIRs have requested a resource certificate and created ROAs for over six /8s worth of address space. To read more about this service, please visit: http://ripe.net/certification If you have any questions, please do not hesitate to contact us at <certification(a)ripe.net> Kind regards, Alex Band Product Manager RIPE NCC

1 0

Syntax Change to Aut-num Object in the RIPE Database
by Denis Walker 09 Oct '13

09 Oct '13

Dear colleagues, We would like to give you a heads-up about a proposal, currently being considered, to add two new attributes to the aut-num object in the RIPE Database: "import-via:" and "export-via:". In this email we are not concerned with the details of this specific change so much as the fact that a change is being considered. We know that these objects are very important for routing and many of them are updated daily in the RIPE Database. We also know that many scripts exist for auto-generating these objects and processing the contents. Although the RFC for RPSL clearly states that scripts should be written to ignore attributes they don't recognise, we don't know if all scripts are written this way. The RIPE NCC is considering the best ways to get information about any changes to routing object syntax in the RIPE Database out to the people who need to know. We would welcome any feedback on this issue from the community. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 0

NCC Services WG Draft Agenda - RIPE 67
by Bijal Sanghani 02 Oct '13

02 Oct '13

Dear colleague, Please see below and online the draft agenda for the NCC Services WG - RIPE 65 - https://ripe67.ripe.net/programme/meeting-plan/services-wg/ Date: Wednesday 26 September 2012 Time: 16.00 - 17.45 Chair: Kurtis Lindqvist Co-Chair: Bijal Sanghani A. Administrative Matters (5 minutes) Welcome Select a scribe Finalise agenda Approve minutes from RIPE 66 B. RIPE NCC Survey Results - Serge Radovcic, RIPE NCC and Desiree Miloshevic, Oxford Internet Institute (15 minutes) C. RIPE NCC outlook - Axel Pawlik, RIPE NCC (20 minutes) D. Services update and address hijacking issues - Andrew de la Haye, RIPE NCC (20 minutes) E. Policy Proposals Update - NCC Services WG Chairs (10 minutes) - 2012-07, RIPE NCC Services to Legacy Internet Resource Holders - 2012-08, Publication of Sponsoring LIR for Independent Number Resources, Nick Hilliard, INEX - 2013-04, Resource Certification for non-RIPE NCC members F. Open Microphone Session Z. AOB regards, Bijal & Kurtis NCC Services WG Chairs

1 0

Re: [ncc-services-wg] [db-wg] RIPE Database Release 1.69 Available Now
by Denis Walker 01 Oct '13

01 Oct '13

Dear Aris This was a small change that we implemented quite some time ago. It was not included in previous releases and added into the latest which is probably why we missed it in the release notes. We had previously announced the change in the 'DIFF' implementation with this now being the default behaviour. We were asked at the last RIPE Meeting for this dry-run behaviour. If it is still considered useful to have a subject line keyword to trigger a dry-run we can change it to a new keyword (DRY-RUN) on the next release. Regards Denis Walker Business Analyst RIPE NCC Database Team On 01/10/2013 13:03, Aris Lambrianidis wrote: > Thanks for the explanation Denis! > > Perhaps it'd be prudent to clarify that somewhere on the website. In > my mind the deprecated use of the DIFF keyword was a completely > separate issue from the dry-run option, as those modifications as to > how objects are parsed were done at different points in time. > > Plus, the warnings and errors produced are not as helpful, there's > the (standard) warning about using the DIFF keyword and then an error > about "dry-run being supported only when a single object is > specified". > > Kind regards, > > Aris Lambrianidis AMS-IX B.V. Tel.+31 (0)6 23 59 41 58 > http://www.ams-ix.net/ > > > > > On Oct 1, 2013, at 12:51 , Denis Walker <denis(a)ripe.net> wrote: > >> Dear Aris, >> >> If you use the keyword 'DIFF' in a subject line of an email update >> the software will treat the update as a dry-run and does not handle >> multiple objects. >> >> There is no need to use 'DIFF' as a keyword to get a diff output. >> By default all notification messages for object modifications now >> return the diff output followed by the full new object. >> >> Regards Denis Walker Business Analyst RIPE NCC Database Team >> >> >> On 01/10/2013 12:34, Aris Lambrianidis wrote: >>> Hello Denis and all, >>> >>> Any chance the new feature broke multiple object updates via a >>> single email (without using the dry-run option, ofc.)? We seem to >>> be getting error messages when trying to do that, I've already >>> notified auto-dbm@ about it. >>> >>> Aris Lambrianidis AMS-IX B.V. Tel.+31 (0)6 23 59 41 58 >>> http://www.ams-ix.net/ >>> >>> On Sep 23, 2013, at 15:50 , Denis Walker <denis(a)ripe.net> wrote: >>> >>>> Dear colleagues, >>>> >>>> Release 1.69 of the RIPE Database has now been fully deployed. >>>> >>>> Regards, >>>> >>>> Denis Walker Business Analyst RIPE NCC Database Team >>>> >>>> >>>> >>>> >>>> -------- Original Message -------- Subject: [db-wg] RIPE >>>> Database Release 1.69 Available Soon Date: Mon, 09 Sep 2013 >>>> 15:27:50 +0200 From: Denis Walker <denis(a)ripe.net> >>>> Organization: RIPE NCC To: Database WG <db-wg(a)ripe.net>, NCC >>>> Services WG <ncc-services-wg(a)ripe.net> >>>> >>>> Dear colleagues, >>>> >>>> The RIPE NCC is pleased to announce that we have deployed a >>>> new release of the RIPE Database to the TEST Database >>>> environment. Detailed information about the new release, >>>> including dates and information about the changes can be found >>>> here: >>>> https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.69 >>>> >>>> >>>> >> >>>> Of special note in this release is the inclusion of "dry-run". Using the >>>> dry-run function you can test whether an update would succeed >>>> or not. The update procedure runs as normal except that no >>>> change is made to the database. Find out more about the dry-run >>>> function here: >>>> https://labs.ripe.net/Members/denis/dry-run-testing-in-the-ripe-database >>>> >>>> >>>> >> >>>> Due to recent issues with the REST API, we've extended the migration >>>> period up until the 1.70 release. This release is currently >>>> scheduled for the end of October. >>>> >>>> If you have any questions or comments, we look forward to >>>> hearing them! >>>> >>>> Regards, >>>> >>>> Denis Walker Business Analyst RIPE NCC Database Team >>>> >>>> >>>> >>>> >>>> >>> >

2 1

Re: [ncc-services-wg] [db-wg] RIPE Database Release 1.69 Available Now
by Denis Walker 01 Oct '13

01 Oct '13

Dear Aris, If you use the keyword 'DIFF' in a subject line of an email update the software will treat the update as a dry-run and does not handle multiple objects. There is no need to use 'DIFF' as a keyword to get a diff output. By default all notification messages for object modifications now return the diff output followed by the full new object. Regards Denis Walker Business Analyst RIPE NCC Database Team On 01/10/2013 12:34, Aris Lambrianidis wrote: > Hello Denis and all, > > Any chance the new feature broke multiple object updates via a single > email (without using the dry-run option, ofc.)? We seem to be getting > error messages when trying to do that, I've already notified > auto-dbm@ about it. > > Aris Lambrianidis AMS-IX B.V. Tel.+31 (0)6 23 59 41 58 > http://www.ams-ix.net/ > > On Sep 23, 2013, at 15:50 , Denis Walker <denis(a)ripe.net> wrote: > >> Dear colleagues, >> >> Release 1.69 of the RIPE Database has now been fully deployed. >> >> Regards, >> >> Denis Walker Business Analyst RIPE NCC Database Team >> >> >> >> >> -------- Original Message -------- Subject: [db-wg] RIPE Database >> Release 1.69 Available Soon Date: Mon, 09 Sep 2013 15:27:50 +0200 >> From: Denis Walker <denis(a)ripe.net> Organization: RIPE NCC To: >> Database WG <db-wg(a)ripe.net>, NCC Services WG >> <ncc-services-wg(a)ripe.net> >> >> Dear colleagues, >> >> The RIPE NCC is pleased to announce that we have deployed a new >> release of the RIPE Database to the TEST Database environment. >> Detailed information about the new release, including dates and >> information about the changes can be found here: >> https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.69 >> >> >> Of special note in this release is the inclusion of "dry-run". Using the >> dry-run function you can test whether an update would succeed or >> not. The update procedure runs as normal except that no change is >> made to the database. Find out more about the dry-run function >> here: >> https://labs.ripe.net/Members/denis/dry-run-testing-in-the-ripe-database >> >> >> Due to recent issues with the REST API, we've extended the migration >> period up until the 1.70 release. This release is currently >> scheduled for the end of October. >> >> If you have any questions or comments, we look forward to hearing >> them! >> >> Regards, >> >> Denis Walker Business Analyst RIPE NCC Database Team >> >> >> >> >> >

3 2

Re: [ncc-services-wg] 2012-08 Review Period extended until 1 October 2013 (Publication of Sponsoring LIR for Independent Number Resources)
by Bijal Sanghani 30 Sep '13

30 Sep '13

Dear All, As per the below mail, the NCC Services working group chairs decided to extend the review period for 2012-08 until the 1st of October. It would really help us and the authors if we had some more feedback on the mailing list, even a +1 to go ahead or -1 if you feel it's not needed. Please take a few minutes (it's not a lot to read) and let us know your thoughts so that we can move to the next steps once the review period has ended. Many thanks, Bijal and Kurtis NCC Service WG Chairs On 2 Sep 2013, at 14:39, Marco Schmidt <mschmidt(a)ripe.net> wrote: > > Dear Colleagues, > > > The Review Period for the proposal 2012-08, "Publication of Sponsoring LIR > for Independent Number Resources", has been extended until 1 October 2013. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2012-08 > > > We encourage you to review this policy proposal and send your comments > to <ncc-services-wg(a)ripe.net>. > > Regards, > > Marco Schmidt > Policy Development Office > RIPE NCC > >

24 31

Update regarding the proposals to improve the technical infrastructure supporting the RIPE Policy Development Process
by Mihnea-Costin Grigore 26 Sep '13

26 Sep '13

Dear colleagues, Before the previous RIPE Meeting in Dublin, a number of proposals were brought forward in the RIPE NCC Services Working Group by members of the community, dealing with suggested updates to the technical infrastructure that supports the Policy Development Process. You can read the corresponding threads here: 1. "plain text" https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002154.h… 2. "PDP names" https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002150.h… 3. "unified diff" https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002151.h… 4. "everything should use GIT" https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-March/002152.h… A lively discussion ensued on the mailing list, and it was also part of the agenda of the Working Group at the RIPE 66 Meeting in Dublin: https://ripe66.ripe.net/archives/steno/13/ Following feedback from the community, a group was formed to address the issue and agree on a problem statement that would approach the issue from a high level, without going into technical and implementation details. The group consisted of Richard Hartmann, Alex Le Heux, Ruediger Volk, Emilio Madaio and myself. The group had a number of remote conferences and email discussions over the summer, and would like to present to you a finalised version of the problem statement (attached below). Please let us know if you think the text can be improved in any way, sending your comments and any suggestions to the list. Once a consensus is reached by the community, the RIPE NCC will evaluate the feedback and propose possible solutions. Regards, Mihnea-Costin Grigore RIPE NCC [------------8<------------] Problem Statement -------------------- The RIPE PDP process is too complicated for everyone: outsiders, new members, experienced members, authors, and the RIPE NCC. Therefore, participation should be made easier, especially for new-comers. Main scope: - The initial focus and effort are on the RIPE PDP -- proposals, drafts and policy documents; if any progress is made here, then we can think of applying the same or similar solutions to other areas of RIPE documentation - Any solutions discussed should also work for non-techies Details of the problem: a) The meta-data provided is incomplete: - RIPE Policy Documents and Policy Proposals don't have unique and clearly identified global names/identifiers - There is no clear version and date for publication - There is no track of who and when requested and approved a certain change - There is no clear up to date succession and obsolescence information within documents - There is no canonical way to get an overview of all currently active documents b) There is no systematic access to all versions of a document: - There is no directly available history - There are no easy to use tools to correlate between versions - There are no tools for authors to submit new/corrected versions of a document as it evolves through the PDP c) There is no plain-text version of each document and version thereof in ASCII format [------------8<------------] -- Mihnea-Costin Grigore RIPE NCC Web Services Team Leader - http://www.ripe.net/

8 9

Introducing the Assisted Registry Check
by Matt Parker 24 Sep '13

24 Sep '13

Dear colleagues, After a successful pilot, the RIPE NCC is pleased to announce the launch of the Assisted Registry Check (ARC) - an improvement to our existing audit activities based on feedback from members and the RIPE community. As mandated by the RIPE community, the RIPE NCC has always conducted regular audits of LIRs to ensure the quality and currency of their registry data. Until now, these audits have largely been conducted whenever an LIR requested an additional IPv4 allocation. However, now that we've reached the final /8 and LIRs can only receive one final /22 IPv4 allocation, there will be a significant drop in the number of these "additional allocation audits" carried out by the RIPE NCC. The ARC review is a way for the RIPE NCC to maintain this periodic contact with LIRs and to ensure that the accuracy of data in the RIPE Registry is maintained, without placing any additional burden on the participating LIR's operations. It was clear from previous feedback that the RIPE NCC's audit activities needed to be more efficient and less time consuming for LIRs. With this in mind, the RIPE NCC will initially conduct ARC reviews for a period of three months, during which time we will closely monitor the time and effort required by LIRs. At the end of this period, we will complete an in-depth review and incorporate any feedback as appropriate. Continual development is a vital component of the ARC review and will ensure that the activity remains relevant, useful and helpful to LIRs. During the ARC review, the RIPE NCC will perform a variety of consistency checks to assess the quality of LIRs' registry data. We will then provide personalised support to help correct any issues that are found. This helps to raise awareness of routing and reverse DNS inconsistencies as well as helping LIRs to strengthen the quality of their registry data. More information about what the ARC review involves can be found here: https://www.ripe.net/lir-services/resource-management/assisted-registry-che… There is also a RIPE Labs article that explains the process in more detail here: https://labs.ripe.net/Members/matt_parker/the-assisted-registry-check-let-u… If you are interested in participating and would like to volunteer for an Assisted Registry Check, please send us an email at<lir-help(a)ripe.net> and we will contact you with further details. Kind regards Matt Parker Registration Services RIPE NCC

1 0