- db-wg - mailman.ripe.net

Support for expansion of an origin into a list of prefixes
by Job Snijders 01 May '14

01 May '14

Dear RIPE DB-WG, Much like my previous request regarding server side expansion of objects, I'd very much like the RIPE Database team to implement two flags which IRRd currently supports: !g & !6 I've filed an enhancement request on github: https://github.com/RIPE-NCC/whois/issues/73 The !g and !6 flags signficantly reduce the amount of RPSL interpretation a client has to perform, as the server provides the clients with a straight answer (abeit simplified). If the DB team implements such a feature, I'd also very much like an implementation in context or RDAP so I can query for lists of prefixes through HTTP rather than WHOIS. Kind regards, Job

2 1

RIPE Database Release 1.73
by Denis Walker 29 Apr '14

29 Apr '14

Dear colleagues, The RIPE NCC is pleased to announce the RIPE Database software release 1.73 to the Release Candidate (RC) environment. For information about features, changes and how this release might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73 Major features introduced in this release include the: -Addition of a "sponsoring-org:" attribute for End User resources -Addition of a "status:" attribute for all AUT-NUM objects -Change of "status:" values for all legacy (early registration) INETNUM objects to 'LEGACY' This release also fixes a number of issues. More details are available in the release notes. Where necessary, data in the RC Database has been changed to reflect the new/changed attributes. Please check your data and test your implementation in the RC environment. More information about the RC environment is available online: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… We look forward to any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 0

Proposal: DB object syntax change
by Piotr Strzyzewski 25 Apr '14

25 Apr '14

Dear working group I would like to propose syntax change of the role attribute of the ROLE object in the RIPE DB. Bellow you can find all details. I would like to hear your opinion about this idea and ask for the support to allow RIPE NCC to implement it. ------------- Short description: I would like to propose to change the syntax of the role attribute of the ROLE object from <person-name> to <organisation-name>, where both <person-name> and <organisation-name> are defined in RIPE Database Update Reference Manual. I would like to emphasize that I don't want to change the syntax of the nic-hdl attribute of the ROLE object. Nevertheless, my proposal influence the automatic mechanism of choosing the nic-hdl attribute value of the ROLE object, while it is created with AUTO directive. Rationale: Abuse-c implementation have influenced business procedures of LIRs and have led to increased importance of ROLE object. Since ROLE object is mandatory in the process of proper abuse-c registration, LIRs could be interested in automatic creation of it. Right now, due to its syntax, the role attribute of the ROLE object has number of limitations and cannot accept bunch of characters and or whole labels/words which are natural parts of company names. As an example, it is impossible to create ROLE objects with one of the following role attributes: - Company Father, Son & Daughter Abuse Team - 4U Network Abuse Team - 123 Ltd. Hostmaster - WOW! Network Dept. and so on. Moreover, the original intention was for the ROLE object to represent business roles and not personal data (see: paragraph 1.2.17 of the RIPE Database Update Reference Manual). Taking this into account the <organisation-name> would be the natural choice since it both perfectly solves the problem and is already well defined and implemented. Possible problems: As for now, the nic-hdl attribute of the ROLE object is auto-generated and based on the value of the role attribute. Since <person-name> do not allow all-numeric labels, this mechanism is quite simple. However, similar mechanism exists for the auto-generated organisation attribute of the ORGANISATION object, where <organisation-name> allows this kind of labels. While this is significant change to syntax, I would like to emphasize that <person-name> is a subset of <organisation-name>. This means that even if some people may rely on the current syntax, this change would most probably not influence their procedures. ----------- Best regards, Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski(a)polsl.pl

7 11

RIPE68 DB-WG Draft Agenda V1
by Wilfried Woeber 23 Apr '14

23 Apr '14

Dear DB-WG folks, Chairpersons, "Meeting"! This is the 1st -rough- draft of an agenda for the DB-WG Meeting at RIPE68 in Warsaw, scheduled for Wednesday, May 14, 2014. For time slot allocations please refer to the most up-to-date meeting plan at https://ripe68.ripe.net/programme/meeting-plan/ The DB-WG Meeting is scheduled for *Wednesday*, starting at 14:00 local time[1], after lunch . The length of our timeslot is 90 Minutes. The overall (draft) RIPE 68 meeting outline is already available at https://ripe68.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 Poland, Wilfried. [1] for remote participation, this 12:00 UTC ________________________________________________________________________ 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 (N.N., RIPE NCC) C. New DB-Software functionality - in test, schduled for deployment (sponsoring LIR) D. Proposals for changes to schema - consensus on removing referral-by:? - discussion changed: vs. last-modified E. 2012-07 implementation F. 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 ________________________________________________________________________ 23.04.2014 13:20 UTC

1 0

