- db-wg - mailman.ripe.net

RIPE DB not accessible over IPv6
by Agoston Horvath 29 Jun '07

29 Jun '07

Dear Colleagues, >From 11:12 on 29 June 2007, the RIPE Database is not able to respond to queries over IPv6. All other services (updates, queries over IPv4) are unaffected. This problem is due to a firewall-related issue in our Juniper routers. We apologise for any inconvenience. If you have any questions or concerns about this, please contact us at: <ripe-dbm(a)ripe.net> Regards, Agoston Horvath Database Group RIPE NCC

1 0

"-c" flag to become default in RIPE Database server
by Katie Petrusha 27 Jun '07

27 Jun '07

[Apologies for duplicate mails] Dear Colleagues, On 1 August 2007, the following changes will be made to the default behaviour for IP queries of the RIPE Database: * The "-c" flag behaviour will become the default for all IP queries. This means that when querying an IP address or range, any query not containing the "-L", "-l", "-M", "-m" or "-x" flags will, by default, return the IRT object referenced by the closest less specific inet(6)num (if such a reference exists). * A new "-C" flag will be implemented to provide the old behaviour and ensure backwards compatibility. The behaviour of the "-c" flag itself will not change, nor will there be any change for those queries that include other IP flags ("-L", "-l", "-M", "-m" or "-x"). Please adjust any software that you maintain that queries the RIPE Database and relies on this behaviour. Regards, Katie Petrusha Database Department RIPE NCC

2 2

Proposal to remove "RIPE Document" status from RIPE database documents
by Katie Petrusha 26 Jun '07

26 Jun '07

[ Apologies for duplicate mails ] Dear colleagues, To your attention the proposal to remove "RIPE Document" status from RIPE Database documents. Introduction ------------ Currently all the RIPE Database documents are classed as official RIPE Documents. This means that any changes to the documents must be made via a formal, and sometimes lengthy, procedure. As a result, changes are grouped and updates to the documents are staged periodically, meaning that the documents are often out of date in some way. Based on discussions at RIPE 54, the RIPE NCC is currently finalising eight proposals to send to the community. Each of these will require changes to the database documentation. There are also a number of other issues still to be discussed by the Data Protection Task Force, any of which may result in further proposals, as well as software or procedure changes, which may require further changes to the documentation. To keep the documents up to date throughout this process will require almost monthly releases, which is not possible under the current scheme. Proposal -------- The documents listed below [1] do not define any RIPE policies. These documents explain how the database software applies policy that is defined in other formal RIPE Policy Documents and RFCs. The RIPE Database Update Reference Manual [1], for example, explains how the database software applies the route authentication process, but the process itself is defined in other official documents. We propose to remove the official RIPE Document status on the documents listed below [1]. This will allow us to more frequently modify these documents and keep them in line with developments as they occur. All documents will remain available to users on the RIPE website in the same format as they are currently presented. References ---------- [1] List of documents: * RIPE Database Query Reference Manual (ripe-401) * RIPE Database Update Reference Manual (ripe-252 and ripe-draft) * RIPE Database User Manual: Getting Started (ripe-402) -- Katie Petrusha Database Department RIPE NCC

1 0

Re: db-wg digest, Vol 1 #520 - 1 msg
by Denis W 26 Jun '07

26 Jun '07

