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-wg] Displaying RegID for all resources
- Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
- Next message (by thread): [db-wg] Displaying RegID for all resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Freedman
david.freedman at uk.clara.net
Tue Nov 8 10:45:41 CET 2011
After the feedback from the DB-WG Meeting in Vienna last week, I'd like to bring this back to the list. I'd like to see the RegID (or equivalent) displayed for all resources in the database, this will help us identify the holder of: * PA Allocations (currently found in alloclist, currently attached Org-ID) * PA Assignments (only found through less specific aggregate inetnum and as per above) * PI Assignments (not found at all) * Autonomous systems (not found at all?) The privacy issues concerning publishing are currently being investigated by the NCC and a number of people have expressed concern about revealing commercial relationships, especially with regards to revealing the sponsoring LIR for a particular end-user resource (though, I did make the point that you can ask the NCC a direct question about who the sponsoring LIR is and lack of policy means they reveal this). The technical issue concerning publishing , is that using the RegID may not be the best idea, the NCC say "It is for internal use" (but it is the only thing I see in my LIR portal?), why not use the OrgID (but this doesn't relate to the RegID , how do I link this to a bone fide LIR?) , one issue with using the regID over the orgID may be that the regID would simply be represented in the database as a string , since there is no related object to tie it to (which may be an undesirable outcome). Dave. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20111108/5b3a2b6d/attachment.html>
- Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
- Next message (by thread): [db-wg] Displaying RegID for all resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]