- db-wg - mailman.ripe.net

Addition of long query options
by Kaveh Ranjbar 05 Apr '13

05 Apr '13

Dear colleagues, With the latest RIPE Database software release, we introduced the choice of longer names for query options. Now each existing query option has an equivalent long name starting with a double dash. These names are more descriptive than the single character options. For example, "-x", which represents exact match searches, has "--exact" as its longer equivalent. The existing behaviour doesn't change; these long names can be used in addition to the short ones, which are all still valid. Using these longer names allows for more descriptive queries. When a query is passed on to a colleague or when it is coded inside a script, the reader will have a better understanding of what the query is searching for without having to consult the documentation. It also allows more flexibility to introduce new query options as more features are added to the RIPE Database. Below you will find the full list of RIPE Database query server options. This list can be generated any time with the query "whois -h whois.ripe.net help" as well. Kind Regards, Kaveh Ranjbar, RIPE NCC Database Group Manager. ... % The following options are available: % % -x, --exact <ip-lookup> % Requests that only an exact match on a prefix be performed. If no % exact match is found no objects are returned. % % -l, --one-less <ip-lookup> % Returns first level less specific inetnum, inet6num or route(6) % objects, excluding exact matches. % % -L, --all-less <ip-lookup> % Returns all level less specific inetnum, inet6num or route(6) % objects, including exact matches. % % -m, --one-more <ip-lookup> % Returns first level more specific inetnum, inet6num or route(6) % objects, excluding exact matches. % % -M, --all-more <ip-lookup> % Returns all level more specific inetnum, inet6num or route(6) % objects, excluding exact matches. % % -C, --no-irt <ip-lookup> % Turns off default option '-c' or '--irt'. % % -c, --irt <ip-lookup> % Requests first level less specific inetnum or inet6num objects with % the "mnt-irt:" attribute (enabled by default). % % -b, --abuse-contact <ip-lookup> % Requests first level less specific inetnum or inet6num objects with % the "abuse-c:" reference. Only object keys and "abuse-mailbox:" % attributes are visible. % % -d, --reverse-domain <ip-lookup> % Enables use of the -m, -M, -l and -L flags for lookups on reverse % delegation domains. % % -i, --inverse <attribute-name> <inverse-key> % Perform an inverse query. % % -F, --brief % Produce output using short hand notation for attribute names. % % -K, --primary-keys % Requests that only the primary keys of an object to be returned. The % exceptions are set objects, where the members attributes will also % be returned. This flag does not apply to person and role objects. % % -k, --persistent-connection (optional normal query) % Requests a persistent connection. After returning the result the % connection will not be closed by the server and a client may issue % multiple queries on the same connection. % Note, that server implements 'stop-and-wait' protocol, when no next % query can be sent before receiving a reply for the previous one. % Except the first -k query, -k without an argument closes the % persistent connection. % % -G, --no-grouping % Disables the grouping of objects by relevance. % % -B, --no-filtering % Disables the filtering of "notify:", "changed:" and "e-mail:" % attributes. % % -r, --no-personal % Switches off recursion for contact information after retrieving the % objects that match the lookup key. % % -T, --filter-types (comma separated list of object types, no white space is allowed) % Restricts the types of objects to lookup in the query. % % -a, --all-sources % Specifies that the server should perform lookups in all available % sources. See also "-q sources" or "--all-sources" query. % % -s, --sources (comma separated list of sources, no white space is allowed) % Specifies which sources and in which order are to be looked up when % performing a query. % % -q (sources|version|types) % "sources" see list-sources. % "version" see version. % % --list-sources % Returns the current set of sources along with the information % required for mirroring. See [REF], section 2.9 "Other server % features" for more information. % % --version % Displays the current version of the server. % % -t, --template <object-type> % Requests a template for the specified object type. % % -v, --verbose <object-type> % Requests a verbose template for the specified object type. % % -V, --client <client-tag> % Sends information about the client to the server. ...

1 0

Access to historical data in the RIPE Database
by Kaveh Ranjbar 04 Apr '13

04 Apr '13

Dear colleagues, We would like to propose making the history of changes to objects available through the RIPE Database. This is one of the most requested features and will help different groups of users by providing more information about objects in the database. Our proposal, along with examples and details about possibilities and restrictions, is published at: https://labs.ripe.net/Members/kranjbar/proposal-to-display-history-of-objec… If accepted, we can enable this feature in a Beta state quite quickly. Please kindly provide us with your feedback. Kind regards, Kaveh Ranjbar, RIPE NCC Database Group Manager

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

