- db-wg - mailman.ripe.net

RE: [db-wg] Slash notation
by ipmaster＠bt.com 22 May '03

22 May '03

Shane, sounds good to me !! Thanx Dave Trickett BTnet -----Original Message----- From: Shane Kerr [mailto:shane@ripe.net] Sent: 21 May 2003 16:56 To: IPMASTER G Cc: db-wg(a)ripe.net Subject: Re: [db-wg] Slash notation On 2003-05-21 16:26:43 +0100, ipmaster(a)bt.com wrote: > Hi > > Quick question:-) > We used to be able to update (via email) the Database with new > inetnums using slash notation. Since the introduction of RPSL, this > facility has been lost, would it be possible to re-introduce it? > I can see the benefits of using the long hand version if I am > updating with a /27 and a /28, such as (*.*.*.64 - *.*.*.111). > But for Inetnums that fall on the bit boundary would not make sense > to enable the slash? > If I update a route object I can still use the slash notation. Short answer: When version 3 of the Database software was designed, one of the principles used was to not change user data as it was submitted. This included the transformation you defined. The easiest solution would be to convert the CIDR to ranges, as you suggest, so: inetnum: 193.0.0.0/20 Would become: ***Warning: inetnum '193.0.0.0/20' converted to '193.0.0.0 - 193.0.7.255' inetnum: 193.0.0.0 - 193.0.7.255 . . . If this makes sense, we'll include this change shortly. Explaination (for the curious): The reason that these types of modifications were avoided in the original design is because RPSL allows a number of formats that can make the changes difficult. For example: inetnum: # this +# is a valid # inetnum attribute 193.0.0.0 + - # heck, you can even put a comment here 193.0.7.255 + # and at the end too Modifying this kind of attribute can be problematic, because the value is split across many lines, and has comments in the middle. However, with your suggestion it would be possible to do something like converting: inetnum: # this +# is a valid # inetnum attribute 193.0.0.0/21 + # but still parsable! Into the following: inetnum: # this +# is a valid # inetnum attribute 193.0.0.0 - 193.0.7.255 + # but still parsable! Since the CIDR-notation is "atomic", we don't have to worry about values split across lines or with comments inside. Note that comments and split lines in the primary attributes are very, very rare, but it is technically possible for any user that wishes to do so. -- Shane Kerr RIPE NCC

2 1

Slash notation
by ipmaster＠bt.com 21 May '03

21 May '03

Hi Quick question:-) We used to be able to update (via email) the Database with new inetnums using slash notation. Since the introduction of RPSL, this facility has been lost, would it be possible to re-introduce it? I can see the benefits of using the long hand version if I am updating with a /27 and a /28, such as (*.*.*.64 - *.*.*.111). But for Inetnums that fall on the bit boundary would not make sense to enable the slash? If I update a route object I can still use the slash notation. Dave Trickett BTnet

3 2

action item AP-42.3 - problems of multiple hashed passwords
by Larry J. Blunk 14 May '03

14 May '03

This is an update on AP-42.3 regarding identifying users of multiple hashed passwords (CRYPT-PW or MD5-CRYPT) in a mntner. Merit has implemented an option in it's web-based update form to include an "id" in the comment field of an "auth:" attribute. Additionally, the date and time of creation of the hashed password is included (should one want to keep track of the age of a particular password). Below is an example -- auth: CRYPT-PW Fa1QDrka0aOOM #Id:billg Created:20030514 09:42:45(UTC) As a further note, we have implemented (but not deployed) support for hashed password hiding. When this is deployed, the hash value of a CRYPT-PW will be replaced with the string "HIDDENCRYPTPW" when a mntner object is queried or mirrored. I'm not sure how much of this is of interest to the RIPE community (particularly with the PKI support on the horizon), but I thought I would throw it out for consideration. Regards, Larry Blunk Merit Network

1 0

Webcast RIPE 45 Announcement
by RIPE NCC Meeting Registration 13 May '03

13 May '03

