- db-wg - mailman.ripe.net

new "via" attributes in aut-num Class
by Aris Lambrianidis 14 Aug '13

14 Aug '13

> Dear colleagues, > > We received the suggested patch to the RIPE Database software from Job Snijders containing the implementation of the features he describes below. The code he submitted meets the quality standards we have in the Database team and from a technical point of view we are willing to apply the patch. > > If the community supports the addition of the proposed attributes the RIPE NCC can go ahead and merge his implementation and make it available in the next release. > > Kind regards, > > Johan Åhlén > Assistant Manager Database > RIPE NCC > > On 14 Aug 2013, at 15:50, Job Snijders <job.snijders at atrato.com> wrote: > Hello Everybody, I think this is a nice, clean way to work towards ratifying some much needed route servers specific attributes, so this is a +1 from me for the patch to be merged. -- Best regards, Aris Lambrianidis AMS-IX NOC http://www.ams-ix.net/

1 0

new "via" attributes in aut-num Class
by Job Snijders 14 Aug '13

14 Aug '13

Dear working group, As some of you might know I've been working on extending the RPSL syntax to make life easier for certain scenario's, such as operating a Route Server. The purpose of the new attributes and the patch is to make life easier for Route Server operators whom have to deal with participants who have been assigned a 32 bit ASN. There currently is no way to relay information between non-adjacent ASNs, and 32 bit ASNs do not fit into standard BGP communities when coupled with an action code. Often Route server operators overload BGP communities to assess which participant should receive what prefixes, the "via" feature addresses exactly that concern. I have submitted the following draft to the IETF: http://tools.ietf.org/html/draft-snijders-rpsl-via And I have submitted a patch for the RIPE whois server to support the feature. https://github.com/job/whois The extension should be backward compatible with minimal impact on existing tools and processes, following Section 10.2 of RFC2622. RPSL parsers which do not understand the new attributes are expected to just ignore it. I am looking for feedback from this community, and especially the community's blessing to allow RIPE NCC to adopt the patch. Kind regards, Job

2 1

Draft proposal: Guidance Requested: Reassigning Referenced ASNs
by Ingrid Wijte 14 Aug '13

14 Aug '13

Dear colleagues, Thank you for your feedback on this issue. Based on the input we have received we propose taking the following action: - The RIPE NCC will send an email to the maintainer and contacts of the RIPE Database objects in which the returned AS numbers are referenced, asking for the reference to be removed. - The RIPE NCC will send three additional reminders, at intervals of three weeks from each other, for a total of four emails. - If after four emails the reference is still in place, the RIPE NCC will update the RIPE Database object itself, removing the reference. - If the reference is being recreated within one month from deletion (possibly due to automatic updates), the RIPE NCC will contact the organisation through means of communication other than email. The total number of RIPE Database objects that reference returned AS numbers is currently about 2000. All references are in the policy attributes of aut-num objects. No route(6) objects are involved. Thank you again and best regards, Ingrid Wijte RIPE NCC

2 1

New RIPE Database Release Available Soon
by Johan Åhlén 08 Aug '13

08 Aug '13

Dear colleagues, We are pleased to announce that a new release of the RIPE Database will be available soon. Details about the upcoming release, including dates, descriptions of the changes and other factors that might affect you as a user, can be found here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.67… The first new feature is a diff functionality, which allows you to see, in detail, what changes were made between two versions of an object in the RIPE Database. Head over to RIPE Labs to read more about the diff feature: https://labs.ripe.net/Members/denis/diff-functionality-in-the-ripe-database We have also improved the way the Global Resource Service (GRS) data is imported. This allows us to present a more complete data set for all Internet resources throughout the world. This RIPE Labs article will bring you up to speed on the GRS improvements: https://labs.ripe.net/Members/denis/the-ripe-global-resource-service Lastly, we have also made several improvements to the REST API. As there are some changes, the new implementation will be deployed and running in parallel to the old version up until the next release. This provides you with time to verify your software and scripts against the new release. The implications of these changes are described in the release notes linked above. If you have any questions or comments, we look forward to hearing them! Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