Call for agenda items, DB-WG Meeting during RIPE66, Dublin, IE
by Wilfried Woeber 22 Mar '13

22 Mar '13

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE66 in Dulin, IE, May 13 - May 17, 2013, have already started a while ago - thus this _call for agenda items_ for the meeting of the Database Working-Group. Please submit (to the WG list!) your item requests and|or suggest topics for discussion to be included in the draft agenda! Please note that the DataBase-WG meeting is *at the moment* scheduled for *Wednesday* (starting at 9:00 local time). This is according to the *draft* meeting plan - which is pretty stable already but may still need to be changed as we get closer to the meeting date! The overall (draft) RIPE 66 meeting outline is already available at https://ripe66.ripe.net/programme/meeting-plan/ Looking forward to a successful meeting and see you soon in Ireland, Wilfried.

1 0

Status of the language: attribute
by Jan-Erik Eriksson 21 Mar '13

21 Mar '13

Dear DB-WG members, My name is Jan-Erik Eriksson, representing the ccTLD AX I would like to express our strong support for the continuance of the, currently beta state, attribute 'language:' for the inetnum and inet6num object type in the RIPE DB. Background: AX is the ISO country code for the Åland Islands. The Åland Islands is an autonomous, demilitarized and neutralized region belonging to Finland. Its official language is Swedish. Åland are governed according to the Act on the Autonomy of Åland and international treaties. The autonomy is well developed and in many ways Åland function like a sovereign state. The symbols of the autonomy can be seen in the own national flag, stamps, the Parliament building and internet top-level domain (.ax). Our special situation as a Swedish speaking area with the country of Finland have and still are imposing great challenges for s in the on-line world. Typically web services, ads, media and other on-line content is presented to our users in the wrong language. To solve these issues today the only way is to approach the presenter of that content, for instance Google, and lobby for them to handle this situation. As you all understand, this task is impossible considering the number of parties that we would need to contact. In this respect, the language attribute, if supported by the RIPE/Internet community, could serve as a de facto source of reference for both operators, content providers and geoip suppliers. We also believe there are other multi-language countries in Europe that could benefit from using this attribute, should there be a widespread adoption of its use. Sincerely, Jan-Erik Eriksson CTO Ålands Telekommunikaton Ab

4 4

RIPE abuse finder
by Max Tulyev 21 Mar '13

21 Mar '13