Dear Colleages, Please note that several sessions at RIPE 45 are being webcast. These sessions include the following: - - EOF - - Routing Working Group - - LIR Working Group - - Tools Working Group - - The RIPE NCC Services BoF - - IPv6 Working Group - - Database Working Group - - Plenary To see the meeting in real time, please use one of the following URLs. As we have limited bandwith to the meeting venue, we ask that you choose a server that is physically closer to you: - - RIPE Meeting Attendees only: mms://webcast.ripemtg.ripe.net/ripemtg - - Spain Mirror: mms://media.rediris.es/ripelive - - Portugal Mirror: mms://wms.fccn.pt/ripelive - - Italy Mirror: mms://stream1-wg.cineca.it/ripelive - - Denmark Mirror: mms://wmslave.fsknet.dk/ripelive - - Czech Republic Mirror: mms://server1.streaming.cesnet.cz/ripemtg - - United Kingdom Mirror: mms://ccs-web2k.brynmill.swan.ac.uk/ripelive - - Netherlands Mirror: mms://stream-ripe.wind.surfnet.nl/ripelive - - Amsterdam Mirror (RIPE NCC Office): mms://webcast.ripe.net/ripemtg Please note that the webcastings are technical trials only and the broadcasts should not be regarded as an official implementation of a webcasting service. More information on the webcastings with detailed instructions can be found at: http://www.ripe.net/ripe/meetings/ripe-45/webcast.html We welcome your feedback on these trials. Please send your comments to <ripecast(a)ripe.net>. Regards, RIPE Meeting Coordination Team

1 0

Prototype of RPSLng Whois server
by DB-News 12 May '03

12 May '03