Changes to Syntax of End User Resources in the RIPE Database
by Denis Walker 17 Apr '14

17 Apr '14

Dear colleagues, The RIPE NCC will soon be deploying to our Resource Candidate (RC) Test Environment some changes to all End User resources. These changes are being implemented to satisfy two recently approved policies - ripe-603, "Publication of Sponsoring LIR for Independent Resources" and ripe-605, "RIPE NCC Services to Legacy Internet Resource Holders". The changes include: -The addition of a "sponsoring-org:" attribute to all End User resources (INETNUM, INET6NUM, AUT-NUM) -The addition of a mandatory "status:" attribute to all AUT-NUM objects -A change of "status:" for all legacy INETNUM objects (including all more specifics) to 'LEGACY' The RC Test Environment will include a copy of the RIPE Database with dummified personal data. All of the status additions and changes will be fully implemented in this test database. The "sponsoring-org:" attributes will all be set to reference a dummy ORGANISATION object in this test database. We do not expect any immediate changes to be necessary for any scripts that you use to generate these objects. Our software is tolerant to these attributes being missing and will generate them where necessary. Provided your scripts are tolerant to unknown attributes, as is recommended in the RPSL RFCs, you should not experience any issues even if your scripts query any of these objects. A comprehensive list of anticipated frequently-asked questions (FAQs) will be published alongside this release. We expect this FAQ will answer most questions. A "remarks:" attribute added to the changed objects will reference this FAQ page. Regards, Denis Walker Business Analyst RIPE NCC Database Team

1 0

Call for agenda items, DB-WG Meeting during RIPE68, Warsaw, PL
by Wilfried Woeber 15 Apr '14

15 Apr '14

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE68 in Warsaw, PL, May. 12 - May. 16, 2014, 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 14: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 68 meeting outline is already available at https://ripe68.ripe.net/programme/meeting-plan/ Looking forward to a successful meeting and see you soon in Poland! Wilfried.

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 08 Apr '14

08 Apr '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

RIPE Database Release 1.72 - including SSO Integration
by Denis Walker 07 Apr '14

07 Apr '14

Dear colleagues, We are pleased to announce RIPE Database release 1.72. For more information about the features, changes and how this release might affect your operations, please see these release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.72 A major feature introduced in this release is the integration of RIPE Database services with RIPE NCC Access. This gives maintainers the option to use their RIPE NCC Access account for authorising updates to the RIPE Database. The first applications that utilise this feature are Webupdates and Syncupdates from a web form. Linking a RIPE NCC Access account to an organisation is a requirement for certifying PI address space. No change has been made to existing authorisation options. This release also fixes a number of issues, so please read the release notes. By fixing certain issues with the JSON output from the REST API, the structure of that output has changed slightly. This should not affect any users as it was broken in the first place. To ensure this is the case, please test your implementation in the Release Candidate environment. More information about the Release Candidate environment is described in this document: https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-envir… We look forward to hearing any questions or comments you might have. Regards, Denis Walker Business Analyst RIPE NCC Database Team

7 12

Status %s not allowed when more specific object has status %s
by Tim Garrison 27 Mar '14

27 Mar '14

Greetings, I was wondering if it would be possible for the "Status %s not allowed when more specific object has status %s" error to be expanded in such a way that it reports what that specific object is. As it stands, it is rather difficult to determine when there is any overlap, especially when the upper and lower bounds of my inetnum object don't return any results when searching by single IP. Thanks in advance for considering this! -- Tim Garrison Lead, Systems Development *SoftLayer, an IBM Company* 315 Capitol Street Suite 205, Houston, TX 77002 281.714.4213 direct | 713.540.4325 mobile | 281.714.4657 fax | tgarrison(a)softlayer.com

2 2

[training] RIPE NCC Webinars - new dates
by Training Services 25 Mar '14

25 Mar '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Suggestion of change for inverse query of notify
by Fredrik Widell 19 Mar '14

19 Mar '14

Hello db-wg. I would like to change the behaviour of the whois-output for the following query whois -h whois.ripe.net -- "-r -T inetnum,route -i notify info(a)resilans.se" Via that question, I will see every object that has the notify info(a)resilans.se set, which right now is inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered However, my request is that the above query should give the exact same output as the below query whois -h whois.ripe.net -- "-r -T inetnum,route 194.14.3.0" which will also display the corresponding route-object, is there any real reason why this is not displayed with an inverse query? it looks like: inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered route: 194.14.3.0/24 descr: Resilans AB origin: AS12381 mnt-by: RESILANS-MNT source: RIPE # Filtered -- Best regards Fredrik Widell Resilans AB http://www.resilans.se/ mail: info(a)resilans.se , fredrik(a)resilans.se phone: +46 8 688 11 80

4 4