Hi Joao I agree. So lets focus first on a consensus for stage 1. Then we can start work on that while we continue discussions on the other stages and the impacts they will have on work flow of LIRs. regards Denis RIPE NCC Cc: Database WG , ncc-services-wg From: Joao Damas Subject: Re: [db-wg] Proposal - Maintaining person, role and domain objects Date: Mon, 25 Jun 2007 11:00:20 +0200 To: Denis Walker Stage 1 makes a lot of sense to me as it has little consequences to older data while it makes sure new information going into the DB has a better chance of being kept as originally posted by the object creator. The other stages do need a bit more discussion as they may in fact affect a lot of legacy data and have the potential to add a burden to LIR operations. I am in favour of those extra steps, just think that there is a need to repeat the warnings and announcements before and insist on people making an impact analysis on their operations. Joao Damas On 21 Jun 2007, at 14:41, Denis Walker wrote: > [Apologies for duplicate mails] > > Dear Colleagues, > > As a result of discussions during the Database Working Group > session at > RIPE 54, the RIPE NCC has nine proposals and implementation plans to > present to the community. Although most of them are now in the final > stages of preparation, we will send them out one at a time over the > next > few weeks for consideration by the community. > > The first one concerns maintaining all objects in the RIPE > Database, which > followed from a recommendation from the Data Protection Task Force > (DP TF) > (see below). We have already had some preliminary discussions about > this > with the DP TF. They provided the RIPE NCC with some very useful > feedback, > which is incorporated in this proposal. > > Regards > Denis Walker > RIPE NCC > > > > Maintaining person, role and domain objects > ------------------------------------------- > > > Implementation > As with the CRYPT-PW deprecation this will have a staged rollout. > > Stage 1 > > * No new person, role or domain objects can be created without a > "mnt-by:" attribute. > * Any un-maintained person, role or domain object cannot be modified > without adding a "mnt-by:" attribute. > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate a warning message in the acknowledgement. > > In this stage the acknowledgement message may include these warnings: > > ***WARNING: Un-maintained person object referenced [DW-RIPE] > ***WARNING: Un-maintained person object referenced [DW-RIPE] in > mntner [AARDVARK-MNT] > > Stage 2 > > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate a warning message in the acknowledgement. > * Any NEW reference to an un-maintained person object or to a mntner > which has such references will generate an error message in the > acknowledgement and the update will fail. > > In this stage the acknowledgement message may include these warnings > and errors: > > ***WARNING: Un-maintained person object referenced [DW-RIPE] > ***WARNING: Un-maintained person object referenced [DW-RIPE] in > mntner [AARDVARK-MNT] > ***ERROR: New reference to un-maintained person object [DW-RIPE] > ***ERROR: New reference to un-maintained person object [DW-RIPE] in > mntner [AARDVARK-MNT] > > Stage 3 > > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate an error message in the acknowledgement and the update > will fail. > > In this stage the acknowledgement message may include these errors: > > ***ERROR: Un-maintained person object referenced [DW-RIPE] > ***ERROR: Un-maintained person object referenced [DW-RIPE] in mntner > [AARDVARK-MNT] > > > Statistics > ---------- > While not a very statistically valid survey, we looked at a few days > just after the RIPE meeting to see how many new person objects were > created with and without mntner objects. We also queried the new > objects some time after creation to allow for a "mnt-by:" to be added > later. We also noted how many unique person objects were referenced in > any objects in update messages with and without mntner objects. AUTO- > references were ignored in both creations and updates, and multiple > instances of the same person object being referenced many times were > counted as one. > > -------------------------------------------------------- > | Date |Created |Created |Referenced |Referenced | > | |with |without |with |without | > |--------------------------------------------------------| > | 20070515 | 156 | 89 | 925 | 726 | > | 20070516 | 111 | 67 | 1022 | 486 | > | 20070517 | 85 | 48 | 476 | 185 | > | 20070518 | 82 | 18 | 679 | 445 | > -------------------------------------------------------- > End of db-wg Digest --------------------------------- New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.

1 0

RIPE NCC Network Maintenance Wednesday 20 June 17:00 to 19:00 UTC/GMT
by Mark Guz 18 Jun '07

18 Jun '07

[apologies for duplicates] Dear Colleagues, On Wednesday 20/06/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our network infrastructure. This may result in brief interruptions to RIPE NCC services during the posted maintenance window. We apologise for any inconvenience that this may cause. This work is due to planned resilience testing of our network. If you have any questions about this, please send an e-mail to: ops(a)ripe.net <mailto:ops@ripe.net>. Regards Mark Guz Senior Engineer RIPE NCC

1 0

***Error: Date in the future in changed: attribute '20070607'
by Max Tulyev 07 Jun '07

07 Jun '07

Hi! I just sent a request for creating a new object in the RIPE DB, but got such error. But we really have June, 07 now here (GMT+2) =) Is it a bug or a feature? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

5 7

Re: Network Maintenance - Tuesday, 5 June 2007
by James Aldridge 05 Jun '07

05 Jun '07

