<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=us-ascii">
<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:"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:"Franklin Gothic Book";
panose-1:2 11 5 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Perter, resolution CSS-R-2015-05-002, concerning agency review of SLE pink sheets, was sent to the CESG chair and copied to the secretariat on Monday (you should have seen this in the CESG email). I can only
assume the poll is being set-up.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Shames, Peter M (312B) <br>
<b>Sent:</b> Wednesday, May 13, 2015 11:22 AM<br>
<b>To:</b> Barkley, Erik J (3970)<br>
<b>Cc:</b> CSTS-WG; Tom Gannett<br>
<b>Subject:</b> Re: A recommendation re ROCF (and similar spec) updates<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Thanks Erik. That may be the best way to do this. I suspect that someone can be encouraged to provide an "amicus curiae" RID to help it along its way. ;-}<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">I looked in the CESG and CMC open andclosed polls and do not see them in any of these. Maybe they are still "in process". Just what is that status?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Thanks, Peter<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><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="color:black">From: </span></b><span style="color:black"><Barkley>, Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Wednesday, May 13, 2015 at 11:15 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>CSTS-WG <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>, Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<b>Subject: </b>RE: A recommendation re ROCF (and similar spec) updates<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><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"><span style="color:#1F497D">Peter,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As it turns out, the pink sheets for all five SLE recommendations will be out for agency review (pending CESG approval) in the very near future. Presumably the review will be for the pink sheets, but it seems
to me that a RID along the lines you have suggested could be filed at that time and I suspect (given consensus from those very knowledgeable bout the recommendations) that this type of editorial thing could be accommodated. A think submission of a RID would
be the best to track this in this case.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Shames, Peter M (312B)
<br>
<b>Sent:</b> Wednesday, May 13, 2015 10:33 AM<br>
<b>To:</b> Barkley, Erik J (3970)<br>
<b>Cc:</b> CSTS-WG; Tom Gannett<br>
<b>Subject:</b> A recommendation re ROCF (and similar spec) updates<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi Erik,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">I am passing this along to put into your CSS "standards revision" queue. I just had a very lengthy exchange with Mike Anderson, all of which was started by him asking the relatively simple question:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.5pt;color:blue">Can you point me to a high level description of an OCF. The ROCF Blue book does not include a definition. I am trying to figure out what information is included in an OCF. Is it a fixed set of
data or is it completely user defined or some combination?</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black">Mike was trying to understand the ROCF and why it was important. I was trying to help. I dug around and provided him with the references to TC, TM, AOS, and the COP. He complained that the ROCF spec should have
told him how the OCF was defined and how it was used (and why ROCF was important). We argued back and forth for quite a while about how CCSDS (and other) specs are written and why they are constructed in this way. This is a part of the "Mike and Peter dialogue
process" and feel free to ignore it. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">However, at the end, and after looking at the ROCF again in detail, I had to admit that another paragraph or two, early in that document, could have avoided all of this discussion. The ROCF devotes page after
page to definitions of the service itself, to the SLE reference model, service management, return frame and OCF production and provisioning, scheduling, underlying services, buffering, security aspects, etc, etc. These introductory materials are the first
47 pages of the spec.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Nowhere does it say anything as simple as:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">"TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF field for use in COP re-transmission operations. The ROCF service is used to provide this CLCW to the user so that these
re-transmission operations may be implemented in the user MOC.".</span><span style="color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">My suggestion is that the next time that this spec, and the rest of these similar specs, are reviewed for update that another paragraph be added somewhere early in the doc, maybe even in the "Purpose of this recommended
standard" section, or in the Overview Section, that provides just exactly this sort of description of the "what" and the "why" and the "how" and the "what for" of the standard. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Does this make sense to you?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Thanks, Peter<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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="color:black">From: </span></b><span style="color:black"><Shames>, Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Date: </b>Wednesday, May 13, 2015 at 9:51 AM<br>
<b>To: </b>Mike Anderson <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>><br>
<b>Subject: </b>Re: [External] Re: OCF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi Mike,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">After going back and looking at the SLE R-OCF I find that it does, in fact, include all of the references to TM, AOS, OCF, and CLCW. What it does not include, however, is some sort of simple statement
like "TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF for use in COP re-transmission operations".</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">So I agree that the spec could carry another paragraph or so that would more clearly state what R-OCF and OCF itself is, why it is important, and how it relates to the other protocols and real
world uses that missions might make. I'll pass that along to the team that is responsible for it.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Ok?</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">There is always room for improvement. That said, anyone who is going to work in any of these technical protocol fields is going to have to steep themselves in the literature. This is the same
in most technical and scientific fields and that has been a fact of life for centuries. A Popular Mechanics view of the world only gets you just so far, after that the hard work begins.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Peter</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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="color:black">From: </span></b><span style="color:black"><Anderson>, Mike Anderson <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>><br>
<b>Date: </b>Wednesday, May 13, 2015 at 8:46 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>Subject: </b>RE: [External] Re: OCF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">You should be able to read the ROCF Blue Book and have an understanding of what an OCF is and what it is used for. Yes, you need the references for the details but a high level description is useful and it is
not onerous.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I have been doing this stuff for 40 years and the CCSDS documents are among the most difficult to follow. I must assume they are written and edited by people with intimate knowledge of the subject. That is
not a bad thing but they do not seem to consider that every reader will not have that same knowledge. There is room for improvement. A few introductory paragraphs for the novices would go a long way.</span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="176" height="38" id="_x0000_i1025" src="cid:image001.png@01D08D6F.B4D10D70" alt="Booz Allen Hamilton"></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Michael Anderson</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Lead Technologist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">443-956-0979</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.boozallen.com/"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif">www.boozallen.com</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> 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> Wednesday, May 13, 2015 11:25 AM<br>
<b>To:</b> Anderson, Michael [USA]<br>
<b>Subject:</b> Re: [External] Re: OCF<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Yup. Me and the 1000's of people who actually work in the IETF, ISO, and CCSDS standards organizations, to name just a few.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">I'm not trying to be difficult Mike, but just imagine if every spec had to contain all of the relevant info for all of the other specs it referenced. Not only would it create a huge issue editing
all of the related and intertwined specs when any one thing would change, it would also increase the size of each spec by the volume of the included references.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Most of the scientific and technical literature operates in exactly this same way, by reference and not by inclusion. Just look at the list of references on any scientific or technical paper.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">The document I just finished editing, the SCCS-ARD (CCSDS 901x1m0), took the approach of "let's include info on all the stuff that is referenced" (see attached). Not only was it a huge job to
create, but it is pretty big, over 150 pages. But it's all in there, or at least enough to tell people how all these parts fit together and what they do. It does cover OCF, ROCF, and CLCW, where they are defined and how they are to be used.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">-p</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<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"><Anderson>, Mike Anderson <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>><br>
<b>Date: </b>Wednesday, May 13, 2015 at 6:08 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>Subject: </b>RE: [External] Re: OCF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="color:black">“Everything should be made as simple as possible, but not simpler.” CCSDS documentation is much more complicated than it needs to be. You shouldn’t have to go to three different documents to understand what ROCF
is meant to do. The ROCF Blue Book should describe the OCF and its intended use. The RAF and other service interface documents should do the same.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="176" height="38" id="Picture_x0020_2" src="cid:image001.png@01D08D6F.B4D10D70" alt="Booz Allen Hamilton"></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Michael Anderson</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Lead Technologist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">443-956-0979</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.boozallen.com/"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif">www.boozallen.com</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> 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> Tuesday, May 12, 2015 11:23 PM<br>
<b>To:</b> Anderson, Michael [USA]<br>
<b>Subject:</b> Re: [External] Re: OCF<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">ROCF is just a service interface to deliver the data, it really doesn't care, nor does it need to, about what is inside. Ditto RAF & most service interfaces. Just like HTTP doesn't care what web sites you look
at.<br>
<br>
All the Internet standards are exactly the same in format & content. They do not repeat anything defined elsewhere.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Cheers, Peter <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><br>
Sent from Peter's iPhone 6 <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Everything should be made as simple as possible, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">but not simpler. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">~Albert Einstein<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"><br>
On May 12, 2015, at 5:29 PM, Anderson, Michael [USA] <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks, I found it eventually. It still boggles the mind that the OCF description wouldn’t be in the ROCF blue book. Too many back and forth between CCSDS documentation.</span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><image001.png></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Michael Anderson</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Lead Technologist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">443-956-0979</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.boozallen.com/"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif">www.boozallen.com</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> 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> Tuesday, May 12, 2015 4:41 PM<br>
<b>To:</b> Anderson, Michael [USA]<br>
<b>Subject:</b> Re: [External] Re: OCF<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi Mike,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">To quote the email I sent you …</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:blue">The actual CLCW data structure is defined in the
<b>TC protocol (CCSDS 232x0b2)</b>, since it is the TC protocol that operates the COP which uses the CLCW. <b>Look at Sec 4.2 of 232x0b2 (attached) for the definition of the CLCW.</b></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">…</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">So the short version of this is that the TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF for use in COP re-transmission operations.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">And yeah, it can be a bit dense, that's why I dug out the actual definition for you.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Peter</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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="color:black">From: </span></b><span style="color:black"><Anderson>, Mike Anderson <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>><br>
<b>Date: </b>Tuesday, May 12, 2015 at 11:36 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>Subject: </b>RE: [External] Re: OCF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks. I bounced from reference to reference. I found high level descriptions but was realy hoping to find something that actually showed the content. Bit 1 means this, bit means that, etc. I actually did
find the definition for bit 1 but the rest was pretty ambiguous. CCSDS speak is very difficult to master, to many references to other documents rather than spelling things out.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="176" height="38" id="_x0000_i1027" src="cid:image002.png@01D08D6F.B4D10D70" alt="Booz Allen Hamilton"></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Michael Anderson</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Lead Technologist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">443-956-0979</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.boozallen.com/"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif">www.boozallen.com</span></a></span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> 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> Tuesday, May 12, 2015 2:26 PM<br>
<b>To:</b> Anderson, Michael [USA]<br>
<b>Subject:</b> [External] Re: OCF<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi Mike,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">The OCF carries the Command Link Control Word. The OCF is a field in the TM and AOS telemetry protocols that carries the CLCW. The OCF_SDU is defined in CCSDS 132x0b1 (attached) in Sec 4.1.5
where it refers to Type-1-Report. The Type-1-Report cross references CCSDS 232x0b2 for the CLCW definition. </span><span style="font-size:10.5pt;color:blue">The actual CLCW data structure is defined in the TC protocol (CCSDS 232x0b2), since it is the TC
protocol that operates the COP which uses the CLCW.</span><span style="font-size:10.5pt;color:black"> Look at Sec 4.2 of 232x0b2 (attached) for the definition of the CLCW.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">So the short version of this is that the TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF for use in COP re-transmission operations.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">You can also look at the COP (CCSDS 232x1b2) for more info on how the CLCW is used in the COP.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Peter</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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="color:black">From: </span></b><span style="color:black"><Anderson>, Mike Anderson <<a href="mailto:Anderson_Michael@bah.com">Anderson_Michael@bah.com</a>><br>
<b>Date: </b>Tuesday, May 12, 2015 at 10:45 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>Subject: </b>OCF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><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-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="color:black">Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Can you point me to a high level description of an OCF. The ROCF Blue book does not include a definition. I am trying to figure out what information is included in an OCF. Is it a fixed set of data or is it
completely user defined or some combination?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><image003.png><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Michael Anderson</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">Lead Technologist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif;color:#595959">443-956-0979</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><a href="http://www.boozallen.com/"><span style="font-size:9.0pt;font-family:"Franklin Gothic Book",sans-serif">www.boozallen.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</body>
</html>