- db-wg - mailman.ripe.net

org-type: NON-REGISTRY (was: New Documents available: RIPE-384, RIPE-385)
by Niall O'Reilly 18 Sep '06

18 Sep '06

[ WG Co-Chair hat on ] On 4 Sep 2006, at 13:26, Antoin Verschuren wrote: > I have some sentimental issues with the new ENUM request forms as I > found out when I had to use them last week. I'm pretty sure that, in English, "sentimental" is the wrong word and is likely to lead to confusion. I think I know what you mean. > The new ENUM registrations ask to register an Organisation holding the > registration. > > This "Organisation" template, has a "org-type:" field. > RIPE tells me to fill in "NON-REGISTRY" in this field. > > I'm aware that we are not an RIR, LIR or NIR as in the RIR world, > but I > do feel the term "NON-REGISTRY" a bit degrading as we are the registry > for .nl and soon hopefully for ENUM. > > Can we invent a new term to use for official ENUM tier-1 registries > here > ? The "optics" do indeed seem non-intuitive. 8-) If some ENUM tier-1 registry would take the initiative to put a proposal on the table, and a few sister organizations gave support, we could have consensus in the ENUM-WG in time to feed into the DB-WG agenda item: Y. Input from other WGs I think we have "all the ducks lined up", as the saying goes; we just need a proposal. Best regards, Niall O'Reilly Co-Chair, RIPE ENUM Working Group

1 0

RIPE53 DB-WG Draft Agenda V3
by Wilfried Woeber, UniVie/ACOnet 18 Sep '06

18 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 3rd draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V12: item Y, iinput from ENUM-WG (t.b.c.) For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/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 (Nigel T.) - 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] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Review irt: e-mail/abuse-mailbox (Philippe B., CyberAbuse) [~15 min] F. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs . ENUM-WG: on (new?) organisation type for Database Object [t.b.c.] Z. AOB

1 0

Call for agenda items, DB-WG Meeting during RIPE53, Amsterdam
by Wilfried Woeber, UniVie/ACOnet 15 Sep '06

15 Sep '06

Dear DB-WG folks, the RIPE NCC has asked us to submit the draft agendas for the WGs within the next few days. Thus, please submit (to the WG list or to me personally) your item requests or suggest topics for discussion to be included in the draft agenda. The DataBase-WG meeting is scheduled for Friday morning, October 6, 2006. The overall RIPE meeting outline is available at http://www.ripe.net/ripe/meetings/ripe-53/meeting-plan.html The list of plenary presentations scheduled may become available at http://www.ripe.net/ripe/meetings/ripe-53/presentations/ (empty right now) See you in Amsterdam, Wilfried.

4 4

RIPE53 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 15 Sep '06

15 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 2nd draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V1: item E, irt stuff, E in V1 becoming F For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/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 (Nigel T.) - 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] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Review irt: e-mail/abuse-mailbox (Philippe B., CyberAbuse) [~15 min] F. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs Z. AOB

1 0

Suggestions to improve the IRT object
by Philippe Bourcier 15 Sep '06

15 Sep '06

Hi, The -c flag which is going to be implemented soon for any standard IP query to the RIPE whois is a good thing. But since most IRT objects returned don't have an abuse-mailbox field, the result is pretty useless (no e-mail will be returned). Developers will keep using -B in their tools so that they can send their abuse reports somewhere... Facts ===== The e-mail field of an IRT object is hidden until you use the -B flag. Most IRT objects have been created without an abuse-mailbox field. For the IRT object, the e-mail field is mandatory, but the abuse-mailbox is optional. The e-mail field of an IRT object is by definition an abuse-mailbox. Proposal ======== One of the easiest way to make the -c flag really useful without -B is to have all IRT objects return an abuse-mailbox. Thus, the abuse-mailbox field should be mandatory and for all IRT objects which don't have one, the e-mail field should be copied to it. (To be logical, the e-mail attribute should be set to optional.) More Thoughts ============= Another issue is to deploy the IRT object (or even the abuse-mailbox...) on a huge number of inetnum's. If we wait for people to modify all their inetnum objects so that they have an abuse-mailbox or irt-mnt attribute, it will take ages. A standard IP query to the RIPE whois now gives one "origin" attribute (or more). Maybe the mnt-irt of that aut-num could be displayed in the default output... A company not owning the AS announcing their prefix, and willing to use its own IRT object (or abuse-mailbox) could use the mnt-irt in their inetnum('s) to specify a "more specific" one. RFD === What do people think about these 2 ideas ? Sincerely, Philippe Bourcier

