- db-wg - mailman.ripe.net

Whois Release 1.112.1
by Edward Shryane 24 Jun '24

24 Jun '24

Dear colleagues, RIPE Database release 1.112.1 has been deployed to the PRODUCTION environment just now. This is a bugfix release to help mitigate the ongoing production issue caused by many updates containing objects with an unusual amount of references. This is the only change from release 1.112. We will also apply this change to the upcoming 1.113 release (due next Monday, 1st July). We will continue to monitor for any more incidents, and will publish a full post-mortem later. Regards Ed Shryane RIPE NCC

1 0

RPSL for for foreigh IPv6 space
by Randy Bush 23 Jun '24

23 Jun '24

hi, All of RGnet's address space, mostly legacy, is in the RIPE whois, with RPKI etc. Except ... RGnet has three IPv6 /48s from NTT. Cogent filters BGP based on RPSL, and wants the RPSL for our ASs to be in the appropriate RPSL route6: objects, each with the appropriate AS. This is pretty old-fashioned and reasonable. Do we figure out how to register the route6: objects in NTT and presume Cogent will pick them up across IRR instances? Do we try some hack to violate the RIPE database's pristine authority model? Do we give up on this silly IPv6 stuff? [ just kidding, gert :) ] Surely other have been here before us. randy

3 2

RIPE Policy document updated “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” (ripe-826)
by Angela Dall'Ara 20 Jun '24

20 Jun '24

Dear Colleagues, The RIPE policy “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region” has been updated to align with the implementation of NWI4, done in Whois release 1.112, which added the option to change the status of an IPv4 allocation object in the RIPE Database from “ALLOCATED PA” to “ALLOCATED-ASSIGNED PA” when the whole address space is assigned to the LIR infrastructure or for use by an End User with services provided by the issuing LIR. The new document is called ripe-826 and is available at: https://www.ripe.net/publications/docs/ripe-826/ Please note that also the following has been updated: 1) In the Abstract: The link to the webpage where to find information on the Address Policy WG from https://www.ripe.net/participate/ripe/wg/ap to https://www.ripe.net/community/wg/active-wg/ap/ 2) In 1.1 Scope: The link to the webpage listing the RIPE community’s policies: from https://www.ripe.net/ripe-policies to https://www.ripe.net/publications/docs/ripe-policies/ 3) In 5.3 Sub-Allocations The option to ask for a conversion of PI to PA via LIR Portal has been added. Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0

So what happened last night to the DB?
by Hank Nussbacher 17 Jun '24

17 Jun '24

3 2

Re: [db-wg] So what happened last night to the DB?
by Lutz Donnerhacke 17 Jun '24

17 Jun '24

> I have thought about doing it so, as I was also included as the > maintainers of the object. The real question is: why did blake66 made > such an object ? And how could we prevent something alike to happen > again (not an easy question -- maybe limiting the amount of mnt-by ?) Especially the DB should not process backscatter messages from MAILER-DAEMON.

1 0

Proposal to allow non-ASCII characters in "org-name:", "person:" and "role:" attributes
by Edward Shryane 28 May '24

28 May '24

