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/
[db-wg] Re: proposal for modification of irt object schema [was "Re: The New "organisation object" Proposal"]
- Previous message (by thread): [db-wg] proposal for modification of irt object schema [was "Re: The New "organisation object" Proposal"]
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ulrich Kiermayr
ulrich.kiermayr at univie.ac.at
Mon Sep 8 18:07:07 CEST 2003
Hi Engin, > Dear Colleagues, > > To be consistent with the new organisation object's schema, we'd propose > to change the schema of irt object in the following way: > - Replace "irt-nfy:" with "ref-nfy:" attribute. The syntax and > semantics do not change, only the name of the attribute > changes. > - Replace "auth:" with "mnt-ref:" attribute. Currently "auth:" > attribute in irt object is used to authorise adding references > to the irt object from other objects. Its syntax is the same > as "auth:" attribute of mntner objects. The proposed "mnt-ref:" > contains references to mntner objects, instead of directly > specifying the auth methods. Thus, the proposed change adds one > more redirection to mntner objects. Although the syntax of "mnt-ref:" > is different than that of "auth:", its functionality is the same. > > With the proposed changes, the new schema of irt object would be: > > irt: [mandatory] [single] [primary/lookup key] > remarks: [optional] [multiple] [ ] > address: [mandatory] [multiple] [ ] > phone: [optional] [multiple] [ ] > fax-no: [optional] [multiple] [ ] > e-mail: [mandatory] [multiple] [lookup key] > signature: [mandatory] [multiple] [ ] > encryption: [mandatory] [multiple] [ ] > admin-c: [mandatory] [multiple] [inverse key] > tech-c: [mandatory] [multiple] [inverse key] > mnt-ref: [mandatory] [multiple] [ ] > ref-nfy: [optional] [multiple] [inverse key] > notify: [optional] [multiple] [inverse key] > mnt-by: [mandatory] [multiple] [inverse key] > changed: [mandatory] [multiple] [ ] > source: [mandatory] [single] [ ] Yes, looks good :-) and I think if it works out it is expandable ... I Resent your message to the tf-csirt mailinglist, to get comments from the CSIRT community as well, because they are the ones using that most atm. If we'd even come up with a clever way to reformat those without to much intervention, like autocreating the appropriate mntner from the data in the irt-object, I see no problem changing it. lG uk -- ------------------------------------------------------------------------ Ulrich Kiermayr Zentraler Informatikdienst der Universitaet Wien Network Security Universitaetsstrasse 7, 1010 Wien, Austria ------------------------------------------------------------------------ eMail: ulrich.kiermayr at univie.ac.at Tel: (+43 1) 4277 / 14104 Hotline: security.zid at univie.ac.at Fax: (+43 1) 4277 / 9140 Web: http://www.univie.ac.at/zid/security.html ------------------------------------------------------------------------ GPG Key fingerprint = BF0D 5749 4DC1 ED74 AB67 7180 105F 491D A8D7 64D8
- Previous message (by thread): [db-wg] proposal for modification of irt object schema [was "Re: The New "organisation object" Proposal"]
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]