<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Aptos;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Aptos;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.TableCell, li.TableCell, div.TableCell
{mso-style-name:"Table Cell";
mso-style-priority:99;
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
text-align:justify;
line-height:14.0pt;
layout-grid-mode:char;
font-size:11.0pt;
font-family:"Arial",sans-serif;
mso-fareast-language:JA;}
span.E-MailFormatvorlage21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.E-MailFormatvorlage24
{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;}
/* List Definitions */
@list l0
{mso-list-id:979260934;
mso-list-template-ids:-550453220;}
@list l0:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:2145615383;
mso-list-template-ids:287493450;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Dear Tom,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I’ve just checked the proposed changes that are fine with me. As such, you can consider close my condition for the publication of the
book.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Gannett <thomas.gannett@tgannett.net>
<br>
<b>Gesendet:</b> Dienstag, 11. Juni 2024 22:36<br>
<b>An:</b> de Cola, Tomaso <Tomaso.deCola@dlr.de><br>
<b>Cc:</b> 'Barkley, Erik J (US 3970)' <erik.j.barkley@jpl.nasa.gov>; 'Shames, Peter M (US 312B)' <peter.m.shames@jpl.nasa.gov>; miles.gannett@logothete.net; 'CESG' <cesg@mailman.ccsds.org><br>
<b>Betreff:</b> RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<br>
<b>Priorität:</b> Hoch<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black">Dear Tomaso:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black">Please respond by return email indicating whether the editorial changes below satisfy your conditions.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black">Tom<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">1) Figure 5-2 should be enhanced (similar comment from Peter)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black;background:yellow;mso-highlight:yellow">Editorial change: Figure 5-2 has been repaired.</span><span lang="EN-US" style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">2) table 9-1 mentions DTN layer with 'BPv7' between brackets: I'd simply point to Bundle Protocol still with 'BPv7' in brackets.
Then as to the description, it emphasises on the routing part. I'd generally point to the store-carry-forward paradigm.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black;background:yellow;mso-highlight:yellow">Editorial change:</span><span lang="EN-US" style="font-family:"Times New Roman",serif;color:black;background:yellow;mso-highlight:yellow"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black;background:yellow;mso-highlight:yellow"><o:p> </o:p></span></p>
<div align="center">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="614" style="width:460.5pt;border-collapse:collapse">
<tbody>
<tr style="page-break-inside:avoid;height:1.0pt">
<td width="192" valign="top" style="width:144.0pt;border:solid windowtext 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<s><span style="font-size:10.0pt;color:red;background:yellow;mso-highlight:yellow">Delay Tolerant Network Layer</span></s><u><span style="font-size:10.0pt;color:blue;background:yellow;mso-highlight:yellow">Bundle Protocol</span></u><span style="font-size:10.0pt;background:yellow;mso-highlight:yellow">
(BPv7)<o:p></o:p></span></p>
</td>
<td width="173" valign="top" style="width:129.6pt;border:solid windowtext 1.0pt;border-left:none;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<span style="font-size:10.0pt;background:yellow;mso-highlight:yellow">Network protocol<o:p></o:p></span></p>
</td>
<td width="250" valign="top" style="width:187.2pt;border:solid windowtext 1.0pt;border-left:none;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<span style="font-size:10.0pt;background:yellow;mso-highlight:yellow">Provides <u>
<span style="color:blue">store-and-forward relay</span></u> <s><span style="color:red">routing through</span></s><u><span style="color:blue">as a core element of</span></u> a
<s><span style="color:red">d</span></s><u><span style="color:blue">D</span></u>elay (and disruption)
<s><span style="color:red">t</span></s><u><span style="color:blue">T</span></u>olerant
<s><span style="color:red">n</span></s><u><span style="color:blue">N</span></u>etwork (DTN) involving a set of space links</span><span style="font-size:10.0pt"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black;background:yellow;mso-highlight:yellow">[Note: DTN is referred to in the next table row, so the call-out is retained in the description.]</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">3) still in table 9-1, there is the pointer to the optical physical item, why not including also the C&S? The table mentioned in the previous rows the
TM/TC C&S (RF part), so that I see the inclusion of the optical one worth for the sake of the completeness.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black;background:yellow;mso-highlight:yellow">Editorial change (new row added at end of table 9-1):</span><span lang="EN-US" style="font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<div align="center">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="614" style="width:460.5pt;border-collapse:collapse">
<tbody>
<tr style="page-break-inside:avoid;height:1.0pt">
<td width="192" valign="top" style="width:143.95pt;border:solid windowtext 1.0pt;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<u><span style="font-size:10.0pt;color:blue;background:yellow;mso-highlight:yellow">Optical Communications Coding and Synchronization<o:p></o:p></span></u></p>
</td>
<td width="173" valign="top" style="width:129.5pt;border:solid windowtext 1.0pt;border-left:none;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<u><span style="font-size:10.0pt;color:blue;background:yellow;mso-highlight:yellow">Channel coding<o:p></o:p></span></u></p>
</td>
<td width="249" valign="top" style="width:187.05pt;border:solid windowtext 1.0pt;border-left:none;padding:2.9pt 5.75pt 2.9pt 5.75pt;height:1.0pt">
<p class="TableCell" align="left" style="margin-top:0cm;text-align:left;line-height:normal">
<u><span style="font-size:10.0pt;color:blue;background:yellow;mso-highlight:yellow">Provides mechanisms for data synchronization and error control</span></u><u><span style="font-size:10.0pt;color:blue">
<o:p></o:p></span></u></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D">Logothete, L.L.C.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D"><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D">+1 443 472 0805<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Barkley, Erik J (US 3970) [<a href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Wednesday, May 22, 2024 3:55 PM<br>
<b>To:</b> Shames, Peter M (US 312B); Thomas Gannett<br>
<b>Cc:</b> <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a>; CESG<br>
<b>Subject:</b> RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">RASDSv2 is a fine term. It’s use consistently throughout the document retires the condition.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Wednesday, May 22, 2024 12:30<br>
<b>To:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>; Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<b>Cc:</b> <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a>; CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject:</b> Re: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Erik & Tom,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">I agree with using one term consistently.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">As for the adoption of RASDS++ vs RASDS v2, I checked with Fred Slane. His ISO TC20/SC14 organization is going to be a co-owner of the final document in ISO. We have agreed to call it: RASDSv2.
This aligns with other similar document version changes, IPv4 vs IPv6, SysML vs SysMLv2, etc. It also reflects that this is going to be published as CCSDS 311.0-B-2. It is an extension and evolution of that original document.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">So I request that Tom, during his editing, change
<b><i>all</i></b> instances of RASDS and RASDS++ to read RASDSv2. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Erik, please signal that this meets your condition.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">I think there was also one question from Wilmot asking if all the new terms would be updated in the SANA Terms registry. My request is that the CTE perform that update after the final version
of the document has been approved.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">One last note about the review and publication process is also in order. I have agreed with Fred Slane, chair of ISO TC20/SC14, that we will follow this process:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">The document will go out for CCSDS Agency (and Observer, etc) review.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">In parallel we will send the Review notice to ISO TC20/SC14 with a request that they ask their Agency membership to participate in the CCSDS review process.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">In parallel I will be inviting outside systems architecture experts to also participate.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">All RIDs that are returned will be reviewed and dispositioned within the SEA SAWG, with the option to augment membership with SC14 participants.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">The final document, after the usual RID dispositioning, will be published as a CCSDS document.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="font-size:11.0pt">That document will then be sent to ISO for the usual “fast track” cover page process, and the final approved document will be jointly published with an ISO number
and attributed to both SC13 and SC14.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Anyone have any issues with this plan?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="color:black">From:
</span></b><span lang="EN-US" style="color:black">Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Tuesday, May 21, 2024 at 4:34</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-US" style="color:black">PM<br>
<b>To: </b>Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<b>Cc: </b>Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>,
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>,
<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a> <<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a>><br>
<b>Subject: </b>RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tom,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I'm happy to see the RASDS++ vs RASDS concern addressed however you would like – just as long as a single term is used consistently, rather than leaving the reader
wondering if there is significance as to when RASDS++ is used vs RASDS. Frankly RASDS++ sounds like a marketing buzz word to me. I’d suggest just indicating RASDS 2.0, but if you choose to use RASDS++ consistently throughout the document that is okay too.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="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" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>
<br>
<b>Sent:</b> Tuesday, May 21, 2024 12:44<br>
<b>To:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Cc:</b> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>;
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a><br>
<b>Subject:</b> RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Erik:
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Since your acquiescence is limited to the UML inheritance condition/question, I believe Peter’s initial response grants editorial freedom to accept
your RASDS++ vs. RASDS proposal. Please respond by return email if you are satisfied that that condition is closed as well. </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Tom
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D">Logothete, L.L.C.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D"><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Times New Roman",serif;color:#1F497D">+1 443 472 0805</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Barkley, Erik J (US 3970) [<a href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Monday, May 20, 2024 9:00 PM<br>
<b>To:</b> Shames, Peter M (US 312B); Thomas Gannett; <a href="mailto:secretariat@mailman.ccsds.org">
secretariat@mailman.ccsds.org</a><br>
<b>Cc:</b> <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a><br>
<b>Subject:</b> RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yes, that works. UML inheritance condition/question resolved. Thank you.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="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" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Monday, May 20, 2024 17:21<br>
<b>To:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>; Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>;
<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a><br>
<b>Cc:</b> <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a><br>
<b>Subject:</b> Re: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Hi Erik,</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="color:black">Yes. You could say that “correspondence” is a specialization of “Association (other relationship, labelled)”. That said, we did explicitly assign a relationship meaning, and a separate type
of arrow, to this relationship. </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="color:black">If we address this in a footnote to Fig 3-3, stated thus:</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt">“Relationships inherited from UML, with Correspondence added as a named extension to Association”</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="color:black">Does that meet your concern?</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="color:black">Thanks, Peter</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="color:black">From:
</span></b><span lang="EN-US" style="color:black">Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Monday, May 20, 2024 at 4:07</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-US" style="color:black">PM<br>
<b>To: </b>Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>,
<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a> <<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>><br>
<b>Cc: </b><a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>,
<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a> <<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a>><br>
<b>Subject: </b>RE: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Peter,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">My suggestion is to note that the correspondence is derived from the UML "Association" relationship. Given that this is making use of UML class diagram definitions
to start with, that seems to be the best “home” for the RASDS derivation. Do you agree?</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><span lang="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" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Monday, May 20, 2024 11:35<br>
<b>To:</b> Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>;
<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a><br>
<b>Cc:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>;
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>; <a href="mailto:miles.gannett@logothete.net">
miles.gannett@logothete.net</a><br>
<b>Subject:</b> Re: [EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Hi Tom,</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">I am completely confident that the issues I pointed out will be satisfied during your final editorial pass over the document.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Having just reviewed the comments from the other ADs I am similarly confident that you can handle all of these as editorial as well. I hope the other ADs concur.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">The only even slightly crunchy comment, IMHO, was Erik’s. He is correct that most of Fig 3-3 was, in fact, inherited from UML. However, in Fig 3-3 we also added “Correspondence”, which is not
a relationship that UML has defined. It is a new relationship added to meet requirements from ISO 42010. Hence “derived from”.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Is that acceptable? Or would you rather put in a footnote stating something like “Inherited from UML, with Correspondence extension”</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Thanks, Peter</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="color:black">From:
</span></b><span lang="EN-US" style="color:black">Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<b>Date: </b>Monday, May 20, 2024 at 9:06</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-US" style="color:black">AM<br>
<b>To: </b><a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a> <<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>>, Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>,
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>,
<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a> <<a href="mailto:miles.gannett@logothete.net">miles.gannett@logothete.net</a>><br>
<b>Subject: </b>[EXTERNAL] RE: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US" style="font-size:11.0pt">Peter:<br>
<br>
As discussed previously, in order to expedite processing, CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1), was placed in CESG polling while undergoing concurrent editing.<br>
<br>
If you are confident, as I am, that the draft resulting from the in-progress editing will correct the editorial issues identified in your conditional approval, perhaps along with other editorial issues, please reply by return email stating that your conditions
are effectively satisfied.<br>
<br>
Tom<br>
<br>
<br>
Logothete, L.L.C.<br>
<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a><br>
+1 443 472 0805<br>
<br>
-----Original Message-----<br>
From: CCSDS Secretariat [<a href="mailto:thomas.gannett@tgannett.net">mailto:thomas.gannett@tgannett.net</a>]
<br>
Sent: Monday, May 20, 2024 12:50 PM<br>
To: <a href="mailto:Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a><br>
Cc: <a href="mailto:Erik.Barkley@jpl.nasa.gov">Erik.Barkley@jpl.nasa.gov</a>; <a href="mailto:Peter.M.Shames@jpl.nasa.gov">
Peter.M.Shames@jpl.nasa.gov</a>; <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a><br>
Subject: Re: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<br>
<br>
Dear Document Rapporteur,<br>
<br>
The CESG poll to approve release of CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review concluded with conditions. Please negotiate disposition of the conditions directly with the AD(s) who voted to
approve with conditions and CC the Secretariat on all related correspondence.<br>
<br>
<br>
CESG E-Poll Identifier: CESG-P-2024-04-002 Approval to release CCSDS 311.0-P-1.1, Reference Architecture for Space Data Systems (Pink Book, Issue 1.1) for CCSDS Agency review<br>
<br>
Results of CESG poll beginning 28 April 2024 and ending 17 May 2024:<br>
<br>
Abstain: 0 (0%) <br>
Approve Unconditionally: 2 (40%) (Aguilar Sanchez, Wilmot)<br>
Approve with Conditions: 3 (60%) (Barkley, Shames, Cola)<br>
Disapprove with Comment: 0 (0%) <br>
<br>
CONDITIONS/COMMENTS:<br>
<br>
Erik Barkley (Approve with Conditions): 1) There are about 90 uses of the term "RASDS++" in the document and about 140 uses of the term "RASDS" (without "++"). There does not seem to be any indication in the book if there is to be inferred singificance
when one term is used vs another. I suspect not, and so would suggest simply introducing this as RASDS V 2.0 and then just uniformly refer to this as RASDS rather than switching terms back and forth.
<br>
<br>
2) figure 3 -3 -- the arrow defintions appear to be inherited from UML rather than derived -- there is not explanation offered as to what the derived properties are. As such I recommend that this be stated as inherited, not derived.
<br>
<br>
Peter Shames (Approve with Conditions): Tom, excellent job with lengthy & challenging input. There are a few typos, as follows:<br>
<br>
Sec 2, pg - all, fix page numbers, they should read 2-1, 2-2…. The first page is just numbered “8”.<br>
Sec 2.2, pg 8, remove highlight on text 5.5.4.<br>
Sec 4, pg 4-1, change title to just “Enterprise Viewpoint”<br>
Sec 5.4.2.2, pg 5-3, Fig 5-2, White background on arrows obscures underlying figure elements<br>
Sec 9.9, pg 9-15, Fig 9-9, White background on arrows obscures underlying figure elements<br>
<br>
Tomaso de Cola (Approve with Conditions): </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Arial",sans-serif"></span><span lang="EN-US" style="font-size:11.0pt">Just two minor points:<br>
<br>
1) Figure 5-2 should be enhanced (similar comment from Peter)<br>
<br>
2) table 9-1 mentions DTN layer with 'BPv7' between brackets: I'd simply point to Bundle Protocol still with 'BPv7' in brackets. Then as to the description, it emphasises on the routing part. I'd generally point to the store-carry-forward paradigm.<br>
<br>
3) still in table 9-1, there is the pointer to the optical physical item, why not including also the C&S? The table mentioned in the previous rows the TM/TC C&S (RF part), so that I see the inclusion of the optical one worth for the sake of the completeness.
<br>
<br>
<br>
Total Respondents: 5<br>
<br>
No response was received from the following Area(s):<br>
<br>
MOIMS<br>
<br>
<br>
<br>
SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions<br>
PROPOSED SECRETARIAT ACTION: Generate CMC poll after conditions have been addressed<br>
<br>
* * * * * * * * * * * * * * * * * * * * * * * *</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>