[ncc-services-wg] LIR association with number resources

On 4 Aug 2012, at 19:25, Nick Hilliard <nick at netability.ie> wrote:

> It's certainly been discussed before without any particular conclusion, but
> I didn't gather from the various WG discussions - either at RIPE meetings
> or on the mailing lists - that it stalled due to privacy concerns.  Do you
> have a reference for this?

First thing I could find is a message by David Freedman from July last year:
http://www.ripe.net/ripe/mail/archives/db-wg/2011-July/003745.html

>> 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 th=
>> e 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 an=
>> d as per above)
>>   *   PI Assignments (not found at all)
>>   *   Autonomous systems (not found at all?)
>> 
>> The privacy issues concerning publishing are currently being investigated b=
>> y the NCC and a number of people have expressed concern about revealing com=
>> mercial relationships,
>> especially with regards to revealing the sponsoring LIR for a particular en=
>> d-user resource (though, I did make the point that you can ask the NCC a di=
>> rect 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/ncc-services-wg/attachments/20120812/e96db636/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2355 bytes
Desc: not available
URL: </ripe/mail/archives/ncc-services-wg/attachments/20120812/e96db636/attachment.p7s>