<html xmlns:v="urn:schemas-microsoft-com:vml" 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;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=en-MU link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Dear DGWG members,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We have worked on a fix to correct the malformed 'changed' attributes and we have implemented validation of the e-mail address to prevent similar problems in the AFRINIC database.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This issue will be resolved after the next scheduled deployment, on Tuesday 27 July 2021<span lang=EN-US>. Y</span>ou may <span lang=EN-US>it </span>follow on <a href="https://status.afrinic.net/" target="_blank">https://status.afrinic.net/</a>.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>Best r</span>egards,<o:p></o:p></p><p class=MsoNormal>Yogesh Chadee<o:p></o:p></p><p class=MsoNormal><span lang=en-MU style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Yogesh Chadee <yogesh@afrinic.net> <br><b>Sent:</b> Monday, 19 July 2021 18:17<br><b>To:</b> dbwg@afrinic.net<br><b>Subject:</b> Re: [DBWG] Malformed changed: fields in route: objects<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=en-MU>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>Thank you very much for reporting this. The software engineering team will look into this bug immediately and correct it.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>Kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>Yogesh Chadee<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=en-MU>From: </span></b><span lang=en-MU><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<o:p></o:p></span></p></div><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>I am attempting to parse the contents of the changed: fields within<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>the route and route6 objects that are present in the redacted form of<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>the AFRINIC WHOIS data base that is available via FTP. (The unredacted<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>form of the data base is still being pointlessly withiheld from legitimate<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>researchers such as myself, so I am obliged to work only with the redacted<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>form of the data base.)<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>The general form of any given changed: field within the data base appears<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>to be:<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU> changed: email-address date<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>This simple format would be easy enough to parse with consistant results<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>if it were not for the two facts that (1) some few nitwits were allowed<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>to enter email addresses of the form:<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU> email-address<<a href="mailto:email-address">mailto:email-address</a>><o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>combined with that fact that (2) AFRINIC's redaction process, via which<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>the redacted version of the data base is gnerated and placed onto AFRINIC's<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>FTP server apparently becomes confused by the above style of malformed<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>email addresses, with the result being that the content of (malformed)<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>changed: fields become truncated at the @ (at-sign) that appears within<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>the <<a href="mailto:XXX">mailto:XXX</a>> part of these malformed changed: lines. Thus, within<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>the redacted WHOIS data base, the lines in question end up looking like<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>this:<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU> changed: <a href="mailto:***@viva.co.zm%3cmailto:asif">***@viva.co.zm<mailto:asif</a><o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>Obviously, it is not pssoble to obtain the relevant date stamp in these<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>cases, because it has been improperly redacted out by AFRINIC's WHOIS<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>redaction process.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>The affected IPv4 route objects are as follows:<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.124.0/22 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.120.0/23 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.122.0/23 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.124.0/23 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.126.0/23 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.120.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.121.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.122.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.123.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.124.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.125.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.126.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.140.127.0/24 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>routesum: 102.223.168.0/22 [328581] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>In the case of IPv6 routes, only the following single IPv6 route object is<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>affected by this problem:<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>route6sum: 2c0f:ec88::/32 [328328] - Missing or malformed changed: field<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>It would be helpful if the hostmaster would correct the form and content of<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>all of the above malformed route objects.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>It would also be helpful if the hostmaster would take whatever steps may<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>be necessary in order to insure that this type of prooblem does not creap<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>back into the data base in the future, i.e. by pre-filtering the email<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>addresses that will ultimately be placed into changed: lines in the data<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>base and by pre-checking them for reasonable and consistant syntactic form.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>rfg<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-MU>_______________________________________________<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU>DBWG mailing list<o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><a href="mailto:DBWG@afrinic.net">DBWG@afrinic.net</a><o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><a href="https://lists.afrinic.net/mailman/listinfo/dbwg">https://lists.afrinic.net/mailman/listinfo/dbwg</a><o:p></o:p></span></p><p class=MsoNormal><span lang=en-MU><o:p> </o:p></span></p></div></body></html>