-------- James Aldridge wrote: > The RIPE NCC will perform planned maintenance work on Tuesday, 5 June > 2007 between 17:00 and 18:00 (UTC). > > This work will affect a number of servers and may result in a short > outage of some RIPE NCC services. We apologise for any inconvenience > that this may cause. This maintenance work has now been successfully completed. Regards, James -- James Aldridge, Senior Systems & Network Engineer, RIPE NCC Tel: +31 20 535 4444 / Fax: +31 20 535 4445

1 0

RE: Changing/Adding route objects
by Michael Markstaller 05 Jun '07

05 Jun '07

Hi, getting back on this topic from quite a while ago, I just found it while having exactly this problem.. >On Wed, Apr 05, 2006 at 08:28:29AM +0200, Ihler, Hermann wrote: >> if OLD-ISP updates his objects as follows it also will >> work: > >But that's winfried's point: the old ISP need to actively enable >creation of the new route object. And/or it needs, as in my case, being able to actually do this in time. My favorite answer for today, waiting since Friday, is "This is an automated system, I cannot do this. I can only delete the object" (Which means in my basic understanding of IRR, if I don't create the new one in time, I'll be filtered by anybody doing best practice and use IRR..) This makes me waiting this night for this magic change to happen sometime.. I somehow don't trust on what this change from an "automated system" being oparted by poeple that don't have the mntner theirselve (maybe for some good reason) will actually do.. So I'm with the inital suggestion: the mntner of the inetnum should be able to override/make changes to the route-object of his own network, regardless which mntner is sitting on it. If there are good reasons against this, I'm happy to learn the these. regards Michael Markstaller

2 1

RIPE NCC Network Maintenance Thursday 07 June 1700-1900 UTC
by Mark Guz 04 Jun '07

04 Jun '07

[apologies for duplicates] Dear Colleagues, Between 17:00 and 19:00 (UTC/GMT) on Thursday, 07 June 2007, the RIPE NCC will carry out planned maintenance work on our network infrastructure. During this period, www.ripe.net and associated sites, ftp.ripe.net, whois.ripe.net and Authorative DNS services as provided by the RIPE NCC may be interupted. We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Department RIPE NCC

1 0

database mirroring
by Andres Riancho 01 Jun '07

01 Jun '07

List, I'm doing some research for my University project and I want to know if it is possible to create a local mirror of the whois server at whois.ripe.net . I have been reading a lot and found some references to "Near Real Time Mirroring" and also to the "-g" option of the whois client, but nothing that I could really use. Please note that I dont want to setup a whois server that forwards requests, I want a mirror. Could someone please point me to a document where I can find the requirements ( if any ) for mirroring the whois database, and also the technical details for making this happend ? Are there any copyright problems I should worry about when doing a whois.ripe.net mirror ? This is my first post to this list, so excuse me if this aint the right place to ask. Thanks in advance for all your replies. Cheers, -- Andres Riancho

1 0

Network Maintenance - Tuesday, 5 June 2007
by James Aldridge 01 Jun '07

01 Jun '07

Dear Colleagues, The RIPE NCC will perform planned maintenance work on Tuesday, 5 June 2007 between 17:00 and 18:00 (UTC). This work will affect a number of servers and may result in a short outage of some RIPE NCC services. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net>. Regards, James -- James Aldridge, Senior Systems & Network Engineer, RIPE NCC Tel: +31 20 535 4444 / Fax: +31 20 535 4445

1 0

Verio renamed NTTCOM in RIPE Database
by Katie Petrusha 30 May '07

30 May '07

Dear Colleagues, On 31 March 2007, the Verio routing registry database was renamed NTTCOM. This change of name has been incorporated in the RIPE Database server which mirrors a number of public databases including the NTTCOM routing registry. More information about the NTTCOM routing registry is available at: http://www.us.ntt.net/about/policy/rr.cfm The list of databases mirrored by the RIPE Database server is available at: http://www.ripe.net/db/mirrored.html -- Katie Petrusha RIPE Database administration RIPE NCC

3 2

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was performed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was preformed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

webupdates.pm
by Michael Theurl 24 May '07

24 May '07

