<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=ks_c_5601-1987">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:±¼¸²;
panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"\@±¼¸²";
panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:±¼¸²;}
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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:±¼¸²;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:±¼¸²;}
span.EmailStyle19
{mso-style-type:personal-compose;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 72.0pt 72.0pt 72.0pt;}
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="KO" link="blue" vlink="purple">
<div class="WordSection1">
<p><span lang="EN-US" style="font-size:10.0pt">Hi, Scott.<br>
I like your way to put those parts in to the document.<br>
I hope the interoperability test participants cooperate to compose the Annex section with helpful contents as a resource of continuing tests between agencies.<br>
<br>
Bests,<br>
<br>
Cheol<br>
<br>
-----Original Message-----<br>
From: SIS-CFDPV1 <sis-cfdpv1-bounces@mailman.ccsds.org> On Behalf Of Burleigh, Scott C (312B) via SIS-CFDPV1<br>
Sent: Wednesday, November 21, 2018 7:39 AM<br>
To: sis-cfdpv1@mailman.ccsds.org<br>
Subject: [SIS-CFDPV1] updated CFDPv1 interoperability test plan<br>
<br>
Hi, all. As we agreed at the CFDP Revisions WG meeting last month, I have posted an updated interoperability test plan for the CFDP Revisions. Cheol, you will notice that this book doesn't look much like the interoperability test overviews you drafted; that
is because CCSDS procedures require that test plans be CCSDS "yellow books" that have to adhere to a number of strict format and content guidelines. I did include a large portion of your supplementary material in an Annex, though, so it is not lost.<br>
<br>
Scott<br>
<br>
-----Original Message-----<br>
From: Burleigh, Scott C (312B)<br>
Sent: Monday, October 15, 2018 1:41 PM<br>
To: Burleigh, Scott C (312B) <Scott.C.Burleigh@jpl.nasa.gov>; sis@mailman.ccsds.org; sis-dtn@mailman.ccsds.org; sis-cfdpv1@mailman.ccsds.org; sis-mia@mailman.ccsds.org; sis-voice@mailman.ccsds.org<br>
Subject: second session on CFDPv1<br>
<br>
Hi again. I believe some subset of us may be interested in hearing more about the CFDPv1 interoperability test planning; if you are among them, a follow-up session will be held in room 080 at 1330 (1:30 pm) on Tuesday afternoon.<br>
<br>
Scott<br>
_______________________________________________<br>
SIS-CFDPV1 mailing list<br>
SIS-CFDPV1@mailman.ccsds.org<br>
<a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-cfdpv1">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-cfdpv1</a></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</body>
</html>