Hi Daniel,
On 5 Sep 2024, at 13:26, Daniel Suchy via db-wg <db-wg@ripe.net> wrote:
Hello, in full changelog I noticed another change, which is not mentioned here: https://github.com/RIPE-NCC/whois/pull/1492/commits
I summarised the main functional changes in my announcement as there are often a lot of small changes, that may not be of interest to a wide audience. The full list of changes is linked from the release notes, including adding validation of the length of an email address : https://github.com/RIPE-NCC/whois/blob/master/changes.txt Differences between releases can also be examined in GitHub: https://github.com/RIPE-NCC/whois/releases
- why is implemented limitation to email lenght to 80 characters, when RFC5341 [1] clearly defines maximum total length of a domain name or number is 255 octets and local-part to 64 octets in sections 4.5.3.1.1 and 4.5.3.1.2?
We now limit the email address to 80 characters to fit into the database index table, which fixed a bug. Previously, if a user submitted a too-long email address, it would fail with a generic "internal error" because the SQL INSERT statement failed. Now, the update will fail with a syntax error on the email address.
I don't think implementing limitations adnd ignoring relevant RFCs here isn't a good approach at all, it can generate unnecessary problems.
Does the 80 character limit cause any problems? We fixed a bug for an issue that occurred once, for an address which seemed to be auto-generated. The average length of all email addresses currently in the RIPE database is 21 characters. If the current limit is too restrictive for the DB-WG then we will increase it to the limit defined in the RFC.
- Daniel
Regards Ed Shryane RIPE NCC