abuse-c + org
by Gilles Massen 04 Jul '13

04 Jul '13

Dear WG, and RIPE NCC staff, While trying to add an abuse-c to our resources, I was quite surprised that you can only attach the abuse-c to an org object (while the policy suggests otherwise and implementation notes are not very clear on the limitation). So I'd like to ask why this restriction exists? What is wrong with adding an abuse-c directly to an inet[6]num or aut-num? Best regards, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

8 15

New Procedure for RIPE Database Software Releases
by Johan Åhlén 28 Jun '13

28 Jun '13

Dear colleagues, We have recently received valuable input on how we can improve our release procedures for the RIPE Database software. In order to further reinforce our processes, we have defined a new procedure together with the Database Working Group (WG) Chairs that will address the concerns that have been raised about the stability of the Database software by the community. The purpose of the new procedure is to give you notice of what the next release will contain and how it might affect you as a user. No matter what the impact of a new feature is, an announcement will always precede the deployment to production and you will be given sufficient time to test your software. The procedure is not too far from how we have been working up until now, but will be more strictly defined and will hopefully eliminate any surprises. We propose to proceed as follows: - We will move to a four to six week release cycle for the Database software - There will be no more than three new features per release - Each new release will be announced to the WG mailing list at least two weeks before we deploy to production - In the event that we are required to deviate from what was stated in the announcement, we will announce this to the WG mailing list - The new release will be available in Test Database at least two weeks before we deploy to production - We will announce to the WG mailing list when we have successfully completed deployments to Test Database - We will announce to the WG mailing list when we have successfully completed deployments to Production Database - In the special case of required emergency fixes, we will announce this to the WG mailing list as well as the website as soon as possible - We will make a follow-up announcement to the WG mailing list and the website as soon as a fixed version has been deployed - These two emergency announcements can be combined for security reasons, or if the problem is solved in less than 30 minutes For the initial release announcements, the following template will be used: Release number Expected date of deployment to Test Database Expected date of deployment to Production Database New features Impact on existing functionality Operational improvements Impact on existing functionality Fixed bugs Impact on existing functionality Expected upcoming features for next release We hope that you will find this procedure beneficial and with your consent we would like to move ahead with it effective immediately. We also intend to publish this procedure to the website together with a roadmap of what we expect that the upcoming releases will contain. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0

DB Software - release and deployment improvements
by Wilfried Woeber 28 Jun '13

28 Jun '13

Dear DB-WG, NCC-Services and Routing WG Community! Over the recent month or so, a deployment of a new version of the DB-SW, to the production environment, turned out to (potentially) have serious impact on automated router configurations in (an) operator's network(s). The issue was reported to the NCC's DB-WG Group and the specific problem has already been fixed (actually on the same day as reported). Here's the link to the service announcement page: http://www.ripe.net/lir-services/service-announcements/ripe-database-query-… However, as the incident seemes serious enough, a small group of interested people (Rüdiger, Nigel Titley, folks from the NCC and myself) started to dig a bit deeper, into what was (and is) perceived to be aspects that need review, more transparency and maybe improvement. We plan to look at some aspects, amongste others, like: - better communication regarding upcoming new SW releases - better transparency when and where (TEST DB, Production DB,...) new software will be deployed - version control and documentation But the most important thing is an improved and more transparent process to deploy new software versions *as soon as possible*! Then we can take it from there... While this message is also sent to the NCC Services and Routing WG, fyi, I'd like to suggest to have follow-up comments and discussion on the DB-WG List! Looking forward to fruitful discussions, best regards, Wilfried

1 0

Re: [db-wg] [address-policy-wg] Cosmetic Surgery Project: Extended Review Period until 9 July on revised RIPE Policy document for IPv6 database objects
by Emilio Madaio 26 Jun '13

26 Jun '13

