<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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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:70.85pt 70.85pt 2.0cm 70.85pt;}
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-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear All, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As I haven’t seen any reaction on this, I kindly remind the follow-up actions, so that we can close this point and have the corrigendum published quickly.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you all!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Tomaso<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> de Cola, Tomaso <br>
<b>Sent:</b> Mittwoch, 11. Juni 2025 09:30<br>
<b>To:</b> techsupport@mailman.ccsds.org; 'secretariat@mailman.ccsds.org' <secretariat@mailman.ccsds.org><br>
<b>Cc:</b> cesg@mailman.ccsds.org; Lux, Jim (US 3370) <james.p.lux@jpl.nasa.gov>; Bob Durst <durst@mitre.org><br>
<b>Subject:</b> FW: [Cesg-all] Results of CESG Polls closing 14 September 2023<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">More than 1 year ago, a resolution for a corrigendum to be applied to CCSDS 734.1-B-1 (Licklider Transmission Protocol (LTP) for CCSDS) was issued with a corresponding CESG poll, which resulted in some conditions raised by Peter. After
a few iterations with him and the new SEA AD (Jim here in cc), all the raised conditions have been successfully implemented in the revised version of the corrigendum. Attached you can find the new version of the document (in track-changes, showing the changes
part of the corrigendum request) and the email exchange between Bob and Jim confirming that the process can be closed. As such, we can now move on with the instruction of the CMC poll towards the final approval for the publication. To this end, I kindly ask
the new tech editors to format the new version of the document and prepare the errata-corrige to be applied at the beginning of the document.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Should you have any questions, please let me know,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Tomaso<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Tomaso de Cola via SIS-DTN<br>
<b>Sent:</b> Freitag, 15. September 2023 22:05<br>
<b>To:</b> <a href="mailto:durst@mitre.org">durst@mitre.org</a><br>
<b>Cc:</b> <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br>
<b>Subject:</b> [Sis-dtn] Fwd: [Cesg-all] Results of CESG Polls closing 14 September 2023<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CESG review of LTP corrigendum completed. One condition from Peter:
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="background:white">Peter Shames (Approve with Conditions): The registration process defined in Sec 3.6 of this document is completely inadequate for the purpose. "LTP Engine IDs" are allocated by the SANA. So far so good.
But the SANA LTP Engine Registry (</span><a href="https://sanaregistry.org/r/ltp_engineid/">https://sanaregistry.org/r/ltp_engineid/</a><span style="background:white">) only records a range of numbers assigned to some organization. There is no: 1) PoC at
that organization to make a request of, 2) guidance as to how those numbers are assigned nor what records must be kept, 3) registry of assigned IDs, 4) ""location of assigned IDs. This really must be fixed if this is to be a useful operational registry.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="background:white">To be discussed in next telcos</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="background:white">Tomaso</span><o:p></o:p></p>
<div>
<p class="MsoNormal">Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Begin forwarded message:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b>From:</b> CCSDS Secretariat via CESG-All <<a href="mailto:cesg-all@mailman.ccsds.org">cesg-all@mailman.ccsds.org</a>><br>
<b>Date:</b> 15. September 2023 at 20:56:37 CEST<br>
<b>To:</b> <a href="mailto:cesg-all@mailman.ccsds.org">cesg-all@mailman.ccsds.org</a><br>
<b>Cc:</b> CCSDS Secretariat <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<b>Subject:</b> <b>[Cesg-all] Results of CESG Polls closing 14 September 2023</b><br>
<b>Reply-To:</b> <a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Peter Shames (Approve with Conditions): The registration process defined in Sec 3.6 of this document is completely inadequate for the purpose. "LTP Engine IDs" are allocated by the SANA. So far so good. But the SANA LTP Engine Registry
(<a href="https://sanaregistry.org/r/ltp_engineid/">https://sanaregistry.org/r/ltp_engineid/</a>) only records a range of numbers assigned to some organization. There is no: 1) PoC at that organization to make a request of, 2) guidance as to how those numbers
are assigned nor what records must be kept, 3) registry of assigned IDs, 4) ""location of assigned IDs. This really must be fixed if this is to be a useful operational registry.<o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</body>
</html>