Hello DB-WG, i need to do some changes in the Webupdates.pm can you give me a hint ? ..if i create a new "inetnum" object via the webupdate.pl i got this template to fill my data into. But now i need a special field called "assigned". Is there a way to put this field into the inetnum template ? ...i was searching in the Webupdates.pm for an array that holds all the "Add New Field" fields, but i didnt find someone. hopefully you can give me some tips where i can add this field. best regards Michael

2 1

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT
by Mark Guz 21 May '07

21 May '07

Dear Colleagues, Between 17:00 and 19:00 (UTC) on Wednesday, 23 May 2007, the RIPE NCC will carry out planned maintenance work on our core network infrastructure. During this period all RIPE NCC services will suffer intermittent interruptions We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

Announcement Routing Registry Training Courses
by Rumy Kanis 21 May '07

21 May '07

[Apologies for duplicate e-mails] Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 27 July 2007 Time: 09:00 - 17:00 Location: Amsterdam, Netherlands AND Date: Friday 17 August 2007 Time: 09:00 - 17:00 Location: Oslo, Norway AND Date: Friday 31 August 2007 Time: 09:00 - 17:00 Location: Berlin, Germany AND Date: Thursday 6 September 2007 Time: 09:00 - 17:00 Location: Nottingham, United Kingdom AND Date: Friday 14 September 2007 Time: 09:00 - 17:00 Location: Lisbon, Portugal AND Date: Friday 28 September 2007 Time: 09:00 - 17:00 Location: Tbilisi, Georgia AND Date: Monday 3 December 2007 Time: 09:00 - 17:00 Location: Barcelona, Spain Hosted by: CESCA: http://www.cesca.es/en/ The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. 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. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Installed succesfully
by Michael Theurl 16 May '07

16 May '07

Hy, I got now an running version of the whois server i did also some config tunes and now i stuck at this point: /opt/whois_cw/bin/dbupdate -c /opt/whois_cw/conf/rip.config.sample -f /tmp/person SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [person] KS1 Kenny South ***Info: Authorisation passed ***Info: Syntax check passed person: Kenny South address: nordpool 12 phone: +43 664 123456 nic-hdl: KS1 changed: bitbucket(a)kyberna.net 20070515 source: SAMPLE ***Error: Please contact database admin: Error no 406 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> What do they mean with this error code number 406 best regards Michael -- [] this Email is made of 100% Recyclable electrons [] visit : www.smog.at ; www.theurl.at ; www.lugv.at [] private: members.smog.at/michael [] mailto : michael.theurl(a)smog.at [] key : www.smog.at/key

2 1

java.xml
by Michael Theurl 15 May '07

15 May '07