Prefix length for the "pingable" attribute
by Tore Anderson 16 Mar '14

16 Mar '14

Hi WG, The documentation unequivocally states the value of the "pingable" attribute in route[6] objects must include a prefix length: $ whois -h whois.ripe.net -- -v route [...] pingable Allows a network operator to advertise an IP address of a node that should be reachable from outside networks. This node can be used as a destination address for diagnostic tests. The IP address must be within the address range of the prefix containing this attribute. An address prefix is represented as an IPv4 address followed by the character slash "/" followed by an integer in the range from 0 to 32. The following are valid address prefixes: 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not strings containing four integers. $ whois -h whois.ripe.net -- -v route6 [...] pingable Allows a network operator to advertise an IP address of a node that should be reachable from outside networks. This node can be used as a destination address for diagnostic tests. The IP address must be within the address range of the prefix containing this attribute. <ipv6-address>/<prefix> Therefore I added mine as /32 and /128. That ended up in me getting complaints that I broke some people's scripts, which were assuming that value of this attribute should be a "bare" IP address. (For example: http://ip.v6net.ru/archives/1764) Contradictory to what the documentation says, the e-mail robot happily accepted my update to remove the prefix length. So hopefully people's scripts are unbroken now. This sparked my curiosity, though: - What exactly is the purpose of the prefix length? - How should one interpret a value that has a prefix length other than /32 (in "route" objects) or /128 (in "route6" objects)? - Why does the documentation say it is mandatory when it clearly is not? - And finally, am I really the only LIR hostmaster in the RIPE that actually do RTFM? :-) $ curl -s ftp://ftp.ripe.net/ripe/dbase/split/ripe.db.route{,6}.gz | zgrep -c '^pingable:.*/' 0 Tore

4 4

[training] RIPE NCC Courses in Sofia, Bulgaria 16-17 April 2014
by Training Services 14 Mar '14

14 Mar '14

Dear Colleagues, The RIPE NCC Training Services Department invites you to register for our upcoming Training Courses in Sofia, Bulgaria: Course type: RIPE Database Training Course Date: Wednesday, 16 April 2014 Time: 09:00-17:30 Course type: IPv6 for LIRs Training Course Date: Thursday, 17 April 2014 Time: 09:00-17:30 How to register: ---------------- You can register up to two people from your LIR for each course by using the LIR Portal at: https://lirportal.ripe.net/training/courses Registration will close when maximum capacity is reached, so please register soon to ensure your attendance. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. RIPE Database Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region. You can find more information about the course at: https://www.ripe.net/lir-services/training/courses/rdb IPv6 for LIRs Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region and if you: * Are thinking about deploying IPv6 in your organisation * Have been told you need to deploy IPv6 * Need to convince your manager that IPv6 needs to be deployed * Looked at an IPv6 address and thought it was too complicated to deploy in your network You can find more information about the course at: http://www.ripe.net/lir-services/training/courses/ipv6 If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, RIPE NCC Training Services

1 0

Implementation plan for 2012-07, "RIPE NCC Services to Legacy Internet Resource Holders"
by Nikolas Pediaditis 12 Mar '14

12 Mar '14

Dear colleagues, The RIPE NCC has published the proposed implementation plan for ripe-605 "RIPE NCC Services to Legacy Internet Resource Holders" (accepted policy proposal 2012-07): The overall implementation: https://labs.ripe.net/Members/nikolas_pediaditis/policy-proposal-2012-07-ri… The implementation that specifically relates to the RIPE Database: https://labs.ripe.net/Members/xavier/policy-proposal-2012-07-db-proposed-im… We are sending this email to three working groups because the implementation is related to anyone holding AUT-NUM or legacy INETNUM objects in the RIPE Database but we ask that comments be made on the RIPE NCC Services Working Group mailing list only. We aim to begin implementation the week of 25 March. Please do not hesitate to contact us if you have any comments or questions. Kind regards, Nikolas Pediaditis IP Resource Analyst RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Mar '14

11 Mar '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 25 Feb '14

25 Feb '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

[training] RIPE NCC Training Courses April-June 2014
by Training Services 18 Feb '14

18 Feb '14

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 St. Julian's, Zagreb, Sofia, Brussels, Edinburgh, Tehran, Helsinki, Moscow, Kiel, Almaty, Reykjavik, Geneva. 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 - IPv6 for LIRs Training Course - Routing Security Training Course - 3 day Deploying IPv6 Training Course (New) - DNSSec Training Course (New) For more information visit: https://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

[training] RIPE NCC Training Courses April-June 2014
by Training Services 17 Feb '14

