Hi guys When you constantly tweak a 30 year old data model there are limits to what you can achieve. There is an answer, but no one will go there...
Cheers Denis On Fri, 6 Dec 2024, 15:27 Cynthia Revström via db-wg, <[email protected]> wrote: > Hi Ed, > > I feel like this was mostly settled by NWI-4 in which iirc the conclusion > was that it wasn't really worth it for the small number of cases in which > it would be applicable. > > I guess that was mostly about the tuple implementation though. I suppose > adding a "end-user-org" field or something along those lines wouldn't > really have any negative impact if that solves the problem. > > -Cynthia > > > On Fri, 6 Dec 2024, 13:32 Edward Shryane, <[email protected]> wrote: > >> Hello Clement, >> >> > On 6 Dec 2024, at 11:53, Clement Cavadore <[email protected]> wrote: >> > >> > Dear all, >> > >> > I am trying to make my first ALLOCATED-ASSIGNED PA block for one of my >> > end user. It seems that I cannot change the org: line, as it's also the >> > same inetnum than my own LIR. >> > >> > Is there any way to be able to associate another org object to the >> > whole inetnum, without loosing the link with the parent LIR of that >> > block ? >> > >> > Thanks in advance for your help ! >> >> The ALLOCATED-ASSIGNED PA status is meant to combine the "ALLOCATED PA" >> and "ASSIGNED PA" status values. According to the policy proposal 2023-04 >> (now RIPE-826) : >> >> "AGGREGATED-BY-LIR: This address space has been assigned to different >> parts of the issuing LIR infrastructure or to End Users for use with >> services provided by the issuing LIR. The purpose and the contact details >> must be consistent throughout the whole assignment. It cannot be kept when >> terminating services provided by the LIR." >> >> The "org:" reference must remain the LIR. Also, only a single "org:" >> reference is allowed on all resource object types (so both orgs cannot be >> registered). >> >> To the DB-WG : do we need to accommodate this use case where an end user >> assignment is the same size as the parent allocation, and register *both* >> organisations? >> >> Regards, >> Ed Shryane >> RIPE NCC >> >> >> >> >> ----- >> 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/ >> > ----- > 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/
----- 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/
