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] RIPE DB question
- Previous message (by thread): [db-wg] RIPE DB question
- Next message (by thread): [db-wg] RIPE DB question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitry Kiselev
dmitry at volia.net
Thu Aug 4 12:42:21 CEST 2005
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! On Thu, Aug 04, 2005 at 12:51:29PM +0400, Max Tulyev wrote: > > Can I delete aut-num object from RIPE DB if it registered by me > > (as LIR) for one of our customers and I have NO auth info refered by > > object's mnt-by field? > > I think you can't. I think too. RIPE-252, part 3.6.2 says: Only those mntners referenced by the "mnt-by:" attributes are authorised to modify or delete the object. For future delete I must keep my own mntner in all mnt-by fields for customer's objects. For inetnum it is not a big problem, its modification rarely needed (mnt-routes helps also). Completely different situation with aut-num object. Import/export fields are subject of frequent change and each customer want to do it by himself according to his routing policy. But he can't while LIR's mntner protect an ASN object. In other way, according to current IPv4 and ASN policies my customer can use resources while "original criteria are still valid". Neither LIR nor RIPE NCC can't free those resources. Any additional agreement between LIR and customer are subject of their country jurisdiction not RIPE. Even if there a contract with words "must return recources if gone" RIPE can't do anything with objects. > So if you need to keep control on objects - keep your mnt-by there. In this case customer must ask LIR to do any changes in RIPE DB. It is not a best choise, I think. - -- Dmitry Kiselev -----BEGIN PGP SIGNATURE----- iD8DBQFC8fENZaocAwQhSAQRAiX0AJ94AzEa54WauVFyBwASPBzuOMM3vQCdH7r1 2LRuKKQBa7JbwVH2V/HxFEo= =qYo1 -----END PGP SIGNATURE-----
- Previous message (by thread): [db-wg] RIPE DB question
- Next message (by thread): [db-wg] RIPE DB question
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]