- db-wg - mailman.ripe.net

RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0
by Wilfried Woeber, UniVie/ACOnet 18 Jan '05

18 Jan '05

Yesterday I had a chat with Rodney T. about the same thing. I'll work with the NCC to come forward with an update on progress. Wilfried. ______________________________________________________________________ From: "Titley, Nigel" <NTitley(a)flagtelecom.com> To: "'MarcoH'" <marcoh(a)marcoh.net>, db-wg(a)ripe.net Subject: RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0 Date: Mon, 17 Jan 2005 16:17:21 -0000 MarcoH wrote: >> [AP49.3 RIPE NCC] To produce a document detailing the programme for >> introducing the changes. >> >> [AP49.4 RIPE NCC] To implement the abuse-email: attribute in the >> irt, person and role objects. > > Not that I want to push people, but is there any progress on this > topic or can anybody from the NCC give some indication on when this > is expected to get done ? I would be expecting both of these to be complete by next meeting, in the absence of any response to the contrary by the Ripe NCC. Nigel --

1 0

RE: [db-wg] Draft minutes of DB-WG meeting RIPE 49 V2.0
by Titley, Nigel 17 Jan '05

17 Jan '05

MarcoH wrote: >> [AP49.3 RIPE NCC] To produce a document detailing the programme for >> introducing the changes. >> >> [AP49.4 RIPE NCC] To implement the abuse-email: attribute in the >> irt, person and role objects. > > Not that I want to push people, but is there any progress on this > topic or can anybody from the NCC give some indication on when this > is expected to get done ? I would be expecting both of these to be complete by next meeting, in the absence of any response to the contrary by the Ripe NCC. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

CVS and Bugzilla for RIPE Whois Server
by RIPE Database Manager 17 Jan '05

17 Jan '05

Dear Colleagues, The RIPE NCC has the source codes of the RIPE Whois Database software available under CVS (a version control system) and is publishing the bugs via Bugzilla (a bug-tracking system). By doing so, this allows anyone to: * have early access to new features of the RIPE Database Whois Server Software and * submit patches to the RIPE Database Whois Server Software. It also provides an easy and accessible method for submitting and tracking bugs and enhancement requests. To accommodate this feature, a web interface is available to browse the source codes at: http://www.ripe.net/cgi-bin/cvsweb.cgi/whoisserver/ while you can submit and track bugs at: http://www.ripe.net/bugzilla/. Stable Source and Binary Releases are available at: ftp://ftp.ripe.net/ripe/dbase/software/. Getting the source codes: You should type the following commands to check out the latest source code under CVS: cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot login [ No password, so just press [ENTER] on password prompt ] cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot co whoisserver These commands apply to the command line version of the CVS client software. A directory of CVS clients is available at: http://dmoz.org/Computers/Software/Configuration_Management/Tools/Concurren… Any suggestions about the system can be directed to ripe-dbm(a)ripe.net . Best Regards, Related Links: More information about CVS is available at: http://www.gnu.org/software/cvs/#TOCintroduction More information about Bugzilla is available at: http://www.bugzilla.org/docs/ -- Can Bican RIPE NCC Software Engineering Department

1 0

whois_rip feature request, multiple inverse attribute queries needed
by Arnd Vehling 07 Jan '05

07 Jan '05

Hello, would it be possible to enhance the RDB query in a way that multiple inverse queries are possible?! I would like to be able to query objects which match a certain set of inverse attributes with only one whois-query. Right now i can only query one inverse attribute a time, which means i need to collect all objects which match one of the attributes and then sort out those who match both. This often results in very huge numbers of objects which i need to compare via a perl script. Would this enhancement be reasonable?! best regards, Arnd -- NetHead Network Design and Security Arnd Vehling av(a)nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Cologne, Germany Fax : +49 221 8809212

2 1

RIPE Whois Database maintenance
by Engin Gunduz 28 Dec '04

28 Dec '04

Dear Colleagues Apologies for any duplicate mails On Wednesday, 29 December 2004, we will perform maintenance on the RIPE Whois Database. After this, the RIPE Whois Database will support RPSLng. You can find more information about this at: http://www.ripe.net/db/news/rpslng-211204.html We plan to start the maintenance at 15:00 Amsterdam time (14:00 UTC). It will take around four hours. During this time, there will be no interruption to Whois queries, however: - You will not be able to make any updates to the Whois Database using either webupdates or the LIR Portal, - We will process any e-mail updates, sent to auto-dbm(a)ripe.net, after we complete the maintenance work. We apologise for any inconvenience this work might cause. Best regards Engin Gunduz RIPE NCC Software Engineering Department

1 0

