This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
Questions: RIPE DB / Handles with no numbers / LONGACK
- Previous message (by thread): Questions: RIPE DB / Handles with no numbers / LONGACK
- Next message (by thread): 1. Draft, proposed agenda DB-WG meeting RIPE-34, Thu.,Sept.23'99
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
RIPE Database Administration
ripe-dbm at ripe.net
Fri Sep 17 15:06:07 CEST 1999
Dear Hans-Joachim, Nacamar AS Guardian <guardian at nacamar.de> writes: * * Hello, * * I haves questions about the current operation of the RIPE-Database: * * >From ripe-157: * > RIPE NIC-handle: <Initials><0-999>-RIPE * * There are person-objects in the RIPE-Database that do not * conform to this format, eg. AA-RIPE and MB10000-RIPE. Since we have more than 10000 person objects with MB initials, we allow numbers grater than 9999 in the NIC handles. * * The numbers greater than 999 are no problem, * but Handles without number are a nuissance, * e.g. when testing for a valid format in a field... * * So, are Handles without a number offically allowed ? * Yes, they are allowed. If you ask for a specific NIC handle without a number it will give you that (if it is available), however if you want the software to assign a NIC handle automatically, it assigns a NIC handle always with a number. * * > If you require a detailed acknowledgement, put the * > keyword "LONGACK" in the `Subject' line of your e-mail. * * We have a script for sending mail to auto-dbm at ripe.net, * and it always uses LONGACK - so the answer-mails * should all look alike. * But as a result, we get mails in different formats, e.g. short: * >>> * From: RIPE Database Management <ripe-dbm at ripe.net> * To: Nacamar Guardian <gurt at gargoyle.nacamar.de> * Subject: SUCCEEDED: LONGACK * .. * The following objects were processed. * * New OK: [person] IB179-RIPE (Ivonne Bankwitz) * <<< * * Sometimes the reply ist "long", it also quotes the content of our mail: * >>> * Date: 17 Sep 1999 08:12:10 -0000 * From: RIPE Database Management <ripe-dbm at ripe.net> * To: Nacamar Guardian <gurt at gargoyle.nacamar.de> * Subject: SUCCEEDED: LONGACK * .. * The following objects were processed. * * New OK: [person] IB179-RIPE (Ivonne Bankwitz) * * person: Ivonne Bankwitz * ... * <<< * * I have no idea, why, and on what condition the database * returns the "short" or the "full" answer. * Can someone tell ? * If there is no warning, than short format is used, but if there is a warning (such as "current date added to changed field") the software returns the acknowledgement along with the warnings and the object created or updated. If you have any more questions, please don't hesitate to contact <ripe-dbm at ripe.net>. Regards, Engin Gunduz ____________________________ RIPE Database Administration. * * Best Regards, * HaJo Gurt * * ------------------------------------------------------------------- * Nacamar Network Administration NACAMAR Data Communications * guardian at nacamar.net Robert-Bosch-Str. 32 * D-63303 Dreieich * Hans-Joachim Gurt Germany * gurt at nacamar.de http://www.nacamar.de * * ***** NEUE Telefon+Faxnummern: ***** NEW Phone+Faxnumbers: ***** * Voice: +49 6103 916 0 Fax: +49 6103 916 222 * ------------------------------------------------------------------- * Documentation is like sex: when it is good, it is very, very good; * and when it is bad, it is better than nothing. - Dick Brandon * * * --============_-1274641660==_============-- *
- Previous message (by thread): Questions: RIPE DB / Handles with no numbers / LONGACK
- Next message (by thread): 1. Draft, proposed agenda DB-WG meeting RIPE-34, Thu.,Sept.23'99
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]