I think I still support this proposal if it would be realistic to implement without breaking too many things. Like what would the impact on RDAP be for example? I guess what I am saying is that I want to see a proper impact analysis before I can decide if I support it or not.
-Cynthia On Wed, Jul 19, 2023 at 8:01 PM denis walker via db-wg <[email protected]> wrote: > > Colleagues > > On Wed, 24 May 2023 at 08:52, Wessel Sandkuijl via db-wg <[email protected]> > wrote: > > > > Hi, > > > > I've reviewed Ed's impact analysis for NWI-4 and his proposal to add a new > > status value "ALLOCATED-ASSIGNED PA". This will not cover all use cases and > > it's use will most likely be limited as most people are used to the > > "ALLOCATED PA" versus "ASSIGNED PA" status values. > > > > I would highly prefer the earlier alternative proposal to use a tuple > > (using both prefix and status) so no new status value is introduced to the > > RIPE database. > > As Wessel pointed out this was one of the earlier proposals and it did > have some support at the time. It is technically more challenging and > has implications on queries and query data output. How do you feel > about such a change? > > cheers > denis > co-chair DB-WG > > > > > > Can this be moved forward? > > > > Regards, > > > > Wessel Sandkuijl > > > > > > -- > > > > To unsubscribe from this mailing list, get a password reminder, or change > > your subscription options, please visit: > > https://lists.ripe.net/mailman/listinfo/db-wg > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
