- db-wg - mailman.ripe.net

Summary of ERX-TF discussion
by leo vegoda 29 Oct '02

29 Oct '02

Dear Colleagues, As promised, here is a summary of the short discussion had on the <erx-tf(a)ripe.net> mailing list over the last few weeks. There have been about 15 messages in total. On 10 October we published the RIPE NCC's proposed ERX process for IPv4 to the Task Force. There were two technical queries: a request for confirmation that all contacts in both databases be e-mailed. Also, there was a request for confirmation on how reverse delegations would be handled. Substantive issues included a question on how early registrations would be handled from a policy point of view. The RIPE NCC confirmed that in the past, the majority of registrants have agreed to meet the current policy requirements for registration. However, we also noted that previous registrations have tended to be done for organisations who place a value on registration data. It was argued that the policy issues were less important than the accuracy of the registration data transferred/updated. No other issues on the transfer process were raised. It appears that the Task Force is happy with the proposed transfer process. As such, we would like to publish the proposed process in the next few days. Regards, -- leo vegoda RIPE NCC Registration Services

1 0

Improved Query Processing on RIPE Database Serve
by RIPE Database Administration 24 Oct '02

24 Oct '02

[ Apologies for multiple copies. ] Colleagues, Whois query processing for the RIPE Database Server has been revised to be more consistent and helpful to users. In the past, the server would make a number of changes to the user query without telling the user, for example removing characters that it did not understand or truncating the query. The new implementation will perform exactly the query the user requested, if possible, and give errors when not. Warnings are now returned where appropriate. A full description of the changes may be found here: http://www.ripe.net/db/whois-query-2002.html In general, all correct queries will provide exactly the same results as on the previous version of the server. If you have any questions please send them to <ripe-dbm(a)ripe.net>. Suggestions may be sent to <ripe-dbm(a)ripe.net>, or discussed on the RIPE Database working group mailing list, details of which may be found here: http://www.ripe.net/ripe/wg/db/index.html -- Shane Kerr RIPE NCC

1 0

[Ted.Hardie@nominum.com: [Ietf-not43] Working Group Last Call: draft-ietf-crisp-requirements-01.txt]
by Stephane Bortzmeyer 16 Oct '02

16 Oct '02

This is also for address registries like RIPE-NCC so I believe everybody should read this post-whois document and comment before the Atlanta meeting.

1 0

RE: FAILED update.
by Pieterjan d'Hertog 14 Oct '02

14 Oct '02

> > -----Mensaje original----- > > De: Iglesias Fuente, Jesus > > Enviado el: viernes 11 de octubre de 2002 13:09 > > Para: 'auto-rpsl(a)ripe.net' > > Asunto: longack > > > > password: 7djsfy25ddn > > Please change your update password :-) --- Pieterjan d'Hertog, Senior Network Engineer Belgacom Skynet NV/SA, 2 Rue Carli, B-1140 Brussels Phone +3227061311 Fax +3227061150 http://www.skynet.be PGP fingerprint: D9AB CD6A 2A78 73CC 68BF 0AFA 8FB3 5821 E4BB 9D2E

1 0

Re: NCC#2002102136 RV: FAILED update.
by RIPE Database Administration 14 Oct '02

14 Oct '02