Hello! Recently our company started to receive a lot of strange complaints relating to network we don't operate or route. I fount these complaints was sent to points of contact got by RIPE abuse finder. This is the fresh sample of it: IP: 31.133.58.219 Output of RIPE abuse finder: https://apps.db.ripe.net/whois/use-cases/abuse-finder.json?source=ripe&prim… { "abuse-resources":{ "service":"abuse-finder", "link":{ "xlink:type":"locator", "xlink:href":"http://apps.db.ripe.net/whois/use-cases/abuse-finder.json?source=ripe&prima…"} , "parameters":{ "primary-key":{ "value":"31.133.58.219"} , "sources":{ "source":{ "name":"RIPE", "id":"ripe"} } } , "irt-objects":null, "abuse-mailbox-attributes":{ "attribute":{ "name":"abuse-mailbox", "value":"support(a)netassist.ua"} } , "objects-with-abuse-related-remarks":null} } whois -B 31.133.58.219 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Information related to '31.133.32.0 - 31.133.63.255' inetnum: 31.133.32.0 - 31.133.63.255 netname: DIDAN descr: FOP Trubnikov Valeriy Muhaylovich country: UA org: ORG-FTVM1-RIPE admin-c: TA3197-RIPE tech-c: TA3197-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT mnt-by: TRUBNIKOV-MNT mnt-routes: TRUBNIKOV-MNT mnt-domains: TRUBNIKOV-MNT changed: hostmaster(a)ripe.net 20110415 changed: hostmaster(a)ripe.net 20110415 source: RIPE organisation: ORG-FTVM1-RIPE org-name: FOP Trubnikov Valeriy Muhaylovich org-type: other address: 86156, Ukraine, Makiyivka, Zeleniy, 60/182 admin-c: TV1866-RIPE tech-c: TA3197-RIPE e-mail: core(a)didan.org mnt-ref: TRUBNIKOV-MNT mnt-by: TRUBNIKOV-MNT changed: core(a)didan.org 20110414 source: RIPE person: Trubnikov Andrey address: 86156, Ukraine, Makiyivka, Zeleniy, 60/182, phone: +380623277657 nic-hdl: TA3197-RIPE changed: core(a)didan.org 20110331 mnt-by: TRUBNIKOV-MNT source: RIPE % Information related to '31.133.48.0/20AS52091' route: 31.133.48.0/20 descr: FOP Trubnikov Valeriy Muhaylovich origin: AS52091 mnt-by: TRUBNIKOV-MNT changed: core(a)didan.org 20110423 source: RIPE % Information related to 'AS52091' aut-num: AS52091 as-name: TRUBNIKOV-AS descr: FOP Trubnikov Valeriy Muhaylovich org: ORG-FTVM1-RIPE import: from AS47694 accept ANY export: to AS47694 announce AS52091 import: from AS21189 accept ANY export: to AS21189 announce AS52091 admin-c: TA3197-RIPE tech-c: TA3197-RIPE mnt-by: RIPE-NCC-END-MNT mnt-by: TRUBNIKOV-MNT mnt-routes: TRUBNIKOV-MNT changed: hostmaster(a)ripe.net 20110415 source: RIPE organisation: ORG-FTVM1-RIPE org-name: FOP Trubnikov Valeriy Muhaylovich org-type: other address: 86156, Ukraine, Makiyivka, Zeleniy, 60/182 admin-c: TV1866-RIPE tech-c: TA3197-RIPE e-mail: core(a)didan.org mnt-ref: TRUBNIKOV-MNT mnt-by: TRUBNIKOV-MNT changed: core(a)didan.org 20110414 source: RIPE person: Trubnikov Andrey address: 86156, Ukraine, Makiyivka, Zeleniy, 60/182, phone: +380623277657 nic-hdl: TA3197-RIPE changed: core(a)didan.org 20110331 mnt-by: TRUBNIKOV-MNT source: RIPE whois -B TRUBNIKOV-MNT % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Information related to 'TRUBNIKOV-MNT' mntner: TRUBNIKOV-MNT descr: FOP Trubnikov Valeriy Muhaylovich admin-c: TA3197-RIPE upd-to: core(a)didan.org auth: MD5-PW # Filtered mnt-by: TRUBNIKOV-MNT referral-by: TRUBNIKOV-MNT changed: core(a)didan.org 20110418 source: RIPE # Filtered person: Trubnikov Andrey address: 86156, Ukraine, Makiyivka, Zeleniy, 60/182, phone: +380623277657 nic-hdl: TA3197-RIPE changed: core(a)didan.org 20110331 mnt-by: TRUBNIKOV-MNT source: RIPE Is it a bug or a feature, and why?

5 14

Soft launch of "abuse-c:", ripe-563: Improving Abuse Contact Information
by Kaveh Ranjbar 19 Mar '13

19 Mar '13