Dear Peter, thank you very much for your input and remark. I apologize if I forgot to include the IPv6 and Database WG mailing lists as decided during RIPE 66 on request of the community. I slavishly followed the procedure defined by the Cosmetic Surgery Project that was meant for the Address Policy WG mailing list only. The original announcement for the extended Review Phase is available at: http://www.ripe.net/ripe/mail/archives/address-policy-wg/2013-June/007931.h… For further feedback the draft of the policy document is online and ready for community review at: https://www.ripe.net/ripe/readability/improving-the-readability-of-ripe-doc… Please send your feedback on this draft document before 9 July 2013. Best Regards Emilio Madaio Policy Development Officer RIPE NCC On 6/25/13 5:51 PM, Peter Koch wrote: > On Tue, Jun 25, 2013 at 03:29:45PM +0200, Emilio Madaio wrote: > >> https://www.ripe.net/ripe/readability/improving-the-readability-of-ripe-doc… > > May I express some doubts about the 'cosmetic surgery project'? > The project was introduced as early as October 2009 and RIPE 513 was published > in February 2011. What appears to happen is a very late post publication copy > editing. In this particular case, the policy itself is a change to the > database attributes and - other than, say, address allocation/assignment > policies - not very likely read its own. Any structural changes > to the document (where's the template, by the way?) and changes to style > (passive voice here and there) or readability might better be invested > in the general database documentation. > > The new draft eliminates the data protection aspect from the > introduction/motivation section, which I consider a loss. The abstract > wins, though. The draft continues to use 2000::/46 for the example > where some chunk of 2001:DB8::/32 as per RFC 3849 might be a better choice. > > -Peter >

1 0

Guidance Requested: Reassigning Referenced ASNs
by Andrea Cima 25 Jun '13

25 Jun '13

[Apologies for duplicates] Dear colleagues, At the Address Policy WG session during RIPE 66, the RIPE NCC requested guidance from the RIPE community on reassigning referenced 16-bit ASNs. Together with the Address Policy WG Chairs, we have decided to seek additional input from the WG mailing list. Background: the RIPE NCC has around 1,400 returned 16-bit ASNs that are currently referenced in route objects, and "import" and "export" lines in aut-num objects. Problem: there is a need for 16-bit ASNs by operators. However, because these ASNs are referenced, they are not being reassigned. At RIPE 66, the RIPE NCC suggested the following potential solutions: A. Not reassign referenced AS numbers B. Reassign AS numbers even if referenced C. Clean up the RIPE Database from references and then reassign the AS numbers C.1. "Silent" update; or C.2. Informing the object holder of the update Please find the RIPE Meeting slides at the following url: https://ripe66.ripe.net/presentations/176-Address_Policy_WG_RIPE_66.pdf This email has been sent to both the Address Policy WG and RIPE Database WG mailing lists, due to the impact the proposals would have on the RIPE Database. However, we would ask to keep the discussion on the Address Policy WG mailing list to facilitate participation and the channeling of feedback. Thank you in advance for your input and best regards, Andrea Cima RIPE NCC

2 1

Object Tags in the RIPE Database
by Johan Åhlén 19 Jun '13

19 Jun '13

Dear colleagues, The recent RIPE Database software rewrite has enabled us to offer new and valuable functionality to the community with minimal effort. One of these features is the Object Tags functionality, initially introduced by Kaveh Ranjbar at RIPE 66 and since then communicated to the community and the Database Working Group Chairs. We are now happy to announce that the Object Tags feature is fully deployed. Object Tags is publicly visible metadata related to an object in the RIPE Database. The tags do not appear by default and users can enable them by supplying the --show-tag-info option. The tags will appear in the comment section and it does not change the default behaviour of your queries. The main goal of the tags is to improve the data quality in the RIPE Database by, for example, better notifying users of potential issues with an object. As a secondary benefit, query results can now be filtered based on tags, making it easier for users to find exactly what they need. The RIPE NCC will maintain a list of the available tags on a webpage referenced in the Help section and in related documentation. Currently, there are two types of tags: - Objects due to be deleted by the automated clean-up are tagged: Unreferenced # will be deleted in n days - All RIPE and GRS resource data is tagged with either: {SOURCE}-REGISTRY-RESOURCE or {SOURCE}-USER-RESOURCE For more information and examples of how the new feature can be used, I'd like to refer you to Kaveh's RIPE Labs article at: https://labs.ripe.net/Members/kranjbar/ripe-database-object-tags We hope that you can come up with creative ways of using this functionality. We are eager to hear how you use this feature and what we can do to make it better. I would also like to take this opportunity to introduce myself as not everyone here knows who I am. My name is Johan Åhlén and I'm the new Assistant Database Team Manager at the RIPE NCC. I'm taking over Kaveh's role of managing the Database Team as Kaveh has accepted the new position of Head of Science Division. Before managing the Database Team, I worked as a Senior Software Engineer in the Business Applications Department where I was involved in the development of both internal and external RIPE NCC applications. I look forward to working with you all. Kind regards, Johan Åhlén Assistant Database Team Manager RIPE NCC