Dear Jesus Iglesias, [Please send any operational problems/doubts with the RIPE database to ripe-dbm(a)ripe.net , this is the best address to have your doubts answered]. The failure of your update is related to the fact that you have sent your object quoted: > as-set: AS-BTTEL > descr: BT Telecomunicaciones customers > members: AS8903 > ... Please don't quote the objects, ie send like as-set: AS-BTTEL descr: BT Telecomunicaciones customers members: AS8903 ... Also, we recommend never to send your password in the clean in mail messages, especially to public mailing lists. If you have any more questions, please contact <ripe-dbm(a)ripe.net>. Regards, Tiago Antao ____________________________ RIPE Database Administration. Original message follows: ------------------------ > Hello, > Can anyone tell me why did this update fail? > The robot answered: > > Update FAILED: Syntax error in object > ***Error: Error with class attribute, class invalid > > Thanks for your help ! > Regards. > > _________________________________ > Jes�s Iglesias Fuente > IP Platforms & Services (Planning) > BT Ignite Spain > jesus.iglesias(a)ignite.com > Phone: (+34) 91.270.62.14 > Fax: (+34) 91.270.63.10 > _____________________________________________ > > > -----Mensaje original----- > De: Iglesias Fuente, Jesus > Enviado el: viernes 11 de octubre de 2002 13:09 > Para: 'auto-rpsl(a)ripe.net' > Asunto: longack > > password: *********************** > > as-set: AS-BTTEL > descr: BT Telecomunicaciones customers > members: AS8903 > members: AS3324, AS21025 > members: AS12334, AS20784 > members: AS12356, AS12636 > members: AS8239, AS12430 > members: AS12845, AS21268 > members: AS9192, AS13066 > members: AS13143, AS15734 > members: AS12946, AS15369 > members: AS15912, AS15937 > members: AS15963, AS16373 > members: AS16203, AS13205 > members: AS20815, AS20944 > members: AS16371, AS21368 > members: AS21193, AS20718 > members: AS20760, AS20607 > members: AS24830, AS21181 > members: AS15919, AS25267 > remarks: BT Telecomunicaciones customers ASs > tech-c: BTT2-RIPE > admin-c: EL729-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > > > aut-num: AS8903 > as-name: BT > descr: BT Tel AS 1 > import: from AS701 action pref=100; accept ANY > import: from AS5400 action pref=100; accept ANY > import: from AS3561 action pref=100; accept ANY > import: from AS2856 action pref=100; accept ANY > import: from AS6895 action pref=100; accept AS6895 > import: from AS3262 action pref=100; accept AS3262 > import: from AS8761 action pref=100; accept AS8761 > import: from AS8782 action pref=100; accept AS8782 > import: from AS8220 action pref=100; accept AS8220 > import: from AS4589 action pref=100; accept AS4589 > import: from AS12457 action pref=100; accept AS12457 > import: from AS12357 action pref=100; accept AS12357 > import: from AS6897 action pref=100; accept AS6897 > import: from AS12479 action pref=100; accept AS12479 > import: from AS12852 action pref=100; accept AS12852 > import: from AS2686 action pref=100; accept AS2686 > import: from AS3352 action pref=100; accept AS3352 > import: from AS3324 action pref=100; accept AS3324 > import: from AS2134 action pref=100; accept AS2134 > import: from AS12359 action pref=100; accept AS12359 > import: from AS3352 action pref=100; accept AS3352 > import: from AS13041 action pref=100; accept AS13041 > import: from AS12386 action pref=100; accept AS12386 > import: from AS9019 action pref=100; accept AS9019 > import: from AS5978 action pref=100; accept AS5378 > import: from AS12482 action pref=100; accept AS12482 > import: from AS9106 action pref=100; accept AS9106 > import: from AS12715 action pref=100; accept AS12715 > import: from AS702 action pref=100; accept AS702 > import: from AS3247 action pref=100; accept AS-3247 > import: from AS766 action pref=100; accept AS-766 > import: from AS3257 action pref=100; accept AS-NACAMAR > import: from AS6669 action pref=100; accept AS-BTES > import: from AS3324 action pref=100; accept AS3324 > import: from AS12334 action pref=100; accept AS12334 > import: from AS12356 action pref=100; accept AS12356 > import: from AS8239 action pref=100; accept AS8239 > import: from AS12430 action pref=100; accept AS12430 > import: from AS12636 action pref=100; accept AS12636 > import: from AS12845 action pref=100; accept AS12845 > import: from AS12946 action pref=100; accept AS12946 > import: from AS9192 action pref=100; accept AS9192 > import: from AS13066 action pref=100; accept AS13066 > import: from AS13143 action pref=100; accept AS13143 > import: from AS15369 action pref=100; accept AS15369 > import: from AS15734 action pref=100; accept AS15734 > import: from AS15912 action pref=100; accept AS15912 > import: from AS15937 action pref=100; accept AS15937 > import: from AS15963 action pref=100; accept AS15963 > import: from AS16373 action pref=100; accept AS16373 > import: from AS16203 action pref=100; accept AS16203 > import: from AS13205 action pref=100; accept AS13205 > import: from AS21025 action pref=100; accept AS21025 > import: from AS20815 action pref=100; accept AS20815 > import: from AS20784 action pref=100; accept AS20784 > import: from AS20944 action pref=100; accept AS20944 > import: from AS16371 action pref=100; accept AS16371 > import: from AS21368 action pref=100; accept AS21368 > import: from AS21268 action pref=100; accept AS21268 > import: from AS21193 action pref=100; accept AS21193 > import: from AS20718 action pref=100; accept AS20718 > import: from AS20607 action pref=100; accept AS20607 > import: from AS20760 action pref=100; accept AS20760 > import: from AS24830 action pref=100; accept AS24830 > import: from AS21181 action pref=100; accept AS21181 > import: from AS15919 action pref=100; accept AS15919 > import: from AS25267 action pref=100; accept AS25267 > export: to AS701 announce AS-BTTEL > export: to AS5400 announce AS-BTTEL > export: to AS3561 announce AS-BTTEL > export: to AS2856 announce AS-BTTEL > export: to AS6669 announce AS-BTTEL AS-BTTELESPANIX AS-BTTELCATNIX > export: to AS2134 announce AS-BTTEL AS-BTES > export: to AS2686 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS3324 announce AS-BTTEL AS-BTES > export: to AS3352 announce AS-BTTEL AS-BTES > export: to AS6895 announce AS-BTTEL AS-BTES > export: to AS6897 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS8220 announce AS-BTTEL AS-BTES > export: to AS4589 announce AS-BTTEL AS-BTES > export: to AS12457 announce AS-BTTEL AS-BTES > export: to AS12357 announce AS-BTTEL AS-BTES > export: to AS12479 announce AS-BTTEL AS-BTES > export: to AS12359 announce AS-BTTEL AS-BTES > export: to AS8782 announce AS-BTTEL AS-BTES > export: to AS12852 announce AS-BTTEL AS-BTES > export: to AS13041 announce AS-BTTEL AS-BTES > export: to AS12386 announce AS-BTTEL AS-BTES > export: to AS9019 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS12482 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS9106 announce AS-BTTEL AS-BTES > export: to AS12715 announce AS-BTTEL AS-BTES > export: to AS5378 announce AS-BTTEL AS-BTES > export: to AS3257 announce AS-BTTEL AS-BTES > export: to AS702 announce AS-BTTEL AS-BTES > export: to AS3247 announce AS-BTTEL AS-BTES > export: to AS766 announce AS-BTTEL AS-BTES > export: to AS12334 announce ANY > export: to AS12356 announce ANY > export: to AS8239 announce ANY > export: to AS12430 announce ANY > export: to AS12636 announce ANY > export: to AS12845 announce ANY > export: to AS9192 announce ANY > export: to AS13066 announce ANY > export: to AS3324 announce ANY > export: to AS13143 announce ANY > export: to AS15734 announce ANY > export: to AS12946 announce ANY > export: to AS15369 announce ANY > export: to AS15912 announce ANY > export: to AS15937 announce ANY > export: to AS15963 announce ANY > export: to AS16373 announce ANY > export: to AS16203 announce ANY > export: to AS13205 announce ANY > export: to AS21025 announce ANY > export: to AS20815 announce ANY > export: to AS20784 announce ANY > export: to AS20944 announce ANY > export: to AS16371 announce ANY > export: to AS21368 announce ANY > export: to AS21268 announce ANY > export: to AS21193 announce ANY > export: to AS20718 announce ANY > export: to AS20607 announce ANY > export: to AS20760 announce ANY > export: to AS24830 announce ANY > export: to AS21181 announce ANY > export: to AS15919 announce ANY > export: to AS25267 announce ANY > admin-c: EL729-RIPE > tech-c: BTT2-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > ********************************************** Noticia legal Este mensaje electr�nico contiene informaci�n de BT Ignite Espa�a S.A.U. que es privada y confidencial, siendo para el uso exclusivo de la persona (s) o entidades arriba mencionadas. Si usted no es el destinatario se�alado, le informamos que cualquier divulgaci�n, copia, distribuci�n o uso de los contenidos est� prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido lo antes posible. Gracias.

