> On 13 Mar 2026, at 13:04, Edward Shryane <[email protected]> wrote:
>
> Dear Jeroen,
>
>> On 11 Mar 2026, at 09:44, Jeroen Massar via db-wg <[email protected]> wrote:
>>
>> Hola all,
>>
>> Hanks message did make me think about something:
>>
>> Why do RPSL objects not have a LIR identifier so that one can easily whois
>> an object and see to which LIR it belongs to; as then a reverse search could
>> be done on the LIR ID.
>>
>
> The Reg ID is intended as an internal identifier between the RIPE NCC and the
> LIR, not for a RIPE Database user to identify an LIR organisation.
>
> An LIR can find both their own Reg ID and Org ID on the Account Details page
> in the LIR Portal.
They are also listed on the website:
https://www.ripe.net/membership/member-support/list-of-members/nl/surf/ =>
nl.surf
https://www.ripe.net/membership/member-support/list-of-members/ch/massar/ =>
ch.massar
https://www.ripe.net/membership/member-support/list-of-members/nl/ripencc-cs/
=> nl.ripencc-cs
https://www.ripe.net/membership/member-support/list-of-members/nl/ripencc-ops/
=> nl.ripencc-ops
https://www.ripe.net/membership/member-support/list-of-members/nl/ripencc-ts/
=> nl.ripencc-ts
https://www.ripe.net/membership/member-support/list-of-members/nl/coloclue/ =>
nl.coloclue
etc. Thus these are publically exposed. And for instance bgp.tools gives a
handy overview:
https://bgp.tools/rir-owner/ch.massar
https://bgp.tools/rir-owner/nl.coloclue
if there are objects related to it. (No clue what Benjojo's magic there is, but
it is handy ;) )
>> We do have the 'org' and related 'organisation' objects but these do not
>> directly map to a LIR.
>
> The unique identifier of any organisation in the RIPE database is the
> organisation: attribute in the organisation object type, and the org-type:
> identifies the organisation as an LIR (or OTHER).
But the "organisation" object does not map directly to LIR.
Thus maybe the correct place is just in the organisation object.
Though, it depends on the purpose of why we would add it; knowing which LIR an
object exists for would be a good thing, and I do not think all objects have an
org reference either, though inetnum/inet6num & amt-num likely yes, thus adding
it to organisation would help a lot already to normalize that.
> A reverse search can be done on org: references to that organisation object.
>
> Also, we will also shortly introduce the Registration Number ("reg-nr:")
> attribute to uniquely identify an organisation (see NWI-21).
But that maps to company, not to the LIR ID.
[..]
>> I would not be surprised that something like this was discussed when the
>> 'organisation' object was introduced, but could not easily find something in
>> $searchengine.
>
> I also didn't find any discussion to publish the Reg ID in the RIPE database
> in the archive:
> https://mailman.ripe.net/archives/list/[email protected]/
https://mailman.ripe.net/archives/list/[email protected]/thread/77NQDFTMHLIOLEHUU2VQSGIS6DKHEIFC/
as per link from
https://www.ripe.net/about-us/news/ripe-ncc-member-update-november-2025/
> Does the working group see value in adding the Reg ID as an additional
> identifier of LIR organisations to the RIPE database?
Personally I would say yes, it would definitely help in research into what
belongs to what and finding patterns there and possibly finding a better
contact for a problem; similar reasoning to the reg-nr.
But, it will be a bit of an effort possibly for the RIPE NCC team adding the
feature and validating that the information is correct. Thus a discussion,
which is why I asked it in a separate thread, would be a good thing indeed ;)
Regards,
Jeroen
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