1 0

Historical data in ripe-db. whois with "--list-versions"
by Bengt Gördén 17 Jun '13

17 Jun '13

Hi, I've been using this service and I like it. But I ran into a problem, I think. I'm trying to see the history for 194.228.90.192/26. whois -h whois.ripe.net 194.228.90.192/26 <-------- Works. I get an inetnum for the network whois -h whois.ripe.net -- "--list-versions 194.228.90.192/26" <--------- Doesn't work. Provides no revision list whois -h whois.ripe.net 194.228.0.0/16 <-------- Works. I get an inetnum for the network whois -h whois.ripe.net -- "--list-versions 194.228.0.0/16" <--------- Works. Gives revision list Am I doing something wrong here? I suspect that the /26 inetnum hasn't changed since 2002 but shouldn't there be at least a rev. 1 for it? Or is it as it says in the proposal "there might have been cases were some changes are missing in the history, mainly for technical reasons"? regards, /bengan

2 2

API - INET6NUM Object Creation Bug
by Tim Garrison 10 Jun '13

10 Jun '13

Greetings, I have understood that doing an HTTP POST to https://apps.db.ripe.net/whois/create will respond with an HTTP201 status code and a 'Location' header pointing to the created object. This seems to work great for 'inetnum' and 'person' objects, but I've discovered that for 'inet6num' objects, the parent network block's handle is used in this header. This is creating problems for me in my current project, and I was wondering if someone could possibly take a look. Thanks! -- Tim Garrison Software Engineer II tgarrison(a)softlayer.com 281.714.4213 Direct 713.540.4325 Cell 866.398.7638 Toll-Free 281.714.4657 Fax SoftLayer Technologies, Inc. 315 Capitol Street Suite 205 Houston, TX 77002 http://www.softlayer.com/

2 2

[Training] New E-Learning Videos: Role Object and Abuse-C Set up
by Sandra Bras 10 Jun '13

10 Jun '13

[Apologies for duplicates] Dear colleagues, We are pleased to announce the launch of two new RIPE Database videos as part of our online training. The topics are: - Create a Role Object https://www.ripe.net/lir-services/training/e-learning/ripe-database/contact… - Set up Abuse Contact Information https://www.ripe.net/lir-services/training/e-learning/ripe-database/contact… For more videos go to https://www.ripe.net/lir-services/training/e-learning. Stay tuned! We plan to announce more exciting E-Learning news in the coming months. RIPE NCC E-Learning Tutorials are a free service available to everyone. If you have any questions or comments, feel free to contact us at <e-learning(a)ripe.net>. Happy learning! Sandra Brás E-Learning Project Manager

1 0

[training] RIPE NCC Training Courses July-September 2013
by Training Team 27 May '13

27 May '13

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 Rome, Chisinau, Munich, Moscow, Prague, London, Ljubljana, Yerevan, Malmö, Istanbul, Amsterdam. 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 - Database Training Course (new) - IPv6 for LIRs Training Course - Routing Security Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

Reminder:Cosmetic Surgery Project, new revised RIPE Policy, document for IPv6 database objects
by Emilio Madaio 21 May '13