1 0

RE: RV: FAILED update.
by Wilfried Woeber, UniVie/ACOnet 14 Oct '02

14 Oct '02

> Hello, > Can anyone tell me why did this update fail? > The robot answered: > ... >********************************************** >Noticia legal >Este mensaje electrónico contiene información de BT Ignite España S.A.U. que >es privada y confidencial, siendo para el uso exclusivo de la persona (s) o >entidades arriba mencionadas. Si usted no es el destinatario señalado, le >informamos que cualquier divulgación, copia, distribución o uso de los >contenidos está prohibida. Si usted ha recibido este mensaje por error, por >favor borre su contenido lo antes posible. >Gracias. Sorry, I am not dealing with mails containing legal disclaimers or privacy restrictions (regardless of the language they are written in ;-) -WW

1 0

RV: FAILED update.
by jesus.iglesias＠bt.es 14 Oct '02

14 Oct '02

> Hello, > Can anyone tell me why did this update fail? > The robot answered: > > Update FAILED: Syntax error in object > ***Error: Error with class attribute, class invalid > > Thanks for your help ! > Regards. > > _________________________________ > Jesús Iglesias Fuente > IP Platforms & Services (Planning) > BT Ignite Spain > jesus.iglesias(a)ignite.com > Phone: (+34) 91.270.62.14 > Fax: (+34) 91.270.63.10 > _____________________________________________ > > > -----Mensaje original----- > De: Iglesias Fuente, Jesus > Enviado el: viernes 11 de octubre de 2002 13:09 > Para: 'auto-rpsl(a)ripe.net' > Asunto: longack > > password: 7djsfy25ddn > > as-set: AS-BTTEL > descr: BT Telecomunicaciones customers > members: AS8903 > members: AS3324, AS21025 > members: AS12334, AS20784 > members: AS12356, AS12636 > members: AS8239, AS12430 > members: AS12845, AS21268 > members: AS9192, AS13066 > members: AS13143, AS15734 > members: AS12946, AS15369 > members: AS15912, AS15937 > members: AS15963, AS16373 > members: AS16203, AS13205 > members: AS20815, AS20944 > members: AS16371, AS21368 > members: AS21193, AS20718 > members: AS20760, AS20607 > members: AS24830, AS21181 > members: AS15919, AS25267 > remarks: BT Telecomunicaciones customers ASs > tech-c: BTT2-RIPE > admin-c: EL729-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > > > aut-num: AS8903 > as-name: BT > descr: BT Tel AS 1 > import: from AS701 action pref=100; accept ANY > import: from AS5400 action pref=100; accept ANY > import: from AS3561 action pref=100; accept ANY > import: from AS2856 action pref=100; accept ANY > import: from AS6895 action pref=100; accept AS6895 > import: from AS3262 action pref=100; accept AS3262 > import: from AS8761 action pref=100; accept AS8761 > import: from AS8782 action pref=100; accept AS8782 > import: from AS8220 action pref=100; accept AS8220 > import: from AS4589 action pref=100; accept AS4589 > import: from AS12457 action pref=100; accept AS12457 > import: from AS12357 action pref=100; accept AS12357 > import: from AS6897 action pref=100; accept AS6897 > import: from AS12479 action pref=100; accept AS12479 > import: from AS12852 action pref=100; accept AS12852 > import: from AS2686 action pref=100; accept AS2686 > import: from AS3352 action pref=100; accept AS3352 > import: from AS3324 action pref=100; accept AS3324 > import: from AS2134 action pref=100; accept AS2134 > import: from AS12359 action pref=100; accept AS12359 > import: from AS3352 action pref=100; accept AS3352 > import: from AS13041 action pref=100; accept AS13041 > import: from AS12386 action pref=100; accept AS12386 > import: from AS9019 action pref=100; accept AS9019 > import: from AS5978 action pref=100; accept AS5378 > import: from AS12482 action pref=100; accept AS12482 > import: from AS9106 action pref=100; accept AS9106 > import: from AS12715 action pref=100; accept AS12715 > import: from AS702 action pref=100; accept AS702 > import: from AS3247 action pref=100; accept AS-3247 > import: from AS766 action pref=100; accept AS-766 > import: from AS3257 action pref=100; accept AS-NACAMAR > import: from AS6669 action pref=100; accept AS-BTES > import: from AS3324 action pref=100; accept AS3324 > import: from AS12334 action pref=100; accept AS12334 > import: from AS12356 action pref=100; accept AS12356 > import: from AS8239 action pref=100; accept AS8239 > import: from AS12430 action pref=100; accept AS12430 > import: from AS12636 action pref=100; accept AS12636 > import: from AS12845 action pref=100; accept AS12845 > import: from AS12946 action pref=100; accept AS12946 > import: from AS9192 action pref=100; accept AS9192 > import: from AS13066 action pref=100; accept AS13066 > import: from AS13143 action pref=100; accept AS13143 > import: from AS15369 action pref=100; accept AS15369 > import: from AS15734 action pref=100; accept AS15734 > import: from AS15912 action pref=100; accept AS15912 > import: from AS15937 action pref=100; accept AS15937 > import: from AS15963 action pref=100; accept AS15963 > import: from AS16373 action pref=100; accept AS16373 > import: from AS16203 action pref=100; accept AS16203 > import: from AS13205 action pref=100; accept AS13205 > import: from AS21025 action pref=100; accept AS21025 > import: from AS20815 action pref=100; accept AS20815 > import: from AS20784 action pref=100; accept AS20784 > import: from AS20944 action pref=100; accept AS20944 > import: from AS16371 action pref=100; accept AS16371 > import: from AS21368 action pref=100; accept AS21368 > import: from AS21268 action pref=100; accept AS21268 > import: from AS21193 action pref=100; accept AS21193 > import: from AS20718 action pref=100; accept AS20718 > import: from AS20607 action pref=100; accept AS20607 > import: from AS20760 action pref=100; accept AS20760 > import: from AS24830 action pref=100; accept AS24830 > import: from AS21181 action pref=100; accept AS21181 > import: from AS15919 action pref=100; accept AS15919 > import: from AS25267 action pref=100; accept AS25267 > export: to AS701 announce AS-BTTEL > export: to AS5400 announce AS-BTTEL > export: to AS3561 announce AS-BTTEL > export: to AS2856 announce AS-BTTEL > export: to AS6669 announce AS-BTTEL AS-BTTELESPANIX AS-BTTELCATNIX > export: to AS2134 announce AS-BTTEL AS-BTES > export: to AS2686 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS3324 announce AS-BTTEL AS-BTES > export: to AS3352 announce AS-BTTEL AS-BTES > export: to AS6895 announce AS-BTTEL AS-BTES > export: to AS6897 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS8220 announce AS-BTTEL AS-BTES > export: to AS4589 announce AS-BTTEL AS-BTES > export: to AS12457 announce AS-BTTEL AS-BTES > export: to AS12357 announce AS-BTTEL AS-BTES > export: to AS12479 announce AS-BTTEL AS-BTES > export: to AS12359 announce AS-BTTEL AS-BTES > export: to AS8782 announce AS-BTTEL AS-BTES > export: to AS12852 announce AS-BTTEL AS-BTES > export: to AS13041 announce AS-BTTEL AS-BTES > export: to AS12386 announce AS-BTTEL AS-BTES > export: to AS9019 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS12482 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS9106 announce AS-BTTEL AS-BTES > export: to AS12715 announce AS-BTTEL AS-BTES > export: to AS5378 announce AS-BTTEL AS-BTES > export: to AS3257 announce AS-BTTEL AS-BTES > export: to AS702 announce AS-BTTEL AS-BTES > export: to AS3247 announce AS-BTTEL AS-BTES > export: to AS766 announce AS-BTTEL AS-BTES > export: to AS12334 announce ANY > export: to AS12356 announce ANY > export: to AS8239 announce ANY > export: to AS12430 announce ANY > export: to AS12636 announce ANY > export: to AS12845 announce ANY > export: to AS9192 announce ANY > export: to AS13066 announce ANY > export: to AS3324 announce ANY > export: to AS13143 announce ANY > export: to AS15734 announce ANY > export: to AS12946 announce ANY > export: to AS15369 announce ANY > export: to AS15912 announce ANY > export: to AS15937 announce ANY > export: to AS15963 announce ANY > export: to AS16373 announce ANY > export: to AS16203 announce ANY > export: to AS13205 announce ANY > export: to AS21025 announce ANY > export: to AS20815 announce ANY > export: to AS20784 announce ANY > export: to AS20944 announce ANY > export: to AS16371 announce ANY > export: to AS21368 announce ANY > export: to AS21268 announce ANY > export: to AS21193 announce ANY > export: to AS20718 announce ANY > export: to AS20607 announce ANY > export: to AS20760 announce ANY > export: to AS24830 announce ANY > export: to AS21181 announce ANY > export: to AS15919 announce ANY > export: to AS25267 announce ANY > admin-c: EL729-RIPE > tech-c: BTT2-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > ********************************************** Noticia legal Este mensaje electrónico contiene información de BT Ignite España S.A.U. que es privada y confidencial, siendo para el uso exclusivo de la persona (s) o entidades arriba mencionadas. Si usted no es el destinatario señalado, le informamos que cualquier divulgación, copia, distribución o uso de los contenidos está prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido lo antes posible. Gracias.

