<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=Windows-1252">
<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:Verdana;
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;}
p.MsoList, li.MsoList, div.MsoList
{mso-style-link:"List Char";
margin-top:9.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-align:justify;
text-indent:-.25in;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.ListChar
{mso-style-name:"List Char";
mso-style-link:List;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1894078745;
mso-list-type:simple;
mso-list-template-ids:941111504;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\2013;
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:"Times New Roman",serif;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="blue" vlink="purple">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Scott,</p>
<p>Understood; that's older text, albeit refactored to remain in line with the "state of the world"... I would approve of your proposed text. Alternately, if there's a relevant section (discussing end-to-end reliability) in the CFDP blue/green books, we can
punt completely and refer to that section.</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Jeremy<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> SIS-MIA <sis-mia-bounces@mailman.ccsds.org> on behalf of Burleigh, Scott C (US 312B) via SIS-MIA <sis-mia@mailman.ccsds.org><br>
<b>Sent:</b> Friday, July 31, 2020 12:37:00 AM<br>
<b>To:</b> 'sis-mia@mailman.ccsds.org'<br>
<b>Subject:</b> Re: [Sis-mia] Resolution SIS-R-2020-04-001 Agency Review of CCSDS 766.1-B-2 Digital Motion Imagery</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi. I was just now leafing through the Digital Motion Imagery pink sheets, in preparation for voting to send it to agency review, when some language in 3.7.22
caught my eye:<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>
<p class="MsoNormal">CFDP provides the following two classes for file transmission:
<o:p></o:p></p>
<p class="MsoList" style="mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Class 1—Unreliable CFDP transfer over a reliable UT layer;<o:p></o:p></p>
<p class="MsoList" style="mso-list:l0 level1 lfo1"><![if !supportLists]><span style="mso-list:Ignore">–<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Class 2—Reliable CFDP.<o:p></o:p></p>
<p class="MsoList" style="margin-left:0in;text-indent:0in">For video data, class 2 CFDP shall be used for end-to-end reliability; however, user requirements may stipulate that Class 1 CFDP may be utilized.
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">A pre-RID, I guess: we really are trying to slowly deprecate class-2 CFDP in favor of running class-1 CFDP over BP/LTP (or just over LTP). That policy isn’t
yet so fully established as to merit a SHALL in this language, but maybe a SHOULD. Something like “Class-1 CFDP is recommended for the transmission of video data files. For reliable transmission, class-1 CFDP over a reliable UT layer, with closure requested,
is recommended.”<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Scott<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>
<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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> CESG <cesg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Burleigh, Scott C (US 312B) via CESG<br>
<b>Sent:</b> Thursday, April 16, 2020 6:44 PM<br>
<b>To:</b> Thomas Gannett <thomas.gannett@tgannett.net><br>
<b>Cc:</b> 'sis-mia@mailman.ccsds.org' <sis-mia@mailman.ccsds.org>; cesg@mailman.ccsds.org<br>
<b>Subject:</b> [EXTERNAL] [CESG] Resolution SIS-R-2020-04-001 Agency Review of CCSDS 766.1-B-2 Digital Motion Imagery<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Hi. A resolution from SIS:<br>
<br>
The Space Internetworking Services Area,<br>
<br>
CONSIDERING that<br>
<br>
· the Motion Imagery and Applications (MIA) Working Group has reviewed Pink Sheets that add the h.265 compression protocol to the Digital Motion Imagery Blue Book, and<o:p></o:p></span></p>
<p style="margin-top:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">· the Working Group has reached consensus on requesting Agency Review of these Pink Sheets,<o:p></o:p></span></p>
<p style="margin-top:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">RESOLVES to request that CESG approve an Agency Review of the Pink Sheets titled “CCSDS 766.1-B-2 Digital Motion Imagery”.<br>
<br>
Scott</span><o:p></o:p></p>
</div>
</div>
</body>
</html>