[ Apologies for multiple messages ] Dear Colleagues, The RIPE NCC Database Group announces an RPSLng prototype Whois server on host rpslng.ripe.net, port 53001. RPSLng is an effort to extend RPSL language, enabling the language to document routing policies for the IPv6 and multicast address families currently used in the Internet. The prototype RPSLng Whois server implements the draft draft-damas-rpslng-00.txt (ftp://ftp.ripe.net/internet-drafts/draft-damas-rpslng-00.txt) In the near future we will be implementing the new RPSLng draft (http://www.radb.net/rpslng.html) The prototype database contains a snapshot of the RIPE Whois Database. It can be updated by sending mails to <rpslng-auto(a)ripe.net>. Please note that this database is for test purposes only. Updates performed on it will _not_ be reflected in the RIPE Whois Database. More details can be found at: http://www.ripe.net/db/rpslng Please contact ripe-dbm(a)ripe.net for any comments. Best regards, Engin Gunduz RIPE NCC Database Group

1 0

message
by CMC 11 May '03

11 May '03

Hello Friends; I have a specific interest in receiving ripe as I am a registered channel manager on the Undernet & in my role must contact Undernet Administrators on people who abuse this chat network on IRC. I am 33 years old; attend grad school and work my way through Grad school. I have been a registered channel manager since 1997 and as such the Undernet has the same address as above for me. It's a requirement. I can offer hostmasks of people who are IRC abusers and help in anyway I am asked if I can do it . Thank you, Sincerely, charles michael capozzi

1 0

SYNC-Update failed
by Nacamar AS Guardian 09 May '03

09 May '03

hi all, i use the sync for create. delete and update my objects in the ripe-db. Today the dbupdate - routine failed, using pgp. via mail the new version is ok. has i left any statemenat from the ripe ? greetings, sven eisenmann ------------------------------------------------------------------- Sven Eisenmann NCC Senior Manager Network Administration Tiscali Business GmbH Robert-Bosch-Strasse 32 D-63303 Dreieich Telefon: +49(0)6103-916 0 Telefax: +49(0)6103-916 1881 E-Mail: guardian(a)nacamar.net www.tiscali.de www.tiscali-business.de -------------------------------------------------------------------

2 1

(typo corr.) draft agenda (v2), for DB-WG meeting, RIPE 45, Barcelona, ES
by Wilfried Woeber, UniVie/ACOnet 02 May '03

02 May '03

[ correction of a small typo, thanks to Mally for spotting it! ] ______________________________________________________________________ Dear WG list members, dear "Meeting Role" @ the NCC, dear WG-Chairs! Attached please find the 2nd - preliminary - draft: Proposed Agenda for the DB-WG Meeting at RIPE 45 in Barcelona, ES. As usual, if you have any comments, corrections or additions please get back to me directly. Looking forward to see many of you in Catalunya, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting 2. Draft A. Administrative stuff (WW, chair) 10 min . scribe: Nigel T. B. Action Items 15 min C. DB operational update (RIPE NCC, Shane K.) 20 min . including status of ERX D. Quality of contact data (RIPE NCC, Shane K.) 10 min . discussion / next steps / which WG? +10 min F. New "dbupdate" (RIPE NCC, Denis W.) 15 min G. Discussion: to disallow auth: NONE ( [ Hank N. ] ) 15 min H. (tbc) DB-SW teams up with... (UniVie-ACOnet, Ulrich K.) 20 min . the UniVie Netw.Info.Sys.: I. follow-Up on last meetings issues (Chair, WW144) 30 min . Organisation object proposal (RIPE NCC, Shane K.) . status: SUB-ALLOCATED PA (Space.Net, Gert D.) . reclaim: - Attribut (Space.Net, Gert D.) . allowing "generated" attributes in updates (WW et.al.) . Key Certificates to person: role: ? Y. Input from other WGs . Z. AOB: . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 2-MAY-2003 12:26:17 UTC _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Only one thing in life is certain: init is Process #1"

1 0

draft agenda (v1), for DB-WG meeting, RIPE 45, Barcelona, ES
by Wilfried Woeber, UniVie/ACOnet 02 May '03

02 May '03

Dear WG list members, dear "Meeting Role" @ the NCC, dear WG-Chairs! Attached please find the 1st - preliminary - draft: Proposed Agenda for the DB-WG Meeting at RIPE 45 in Barcelona, ES. As usual, if you have any comments, corrections or additions please get back to me directly. Looking forward to see many of you in Catalunya, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting 1. Draft A. Administrative stuff (WW, chair) 10 min . scribe: Nigel T. B. Action Items 15 min C. DB operational update (RIPE NCC, Shane K.) 20 min . including status of ERX D. Quality of contact data (RIPE NCC, Shane K.) 10 min . discussion / next steps / whihc WG? +10 min F. New "dbupdate" (RIPE NCC, Denis W.) 15 min G. Discussion: to disallow auth: NONE ( [ Hank N. ] ) 15 min H. (tbc) DB-SW teams up with... (UniVie-ACOnet, Ulrich K.) 20 min . the UniVie Netw.Info.Sys.: I. follow-Up on last meetings issues (Chair, WW144) 30 min . Organisation object proposal (RIPE NCC, Shane K.) . status: SUB-ALLOCATED PA (Space.Net, Gert D.) . reclaim: - Attribut (Space.Net, Gert D.) . allowing "generated" attributes in updates (WW et.al.) . Key Certificates to person: role: ? Y. Input from other WGs . Z. AOB: . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 2-MAY-2003 11:44:15 UTC _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Only one thing in life is certain: init is Process #1"

1 0

Announcement RIPE NCC RR Training Course
by RIPE NCC Training 01 May '03

01 May '03

------- Dear Colleagues, [apologies for duplicate postings] As a service to its members the RIPE NCC offers the "Routing Registry Training Course". 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 describe how to receive Internet resources from the RIPE NCC not describe 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 Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership fee. More information about the Routing Registry Training Course can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a Routing Registry Training Course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this e-mail and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either: - be an LIR contact - be confirmed by an LIR contact LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the Routing Registry Training Course will not be an authoritative contact person for their LIR, and therefore will be, refused by the course registration "robot". In order to be admitted to the course, a confirmation e-mail must be sent to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team ******************************************************************************** COURSE DATES AND VENUES ======================= Date: Friday 11 July 2003 Time: 0900 - 1700 Location: Vienna, Austria AND: Date: Friday 29 August 2003 Time: 0900 - 1700 Location: Helsinki, Finland AND Date: Monday 8 September 2003 Time: 0900 - 1700 Location: Amsterdam, The Netherlands *********************************************************************************** REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The course you plan to attend (date and location) # COURSE [ ] %END

1 0