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/db-wg@ripe.net/

[db-wg] Whois Release 1.112

Previous message (by thread): [db-wg] Whois Release 1.112
Next message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ben Cartwright-Cox ripencc at benjojo.co.uk
Tue May 21 11:06:30 CEST 2024

Thanks! I've managed to set this now, For what it's worth, it is still
not possible to set this from the "Update Object" button from the "My
Resources" flow, but if I use the "Ripe Database" button and search
for my object, press update object from there, then I can do it :)

On Tue, 21 May 2024 at 09:25, Edward Shryane <eshryane at ripe.net> wrote:
>
> Hello Ben,
>
> > On 20 May 2024, at 18:37, Edward Shryane <eshryane at ripe.net> wrote:
> >
> > ...
> > Apologies, this is a bug. You should be allowed to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page, but ALLOCATED-ASSIGNED PA is missing.
> >
>
> We've now deployed a fix for this bug, it's now possible to change between ALLOCATED PA and ALLOCATED-ASSIGNED PA on the modify inetnum page.
>
> Apologies for any inconvenience.
>
> Regards
> Ed Shryane
> RIPE NCC
>
>

Previous message (by thread): [db-wg] Whois Release 1.112
Next message (by thread): [db-wg] Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]