[Apologies for duplicate emails] Dear Colleagues, RIPE NCC has initiated a soft launch of phase one of RIPE Policy 563: "Abuse Contact Management in the RIPE Database". All facilities to provide abuse contact information for organisations registered in the RIPE Database are be in production state. Please see the announcement sent earlier to the RIPE Anti-Abuse Working Group mailing list (http://www.ripe.net/ripe/mail/archives/anti-abuse-wg/2013-March/002226.html). Kind Regards, Kaveh Ranjbar Database Group Manager RIPE NCC

1 0

Redevelopment of the RIPE Database software is complete
by Kaveh Ranjbar 25 Feb '13

25 Feb '13

Dear Colleagues, The RIPE NCC is proud to announce that our redevelopment of the RIPE Database software is complete. At RIPE 63, the RIPE NCC announced that we were starting a project to replace the 11-year old legacy RIPE Database software with a new system. At RIPE 64, we were able to report completion of the new query software and the start of the update project. The new query software has been handling all queries for almost a year, and the new update software is now in place and handling all updates. This new software is able to scale the RIPE Database to meet the expanding requirements of the members, the RIPE community and the RIPE NCC. It will also improve our response times on bug fixes, changes and major feature requests. With near complete unit test coverage of the code, higher level integration tests and extensive end to end 'use case' testing we have greatly improved the maintainability and reliability of the entire RIPE Database infrastructure. The new systems were rolled out incrementally, so the process was almost invisible to users of the service. The new software is mostly backwards compatible, although we have introduced some long-anticipated features and requirements. On our website, we are publishing software release notes that are updated for each new release. These can be found here: http://www.ripe.net/data-tools/db/release-notes With the new software now in place, we have a lot of opportunity for future expansion of the service and to implement features desired by the members and the wider community. During the redevelopment process we also had the chance to improve the behaviour of our system. Some of the areas improved are: - Some community-approved policies which were not fully enforced within the RIPE Database are now enforced by the new software for all RIPE address space. - A lot of issues in the authorisation are resolved. Resource holders now have full control over the resources they maintain and situations where they might lose control of their resources by mistake are no longer possible. - All resources allocated or assigned by the RIPE NCC have their entries in the RIPE Database protected against accidental deletion by users. - The new system accepts IPv6 network addresses in different formats, but always normalises the input to a single format which is used for storing, searching and displaying the records. If you query, create, modify or delete an object, no matter what format you specify the address in, it will first be normalised, then the operation will be actioned. In general, the new system is much smarter in the interpretation of IPv4 and IPv6 addresses on input and can handle different notations. - New error messages are more comprehensive and the system provides more specific error messages and logging and in many different situations. - The new system is about four times faster on queries and three times faster on processing updates. We have published an article on RIPE Labs with details about the features in the new system: https://labs.ripe.net/ripe-database/changes-to-the-processing-of-ripe-datab… Internally, the new system has a lot of benefits as well: - The new software has been designed from scratch with distribution in mind. Additional query and update nodes can easily be added for redundancy and performance. - Hot deployments of new software are now possible with no interruption to the service. - Some additional security measures have been introduced to improve the overall security of the system. - Logging and debugging facilities have been improved for easier support and maintenance. - The whole system is integrated and self-contained. It doesn't rely on external scripts for any task (such as the import of external data for mirroring or automatic data clean-up of unreferenced objects) and so is much easier to maintain. - Internal management and monitoring facilities have been improved and integrated into the system, so support and maintenance can provide users with direct feedback from the production system. - The memory footprint of the new system is much smaller. - The code base is much cleaner, making it easier to understand and maintain. Java is now the single language, replacing a mix of C, Perl and Java code. So, what's next? - Currently we are working on a new set of RIPE Database documentation that will be clean, concise and linked directly to each release, including a further review of error messages and all information provided when interacting with RIPE Database. - Investigate with the community the integration of RIPE Database authentication with the single sign-on (SSO) service for RIPE NCC services. - Implementing the IETF WEIRDS RDAP Protocol, fully integrated into the RIPE Database API, as a cooperative software development project with APNIC. - Using business rules to 'fix' parts of resource objects that users should not change, then allowing all objects to be updated by normal methods rather than special editors in the LIR Portal. - Providing the new software to the public and making the project open source and accessible for third parties. - Liaise with the community on new features and data clean-up as announced at the last RIPE Meeting. As always, you can contact us at <ripe-dbm(a)ripe.net> for any issues, feature requests or suggestions. Kind regards, Kaveh Ranjbar Database Group Manager RIPE NCC

2 1

[training] RIPE NCC Training Courses April-June 2013 - BA UK AE DE NL PL LI RU FR ES HU FI
by Training Mailbox 25 Feb '13

25 Feb '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 Sarajevo, Leeds, Dubai, Berlin, Amsterdam, Warsaw, Vaduz, St. Petersburg, Marseilles, Madrid, Budapest, Helsinki. 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 1

bug? accepting larger than 32 bit BGP Communities in RPSL
by Job Snijders 07 Jan '13

07 Jan '13

Dear RIPE DB group, A small snippet from the current AS15562 object as stored in the RIPE DB. remarks: Larger than 32bit BGP Community test remarks: 64 bit export: to AS199036 action community .= { 0000199036:0000199036 }; announce AS-SNIJDERS The value "0000199036:0000199036" is a 64 bit integer: (199036<<32)+199036 = 854853110925692 854853110925692 Is far larger than what RFC 2622 [1] allows in section 7.1: typedef: # a community value in RPSL is either # - a 4 byte integer (ok to use 3561:70 notation) # - internet, no_export, no_advertise (see RFC-1997 ) community_elm union integer[1, 4294967295], enum[internet, no_export, no_advertise], So my main question is, why is the RIPE DB allowing such values to be stored? This is not conforming to any specification that I am aware of. Currently there is no consensus on what the future of BGP communities will look like within the IETF. Kind regards, Job [1] http://tools.ietf.org/html/rfc2622

6 8