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/
status attribute of the inetnum object.
- Previous message (by thread): Problems with whois and auto-dbm.
- Next message (by thread): status attribute of the inetnum object.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
RIPE Database Administration
ripe-dbm at ripe.net
Thu Jul 9 21:19:18 CEST 1998
Dear Colleagues, We intend to make the status attribute of the inetnum object mandatory on Monday, 13th July next. This has been discussed and agreed previously. However, if you have software that is _unavoidably_ dependent on this attribute being optional, please contact us. The new version of the inetnum object will be: inetnum: [mandatory] [single] [primary/look-up key] netname: [mandatory] [single] [look-up key] descr: [mandatory] [multiple] [ ] country: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] rev-srv: [optional] [multiple] [ ] status: [mandatory] [single] [ ] # mandatory !!! remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] mnt-lower: [optional] [multiple] [ ] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] If you have anymore questions, please contact <ripe-dbm at ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.
- Previous message (by thread): Problems with whois and auto-dbm.
- Next message (by thread): status attribute of the inetnum object.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]