<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" dir="auto">
<span style="color: rgb(33, 33, 33);"></span>Dear all,</div>
<div id="ms-outlook-mobile-body-separator-line" data-applydefaultfontstyles="true" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;" dir="auto">
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">There are two separate questions here, and they should not be collapsed into one.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">First, writing assistance does not determine whether a contribution is valid. The participant remains responsible
for the argument submitted. Concision and evidence are reasonable expectations for everyone, but the tools used to prepare a message are a matter of individual choice, not a basis for excluding it.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Second, showing that hierarchical naming offers an improvement does not automatically prove that it should become
mandatory policy. “Better than today” is not the end of the analysis. The community must still test necessity, proportionality, scope, alternatives, and the authority being granted to the registry.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Operational experience is valuable evidence, but it is not a mandate to define consensus or dismiss non-operators.
Likewise, repeated objections should not gain weight merely through volume, but neither should repeated support from familiar participants.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">The co-chairs should identify the distinct arguments and assess them on their merits. Rough consensus is not
a headcount, a reputation contest, or permission for the established group to declare the discussion finished.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Participation may provide expertise, support, warning, or objection. It does not create authority over everyone
else.</span></p>
<p><span style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Regards,<br>
Tshepo </span></p>
<div dir="auto" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(33, 33, 33);">
<br>
</div>
</div>
</body>
</html>