1 0

AW: Hierarchical authorisation failed, request forwarded to maint aine r ???
by Marcus.Ruchti＠colt.de 14 Oct '02

14 Oct '02

yes, I 've made the same experiences! 2 route objects, 2 different AS, same precision (/22). In the the RIPE DB are some of these examples... Marcus Ruchti -----Ursprüngliche Nachricht----- Von: Gert Doering [mailto:gert@space.net] Gesendet am: Montag, 14. Oktober 2002 10:38 An: Shane Kerr Cc: Ruchti, Marcus; db-wg(a)ripe.net Betreff: Re: Hierarchical authorisation failed, request forwarded to maintaine r ??? Hi, On Mon, Oct 14, 2002 at 10:23:14AM +0200, Shane Kerr wrote: > Most objects are uniquely identified by the first attribute, or > "route:" in this case. However, you must include the "origin:" > attribute for a route object. So this is: > > route: 143.58.120.0/22 > origin: AS3320 > > The object you are trying to create will be: > > route: 143.58.120.0/22 > origin: AS8220 Shane, your explanation is confusing me. There are other examples with "same route, different origin AS" in the RIPE-DB (check 194.97.0.0/16), which is sometimes necessary while migrating a network to a new origin AS. So the database should permit entry of this *new* object, instead of checking for modification permission on the *existing* object. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 48282 (47686) SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