Hello DB-WG, I have a problem with the build of the whois server. I checked the latest from the cvs server out. The ./configure setup worked without an problem. Hopefully you can help me out: make all-recursive make[1]: Entering directory `/home/theurlm/whois/whoisserver' Making all in src make[2]: Entering directory `/home/theurlm/whois/whoisserver/src' Making all in defs make[3]: Entering directory `/home/theurlm/whois/whoisserver/src/defs' ---------- 1. ERROR in AttributeSyntax.java (at line 22) import javax.xml.parsers.*; ^^^^^^^^^^^^^^^^^ The import javax.xml cannot be resolved ---------- 2. WARNING in AttributeSyntax.java (at line 24) import org.xml.sax.*; ^^^^^^^^^^^ The import org.xml.sax is never used ---------- 2 problems (1 error, 1 warning) make[3]: *** [AttributeSyntax.class] Error 255 make[3]: Leaving directory `/home/theurlm/whois/whoisserver/src/defs' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/theurlm/whois/whoisserver/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/theurlm/whois/whoisserver' make: *** [all] Error 2 best regards Michael

2 1

RIPE54 DB-WG Draft Agenda V3
by Wilfried Woeber, UniVie/ACOnet 10 May '07

10 May '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 3rd draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. Changes from V2: (in order to take into account on-site stuff) - removed rDNS topic (may come up again in autumn) - added detail to item C. - item Y, "scaled-down" item CA-TF report For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-54/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (N. Titley) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (Jos B., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . status of DB documentation . abuse handling C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~30 min] . Follow-up proposals/discussion: require link to maintainer for all objects (person, role!) re-open discussion on country: attribute D. Treatment of orphaned objects (N.N., RIPE NCC) [~10 min] . proposal to remove orphaned person objects Y. Input from other WGs and TFs . Resource Certification TF: impact on DB, if any (Nigel T.) for full CA-TF report please see http://www.ripe.net/ripe/meetings/ripe-54/presentations/Certification_Task_… . DNS: retire rev-srv: attribute in inetnum: (Peter K, DENIC) Z. AOB . do we need to perform a review of our WGs mandate? (WW144) ________________________________________________________________________

1 0

Compile the Whois server
by Michael Theurl 08 May '07

08 May '07

Hello DB-WG, I tried to compile the Whois server software but I got the following error: ./build.sh --prefix=/opt/whoisserver ./build.sh: line 36: ./configure: No such file or director It seem that the "configure" file is missing ! I downloaded the last version from the whoisserver software from the ripe ftp server. hopefully you can help me. best regards Michael -- [] this Email is made of 100% Recyclable electrons [] visit : www.smog.at ; www.theurl.at ; www.lugv.at [] private: members.smog.at/michael [] mailto : michael.theurl(a)smog.at [] key : www.smog.at/key

2 1

New E-Learning Module: Using PGP and X509 to Protect MNTNER Objects
by Rumy Kanis 03 May '07

03 May '07

Dear Colleagues, We are pleased to announce the launch of the latest module on the RIPE NCC E-Learning Centre: - Using PGP Keys and X509 Certificates in MNTNER objects This module explains the steps required to use a PGP Key and/or X509 Certificate to protect objects in the RIPE Database. The module provides step-by-step guidelines for: - Creating a KEY-CERT object - Adding the KEY-CERT object to an existing MNTNER object as a method of authentication - Updating an object protected by that MNTNER using the PGP key or X509 certificate The RIPE NCC E-Learning Centre is a free of charge service available to everyone, and can be found at https://e-learning.ripe.net. If you have any questions, please feel free to contact us at: e-learning(a)ripe.net Happy Learning, Rumy Kanis Training Services Manager

1 0

Fwd: [db-wg] RIPE54 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 27 Apr '07

27 Apr '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 2nd draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. Changes from V1: - moved one line down to AOB, where it belongs, - added 1 item for "Input from..." For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-54/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (N. Titley) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . status of DB documentation . abuse handling . revDNS scrpit behaviour (t.b.c.) C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~30 min] D. Treatment of orphaned objects (N.N., RIPE NCC) [~10 min] . proposal to remove orphaned person objects Y. Input from other WGs and TFs . Resource Certification Task Force (impact on DB, if any) [t.b.c.] . DNS: retire rev-srv: attribute in inetnum: (Peter K, DENIC) Z. AOB . do we need to perform a review of our WGs mandate? (WW144)

1 0

RIPE54 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 27 Apr '07

27 Apr '07

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 1st draft of an agenda for the DB-WG at RIPE54 in Tallinn, May 2007. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-54/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (N. Titley) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . operational update . status of CRYPT-PW retirement . status of DB documentation . abuse handling . revDNS scrpit behaviour (t.b.c.) C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~30 min] D. Treatment of orphaned objects (N.N., RIPE NCC) [~10 min] . proposal to remove orphaned person objects Y. Input from other WGs and TFs . Resource Certification Task Force (impact on DB, if any) [t.b.c.] . do we need to perform a review of our WGs mandate? (WW144) Z. AOB

1 0

RIPE Database update problem
by Denis Walker 26 Apr '07

26 Apr '07

[Apologies for duplicate e-mails] Dear Colleagues, >From 21:30 (UTC) on 24 April 2007 until 10:20 (UTC) on 26 April 2007, e-mail updates sent by users to the RIPE Database update service were not processed by the RIPE Database. This problem has now been resolved. ALL the updates submitted have now been processed. No updates were lost. We apologise for this problem with the RIPE Database update service. This was caused by some network adjustments affecting our firewall and mail servers. It had no effect on updates submitted using syncupdates or webupdates, or changes made using the LIR Portal interface. Any changes made by the RIPE NCC Registration Services Department on behalf of RIPE NCC members were also unaffected. We would like to thank all our users for their patience while we fixed this problem. Regards Denis Walker Database Group RIPE NCC

1 0