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/
draft minutes of DB-WG meeting at RIPE 25
- Previous message (by thread): draft minutes of DB-WG meeting at RIPE 25
- Next message (by thread): draft minutes of DB-WG meeting at RIPE 25
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
davidk at isi.edu
davidk at isi.edu
Wed Oct 9 20:49:11 CEST 1996
Hi Wilfried, > Wilfried Woeber, UniVie/ACOnet writes : > > - persons (multiple) with and without nic-hdls. > > The various checks, when they get implemented eventually, should at least > generate warnings, both at the time of an update and on a regular basis. One note on this one: The new software doesn't create a new object anymore when adding a NIC handle to an existing object. It will only do this when there are other differences between the new and old object then the 'changed:' and the added NIC handle attribute. > Daniel proposed to add that functionality toi the software itself, probably > by adding a whois -T with -v and possibly whois -T to report all objects. > This is is already available for listing the schema for an individual object. Wasn't this proposal on the wish list for a long, long time (and even accepted by the database working group as a good thing) ?!? davidk> List of current proposals: davidk> davidk> 5) whois -tv > Action (11) on RIPE NCC (Ambrose Magee), > To change the DB-SW to obsolete the advisory: attribute in inetnum: objects. ^^^^^^^^ No further comments ... ;-) David K. ---
- Previous message (by thread): draft minutes of DB-WG meeting at RIPE 25
- Next message (by thread): draft minutes of DB-WG meeting at RIPE 25
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]