- db-wg - mailman.ripe.net

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

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