21 May '13

Dear colleagues, As part of the Cosmetic Surgery Project, the RIPE NCC is moving forward with a review of the policy document ripe-513, "Value of the "status:" and "assignment-size:" attributes in INET6NUM objects for sub-assigned PA space". At the request of the proposers of the original policy proposal that produced ripe-513, we’re sending a reminder about the document review and inviting the IPv6 Working Group Mailing List and Database Working Group Mailing List subscribers to participate in the review process. A draft of the policy document is now online and ready for community review at: https://www.ripe.net/ripe/readability/improving-the-readability-of-ripe-doc… We encourage you to read the edited draft of ripe-513 and send any comments to <address-policy-wg at ripe.net> by 10 June 2013. Kind Regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

RIPE 66 Draft minutes
by Nigel Titley 15 May '13

15 May '13

Dear WG For your delight and delectation, please find the draft minutes for the DB-WG meeting at RIPE 66 are attached Comments and corrections to me please Nigel

3 2

Removing personal data from bulk output from the RIPE Database
by Denis Walker 14 May '13

14 May '13

Dear colleagues, We are proposing an improvement to the algorithm used for removing personal data from the bulk provisioning of RIPE Database data. Below you will find an explanation of the current process, why we’re proposing to change it and how the new process would work. ------------------------ Current process ------------------------ At the moment this data is published in three forms: • Complete dump, accessible from: <ftp://ftp.ripe.net/ripe/dbase/ripe.db.gz> • Split dump of each object type, accessible from: <ftp://ftp.ripe.net/ripe/dbase/split/> • A live feed using NRTM protocol, described at: < https://www.ripe.net/data-tools/db/nrtm-mirroring> These data dumps and streams are mainly used for keeping an up-to-date local copy of the RIPE Database or for research and analytical purposes. To prevent the bulk publishing of personal data, for example names, email addresses and phone numbers, we remove all personal data from these datasets. We call this process "dummification of personal data". At the moment it consists of replacing all PERSON and ROLE objects with a single dummy placeholder object as well as changing all references to the personal data objects from all other objects to refer to this dummy placeholder object. ------------------------------------------------- Rationale for Improving the Process -------------------------------------------------- We’ve received feedback from different users and researchers that we are overdoing the dummification. For example, one can obtain all references to personal objects without hitting any personal object result limits by querying the live RIPE Database with proper flags (like -r). This makes the "dummification" of these references in the data dumps meaningless. For more information, see: <http://www.ripe.net/data-tools/support/documentation/aup> ----------------------------------------------------- Proposal for New Dummification Algorithm ----------------------------------------------------- In order to improve the usability of the data dumps and streams, we are proposing to change the "dummification" algorithm to keep the actual personal objects and all references to them and only obfuscate the fields with personal data (for example real names, phone numbers and addresses). The new algorithm will also try to preserve data that is useful for researchers, while not revealing any data that might expose the identity of the date subject. For example, we are proposing to keep the first half of phone number digits or to keep the domain part of email addresses. The proposed changes should not affect any End User scripts currently running because the data will still be in the valid RIPE RPSL format. We propose to run the two datasets in parallel for some time to ensure a smooth transition. Further details and examples of how the dummified objects will change are detailed in a RIPE Labs article at: <https://labs.ripe.net/Members/kranjbar/proposed-improvements-to-dummificati…> Please let us know if you agree with the proposed improvements. Regards, Denis Walker Business Analyst RIPE NCC Database Group

4 4

Re: [db-wg] Removing personal data from bulk output from the RIPE Database
by Tore Anderson 10 May '13

10 May '13

