- db-wg - mailman.ripe.net

Re: NCC#2001014534 WHOIS-Database .at-Domains (fwd) de.aball (fwd) X-NCC-RegID: de.aball (fwd)
by Andreas Jennen 14 Jan '01

14 Jan '01

Hi, please answer my questions idown in my text ! Yhanks. Will i have soon 20 hdl ? Is that, what you wanted ? Gruss Andreas Jennen. -- / \__ Festverbindungen auch 34 MBit/s und 155 MBit/s erhaeltlich ( *\___ <- Nando,Andreas Jennen, Roscherstr. 12, 30161 Hannover, DE / O EMAIL jennen(a)aball.de Voice: (+49 511)270 737-0, Fax:699091 / (_____/ Pos(Grad, Minuten): N 52 18.559';E 009 35.714' Hoehe: 112 m /_____/ U http://www.aball.de Privat: http://www.jennen.de ----- Forwarded message from RIPE NCC Hostmaster ----- Message-Id: <200101121426.PAA15401(a)x60.ripe.net> To: jennen(a)aball.de Subject: Re: NCC#2001014534 WHOIS-Database .at-Domains (fwd) de.aball (fwd) X-NCC-RegID: de.aball In-reply-to: Your message of Fri, 05 Jan 2001 22:46:46 +0100. <200101052146.WAA20734(a)sonne.aball.de> References: <200101052146.WAA20734(a)sonne.aball.de> From: RIPE NCC Hostmaster <hostmaster(a)ripe.net> X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 535 4444 X-Fax: +31 20 535 4445 Date: Fri, 12 Jan 2001 15:26:11 +0100 Sender: hostmaster(a)ripe.net Hi Andreas, This change was agreed by the Database Working Group. If you have a problem with this decision please raise it on the <db-wg(a)ripe.net> mailing list or at the working group meeting during this month's meeting. Sorry to have upset you - have a good weekend. Regards, ------------------- Geoff Charters Ripe NCC Hostmaster ------------------- "QUICK TIPS FOR REQUESTS": <http://www.ripe.net/ripencc/tips/tips.html> In the previous mail Andreas Jennen <jennen(a)aball.de>, wrote: * * from Andreas Jennen * jennen(a)aball.de * x-NCC-RegID: de.aball * * Dear hostmaster, * * what a hell why is this ? See below * * Is this correct, what *.at need ? * * One handle for every European contry, where i am admin of an domain ? * * Before i was in Europe and also USA: * * AJ4-RIPE * * now i need 20 or 30 handles ? * * Why is RIPE so stupid ? * * Whatfor we pay 2100 Euro every jear ? * * * Please also give the national domain organisation like e.g. * Denic * * the order to take our full Ripe handles as nic-hdl. * * e.g. * whois -h whois.ripe.net AJ4-RIPE * * RIPE says: * * % Rights restricted by copyright. See http://www.ripe.net/ripencc/pub-servic * es/db/copyright.html * * person: Andreas Jennen * address: aball Internet Netzdienste GmbH * address: Roscherstr. 10 * address: D-30161 Hannover * address: Germany * phone: +49 511 270 737-0 * fax-no: +49 511 69 90 91 * e-mail: jennen(a)aball.de * nic-hdl: AJ4-RIPE * notify: quardian(a)aball.de * mnt-by: ABALL-NCC-MNT * changed: knocke(a)nic.de 19941214 * changed: knocke(a)nic.de 19950103 * changed: jennen(a)aball.de 19990623 * changed: jennen(a)aball.de 20000621 * source: RIPE * * whois -h whois.denic.de AJ4-RIPE * the denic says: * * % Copyright (c)2000 by DENIC * % * % Restricted rights. * % * % * % Except for agreed Internet operational purposes, no part of this * % information may be reproduced, stored in a retrieval system, or * % transmitted, in any form or by any means, electronic, mechanical, * % recording, or otherwise, without prior permission of the DENIC * % on behalf of itself and/or the copyright holders. Any use of this * % material to target advertising or similar activities are explicitly * % forbidden and will be prosecuted. The DENIC requests to be notified * % of any such activities or suspicions thereof. * * person: Andreas Jennen * address: aball Internet Netzdienste GmbH * address: Roscherstr. 10 * address: 30161 Hannover * address: DE * e-mail: jennen(a)aball.de * nic-hdl: AJ4-RIPE * changed: lastchange(a)denic.de 20000621 * source: DENIC * * that is not the same, we do not see> notify. mtn-by, history * * That is nonsence ! * * * Are you not able to let work an domain whois server for Europe ? * * No, then i will say on the next meeting, that the RIPE organisation * should change to an new and better and cheaper organisation ! * * If you don not want to answer this request, please give it to your * General Manager ! * * * Gruss Andreas Jennen. * -- / \__ Festverbindungen auch 34 MBit/s und 155 MBit/s erhaeltlich * ( *\___ <- Nando,Andreas Jennen, Roscherstr. 12, 30161 Hannover, DE * / O EMAIL jennen(a)aball.de Voice: (+49 511)270 737-0, Fax:699091 * / (_____/ Pos(Grad, Minuten): N 52 18.559';E 009 35.714' Hoehe: 112 m * /_____/ U http://www.aball.de Privat: http://www.jennen.de * * * ----- Forwarded message from whois-info(a)nic.at ----- * * From whois-info(a)nic.at Fri Jan 5 20:51:41 2001 * From: whois-info(a)nic.at * Message-ID: <645525DACC86A945B4DA2B199D8481F64412BA(a)nics-01.sbg.nic.at> * To: jennen(a)aball.de * Subject: WHOIS-Database .at-Domains * Date: Fri, 5 Jan 2001 20:48:24 +0100 * X-Mailer: Internet Mail Service (5.5.2650.21) * X-MIME-Autoconverted: from quoted-printable to 8bit by sonne.aball.de id UAA * 20098 * * Sehr geehrte Damen und Herren! * * Sie erhalten folgende Information von nic.at, da Sie als Kontaktperson * (tech-c oder zone-c) einer .at-Domain eingetragen sind. * * This is an information from nic.at to all contacts (tech-c and zone-c) of * .at-domains. To view the english version please click here: * www.nic.at/english/whois_info.html. Please note your nicat-handle below. * * Aus administrativen Gruenden kann die Organisation Ripe (www.ripe.net) ihre * Datenbank nicht mehr zur Speicherung von Domain-Daten ("Whois"-Abfragen) zur * Verf|gung stellen. * nic.at wird daher die relevanten Daten aus der Ripe-Datenbank absiedeln und * lokal verwalten. Die Funktionalitaet und Wartung von Domains ist damit in * keinster Weise beeintraechtigt. Die Domain-Daten sind weiterhin (auch |ber * www.ripe.net) oeffentlich abrufbar und sicher verwaltet - es wird lediglich * bei Abfragen direkt auf die nic.at-Datenbank zugegriffen. * * Im Zusammenhang mit dieser Umstellung werden alle bestehenden Ripe-Handles * bei .at-Domains automatisch durch NICAT-Handles ersetzt. Nach einer * Uebergangsphase wird nic.at bei Neuregistrierungen und Aenderungen nur noch * NICAT-Handles akzeptieren. Beruecksichtigen Sie das bitte, falls Sie * Ripe-Handles in Ihrer internen Software zur Verwaltung von .at-Domains * verwenden. * Sollten Sie Ihr Ripe-Handle f|r andere Ripe-Services benutzen, bleibt er * nat|rlich bestehen und ist bei Ripe weiterhin g|ltig. * * ********************************************************** * Ihr 'alter' Ripe-Handle/your old ripe-handle: AJ4-RIPE * Ihr neuer NICAT-Handle/your new nicat-handle: AJ552432-NICAT * ********************************************************** * * Folgender Zeitplan ist f|r die Umstellung vorgesehen: * ab 12.1.2001 kvnnen NICAT-Handles verwendet werden - es sind Ripe-Handles * UND NICAT-Handles gueltig. Alle domain objects, die davor angelegt oder * geaendert wurden, werden im alten Format ausgegeben. Alle neuen domain * objects, erzeugt durch Neuantrag oder Aenderung werden im neuen Format * ausgegeben. Eine Aenderung bewirkt, dass das Object in der Ripe Datenbank * geloescht wird und das in Object in der nic.at-Datenbank zum Tragen kommt. * ab 29.1. gelten bei nic.at nur mehr NICAT-Handles, die .at-Domain Objects * werden in der Ripe-Datenbank geloescht. Bitte verwenden Sie ab 29.1. keine * RIPE-Handles mehr! Bis zum Ende der Loeschaktion kann es zwei Ausgabeformate * (alt oder neu) geben. * * Eine detaillierte Beschreibung der Aenderungen in den Domain und Person * Objects finden Sie auf unserer Homepage unter * (www.nic.at/german/whois_info.html), FAQ's zum Thema Whois unter * www.nic.at/german/whois_FAQ.html. * * Bei weiteren Fragen kontaktieren Sie bitte das nic.at Team unter 0800 800 * 888 844 bzw. per E-Mail unter whois-info(a)nic.at * Wir helfen Ihnen gerne weiter. * * Ihr nic.at Team * * nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H. * Jakob-Haringer-Stra_e 8 * A-5020 Salzburg * * Infos zu Domainregistrierung www.nic.at * * E-Mail: whois-info(a)nic.at * Tel.: +43 (662) 4669-844 * Fax: +43 (662) 4669-29 * In Oesterreich gebuehrenfrei: * Tel.: 0800 800 888-844 * Fax: 0800 800 888-29 * * ----- End of forwarded message from whois-info(a)nic.at ----- * * ----- End of forwarded message from Andreas Jennen ----- ----- End of forwarded message from RIPE NCC Hostmaster -----

1 0

formular for access to dbm
by glaess＠element5.de 12 Jan '01

12 Jan '01

hi folks, i need the name of the formular what i will send to auto-dbm(a)ripe.net for mirror the dbm . in the documents (ripe-157) under 2.5 are written you must be in the access list ... send us the ip address after the the emailaddr. but what kind of formular ?

2 1

RE: Loop in AS macro
by Lu, Ping 11 Jan '01

11 Jan '01

Hi, I am new to this list and would like to ask a (maybe stupid) question to the dicussion: If we want to write a script to expand the AS MACRO, how can we avoid to go into a loop if multiple AS-MACROs reference each other ? Ping Lu Cable & Wireless USA Network Tools and Analysis Group W: 703-292-2359 E: plu(a)cw.net > -----Original Message----- > From: Cengiz Alaettinoglu [mailto:cengiz@packetdesign.com] > Sent: Wednesday, January 10, 2001 12:14 PM > To: Shane Kerr > Cc: Wilfried Woeber, UniVie/ACOnet; farrache(a)cc.in2p3.fr; > db-wg(a)ripe.net; routing-wg(a)ripe.net; Henk.Uijterwaal(a)ripe.net > Subject: RE: Loop in AS macro > > > > Shane Kerr (shane(a)ripe.net) on January 10: > > Gilles, Wilfried, and all, > > > > This is not a bug, or even an inconsistency. Consider the following > > as-macro objects: > > > > as-macro: AS-X > > members: AS-Y, AS123 > > > > as-macro: AS-Y > > members: AS-X, AS456, AS789 > > > > In this case, AS-X and AS-Y both expand to the same aut-num objects: > > AS123, AS456, and AS789. However, they may have different > maintainers, > > contacts, descriptions, and so on. In RPSL, many more > kinds of loops are > > possible as well, in as-set, route-set, and filter-set objects. > > RPSL defines semantics when loops exist. However, it does not promote > them, or prohibit additional restrictions by the registry operators > not to have loops. > > > > > External software that deals with the set objects needs to do loop > > detection in order to prevent infinite loops. For as-set > objects (which > > are as-macro objects in RIPE-181), this is fairly easy: > keep a list or > > hash of the AS sets expanded, and don't expand them again. > For route-set > > and filter-set objects it is not quite so easy. If you > need help with > > these, you can send me and e-mail and I can explain the > techniques that > > I've used for these objects. > > > > Shane Kerr <shane(a)ripe.net> > > Database Software Engineer > > RIPE NCC > > +31 20 535 4427 > > > > p.s. This is actually a feature, not an bug. :) > > > > p.p.s. It has been argued (by me) that RPSL allows objects that are > > logically impossible, but the RFC authors don't seem to think so! > > > > On Wed, 10 Jan 2001, Wilfried Woeber, UniVie/ACOnet wrote: > > > > > Hi Gilles, > > > > > > I guess we wouldn't be able to check against those > accidents at the time > > > of a DB _update_... > > > > > > But checking the RR internal _data_ consistency could > maybe become part > > > of the RIS (or similar) project? > > > > > > Henk, any comments? > > > > > > An interesting aside: I guess similar problems could occur with > > > RPSL-based RRs? > > > > > > -WW > > > > _________________________________:____________________________ > _________ > > > 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 > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~ > > > > > > To: staff(a)ip.tele.dk, peering(a)tli.de, ip-oper(a)tli.de, > admin-c(a)tli.de > > > CC: farrache(a)cc.in2p3.fr, db-wg(a)ripe.net, routing-wg(a)ripe.net > > > Subject: Loop in AS macro > > > Date: Wed, 10 Jan 2001 10:28:15 +0100 > > > From: Gilles Farrache <farrache(a)cc.in2p3.fr> > > > > > > Dear database managers, > > > > > > I notice a loop in the followings AS-MACRO, in fact > AS-TELEDANMARKINTERNATIONAL > > > is calling AS-TLI which is calling AS-TELEDK which is > calling AS-TELEDANMARKINTERNATIONAL. > > > (and all that make that our automatic filter generation > tool fails) > > > > > > Could you correct those macro and will the Ripe database > management provide any > > > control on that kind of loop ? > > > > > > Gilles > > > > > > as-macro: AS-TELEDANMARKINTERNATIONAL > > > descr: Tele Danmark customers outside Denmark > > > as-list: AS1902 AS12461 > > > as-list: AS8881 AS-KOMTEL > > > as-list: AS13194 AS-BITE > > > as-list: AS6709 > > > as-list: AS8650 AS-TLI > > > as-list: AS8542 > > > as-list: AS12294 AS-TSUA AS6807 AS8349 AS12788 > AS12837 AS12872 AS13249 AS15386 AS15497 AS15929 AS16007 > > > as-list: AS12546 > > > as-list: AS15389 > > > tech-c: AS5071-RIPE > > > admin-c: AS5071-RIPE > > > notify: staff(a)ip.tele.dk > > > notify: peering(a)tli.de > > > mnt-by: AS3292-MNT > > > changed: jesper(a)skriver.dk 20001103 > > > changed: toba(a)tdk.dk 20001117 > > > changed: tee(a)tdk.dk 20001123 > > > changed: jesper(a)skriver.dk 20001228 > > > changed: jesper(a)skriver.dk 20010109 > > > source: RIPE > > > > > > as-macro: AS-TLI > > > descr: Talkline GmbH, Internet Division > > > descr: List of ASes according to Talkline Internet (AS8650) > > > descr: and customers > > > as-list: AS5605 > > > as-list: AS6783 > > > as-list: AS8650 > > > as-list: AS8881 > > > as-list: AS12461 > > > as-list: AS12546 > > > as-list: AS-TELEDK > > > as-list: AS-GLOBAL > > > tech-c: TLIP1-RIPE > > > admin-c: TLIP1-RIPE > > > notify: peering(a)tli.de > > > mnt-by: TALKLINE-MNT > > > changed: thomas(a)tli.de 19990923 > > > changed: thomas(a)tli.de 19991020 > > > changed: thomas(a)tli.de 19991025 > > > changed: thomas(a)tli.de 20001023 > > > changed: thomas(a)tli.de 20001025 > > > source: RIPE > > > > > > as-macro: AS-TELEDK > > > descr: Tele Danmark and Tele Danmark customers > > > as-list: AS-TELEDANMARKDANISH > > > as-list: AS-TELEDANMARKINTERNATIONAL > > > as-list: AS-BELBONEMEMBERS > > > as-list: AS-GLOBAL > > > tech-c: AS5071-RIPE > > > admin-c: AS5071-RIPE > > > notify: staff(a)ip.tele.dk > > > notify: peering(a)tli.de > > > mnt-by: AS3292-MNT > > > changed: jesper(a)skriver.dk 19990922 > > > changed: jesper(a)skriver.dk 19991019 > > > changed: jesper(a)skriver.dk 19991025 > > > changed: jesper(a)skriver.dk 19991210 > > > changed: toba(a)tdk.dk 20000903 > > > source: RIPE > > > > -------------------------------------------------------------- > ------------------ > > > > > > > > > > Cengiz > > -- > Cengiz Alaettinoglu Packet Design Inc. > >

4 3

inetnum update
by Panagiotis Skoulikaritis 11 Jan '01

11 Jan '01

Hi, I am new to this list and would like to ask a (maybe stupid) question to the dicussion: how can I update the inetnum object in the database. The company I work for got a new allocation and they asked me to update the database, I' new to the company and I have no prior experience in managing/updating the database objects. If anyone could help me it would be appreciated. Thanks Panagiotis

1 0

Re: inetnum update
by RIPE NCC Staff 11 Jan '01

11 Jan '01

Dear Panagiotis Skoulikaritis, Information on creating, updating and deleting objects in the RIPE Network Management Database is available from: <http://www.ripe.net/ripe/docs/ripe-157.html> <ftp://ftp.ripe.net/ripe/docs/ripe-157.ps> <ftp://ftp.ripe.net/ripe/docs/ripe-157.txt> with a supplement available at: <http://www.ripe.net/ripe/docs/ripe-189.html> <ftp://ftp.ripe.net/ripe/docs/ripe-189.ps> <ftp://ftp.ripe.net/ripe/docs/ripe-189.txt> Help on using <auto-dbm(a)ripe.net> is available by sending an e-mail to <auto-dbm(a)ripe.net> with HELP in the Subject line. Help on using whois is available by doing whois -h whois.ripe.net HELP If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Engin Gunduz -------------------------------- RIPE NCC Database Administration Original Message follows: ------------------------- This is a multi-part message in MIME format. ------=_NextPart_000_016E_01C07BD1.1453C730 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Hi, I am new to this list and would like to ask a (maybe stupid) = question to the dicussion: how can I update the inetnum object in the database. The company I work = for got a new allocation and they asked me to update the database, I' = new to the company and I have no prior experience in managing/updating = the database objects. If anyone could help me it would be appreciated. Thanks=20 Panagiotis ------=_NextPart_000_016E_01C07BD1.1453C730 Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-7"> <META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2> <DIV><FONT size=3D2><FONT size=3D3>Hi, I am new to this list and would = like to ask a=20 (maybe stupid) question to the dicussion:<BR></FONT>how can I = update the=20 inetnum object in the database.  The company I work for got a new=20 allocation and they asked me to update the database,  I' new to the = company=20 and I have no prior experience in managing/updating the database = objects. =20 If anyone could help me it would be appreciated.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Thanks </FONT></DIV> <DIV><FONT size=3D2>Panagiotis</FONT></DIV></FONT></DIV></BODY></HTML> ------=_NextPart_000_016E_01C07BD1.1453C730--

1 0

RE: Loop in AS macro
by Wilfried Woeber, UniVie/ACOnet 10 Jan '01

10 Jan '01

Hi Gilles, I guess we wouldn't be able to check against those accidents at the time of a DB _update_... But checking the RR internal _data_ consistency could maybe become part of the RIS (or similar) project? Henk, any comments? An interesting aside: I guess similar problems could occur with RPSL-based RRs? -WW _________________________________:_____________________________________ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To: staff(a)ip.tele.dk, peering(a)tli.de, ip-oper(a)tli.de, admin-c(a)tli.de CC: farrache(a)cc.in2p3.fr, db-wg(a)ripe.net, routing-wg(a)ripe.net Subject: Loop in AS macro Date: Wed, 10 Jan 2001 10:28:15 +0100 From: Gilles Farrache <farrache(a)cc.in2p3.fr> Dear database managers, I notice a loop in the followings AS-MACRO, in fact AS-TELEDANMARKINTERNATIONAL is calling AS-TLI which is calling AS-TELEDK which is calling AS-TELEDANMARKINTERNATIONAL. (and all that make that our automatic filter generation tool fails) Could you correct those macro and will the Ripe database management provide any control on that kind of loop ? Gilles as-macro: AS-TELEDANMARKINTERNATIONAL descr: Tele Danmark customers outside Denmark as-list: AS1902 AS12461 as-list: AS8881 AS-KOMTEL as-list: AS13194 AS-BITE as-list: AS6709 as-list: AS8650 AS-TLI as-list: AS8542 as-list: AS12294 AS-TSUA AS6807 AS8349 AS12788 AS12837 AS12872 AS13249 AS15386 AS15497 AS15929 AS16007 as-list: AS12546 as-list: AS15389 tech-c: AS5071-RIPE admin-c: AS5071-RIPE notify: staff(a)ip.tele.dk notify: peering(a)tli.de mnt-by: AS3292-MNT changed: jesper(a)skriver.dk 20001103 changed: toba(a)tdk.dk 20001117 changed: tee(a)tdk.dk 20001123 changed: jesper(a)skriver.dk 20001228 changed: jesper(a)skriver.dk 20010109 source: RIPE as-macro: AS-TLI descr: Talkline GmbH, Internet Division descr: List of ASes according to Talkline Internet (AS8650) descr: and customers as-list: AS5605 as-list: AS6783 as-list: AS8650 as-list: AS8881 as-list: AS12461 as-list: AS12546 as-list: AS-TELEDK as-list: AS-GLOBAL tech-c: TLIP1-RIPE admin-c: TLIP1-RIPE notify: peering(a)tli.de mnt-by: TALKLINE-MNT changed: thomas(a)tli.de 19990923 changed: thomas(a)tli.de 19991020 changed: thomas(a)tli.de 19991025 changed: thomas(a)tli.de 20001023 changed: thomas(a)tli.de 20001025 source: RIPE as-macro: AS-TELEDK descr: Tele Danmark and Tele Danmark customers as-list: AS-TELEDANMARKDANISH as-list: AS-TELEDANMARKINTERNATIONAL as-list: AS-BELBONEMEMBERS as-list: AS-GLOBAL tech-c: AS5071-RIPE admin-c: AS5071-RIPE notify: staff(a)ip.tele.dk notify: peering(a)tli.de mnt-by: AS3292-MNT changed: jesper(a)skriver.dk 19990922 changed: jesper(a)skriver.dk 19991019 changed: jesper(a)skriver.dk 19991025 changed: jesper(a)skriver.dk 19991210 changed: toba(a)tdk.dk 20000903 source: RIPE --------------------------------------------------------------------------------

6 6

RE: Loop in AS macro
by Christian Storch 10 Jan '01

10 Jan '01

Please don't say 'include'. - What about "expand" as Shane used it already? So think about a macro as a set of AS'es and only form the set union of it. Every AS should be a set of size 1 and a macro a set of size n. As a result you would get an infinite iteration but A = B! So if somebody would suggest it to be nonsense, what about Pi etc.? ;-)) I think a script has only to expand a macro and to insert it into a list of already expanded macros. ... Christian -----Original Message----- From: Gilles Farrache [SMTP:farrache@cc.in2p3.fr] Sent: Wednesday, January 10, 2001 12:17 PM To: Shane Kerr Cc: Wilfried Woeber, UniVie/ACOnet; farrache(a)cc.in2p3.fr; db-wg(a)ripe.net; routing-wg(a)ripe.net; Henk.Uijterwaal(a)ripe.net; farrache(a)cc.in2p3.fr; Jesper Skriver Subject: Re: Loop in AS macro Shane and al, When I was at school (a long time ago) I learn what was called the "set theory" ( "Theorie des ensembles" in French) that was part of what was called the NEW Mathematics. In those courses I learned that : If set A is included in set B and if set B was included in set A then A = B. Whet your telling me is that there are New New mathematics (as there is a new economy) in which : if set A is included in set B and set B included in set A that does not implie A = B. I am very interrested by that theory and will be happy that you give me some pointers to it. :-) Or what is an AS-MACRO ? It is a set of AS (or a set of set of AS ....). So they have to follow the set theory. Gilles