17 Feb '14

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 St. Julian's, Zagreb, Sofia, Brussels, Edinburgh, Tehran, Helsinki, Moscow, Kiel, Almaty, Reykjavik, Geneva. 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 - IPv6 for LIRs Training Course - Routing Security Training Course - 3 day Deploying IPv6 Training Course (New) - DNSSec Training Course (New) For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Feb '14

11 Feb '14

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Multiple Sources and the REST API?
by Aleksi Suhonen 07 Feb '14

07 Feb '14

Hello, I'm trying to fetch data from the RIPE db and the mirrored databases at the same time: http://rest.db.ripe.net/search?source=ripe&source=apnic&inverse-attribute=o… I get 400 Bad Request even tho it should work according to the documentation I'm reading: https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API-search Halp. -- +358 4567 02048 / http://www.trex.fi/ Aleksi Suhonen / TREX Regional Exchanges Oy You say "potato", I say "closest-exit."

2 1

New minor release 1.71.1 to fix REST API JSON issue
by Denis Walker 06 Feb '14

06 Feb '14

Dear colleagues, We have identified the cause of the REST API JSON issues some users have been experiencing. Details can be found on github: https://github.com/RIPE-NCC/whois/issues/114 We deployed a new minor version (1.71.1) of the RIPE Database software today at 17:15 (UTC +1) to fix this issue. Release notes can be found here: https://www.ripe.net/data-tools/db/release-notes Regards, Denis Walker Business Analyst RIPE NCC Database Team

3 4

RC version of the JSON API?
by Job Snijders 06 Feb '14

06 Feb '14

Hi, I want to use the JSON API RC edition of the database in an automated fashion to detect changes that break our software earlier. But I have trouble finding the correct endpoint. For production I use the following URL: https://apps.db.ripe.net/whois What is the equivalent URL for the RC version of the database? From the post on http://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-enviro… it is not clear which of the URLs would emulate apps.db.ripe.net/whois. I tried: rc.db.ripe.net/whois rest-rc.db.ripe.net/whois whois-rc.ripe.net/whois I kinda expect rest-rc.db.ripe.net/whois to work, but it gives me a "The requested URL /whois/create was not found on this server." error. What is the endpoint? Kind regards, Job

2 1

Release 1.71.1 reverted, current RIPE Database release is 1.71
by Johan Åhlén 06 Feb '14

06 Feb '14

Dear colleagues, Earlier today we deployed a minor release of the RIPE Database software. The release contained a correction of an invalid data structure returned in the JSON format. The issue is described in detail here: https://github.com/RIPE-NCC/whois/issues/114 The beta REST API was decommissioned with the deployment of 1.71. As the issue above was affecting users that had not yet migrated to the new API we decided to go ahead with the minor release. However, we were just informed that there are users that rely on this specific structure for their operations so we have reverted the minor release. The current RIPE Database version in production is now back to 1.71 We’ve also made sure that the old beta API is available for any users that can’t migrate because of the issue mentioned above. Please contact me directly and I will provide you with the details on how you can connect to the old beta API. We are sorry for any inconvenience this might have caused you and if you have any questions or concerns then please let me know. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0

RIPE Database Release 1.71
by Johan Åhlén 04 Feb '14

04 Feb '14

Dear colleagues, We are pleased to announce RIPE Database release 1.71. You can find details about the new features, changes and how you might be affected, and important dates in the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.71 The new release contains the "import-via" and "export-via" attributes that were discussed in the Database and Routing Working Groups at RIPE 67, the initial implementation of which was made by Job Snijders. After further discussions on the mailing lists, the working group chairs decided that this feature should be incorporated in the RIPE Database. You can find out more about these attributes here: http://www.ietf.org/id/draft-snijders-rpsl-via-02.txt With this release we would also like to introduce our new Release Candidate environment. The Release Candidate environment is distinct from the TEST Database, and aims to provide an environment as close as possible to "production" where you can test that your software will work with upcoming RIPE Database releases. You can find out more about the Release Candidate environment in the release notes linked above. We look forward to hearing any questions or comments you might have! Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

2 2

Proposed Implementation Plan for 2012-08, "Publication of Sponsoring LIR for Independent Number Resources"
by Johan Åhlén 30 Jan '14

30 Jan '14

Dear colleagues, Last week, the RIPE community reached consensus on the policy proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources”. The RIPE NCC’s proposed implementation plan of the policy can be found here: https://labs.ripe.net/Members/johan_ahlen/policy-2012-08-proposed-plan-for-… You can find the full policy proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 The corresponding RIPE Document is ripe-603, which is available at: https://www.ripe.net/ripe/docs/ripe-603 If you have any comments or concerns, please let us know. Note: this email has been sent to both the RIPE NCC Services WG and the RIPE Database WG mailing lists. We would like to ask you to keep the discussion on the RIPE NCC Services WG mailing list to better facilitate participation. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC

1 0