<html 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="Title" content="">
<meta name="Keywords" content="">
<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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle18
{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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear SAWG Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In CCSDS it is typical that cross cutting topics get handled by the SEA Area. Time codes are one such topic and the key CCSDS document defining these now needs to be reviewed. The CESG has asked SEA to do this and the obvious WG to do
this right now is the SAWG.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The current document, and a proposed page edit with some modifications that make explanatory updates, is attached. The document itself, in its current published form is also attached. Note that the most recent publication date is Nov
2010. This is a relatively short document, at 43 pages in length, and the normative materials are only 8 of those pages. Aside from it being time to re-confirm this document, what prompted this review was a confusion as to what was a valid truncation of
the time code field, as described on pgs 3-6 and 3-7. This has been discussed and resolved in the CESG. The result was to agree that the document spec was correct as stated, and to acknowledge that it does allow a variety of truncations, but to clarify
what is acceptable by adding the non-normative examples on the “ProposedMods” pages.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What I would like is to request some help from one of you. Would one of you be willing to take on the task of reviewing this document, and the proposed modifications, and determine if there is anything else in this document that should
be updated? The only other item we know of is a reference in sec 3.5.1.d, pg 3-8, to “the need to accommodate the upcoming century rollover in only 11 years”. Clearly that is now in the past and should be removed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If there are only these sort of editorial changes these can easily be accommodated in a Corrigendum or as an editorial matter, but we need someone to review the document and make that determination.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can I get a volunteer to do this so that we may discuss it, hopefully quickly, during the upcoming working meeting?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Tuesday, September 6, 2016 at 4:07 PM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[CESG] Proposed modification to CCSDS time-code format</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal">CESG Colleagues,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Based on the interactions/e-mails from Gippo, Mario, and Peter, attached please find a proposal for update of the timecode blue book. By way of summary, I found that the language, upon close reading, was essentially okay and that it really
already allows for fractional seconds to be optional in either timecode A or timecode B and in fact abbreviations/omissions in other respects as well. I took advantage of the examples offered by Mario as I believe these help to make to illustrate more clearly
how the rules of abbreviation can be applied. I look forward to discussing this at the CESG telecon/webex tomorrow.<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">-Erik<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</body>
</html>