<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=en-MU link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you very much for reporting this. The software engineering team will look into this bug immediately and correct it.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kind regards,</p><p class=MsoNormal>Yogesh Chadee</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:rfg@tristatelogic.com">Ronald F. Guilmette</a><br><b>Sent: </b>Sunday, 11 July 2021 07:23<br><b>To: </b><a href="mailto:hostmaster@afrinic.net">hostmaster@afrinic.net</a>; <a href="mailto:dbwg@afrinic.net">dbwg@afrinic.net</a><br><b>Subject: </b>[DBWG] Malformed changed: fields in route: objects</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am attempting to parse the contents of the changed: fields within</p><p class=MsoNormal>the route and route6 objects that are present in the redacted form of</p><p class=MsoNormal>the AFRINIC WHOIS data base that is available via FTP. (The unredacted</p><p class=MsoNormal>form of the data base is still being pointlessly withiheld from legitimate</p><p class=MsoNormal>researchers such as myself, so I am obliged to work only with the redacted</p><p class=MsoNormal>form of the data base.)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The general form of any given changed: field within the data base appears</p><p class=MsoNormal>to be:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> changed: email-address date</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This simple format would be easy enough to parse with consistant results</p><p class=MsoNormal>if it were not for the two facts that (1) some few nitwits were allowed</p><p class=MsoNormal>to enter email addresses of the form:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> email-address<mailto:email-address></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>combined with that fact that (2) AFRINIC's redaction process, via which</p><p class=MsoNormal>the redacted version of the data base is gnerated and placed onto AFRINIC's</p><p class=MsoNormal>FTP server apparently becomes confused by the above style of malformed</p><p class=MsoNormal>email addresses, with the result being that the content of (malformed)</p><p class=MsoNormal>changed: fields become truncated at the @ (at-sign) that appears within</p><p class=MsoNormal>the <mailto:XXX> part of these malformed changed: lines. Thus, within</p><p class=MsoNormal>the redacted WHOIS data base, the lines in question end up looking like</p><p class=MsoNormal>this:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> changed: ***@viva.co.zm<mailto:asif</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Obviously, it is not pssoble to obtain the relevant date stamp in these</p><p class=MsoNormal>cases, because it has been improperly redacted out by AFRINIC's WHOIS</p><p class=MsoNormal>redaction process.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The affected IPv4 route objects are as follows:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>routesum: 102.140.124.0/22 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.120.0/23 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.122.0/23 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.124.0/23 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.126.0/23 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.120.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.121.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.122.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.123.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.124.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.125.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.126.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.140.127.0/24 [328328] - Missing or malformed changed: field</p><p class=MsoNormal>routesum: 102.223.168.0/22 [328581] - Missing or malformed changed: field</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the case of IPv6 routes, only the following single IPv6 route object is</p><p class=MsoNormal>affected by this problem:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>route6sum: 2c0f:ec88::/32 [328328] - Missing or malformed changed: field</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It would be helpful if the hostmaster would correct the form and content of</p><p class=MsoNormal>all of the above malformed route objects.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It would also be helpful if the hostmaster would take whatever steps may</p><p class=MsoNormal>be necessary in order to insure that this type of prooblem does not creap</p><p class=MsoNormal>back into the data base in the future, i.e. by pre-filtering the email</p><p class=MsoNormal>addresses that will ultimately be placed into changed: lines in the data</p><p class=MsoNormal>base and by pre-checking them for reasonable and consistant syntactic form.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,</p><p class=MsoNormal>rfg</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>DBWG mailing list</p><p class=MsoNormal>DBWG@afrinic.net</p><p class=MsoNormal>https://lists.afrinic.net/mailman/listinfo/dbwg</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>