<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I would add, however, the observation that a large amount of
internet traffic does not involve humans at all. Rather it is
device-to-device traffic.</p>
<p>I work with trying to test and improve the resilience of devices
to real or potential, but usually inadequately tested conditions.
Many devices wobble or simply fail when they face conditions
beyond the nice, calm networks of their developers. Those
conditions may be caused by natural conditions or otherwise.</p>
<p>I have, for example, seen how the introduction of new devices,
that may speak a slightly different (but fully RFC compliant)
version of a protocol can knock-out what were previous stable
devices on the network. One of favorite examples comes from the
days when we still had TCP/IP bakeoffs when the introduction of a
single PC using FTP Software's stack could crash any and every
instance of machines running one of the their competitor's
protocol stacks - the cause was simply that they they sent a
sequence of IP fragments with the last fragment first (which
allows the receiver to better optimize its buffer space). That's
100% RFC legitimate, but it crashed other devices.</p>
<p>Back to UA - We usually forget that anything beyond the most
basic cases will be mis- or weakly implemented and inadequately
tested - and thus potentially subject to outages due to "unusual"
network traffic.</p>
<p>I have fear that the "U" part in "UA" efforts will drive the
addition of that kind of mis- or weakly implemented UA code in
devices that almost always will not have any operational reason to
go beyond classic ASCII. Such devices may be in critical roles -
self driving vehicles, power plant controls, etc etc. (An
appropriate protective strategy for such devices might simply be
for them to silently reject and drop anything that is not ASCII
rather than trying to deal with it.)<br>
</p>
<p>I have a Tesla automobile. It is already filled with some really
badly designed and badly written code. Automobiles are already
speaking TCP/IP on automotive Ethernets that are sometimes
connected to the outside world. A typical vehicle of today may
have hundreds of processors attached-to and chatting-on those
internet networks. I fear further risks should, hypothetically,
should something like a Unicode string get onto a controller net
in a car and cause something like a brake
anti-lock/stability-control processor to go awry. (I've already
experienced what can happen when a stability control system goes
bad - it can be a shockingly terrifying experience, especially if
it happens on a crowded highway downhill curve at high speed.)
(And I am reminded of the fate of the <span class="BxUVEf ILfuVd"
lang="en"><span class="hgKElc">Mars Climate Orbiter when a
mismatch between US measurements [inches, feet] and metric
measurements caused the probe to crash.)<br>
</span></span></p>
<p>As a kid I worked with my grandfather and father repairing TVs -
ones with vacuum tubes! Those boxes were very sensitive to
less-than usual operating conditions - like being used on the same
power circuit as a refrigerator that had a motor that generated
noise onto the utility power wiring in a house. In those days
there was a joke that was quite applicable: A person goes to a
Doctor and says it hurts when I do this (and demonstrates some
activity that constitutes "this"). The Doctor's reply is: Then
stop doing that.</p>
<p>Same for UA. Perhaps the "Universal" part needs to be
de-emphasised by a recognition that there will be large parts of
our internet for which that is not necessary, could add costs,
and, worse, could create risks.<br>
</p>
<p> --karl--<br>
</p>
<div class="moz-cite-prefix">On 3/29/24 9:51 AM, Carlton Samuels via
At-Large wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOZQb9TpZNh_0yMg52XMOXrWZEKGOGmUmJdQa=CdiT_EKeN3mQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default" style="font-family:tahoma,sans-serif">A
proposition worthy of our support, especially from those of us
that are still concerned with equitable Internet access! An
insightful view of how a change in the conversation could
positively impact the lowly end user.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif">Many
thanks Roberto.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif">Carlton</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div><br>
==============================<br>
<i><font face="comic sans ms, sans-serif">Carlton A
Samuels</font></i><br>
<font face="comic sans ms, sans-serif"><i>Mobile:
876-818-1799<br>
<font color="#33CC00">Strategy, Process,
Governance, Assessment & Turnaround</font></i></font><br>
=============================</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 29 Mar 2024 at 11:23,
Roberto Gaetano via At-Large <<a
href="mailto:at-large@atlarge-lists.icann.org"
moz-do-not-send="true" class="moz-txt-link-freetext">at-large@atlarge-lists.icann.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Hi all
<div><br>
</div>
<div>I have attended the UA Days in Belgrade. I am taking
the opportunity of a delay in my flight back to drop some
notes.</div>
<div><br>
</div>
<div>The meeting was very interesting. We had a full house
in the morning, with numbers decreasing in the afternoon.
I don’t know about the online participation. Please find
the programme here: <a
href="https://uaday.rs/program/?lang=en" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://uaday.rs/program/?lang=en</a></div>
<div><br>
</div>
<div>The first panel was about multilingualism, Sally
Costerton was among the speakers. It seems that the
concept that the ultimate goal is multilingualism in the
Internet is taking speed. To be noted that Anil Kumar
Jain, UASG Chair, mentioned the four “pillars” among which
there is no mention of the role of the user community.
Interesting contribution by Leonid Todorov, arguing that
we will have a stronger push to UA readiness from places
and people that are more disadvantaged rather than from
places and people that are better aware - in an
intellectual way - about the need for equality of
opportunities in internet access.</div>
<div><br>
</div>
<div>The second panel featured some registries that have
been active in achieving results in term of UA readiness.
I was the last speaker, and brought the point of view of
the users, who are the most affected by lack of UA, making
also a couple of examples. The good news is that my
contribution was well received, the bad news is that I
made the point that the user community should play a role
- I argued that it should be the “fifth pillar” in the UA
strategy - as users can put pressure on the providers that
are not UA ready, proposing that we have a paradigm shift
from “providers will graciously become UA compliant as a
bonus for the users” to “users worldwide have the right to
demand that all users have the same Internet experience
regardless their language or script they use”. The bad
news is in the fact that I have proposed that the user
community - and At-Large at the forefront - use their
footprint in the wider community to build awareness of the
user rights and produce pressure - also in collaboration
with governments - to providers to be UA compliant. That
means a call for action for At-Large.</div>
<div><br>
</div>
<div>In summary, we need to move from being spectators,
waiting for things to happen, for the technical community
to provide solutions, for providers to deploy UA-compliant
services, to an active part of the community to demand and
obtain the same level of service for all Internet users,
regardless language, script, physical location, or other
factors.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Roberto</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
_______________________________________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">At-Large@atlarge-lists.icann.org</a><br>
<a
href="https://atlarge-lists.icann.org/mailman/listinfo/at-large"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://atlarge.icann.org</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the
processing of your personal data for purposes of subscribing
to this mailing list accordance with the ICANN Privacy Policy
(<a href="https://www.icann.org/privacy/policy"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your membership
status or configuration, including unsubscribing, setting
digest-style delivery or disabling delivery altogether (e.g.,
for a vacation), and so on.</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
At-Large mailing list
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/at-large">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a class="moz-txt-link-freetext" href="http://atlarge.icann.org">http://atlarge.icann.org</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
</body>
</html>