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/[email protected]/
DB Minutes
- Previous message (by thread): DB Minutes
- Next message (by thread): DB Minutes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
woeber at cc.univie.ac.at
Fri Oct 1 11:04:47 CET 1993
>I propose to add the text below to the DB minutes: Good idea. I think the example 2 should be corrected. See below. ---- |In case two or more guardians want to set an attribute |which can only have one value, the current state of the |attribute will not be changed and all guardians concerned will |be notified. | |Example: | |The aut-sys attribute of network 193.193.193.0 in the database is AS193. |AS4711 adds this network to his guardian file. At the next database cleanup |all guardian files will be examined. | | 1) if the AS193 guardian file still contains 193.193.193.0 a conflict | exists and the cuurent database state prevails: AS193 will remain | | 2) if 193.193.193.0 has been removed from the AS193 guardian file | no conflict exists and AS193 will be replaced by AS4711 ^^^^^^ |Similarly the aut-sys attribute will remain undefined if it is undefined |and two guardians add it simultaneouly. | |Since the cleanup runs every 24 hours guardians involved in a change should |coordinate their changes such that they are done in the same 24h period. | ---- >clear? Yes, Sir! :-) Wilfried.
- Previous message (by thread): DB Minutes
- Next message (by thread): DB Minutes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]