2 1

Loop in AS macro
by Gilles Farrache 10 Jan '01

10 Jan '01

Dear database managers, I notice a loop in the followings AS-MACRO, in fact AS-TELEDANMARKINTERNATIONAL is calling AS-TLI which is calling AS-TELEDK which is calling AS-TELEDANMARKINTERNATIONAL. (and all that make that our automatic filter generation tool fails) Could you correct those macro and will the Ripe database management provide any control on that kind of loop ? Gilles as-macro: AS-TELEDANMARKINTERNATIONAL descr: Tele Danmark customers outside Denmark as-list: AS1902 AS12461 as-list: AS8881 AS-KOMTEL as-list: AS13194 AS-BITE as-list: AS6709 as-list: AS8650 AS-TLI as-list: AS8542 as-list: AS12294 AS-TSUA AS6807 AS8349 AS12788 AS12837 AS12872 AS13249 AS15386 AS15497 AS15929 AS16007 as-list: AS12546 as-list: AS15389 tech-c: AS5071-RIPE admin-c: AS5071-RIPE notify: staff(a)ip.tele.dk notify: peering(a)tli.de mnt-by: AS3292-MNT changed: jesper(a)skriver.dk 20001103 changed: toba(a)tdk.dk 20001117 changed: tee(a)tdk.dk 20001123 changed: jesper(a)skriver.dk 20001228 changed: jesper(a)skriver.dk 20010109 source: RIPE as-macro: AS-TLI descr: Talkline GmbH, Internet Division descr: List of ASes according to Talkline Internet (AS8650) descr: and customers as-list: AS5605 as-list: AS6783 as-list: AS8650 as-list: AS8881 as-list: AS12461 as-list: AS12546 as-list: AS-TELEDK as-list: AS-GLOBAL tech-c: TLIP1-RIPE admin-c: TLIP1-RIPE notify: peering(a)tli.de mnt-by: TALKLINE-MNT changed: thomas(a)tli.de 19990923 changed: thomas(a)tli.de 19991020 changed: thomas(a)tli.de 19991025 changed: thomas(a)tli.de 20001023 changed: thomas(a)tli.de 20001025 source: RIPE as-macro: AS-TELEDK descr: Tele Danmark and Tele Danmark customers as-list: AS-TELEDANMARKDANISH as-list: AS-TELEDANMARKINTERNATIONAL as-list: AS-BELBONEMEMBERS as-list: AS-GLOBAL tech-c: AS5071-RIPE admin-c: AS5071-RIPE notify: staff(a)ip.tele.dk notify: peering(a)tli.de mnt-by: AS3292-MNT changed: jesper(a)skriver.dk 19990922 changed: jesper(a)skriver.dk 19991019 changed: jesper(a)skriver.dk 19991025 changed: jesper(a)skriver.dk 19991210 changed: toba(a)tdk.dk 20000903 source: RIPE

