<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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><!--[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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter: Corrigenda are by definition discrete changes. They have no effect on the systematic review schedule. –Tom<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><span style='color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'>Thomas Gannett<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>thomas.gannett@tgannett.net<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p></div><p class=MsoNormal><span 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 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Shames, Peter M (312B) [mailto:peter.m.shames@jpl.nasa.gov] <br><b>Sent:</b> Thursday, April 06, 2017 1:27 PM<br><b>To:</b> Thomas Gannett; Gian.Paolo.Calzolari@esa.int<br><b>Cc:</b> 'CCSDS Engineering Steering Group - CESG Exec'<br><b>Subject:</b> Re: [CESG] CCSDS Document Status for: [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><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi Tom, et al,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Following your (and Gippo's) suggestions here is my feedback on the document status list. I have noted some errors for SEA, in particular, which I would request be fixed. I also took the liberty, apropos the earlier exchange with Gippo, of highlighting all of the documents that are now past their "Reconfirmation Review" dates. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Please note that I'm not suggesting in any way that we should all drop everything and rush off to deal with this, I just did it to highlight the magnitude of the situation vis-à-vis how far away we are from our nominal goal of a five year review cycle. I did not distinguish Green from Blue / Magenta either and that is clearly a consideration.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I also found what looked like some docs that could usefully be re-assigned to current WG so that they could just be re-confirmed, if that is what was deemed the best approach, or merged in with current work items. I also noted a bunch of older report (YB) style docs that look like they could be "Silvered".<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I'll also point out to Tom that it's a little confusing to track in this table what the real "reconfirmation review" date is when there have been corrigenda applied. I suggest that the most current reconfirmation review date should be shown for the parent document, but updated to align with the most recent corrigendum. When we download a document by number we get the latest, with Corrigenda applied, so that's really the relevant date for the document. It's a twiddle to the table, but a useful one, I think.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Cheers, Peter<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>PS – apologies for using more than 140 characters. Just could not help myself. Sad.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><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","sans-serif";color:black'>From: </span></b><span style='font-family:"Calibri","sans-serif";color:black'>Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br><b>Date: </b>Thursday, April 6, 2017 at 8:03 AM<br><b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br><b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br><b>Subject: </b>RE: [CESG] CCSDS Document Status for: [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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter: It is a new age: “I see errors, but I won’t tell you what they are” without “it’s going to be really big!” or “they’re sooo bad!” is Obama-era grousing. –Tom</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'> </span><o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>Thomas Gannett</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>+1 443 472 0805</span><o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><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-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Shames, Peter M (312B) [<a href="mailto:peter.m.shames@jpl.nasa.gov">mailto:peter.m.shames@jpl.nasa.gov</a>] <br><b>Sent:</b> Thursday, April 06, 2017 10:48 AM<br><b>To:</b> <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a><br><b>Cc:</b> CCSDS Engineering Steering Group - CESG Exec; Tom Gannett<br><b>Subject:</b> Re: [CESG] CCSDS Document Status for: [CESG] FW: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span><o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Thanks Gippo.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I had actually forgotten about this file, which is quite useful. It also has some errors that need correcting, so I suspect that there should be a CESG action item to review and update it.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Cheers, Peter</span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:1.0in'><b><span style='font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-family:"Calibri","sans-serif";color:black'>Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br><b>Date: </b>Thursday, April 6, 2017 at 6:24 AM<br><b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br><b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br><b>Subject: </b>[CESG] CCSDS Document Status for: [CESG] FW: Shall FF-CSTS implement the FOP? / Technical corrigendum option / Just one warning</span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:1.0in'> <o:p></o:p></p></div><p class=MsoNormal style='margin-left:1.0in'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Peter,</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> for your exercise about documents to be updated (sooner or later) you may find useful to profit of Tom's effort in keeping this up to date: </span><a href="https://cwe.ccsds.org/cesg/docs/CCSDS%20Document%20Status.pdf"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>https://cwe.ccsds.org/cesg/docs/CCSDS%20Document%20Status.pdf</span></a> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Best regards</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Gian Paolo</span> <o:p></o:p></p><pre style='margin-left:1.0in'>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:1.0in'>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre style='margin-left:1.0in'>content is not permitted.<o:p></o:p></pre><pre style='margin-left:1.0in'>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:1.0in'>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre style='margin-left:1.0in'> <o:p></o:p></pre><pre style='margin-left:1.0in'>Please consider the environment before printing this email.<o:p></o:p></pre><pre style='margin-left:1.0in'> <o:p></o:p></pre></div></body></html>