<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">We regularly reference Green Books and expect them to provide correct descriptions of our standards and how to use them. Having them out of date or inaccurate leaves us at risk of mis-leading
our community.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">That said, I would completely agree that Blue and Magenta Books should take precedence.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks for the 740.0-G-1 correction.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, April 5, 2017 at 10:21 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] FW: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"sans-serif","serif"">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""> note that discussing in the CESG was your proposal not mine......</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">For your list I also have a correction for </span><span style="font-size:10.0pt;font-family:Tahoma">CCSDS 740.0-G-1 Mars Mission Protocol Profiles--Purpose and Rationale. Green Book. Issue 1.
July 2008.</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">This book is not under SLS and according to Tom is under SIS, produced by the Mars 2015 Interoperability Working Group.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Moreover I think that Green Books should be taken out from that list (it may be to a separate one) are they are not specifications.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Gippo</span> <br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"CCSDS Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">05/04/2017 18:29</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">[CESG] FW: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Dear CESG colleagues,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I am forwarding this to the whole CESG so they are aware of the issues. Apologies to those who have already seen it.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Cheers, Peter</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri">Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Date: </b>Wednesday, April 5, 2017 at 8:35 AM<b><br>
To: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Cc: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Keith Scott <kscott@mitre.org>, "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, Tom Gannett <thomas.gannett@tgannett.net>, Tim Pham <timothy.t.pham@jpl.nasa.gov>, Wolfgang Hell <wo_._he@t-online.de>,
Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Subject: </b>Re: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Hi Gippo,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">The short answer to your question is that it is "in the queue", waiting for the resources to tackle this update and others, driven by changes such as USLP and optical. We probably could use some sort of "queue"
or "parking lot" to track these as they show up.</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">The longer answer is that I am fine with discussing this topic in the CESG. I think it is important for us to keep all of our specs up to date, but also to keep them as stable as is practical. This is an
interesting balancing act since some of the new standards really need to evolve beyond where we started with TC, TM, and SPP, and that may involve accepting backward changes as well so as to not "hobble" the ones that are moving forward. That said, when we
do have this discussion I think we need to consider all of the "omnibus" type specs that we have, since they exist in more than one area and WG. And some of the new specs have introduced features that should be retrofitted to older ones in order to keep the
whole set aligned. </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Those that I identified in a quick search (probably not a complete list) are these:</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
1. <span style="font-size:10.0pt;font-family:Calibri">CSS SCCS-ADD & ARD (of course, the COP issue and new standards like USLP & optical)</span>
<br>
2. <span style="font-size:10.0pt;font-family:Calibri">CSS Cross Support Concept — Part 1: Space Link Extension (CSTS and deprecated specs)</span>
<br>
3. <span style="font-size:10.0pt;font-family:Calibri">CSS Cross Support Reference Model—Part 1: Space Link Extension Services. (CSTS and deprecated specs)</span>
<br>
4. <span style="font-size:10.0pt;font-family:Calibri">SLS OSCP (coding changes, USLP, & optical comm)</span>
<br>
5. <span style="font-size:10.0pt;font-family:Calibri">SLS Coding Green Book</span>
<br>
6. <span style="font-size:10.0pt;font-family:Calibri">SLS Telecommand Summary of Concept and Rationale (integrate AOS and USLP forward)</span>
<br>
7. <span style="font-size:10.0pt;font-family:Calibri">SLS TM Channel Coding profiles (AOS & USLP, optical)</span>
<br>
8. <span style="font-size:10.0pt;font-family:Calibri">SLS Mars Mission Protocol Profiles--Purpose and Rationale</span>
<br>
9. <span style="font-size:10.0pt;font-family:Calibri">SIS SSI Architecture</span>
<br>
10. <span style="font-size:10.0pt;font-family:Calibri">MOIMS Mission Operations Services Concept. Green Book</span>
<br>
11. <span style="font-size:10.0pt;font-family:Calibri">MOIMS Mission Operations Reference Model</span>
<br>
12. <span style="font-size:10.0pt;font-family:Calibri">MOIMS Navigation Data—Definitions and Conventions</span>
<br>
13. <span style="font-size:10.0pt;font-family:Calibri">MOIMS Standard Formatted Data Units — Control Authority Data Structures (align with RMP)</span>
<br>
14. <span style="font-size:10.0pt;font-family:Calibri">MOIMS OAIS & PAIS (align with RMP)</span>
<br>
15. <span style="font-size:10.0pt;font-family:Calibri">SOIS Spacecraft Onboard Interface Services. Green Book (deal with the slew of silver standards)</span>
<br>
16. <span style="font-size:10.0pt;font-family:Calibri">Unique Identification of CCSDS Objects and Services (I forgot this even existed, RMP alignment)</span>
<br>
17. <span style="font-size:10.0pt;font-family:Calibri">And the MOIMS and SOIS Application & Support Layer architecture that is now in work …</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Seems pretty obvious that there is a slew of CCSDS docs of various flavors that need to be brought up to date to ensure alignment with our evolving set of standards. There is also a significant cost involved
in doing this, along with the "churn" that will be involved in what has been a stable, if now somewhat out of date and inconsistent, full set of standards.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">As I said before, I don't have a good answer re how we plan to keep all of this up to date and also develop new standards, but it is a topic that should be discussed. And it is clearly broader than just a
tweak to COP in the SCCS ADD.</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Thanks, Peter</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Wednesday, April 5, 2017 at 6:18 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Keith Scott <kscott@mitre.org>, "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, Tom Gannett <thomas.gannett@tgannett.net>, Tim Pham <timothy.t.pham@jpl.nasa.gov>, Wolfgang Hell <wo_._he@t-online.de>,
Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Subject: </b>Re: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<br>
<b><span style="font-size:10.0pt">Peter</span></b><span style="font-size:10.0pt">,</span>
<span style="font-size:10.0pt"><br>
where do we stand with this update to <CCSDS 901.1-M-1 Space Communications Cross Support--Architecture Requirements Document. Magenta Book. Issue 1. May 2015>?</span>
<span style="font-size:10.0pt"><br>
I admit that I got somehow lost as at a certain point I had the impression that the Technical corrigendum option was considered suitable but I haven't seen further activity on this.</span>
<br>
<b><span style="font-size:10.0pt"><br>
Nestor</span></b><span style="font-size:10.0pt">,</span> <span style="font-size:10.0pt">
<br>
as Peter states that "</span><span style="font-size:10.0pt;font-family:Calibri">CESG needs to come to agreement on how these sorts of "omnibus" specs are to be updated</span><span style="font-size:10.0pt">" should this become an agenda item for CESG
Meeting/Discussion?</span> <br>
<span style="font-size:10.0pt"><br>
Regards</span> <br>
<span style="font-size:10.0pt"><br>
Gian Paolo</span> <br>
<br>
<br>
<span style="font-size:7.5pt;color:#5F5F5F"><br>
From: </span><span style="font-size:7.5pt">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<span style="font-size:7.5pt;color:#5F5F5F"><br>
To: </span><span style="font-size:7.5pt">"Barkley, Erik J (3970)" <erik.j.barkley@jpl.nasa.gov>, "Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span>
<span style="font-size:7.5pt;color:#5F5F5F"><br>
Cc: </span><span style="font-size:7.5pt">"Keith Scott" <kscott@mitre.org>, "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, "Tom Gannett" <thomas.gannett@tgannett.net>, "Pham, Timothy T (3300)" <timothy.t.pham@jpl.nasa.gov>, "wo_._he@t-online.de"
<wo_._he@t-online.de></span> <span style="font-size:7.5pt;color:#5F5F5F"><br>
Date: </span><span style="font-size:7.5pt">16/11/2016 20:49</span> <span style="font-size:7.5pt;color:#5F5F5F">
<br>
Subject: </span><span style="font-size:7.5pt">Re: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Yes.</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
But more than that, the CESG needs to come to agreement on how these sorts of "omnibus" specs are to be updated. We are also in the midst of, at CMC request, generating another one for the other two CCSDS areas, SOIS and MOIMS.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
Peter</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <b><span style="font-family:Calibri"><br>
From: </span></b><span style="font-family:Calibri">Erik Barkley <erik.j.barkley@jpl.nasa.gov><b><br>
Date: </b>Wednesday, November 16, 2016 at 11:47 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Cc: </b>Keith Scott <kscott@mitre.org>, "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, Tom Gannett <thomas.gannett@tgannett.net>, Tim Pham <timothy.t.pham@jpl.nasa.gov>, Wolfgang Hell <wo_._he@t-online.de><b><br>
Subject: </b>RE: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
I think we have identified about as good a plan as we can for the moment. I think it may be a CESG "problem" to the extent that CESG should, collectively, have, and work towards maintaining, a good idea of the architecture against which the CCSDS standards
are being developed. </span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080">
<br>
</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080"><br>
Best regards,</span> <span style="font-size:10.0pt;font-family:Calibri;color:#004080">
<br>
-Erik</span> <b><span style="font-size:10.0pt;font-family:Calibri"><br>
From:</span></b><span style="font-size:10.0pt;font-family:Calibri"> Shames, Peter M (312B)
<b><br>
Sent:</b> Wednesday, November 16, 2016 10:03 AM<b><br>
To:</b> Gian.Paolo.Calzolari@esa.int; Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov><b><br>
Cc:</b> Keith Scott <kscott@mitre.org>; Margherita.di.Giulio@esa.int; Tom Gannett <thomas.gannett@tgannett.net>; Pham, Timothy T (3300) <timothy.t.pham@jpl.nasa.gov>; wo_._he@t-online.de<b><br>
Subject:</b> Re: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
I think Gippo makes a good point about the intended scope of TC's. While I disagree that the document is "unstable by nature" I do agree that it is fundamentally a different kind of document than any others that we have published. Most standards address one
layer. Some, like utilization profiles, may address 2 or three layers. This one addresses 90 separate standards, services, seven layers of protocol stacks, component features, and end-to-end deployments.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
I think we need to find a way to deal with the evolution of the four CCSDS areas of work that are covered by this and do it in a way that is effective and that also makes this document effective and credible. This is not an issue we have had to face before
and we did not, to be honest, think it all through ahead of time.</span> <span style="font-size:10.0pt;font-family:Calibri">
<br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
I do not have a good answer to offer at this moment, but I do think that gathering the edits, in a well documented form, agreeing on them, and queuing them up for "batch" is one way to achieve a level of stability. If that results in needing to periodically
invoke the usual, more formal, Pink Sheet process then that may be the best way forward.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
Any other ideas on how to best handle the general case presented by this document? Maybe this is a CESG topic?</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
Thanks, Peter</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <b><span style="font-family:Calibri"><br>
From: </span></b><span style="font-family:Calibri">Gian Paolo Calzolari <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-family:Calibri;color:#0082BF">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-family:Calibri">><b><br>
Date: </b>Wednesday, November 16, 2016 at 2:16 AM<b><br>
To: </b>Erik Barkley <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-family:Calibri;color:#0082BF">erik.j.barkley@jpl.nasa.gov</span></a><span style="font-family:Calibri">><b><br>
Cc: </b>Keith Scott <</span><a href="mailto:kscott@mitre.org"><span style="font-family:Calibri;color:#0082BF">kscott@mitre.org</span></a><span style="font-family:Calibri">>, "</span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-family:Calibri;color:#0082BF">Margherita.di.Giulio@esa.int</span></a><span style="font-family:Calibri">"
<</span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-family:Calibri;color:#0082BF">Margherita.di.Giulio@esa.int</span></a><span style="font-family:Calibri">>, Peter Shames <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-family:Calibri;color:#0082BF">peter.m.shames@jpl.nasa.gov</span></a><span style="font-family:Calibri">>,
Tom Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-family:Calibri;color:#0082BF">thomas.gannett@tgannett.net</span></a><span style="font-family:Calibri">>, Tim Pham <</span><a href="mailto:timothy.t.pham@jpl.nasa.gov"><span style="font-family:Calibri;color:#0082BF">timothy.t.pham@jpl.nasa.gov</span></a><span style="font-family:Calibri">>,
Wolfgang Hell <</span><a href="mailto:wo_._he@t-online.de"><span style="font-family:Calibri;color:#0082BF">wo_._he@t-online.de</span></a><span style="font-family:Calibri">><b><br>
Subject: </b>RE: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Dear All,</span> <span style="font-size:10.0pt;font-family:Arial"><br>
I have just one warning.</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
IMO a Technical Corrigendum is appropriate for a limited number of corrections (and indeed the F-Frame case - 2 clauses and 1 note - falls into this classification).</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
If we expect to collect many items together we may exit from the Technical Corrigendum case.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
If this would happen we would realize that there is a need for a formal Pink Review and also the easy correction will be queued up and delayed.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
I can also agree that making several corrections may give the impression that a document is unstable but - on the other hand - this document is somehow "unstable by nature" with so many references to future needs/solutions.
<br>
<br>
Just my cent.........................</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
<br>
Regards</span> <span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Gian Paolo</span> <span style="font-size:10.0pt;font-family:"Courier New""><br>
this message and any attachments are intended for the use of the addressee or addressees only.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
content is not permitted.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
If you received this message in error, please notify the sender and delete it from your system.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
</span> <span style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""> </span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
<pre style="margin-left:.5in">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
</div>
</body>
</html>