2 1

RIPE53 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 14 Sep '06

14 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 1st draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V.: ---. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/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 (Nigel T.) - 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] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs Z. AOB

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 29 Aug '06

29 Aug '06

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 1 September 2006 Time: 0900 - 1700 Location: Reykjavik, Iceland AND Date: Thursday 26 October 2006 Time: 0900 - 1700 Location: London, United Kingdom AND Date: Friday 4 November 2006 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND Date: Monday 27 November 2006 Time: 0900 - 1700 Location: Rome, Italy Hosted by: CASPUR http://www.caspur.it/ Hosted by: NAMEX http://www.namex.it/ 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

re: Proposal for returning IRT objects
by Denis Walker 17 Aug '06

17 Aug '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC has re-implemented the way IRT objects are returned in RIPE Database query results. The proposal can be found at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00087.html The first stage of this implementation as described in the proposal is now complete. The main objectives were to: - Increase the availability of the IRT information to users - Promote the use of the IRT object - Make it easier for third party tool writers to find the correct contacts New Behaviour ------------------------ The behaviour of the "-c" flag and the "-rc" flag is as follows: A standard query for address space including the "-c" query flag returns the queried INETNUM and related objects. This also includes an IRT object referenced by the queried INETNUM object or the closest, less specific INETNUM object, if one exists. It will also still include any ROUTE objects. By using the "-rc" flags, the related personal objects are filtered out. The IRT object will still be returned together with any ROUTE objects. An additional consequence of this change is the way the "-b" flag works. The "-b" flag will always return the primary key of any address space object queried. It also returns the "abuse-mailbox:" attributes from the address space object and any related IRT objects. The RIPE Database Query webpage has also been updated: http://www.ripe.net/fcgi-bin/whois For all address space queries made via this webpage, the "-c" flag will be added, making it the default. This only occurs if no other address space query flags (lLmMxbc) are present. A link has also been added to enable users to switch between the test and production databases. This makes it easier to query the RIPE Test Database. Regards Denis Walker Software Engineering Department RIPE NCC

1 0

The RIPE Database and DNS management system has been updated
by Katie Petrusha 03 Aug '06

03 Aug '06

Dear Colleagues, We have updated the RIPE Database and DNS management system to implement several new features. The change in the RIPE Database: - There is a new syntax for the "nserver:" attribute in the DOMAIN object to support IPv4 and IPv6 glue name servers. The changes in the DNS management system: - The management of DNS delegation in the e164.arpa (ENUM) zone has been brought under the same provisioning system as reverse DNS management. - The Delegation Checker has been updated to support glue name servers for IPv4 and IPv6 - The Web Zone Delegation Checker has also been updated You can find more details about the proposal for implementation at: http://www.ripe.net/ripe/maillists/archives/dns-wg/2006/msg00128.html -- Katie Petrusha RIPE NCC

1 0

RIPE Database maintenance
by Denis Walker 03 Aug '06

03 Aug '06

Dear Colleagues, We will carry out maintenance work on the RIPE Database update server, cello.ripe.net, on Friday, 4 August 2006 between 09:00-10:00 (UTC). During this period, you may experience outages when trying to use the following services: - RIPE Database updates (including the web interface and synchronous interface) - Queries to our mirrored databases (using -a query flag) Any updates sent to the mail interface will be queued and processed later. We apologise for any inconvenience. If you have any questions, please contact: ripe-dbm(a)ripe.net. Regards, Denis Walker Software Engineering Department RIPE NCC

1 0