1 0

Mailing List Software Migration
by RIPE NCC WebMaster 10 Oct '02

10 Oct '02

Dear Mailing List Subscriber, The RIPE NCC will change its mailing list software from "majordomo" to "mailman" on 17 October 2002. The new mailing list software will give users more options to manage their subscriptions to the RIPE and RIPE NCC mailing lists. Additionally, this change is being made to ensure stability and continuity of mailing list management and archiving. The new mailing list software will give users a number of options using a web interface: - Subscribing and Unsubscribing to mailing lists - Reviewing general information about the mailing lists - Viewing subscriptions to mailing lists - Temporarily disabling mail delivery - Choosing between regular and digests of mailing list postings - Acknowledgements to postings The web interface will be located at the following URL: http://www.ripe.net/mailman/ As well as using the web interface, mailing list users can manage their subscription and retrieve information by using an e-mail client. Further details on this are available at the above URL. Please note that if mailing list users are already subscribed to one or more mailing lists, they do not have to take any action. Messages can still be sent to the regular mailing lists addresses and subscriptions will not have to be re-confirmed. If you have any questions about this migration, please feel free to send an e-mail to <webmaster(a)ripe.net> Kind Regards, Jeroen Bet RIPE NCC Mailing List Moderation

1 0

RIPE Whois Server version 3.1.1
by RIPE Database Administration 09 Oct '02