* denis(a)ripe.net > Everyone is correct in what they have said. But when it comes to the > "changed:" attribute you have to rely on assumptions, estimates and 'good > enough' because the dates are not precisely defined. It is possible 90% of > changed dates are spot on, but you don't know that. > > No one would suggest that anyone would deliberately enter the wrong date. > And of course if you don't add a date the software will generate the > correct date for you. But if you wrote a template some time ago for > creating assignments and that template has a date in it, then everytime > you fill in the template to create a new assignment, it will have the > wrong date. Or if you 'change' the date on a single "changed:" attribute > every time you update the object, it will only show the 'last updated' > date. Or as Kaveh pointed out, maybe the object was created 10 years ago, > but you updated the information last week, without altering the changed > date. Do you consider the object to be stale data? There are so many ways > this date can represent something different to what you assume it to be. So while I have no illusions about that I'd get an exact number from looking at the "changed:" attribute, what I was really trying to say is that tried to use the database dumps on ftp.ripe.net for some purpose, but due to excessive dummification I couldn't. Hence I support the proposal to reduce the amount of dummification. Whether or not my desired query would stand up to any "scientific" scrutiny is really besides the point. That said, going slightly off topic wrt. the proposal itself: I'm still no closer to finding an answer to my question, which could be stated as: «How many IPv4 PA Assignments have been made by RIPE NCC LIRs since the 14th of September 2012? (If possible, but less important: How many addresses did these assignments consist of, in total?)» Even a very rough estimation is useful to me. Even just the order of magnitude would be interesting. "A dozen", "about five thousands", or "hundreds of thousands" - these are all results I could put in my slides to underline the point I want to make. While I think the use of the "changed:" attribute I originally planned would give me a useful enough result, I'm in no way married to that particular approach. So if there's some other way to get the number, possibly by having any of you RIPE NCC guys fetch it for me from some internal data source, that would be much appreciated! :-) I'd need it before Wednesday (well, preferably ASAP) if I'm going to be able to make use of it though. > As Kaveh also pointed out, you can query an object with the > '--list-versions' option and get a more accurate, reliable list of dates > for when an object was created and each update. But if you want to find > which PA assignments were created within a time period, you would have to > query them all to get the accurate historical dates. There are 3.7 million > assignment objects. For this type of analysis it might be easier if the > split file had a well defined date(s) you could rely on. No, I really wouldn't want to script 3.7M queries to your whois server...having an auto-generated "created:" attribute in the dumps (and in the whois service too for that matter) would certainly be better. Tore

2 2

Re: [db-wg] Removing personal data from bulk output from the RIPE Database
by James A. T. Rice 09 May '13

09 May '13

On Thu, 9 May 2013, denis(a)ripe.net wrote: > The "changed:" attribute is almost useless. Disagree, it gave a good indication of how stale an object was likely to be. If an object is is 15 years old, one wouldn't be too surprised if it's inaccurate. If it's from last month, then it's a lot more likely to be accurate. Cheers James

3 2

Re: [db-wg] Removing personal data from bulk output from the RIPE Database
by Tore Anderson 09 May '13

09 May '13

* denis(a)ripe.net > Unfortunately no dump will help you with this process. The "changed:" > attribute is almost useless. For what you want to do it IS useless. The > syntax requires all objects to have at least one mandatory "changed:" > attribute. The user can set the date to almost anything. It can be > tomorrow or ten years ago. When the object is changed, there is no > requirement to make any changes to this date or add any additional > "changed:" attributes. It is user generated and only has meaning to the > user. What you want to do would only work if these were auto generated > timestamps by the update software. But that is not the case. That may be so. But to turn it around - are you of the opinion that the LIRs to a great extent are deliberately supplying incorrect changed dates? If "no", it would be good enough for me, really. For my uses, an approximation will suffice. To be honest, I would actually be more concerned about the number being wrong because of LIRs assigning addresses to their customers without registering the assignments in the database, than I would be about LIRs registering their assignments, but with incorrect dates. BTW - the update software *does* generate time stamps. At least, I always send only my e-mail address, the bot does the rest. Tore

1 0

Re: [db-wg] Removing personal data from bulk output from the RIPE Database
by Tore Anderson 09 May '13

09 May '13

