- db-wg - mailman.ripe.net

Prototype IRIS server deployed at the RIPE NCC
by Peter Banik 28 Sep '05

28 Sep '05

Dear Colleagues, As part of a project to implement the IRIS protocol (also known as CRISP), the RIPE NCC has set up a prototype IRIS server for public testing. We announced this project during the RIPE 49 Meeting in Manchester: http://www.ripe.net/ripe/meetings/ripe-49/presentations/ripe49-db-crisp-upd… We have set up the prototype server as a proxy in front of the RIPE Whois Database. It is based on the FlowerBed server implementation developed by VeriSign Labs: http://iris.verisignlabs.com/blojsom/blog/iris/flowerbed/ The server uses the AREG protocol, you can find more information about this at: http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-areg-12.txt We have developed a prototype Perl client that can be used to make queries to AREG servers. This is not a complete client implementation, but we have made it available as we feel it will be useful for those that want to test the service. A web interface for querying the prototype server is available at: http://www.ripe.net/cgi-bin/test-iris/areg-query.pl You can find more details about this project at: http://www.ripe.net/db/iris-pilot/ Regards, Peter Banik RIPE NCC

1 0

Updated syncupdates?
by Peter Schroeder 27 Sep '05

27 Sep '05

Hello, I am a consultant working to develop software that will aid in keeping entries in the RIPE database up-to-date. I've been working to get a local version of the RIPE database running for our testing purposes. We're using the syncupdates interface to make changes in the database but it seems out-of-date because it is using command line switches in dbupdate that are no longer valid. Is there a newer version than 1.0.1? Thanks in advance, Peter Schroeder

4 4

Proposed changes for object ordering
by hairy 19 Sep '05

19 Sep '05

Hi, when will these changes be implemented? Will we know when the change occurs?

2 1

DNSSEC deployment on the reverse tree.
by Henk Uijterwaal 12 Sep '05

12 Sep '05

Dear Colleagues, In June, Olaf Kolkman wrote: >The RIPE NCC has been involved with the development of the DNSSEC >protocol. Now that the protocol has become available, we plan to >implement DNSSEC on our domains in the reverse DNS tree. The >deployment of DNSSEC is the second and last phase of the Reverse DNS >restructuring project. [...] >We welcome your feedback on this poposal before 1 August 2005. Please >send your comments to the DNS Working Group Mailing List. The comment period was extended to 1 September and some comments were posted to the list. These have all been incorporated and the new documents are at: >You can find the proposed policy at: > ><http://www.ripe.net/rs/reverse/dnssec/draft-dnssec-policy.html>http://www.ripe.net/rs/reverse/dnssec/draft-dnssec-policy.html. > "DNSSEC Key Maintenance Procedure" > ><http://www.ripe.net/rs/reverse/dnssec/key-maintenance-procedure.html>http://www.ripe.net/rs/reverse/dnssec/key-maintenance-procedure.html > "Procedure for Requesting DNSSEC Delegations" > ><http://www.ripe.net/rs/reverse/dnssec/registry-procedure.html>http://www.ripe.net/rs/reverse/dnssec/registry-procedure.html I'm going to suggest to the chairs of the WG to do a last call on these documents and have them published as RIPE documents. Kind regards, Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)

1 0

RIPE Policy Development Process
by Paul Rendek 01 Sep '05

01 Sep '05

Dear Colleagues We are pleased to announce that Rob Blokzijl, RIPE Chair, has published a new RIPE Document, "Policy Development Process in RIPE", (ripe-350). This document formally describes the policy development process. The updated process is operational from today, 1 September 2005. A new RIPE web page describes all the active policy proposals and their status. Each proposal has a page showing its history, status and all supporting documentation. This page can be found at: http://www.ripe.net/ripe/policies/proposals/index.html A new mailing list <policy-announce(a)ripe.net> has been created for announcing policy proposals and tracking them through the policy development process. This is not a discussion list; discussions will continue to take place on relevant RIPE Working Group lists and at RIPE Meetings. You can subscribe to the policy-announce list at: http://www.ripe.net/mailman/listinfo/policy-announce List archives are available at: http://www.ripe.net/ripe/maillists/archives/policy-announce/ Kind regards Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

call for items for the DB-WG meeting, RIPE51, Amsterdam
by Wilfried Woeber, UniVie/ACOnet 01 Sep '05

01 Sep '05

The next RIPE meeting ( http://www.ripe.net/ripe/meetings/ripe-51/ ) is coming closer, and I have already collected a couple of suggestions for the DB-WG Meeting [1]. So this is a call for suggestions of items for the draft agenda. As I am going to be off the net for the next 2 weeks, please cc: Nigel Titley in case you want to reply to me individually, or to the list. Thanks, and see you in Amsterdam! Wilfried. [1] . impact of the new PDP ("policy" development process) . secureDNS requirements for the DB . whois functionality/service - follow-up (tbc)

2 2

Database Loading Error
by Peter Schroeder 31 Aug '05

31 Aug '05

Hello, I have been trying to set up a local snapshot of the RIPE database. I have been receiving this error after several hours of loading data: query not defined for this type of attribute[74] died: +781 modules/ud/ud_core.c ./load_all.sh: line 1: 29427 Broken pipe cat ./load_all.sh: line 72: 29425 Broken pipe ${UNZIP1} ${object_file} 29426 Exit 141 | eval ${FILTER} 29428 Segmentation fault | $LOADER -L $1 -p ${PROPERTIES} -s ${SOURCE} I am using ripe.db.gz from a few days ago. Does anyone know why I would be getting this error? Pete

1 0

To post to this list
by contact＠internetprogress.org 11 Aug '05

11 Aug '05

To post to this list, my emailadress : contact(a)internetprogress.org Sincerely, Guy Lombart

1 0

Database updates not visible
by Shane Kerr 11 Aug '05

11 Aug '05

Dear Colleagues Our query servers are not synchronising with our update server. A large update is taking place. You may have received an acknowledgement to your update, but do not see your changes when you query the database. Do not worry, the changes have been made, and will be visible as soon as we can update our query servers. If you have not received an acknowledgement to your update, please be patient. The server will process your update as soon as possible. Apologies for any inconvience. -- Shane Kerr Software Engineering Department Manager RIPE NCC

1 1

Anything wrong with RIPE DB?
by Marcus.Ruchti＠colt.net 11 Aug '05

11 Aug '05

Hi all, Do you know if anything happened with the RIPE DB last evening or even this morning? Our RIPE robot, reading out AS-sets and route objects, deleted a lot of prefixes. Started just a few minutes ago again without any changes to the Robot we got many prefixes back. This was of course service affecting for single-homed PI customers :-( Now I wonder if RIPE is doing something with the DB. I've seen the output has been changed (reduced mainly) but this does not affect my script. So any hints from your side are appreciated. Thanks Marcus Ruchti COLT Telecom, Frankfurt ************************************************************************************* The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security(a)colt.net and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

2 1