09 Oct '02

Dear Colleagues, [ Apologies for multiple messages. ] The RIPE NCC is pleased to announce the release of Version 3.1.1 of the RIPE Whois server. This software is compliant with both RPSL (RFC-2622) and RPS-Security (RFC-2725). This release adds several user-visible improvements: - MD5-PW authentication added. - IPv6 status changed to comply with new RIPE policy. Detailed release notes can be found at the following URL: ftp://ftp.ripe.net/ripe/dbase/software/RELEASE-NOTES-3.1.1 You can download this release by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.1.1.tar.gz If you do not intend to use the cross-reference files or prefer to build them yourself via "make docs", you can download the source without these files by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.1.1-nocxref.tar.gz A diff for the 3.1.1 "nocxref" version is also available, if you already have 3.1.0 and would prefer to patch that version instead, at the following URL: ftp://ftp.ripe.net/ripe/dbase/software/patch-ripe-dbase-3.1.0-nocxref-3.1.1… The client has been updated, with a minor performance increase: ftp://ftp.ripe.net/tools/ripe-whois-3.1.1.tar.gz The Object Parsing Library (OPL) standalone source has also been updated, and is identical to the library used with the release. In the future, we will be releasing the OPL at the same time as the RIPE Whois server to keep them synchronised: ftp://ftp.ripe.net/ripe/dbase/software/RPSL-OL-3.1.1.tar.gz If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net> -- Shane Kerr RIPE NCC

3 6