(Apologies for breaking threading, I just subscribed to the list.) In general, the proposal seems fine to me and I agree with its goals. In preparing for my APWG presentation next week, I've been wanting to find the answer to the question «how many IPv4 PA Assignments have been registered between dates A and B?». I thought I could do this by examining the inetnum database export - but that didn't work out, due to the fact that all the "changed:" attributes gets rewritten to "unread‌‌(a)ripe.net 20000101". So while I don't care about the e-mail addresses, I'd need the dates to be left intact. Also, the current algorithm folds all changed attributes into a single one. It's not clear from the Labs article whether or not this practise will stop - I hope it will. Would it by any chance be possible to get a sneak preview of the new inetnum dump, so that I could find the numbers I want before heading to Dublin? If so that would be greatly appreciated! Best regards, Tore Anderson

2 1

Reclaim Functionality for Resource Holders
by Denis Walker 29 Apr '13

29 Apr '13

Dear colleagues, With the new RIPE Database software now in place, the RIPE NCC has been able to automate a process that was previously handled manually. This process now allows resource holders to reclaim any operational database object related to the resources allocated and assigned to them by the RIPE NCC. You can find more details in a new article on RIPE Labs: https://labs.ripe.net/Members/denis/reclaim-functionality-for-resource-hold… Regards Denis Walker Business Analyst RIPE NCC Database Group

2 1

RIPE66 DB-WG Draft Agenda V1
by Wilfried Woeber 17 Apr '13

17 Apr '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear DB-WG folks, Chairpersons, "Meeting"! This is the 1st draft of an agenda for the DB-WG Meeting at RIPE66 in Dublin, May 15, 2013. For time slot allocations please refer to the most up-to-date meeting plan at https://ripe66.ripe.net/programme/meeting-plan/ The DB-WG Meeting is scheduled for *Wednesday*, starting at 09:00 local time / 08:00 UTC in the morning. The length of our timeslot is 90 Minutes. The overall (draft) RIPE 66 meeting outline is already available at https://ripe66.ripe.net/programme/meeting-plan/ Please feel free to propose additional topics to be discussed! I'd also suggest that you submit your points of view regarding the topics on the proposed agenda on the mailing list, preferably before the WG meeting's start :-) Best regards, hope to see you soon in Dublin, Wilfried. ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from previous WG meeting(s) . review of action list B. Data Base Operational Update (Kaveh Ranjbar, RIPE NCC) C. New DB-Software functionality - in beta - proposed D. Status update on IETF WEIRDS activities (N.N. t.b.c.) Y. Input from other Working Groups and/or Task Forces - review of abuse contact stuff (N.N. t.b.c.)) Z. AOB ________________________________________________________________________ 17.04.2013 16:00 UTC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQCVAwUBUW7IBd/RXX7wrLNpAQJymwP8D1Vt3oXoSkrfFuX05mNS2FLNIwucVYha uiAV89Zzk7uTxXa8dAQDpJgrVXIqaqaUgTjqpl1k8kYC85iuFsC8SEvjqQyx4czI oO99voS2x/qDXKI3nJj++4nuvswdDutYxSS5/ETk46sNWR8lsscMJ3Y8li1ttLEt eAJzPP8s9SQ= =YObZ -----END PGP SIGNATURE-----

1 0

Object Tags: a new feature proposal
by Kaveh Ranjbar 17 Apr '13

17 Apr '13

Dear colleagues, We would like to propose a method for providing metadata about objects in the RIPE Database. This new feature will enable a lot of flexibility to inform users about the state of each object and will help improve the quality of data in the RIPE Database. It can also provide a mechanism to fine-tune RIPE Database query outputs, which will give users who have less knowledge about address hierarchy, placeholder objects, etc. easier access to the data they are looking for. You can find more information about this proposal, along with some examples, at: https://labs.ripe.net/Members/kranjbar/ripe-database-object-tags Please kindly provide us with your feedback. Kind regards, Kaveh Ranjbar RIPE NCC Database Group Manager

1 0

Access to historical data in the RIPE database
by Nigel Titley 16 Apr '13

16 Apr '13

Following the announcement and the general positive feedback on this list, the RIPE NCC will be shortly enabling access to historical data in the RIPE database. Best regards Nigel

2 1