3 4

RIPE Whois RPSL Migration
by RIPE NCC 21 Dec '00

21 Dec '00

[ Apologies for duplicate mails ] RIPE Whois RPSL Migration The RIPE Database re-implementation project is nearing completion. A key feature of the new database is the implementation of RPSL, to replace the old RIPE-181 standard. RPSL is similar, but not identical, to RIPE-181. The RIPE NCC expects that many programs that use the RIPE Whois database will continue to operate properly without modification. However, some programs may have problems parsing the RPSL format, or be confused by differences in behaviour. We would like to ensure that the transition to RPSL is as easy as possible. Therefore, we are working with the RIPE community to provide resources you can use to check any programs or scripts that you have that use the RIPE Whois database. Please visit our Migration page for further information: http://www.ripe.net/ripencc/pub-services/db/rpsl/index.html This page will be updated regularly with the latest information. We will provide additional tools and information as they become available. The actual timeline of when the RPSL server will replace the existing RIPE-181 server will be decided at the RIPE-38 meeting. If you want input on when the change will occur, then you should either attend this meeting or post your comments on the RIPE DB mailing list. http://www.ripe.net/ripe/meetings/current/ripe-38/index.html http://www.ripe.net/ripe/wg/db/index.html Regards, The RIPE Database Group. RIPE NCC