Announcement: Policy Development Process in RIPE
by Rob Blokzijl 21 Dec '04

21 Dec '04

To the RIPE Community, later today I will publish a draft document that describes the policy making process in RIPE. It is draft, so your input is requested in order to come to a generally accepted final document. Logistics: - deadline for comments on the first draft: 1 Februari 2005 - discussion takes place on ripe-list(a)ripe.net - if you are not subscribed to ripe-list(a)ripe.net yet, go to http://www.ripe.net/mailman/listinfo/ripe-list#subscribers - for any questions, don't hesitate to contact chair(a)ripe.net As always, apologies for receiving multiple copies of this announcement. Best regards, Rob Blokzijl RIPE Chairman

1 0

RPSLng in the RIPE Whois Database
by Shane Kerr 21 Dec '04

21 Dec '04

Dear Colleagues, Beginning Wednesday 29 December 2004, the RIPE Database will support RPSLng. RPSLng extends the Routing Policy Specification Language (RPSL) allowing description of IPv6 and multicast routing policies. It includes a new object type, ROUTE6, and new attributes, such as "mp-import:" and "mp-export:". RPSLng was submitted to the IETF to become an RFC. You can read the most recent draft at: http://www.radb.net/rpslng-08.html This change will not affect the current contents of the database. It is optional for any objects you maintain. The main differences for query users are as follows: - Currently a query for an IPv4 address or network may return INETNUM, ROUTE, and INET-RTR objects. A query for an IPv6 address or network can only return an INET6NUM object. After we put RPSLng into production, IPv6 queries will start to also return ROUTE6 and INET-RTR objects, if they are in the database. - Currently an inverse query (using the "-i" flag) for AUT-NUM objects may return ROUTE objects. After we put RPSLng into production, a query will return both ROUTE and ROUTE6 objects. If you want to limit your query, you can use the "-T" flag. For example, if you only want ROUTE objects returned to an inverse query, you can type: whois -h whois.ripe.net -T route -i origin AS3333 Please change your scripts if necessary. We will not move the contents of the RPSLng prototype Whois server to the RIPE Whois Database. You will have to create any objects that define your routing policy in the production RIPE Whois Database. You can update the RPSLng prototype Whois server until the start of January 2005. The query interface will be available until the end of January 2005. -- Shane Kerr Software Manager RIPE NCC

3 2

IRRToolSet maintenance moved from RIPE NCC to ISC
by Shane Kerr 17 Dec '04

17 Dec '04

Colleagues, We are happy to announce that the maintenance for the IRRToolSet has moved from the RIPE NCC to the Internet Systems Consortium (ISC). Starting now, ISC will support software development and maintenance of this suite. The new web page for this is: http://www.isc.org/sw/IRRToolSet/ The mailing list has been moved. The new address is <irrtoolset(a)isc.org>. E-mail will be forwarded from the existing mailing list (*). The RIPE NCC believes that ISC's software development model matches the IRRToolSet requirements, and that ISC will be a better home for the software. Operators and developers will have a set-up that is more typical to collaborative open source software, from a company that is experienced and focused on it. The RIPE NCC is grateful to ISC for agreeing to maintain this useful set of tools. We will continue to provide support for RIPE-specific portions and work with ISC in refining the software. -- Shane Kerr Software Manager RIPE NCC (*) When the mailing list forwarding began, Thursday 2004-12-16, filtering was removed. Shortly after the mailing list filtering policy was changed to "subscriber only". Apologies for the unwanted mail received during this period.

1 0

Re: [db-wg] Modifying the ACL for the whois server
by Nicolas Raux 06 Dec '04

06 Dec '04

when I try this set acl 127.0.0.1 deny=0 it seems ok (no error is returned) but I still can t query my local whois server here is what I get when I type : show acl ip maxprivate maxpublic maxdenials deny trustpass threshold maxconn 0.0.0.0/0 -1 -1 10 0 0 4 6 127.0.0.1/32 -1 -1 10 1 0 4 6 Found 2 nodes

2 1

Problems with ERX for 192.0.0.0/8
by leo vegoda 01 Dec '04

01 Dec '04

Dear Colleagues, An error in the software managing the ERX process for 192.0.0.0/8 resulted in the creation of INETNUM objects with incorrect contact information for registrations in this range. As a consequence, e-mail notifications were sent to incorrect contacts on 18 November. Errors made when registering the contact information in the database have now been corrected. Any user updates to these INETNUM objects or maintainers since 11 November have been undone. A new set of ERX notification e-mails will be sent to the relevant contacts and the schedule will be extended by two weeks. The completion date will now be 17 February 2005. We apologise for any inconvenience caused. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0