Dear colleagues, Currently the RIPE database only allows a subset of ASCII characters in the "org-name:", "person:" and "role:" attributes, for a few reasons including: * These attributes are also a look-up key and the Whois protocol does not allow specifying character sets in queries. * RPSL names are ASCII according to RFC2622 * Using a normalised name makes the object easier to query * Reading a normalised name is easier to interpret However there are some drawbacks to forcing names to only use a subset of ASCII characters: * Organisations, roles and persons cannot use their actual name if it includes characters outside this subset. * Normalisation is not standard, but is an interpretation done by each maintainer, e.g. characters could be excluded or converted in different ways. Since we support the Latin-1 character set in the RIPE database, I propose we also allow non-ASCII Latin-1 characters in these attributes. Querying for a name can be done either using the latin-1 characters (proposed) or a normalised, ASCII representation (currently). The normalised version will be generated by Whois and stored in a database index for querying. The primary key will also be generated from the normalised version. Please let me know your feedback. Regards Ed Shryane RIPE NCC --- Whois attribute verbose description (copied from the help text). org-name -------- Specifies the name of the organisation that this organisation object represents in the RIPE Database. This is an ASCII-only text attribute. The restriction is because this attribute is a look-up key and the whois protocol does not allow specifying character sets in queries. The user can put the name of the organisation in non-ASCII character sets in the "descr:" attribute if required. A list of 1 to 30 words separated by white space. A word is made up of ASCII alphanumeric characters and additionally: ][)(._"*@,&:!'`+/- A word may have up to 64 characters and is not case sensitive. Each word can have any combination of the above characters with no restriction on the start or end of a word. person ------ Specifies the full name of an administrative, technical or zone contact person for other objects in the database. It should contain 2 to 10 words. A word is made up of ASCII alphanumeric characters and additionally: .`'_- The first word should begin with a letter. At least one other word should also begin with a letter. Max 64 characters can be used in each word. role ---- Specifies the full name of a role entity, e.g. RIPE DBM. A list of 1 to 30 words separated by white space. A word is made up of ASCII alphanumeric characters and additionally: ][)(._"*@,&:!'`+/- A word may have up to 64 characters and is not case sensitive. Each word can have any combination of the above characters with no restriction on the start or end of a word.

9 17

Historical data on deleted objects
by Yang Yu 27 May '24

27 May '24

Hi, According to https://apps.db.ripe.net/docs/Types-of-Queries/Historical-Queries/ , historical query doesn't return data on deleted objects. This behavior makes it difficult to distinguish whether a resource was squatted on / analyze history associated with abuse on the resource. And it is not consistent with other RIR's whowas behavior. Currently on RIPE whowas UI unallocated and deleted objects look exactly the same. https://stat.ripe.net/widget/historical-whois#w.resource=as199256 Last time the discussion came up appears to be https://www.ripe.net/ripe/mail/archives/db-wg/2013-November/004195.html Can history support for deleted objects get implemented? Thanks. Yang

3 5

Preferred names in the database
by Harry Cross 22 May '24

22 May '24

Dear all (copying this to both the Diversity list and the Database list), I hope you’re having a wonderful weekend and recovering from Rome. I’d like to begin thinking about a proposal for preferred names in the database/on resources. Some may have noticed this week (and for a bit prior), I have begun going by Harri instead of Harry. At the moment there is no correct way for me to represent this in the database, as an LIR the details have to match my legal name. I may think about going through the legal processes to change this soon (albeit in the UK this is easier than a lot of places). I know a few people hold their resources under a shell company for this purpose, (e.g I could incorporate Harri Cross Limited to hold the resources and be in the database). This applies to end users who hold PI or ASNs alongside LIRs. It would be good for us to think about a way for these preferred names (and pronouns?) to be shown in the database alongside the process for changing the name of an end user. I know the preferred way a lot of people in this situation would like this to be handled is to totally mask the legal name in the database. The NCC could still validate legal names to know who they are working with - and we will need some compromise here I suspect. A complete lack of verification is of course a bad thing. I have experienced talking to the NCC when handling end users in these situations who have legally name changed and the process seems to be incredibly hard with the lack of understanding on documentation for name changes. Responses from the Registry have included “How can we be sure that <oldName> and <newName> are not identical twins?” (Which in my mind, is rather disrespectful). I also have another name change in process that is being stonewalled by a lack of understanding of documents in different jurisdictions for this. Kind Regards, Harri Sent from Outlook for iOS<https://aka.ms/o0ukef>

3 2

RIPE 88 chair selection
by David Tatlisu 21 May '24

21 May '24

Dear colleagues, This is a brief reminder that the DB WG co-chair selection will happen at the Database Working Group session on Thursday. Please have your personal Meetecho link ready. We planned a time slot to discuss the recent changes in the chair selection process, as there has been a lot of discussion between the chairs. Kind regards, David RIPE DB WG co-chair

1 0

Whois Release 1.112
by Edward Shryane 21 May '24

21 May '24

Dear colleagues, RIPE Database release 1.112 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 16th May. The 1.112 release has the following main changes: * NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432) * Set Charset Flag (#1450) * Don't allow "mnt-lower" on assignments (#1452) * Fixed Syncupdates HELP Bug (#1453) * RDAP Link Title is a String not List (#1445) * Route ROA checker (#1416) * Allow inverse query for sponsoring-org from all addresses (#1431) * Return 404 on invalid NRTMv4 notification file path (#1422) The release notes are on the website: https://rc.db.ripe.net/docs/Release-Notes/#ripe-database-release-1-112 More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/ The data in the RC environment is a dummified copy of production from 30th April. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

2 5