1 0

Announcement: RIPE Whois Database version 3.0 beta is out
by RIPE Database Administration 08 Dec '00

08 Dec '00

Dear All, [ Apologies for duplicate messages ] This mail is to inform you that version 3.0 beta of the RIPE Whois Database is out. Read on! You will be affected too. The RIPE Database is about to change its data format, from RIPE181 to RPSL (the Routing Policy Specification Language, see RFC2622). This will affect all object types, including "person", "domain" and "inetnum". The version 2 of the RIPE Database, the one currently in production on whois.ripe.net, will in the next months be replaced by version 3. All the entries in the RIPE Database will be translated into RPSL format, and that is the format you will get when you will be querying the Database. Don't be mistaken: for the moment, whois.ripe.net continues running with version 2 and answering to your queries in the old-fashioned way. But this will not last forever; in a few months, all will become RPSL. So if you use the Whois database, we encourage all of you to prepare for this change as soon as possible. We strongly suggest you to start to get used to RPSL and version 3.0 . In this aim, you can do the following: - Query rpsl.ripe.net at port 43. You will find there exactly the same objects that are in whois.ripe.net, mirrored live and in RPSL format. - If you have any script that runs by querying whois.ripe.net, test it by pointing it to rpsl.ripe.net and make it v3.0-compliant. - Try our CGI interface to the RPSL server: you can find it at http://www.ripe.net/ripencc/pub-services/db/reimp/. - Get to know the new update path: use our "sandbox" database for RPSL updates. Send your updates to <auto-rip(a)ripe.net> and query the corresponding database at rpsl.ripe.net, port 4343 . Remember that in a few months, that's the way the RIPE Database will be running; so the earlier you start working with it, the less likely you are to be unpleasantly surprised later. We are currently preparing additional resources to help ease the transition; we will announce them as soon as they are available, which will happen later this month. Please note that the software is still in a "beta" phase. So we need your feedback! If you happen to find something that looks like a bug when you are testing the RPSL database, don't hesitate... Send us a bug report at <dbrip(a)ripe.net> ! If you want to actively participate to the migration effort, you could join the "RIP migration Task force" and let yourself be heard. Just write to <ripe-dbm(a)ripe.net> and ask to join the Task Force. For the ones interested in viewing or trying the code, you can download it at: ftp://ftp.ripe.net/ripe/dbase/reimp/whois-rip-3.0beta1.tar.gz You can also join a discussion list related to version 3.0 beta of the RIPE Database Software. To subscribe to this list, send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. It is a moderated mailing list so some delays in subscription are possible. Regards, The RIPE Database Group.

1 0