<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/11/2023 6:43 am, Alexandre
Petrescu via Starlink wrote:<br>
</div>
<blockquote type="cite" cite="mid:b71d5728-5286-4dfd-bdbb-dafbb921c12a@gmail.com">
<br>
For me, the filing has a syntax error in the name (a superfluous <br>
preceding quote in "'ESIAFI II"). It is an English error. It
should be <br>
corrected. See that quote in the field 'Satellite Name' at <br>
<a href="https://www.itu.int/ITU-R/space/asreceived/Publication/DisplayPublication/53068" moz-do-not-send="true">https://www.itu.int/ITU-R/space/asreceived/Publication/DisplayPublication/53068</a><br>
<br>
</blockquote>
<p>It's not English, it's Tongan, and it's not a syntax error (nor a
typing error) either. It's what linguists call a "glottal stop"
and Tongan (like some other Polynesian languages) is awash with
it.</p>
<p>It is quite common in front of vowels at the start of a word, and
indicates that the vowel that follows is short. Examples (wink,
wink): 'Etuate (transliteration of "Edward" or 'Etuini
(transliteration of "Edwin"). <br>
</p>
<p>They also occur inside words - such as "Ha'apai".</p>
<p>The first example is the first name of the (to the best of my
knowledge) first PhD graduate in Computer Science ever from Tonga,
'Etuate Cocker. I was his supervisor, so am fairly familiar with
the complaint from referees moaning that "these guys can't spell
so their paper must have been written in a haste". Which makes me
a little sympathetic to SpaceX's near complete avoidance of the
publishing circus.</p>
<p>I've lost count of the number of times where some online form
wouldn't accept it, or where we got challenged because of some
mismatch. 'Etuate like many Tongan often leaves it out to make it
easier for everyone, however I've always used it as I'd like to
respect Tongan culture and pronunciation. BTW 'Esiafi is
pronounced E-si-ah-fi with E as in "Edward", si as in the Spanish
"yes" and fi as in "fee".</p>
<blockquote type="cite" cite="mid:b71d5728-5286-4dfd-bdbb-dafbb921c12a@gmail.com">
The frequencies: hopefully there is no syntax error there too. If
there <br>
is a superfluous zero, then the filing might actually be around
13GHz <br>
and not 130GHz. This should be asked whether they are sure about
it or not.<br>
</blockquote>
I'm sure they are sure.<br>
<blockquote type="cite" cite="mid:b71d5728-5286-4dfd-bdbb-dafbb921c12a@gmail.com">
<br>
The D-band: I am not an expert at that high freqs. The wikipedia
page <br>
tells D-band is "110 GHz to 170 GHz". But the ITU filinggoes up
to <br>
174.5GHz (if there is no syntax error in the freqs) , which is
above the <br>
limit. This should be clarified.<br>
</blockquote>
Band labeling up there is a bit approximate.<br>
<blockquote type="cite" cite="mid:b71d5728-5286-4dfd-bdbb-dafbb921c12a@gmail.com">
<br>
The orbits: not sure how to see precisely the orbit altitudes,
planes, <br>
etc. in a table manner. The reddit poster shown a table, claimed
<br>
similarity to FCC orbits, but he did not say how he built that
table. <br>
He should clarify.<br>
</blockquote>
If you look at the FCC filings by SpaceX over time, you'll notice
that the orbital parameters more than anything have changed wildly.
I wouldn't put much weight on them. <br>
<blockquote type="cite" cite="mid:b71d5728-5286-4dfd-bdbb-dafbb921c12a@gmail.com">
<br>
I think there could be a way to request clarifications about this
filing <br>
at ITU; I will look at that maybe later, everyone can. The Tonga
gov't <br>
should accept request for clarifications as well.<br>
</blockquote>
<p>I'm sure they will.</p>
--
<pre class="moz-signature" cols="72">****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
<a class="moz-txt-link-abbreviated" href="mailto:u.speidel@auckland.ac.nz">u.speidel@auckland.ac.nz</a>
<a class="moz-txt-link-freetext" href="http://www.cs.auckland.ac.nz/~ulrich/">http://www.cs.auckland.ac.nz/~ulrich/</a>
****************************************************************
</pre>
</body>
</html>