<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 12 (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]-->
<title>Re: [Sis-ipo] IPE test results viewgraphs loaded to SIS-IPO CWE</title>
<style>
<!--
 /* Font Definitions */
 @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;}
@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";}
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;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</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>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Folks &#8211;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I assume Ed is referring to the CxP arch.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There is a misconception among a lot of people about how IPSEC
is applied within Cx.&nbsp; All Cx systems must provide the ability to protect
information using IPSEC.&nbsp; They do not all have to turn it on.&nbsp; That
decision depends on the type of traffic flowing at a given time and how that
information must be protected.&nbsp; For example, command must be authenticated
(meaning it came from an authenticated user) but does not need to have
confidentiality provided by encryption.&nbsp; Crew medical communication
(email, medical conferences, etc) must have confidentiality provided, but not
source authentication.&nbsp; Neither feature is turned on for the bulk of the
traffic.&nbsp; This means that most of the traffic in a channel is NOT using
IPSEC in any way, and therefore receives the benefit of IPHC.&nbsp; This is a different
model than traditional &#8220;encrypt it all&#8221; link design.&nbsp; Remember
we are building a networked end-to-end architecture, and using application and network
layer techniques in place of the legacy link layer techniques.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Now, at the end of the day, lets assume that we DO need to use
IPSEC, and that we DO need to have a lot of it.&nbsp; Our links are designed
with data margin.&nbsp; In the nominal case (what we are designing to), that
margin remains for on-orbit low-priority traffic (background file transfers,
recorder dumps, science offload, etc).&nbsp; If it turns out that the risk
assessments (which are in process) show that we need to protect more traffic
than we thought, we have less margin &#8211; but we fit &#8211; both in terms
of reserved data bandwidth w/ the current RF powers, and also with additional RF
design margin if needed.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There are a lot of issues for our program with delivering data
from MCC to the ground site with SLE.&nbsp; These include technical (inability
to route link layer crypto, support for multiple sources of data, &#8220;forcing&#8221;
JSC MOD to be the &#8220;network concentrator&#8221; for the moon for all time&#8230;),
but also cost, manpower, and scheduling complexity.&nbsp; These are being
discussed by the Cx Program Manager and the head of Mission Operations at JSC.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>- Jason<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</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"'> Israel, David J.
(GSFC-5670) <br>
<b>Sent:</b> Tuesday, April 21, 2009 8:32 AM<br>
<b>To:</b> Greenberg, Edward; Kazz, Greg J; sis-ipo@mailman.ccsds.org<br>
<b>Subject:</b> RE: [Sis-ipo] IPE test results viewgraphs loaded to SIS-IPO CWE<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Ed,</span><o:p></o:p></p>

<p class=MsoNormal>&nbsp;<o:p></o:p></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>It is important to identify whether or not this comment will affect
the completion of the IPO document under development.&nbsp; Do you think it
does?&nbsp; I think this comment is specific to a particular users implementation
and ops plan an we should move the discussion to a different forum.</span><o:p></o:p></p>

<p class=MsoNormal>&nbsp;<o:p></o:p></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Regards,</span><o:p></o:p></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Dave</span><o:p></o:p></p>

<p class=MsoNormal>&nbsp;<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div class=MsoNormal align=center style='text-align:center'>

<hr size=2 width="100%" align=center>

</div>

<p class=MsoNormal style='margin-bottom:12.0pt'><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"'> sis-ipo-bounces@mailman.ccsds.org
[mailto:sis-ipo-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Greenberg,
Edward<br>
<b>Sent:</b> Tuesday, April 21, 2009 12:13 AM<br>
<b>To:</b> Kazz, Greg J; sis-ipo@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Sis-ipo] IPE test results viewgraphs loaded to SIS-IPO CWE</span><o:p></o:p></p>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:9.0pt;
font-family:"Verdana","sans-serif"'><br>
I hate to say it but trying to show that you can squeeze a data stream that is
10% higher than the allowable bandwidth by using header compression without
Ipsec is a useless example when the defined architecture requires Ipsec.
&nbsp;The example however, becomes useful only if the framing is performed at
MS, includes Link layer security and is delivered to the station via SLE to
achieve the necessary security. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
<br>
On 4/20/09 8:46 PM, &quot;Kazz, Greg J&quot; &lt;greg.j.kazz@jpl.nasa.gov&gt;
wrote:</span><o:p></o:p></p>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif"'>All,<br>
&nbsp;<br>
As promised please go to the following URL to download the presentation Loren
Clare made today on interoperability testing of the CCSDS Internet Protocol
Extension (IPE).<br>
&nbsp;<br>
<a
href="http://cwe.ccsds.org/sis/docs/Forms/AllItems.aspx?RootFolder=%2fsis%2fdocs%2fSIS%2dIPO%2fDraft%20Documents&amp;FolderCTID=&amp;View=%7b390C4ADA%2dA69B%2d4E52%2dA0DA%2d50C48F989C4B%7d">http://cwe.ccsds.org/sis/docs/Forms/AllItems.aspx?RootFolder=%2fsis%2fdocs%2fSIS%2dIPO%2fDraft%20Documents&amp;FolderCTID=&amp;View=%7b390C4ADA%2dA69B%2d4E52%2dA0DA%2d50C48F989C4B%7d</a>
<a
href="http://cwe.ccsds.org/sis/docs/Forms/AllItems.aspx?RootFolder=%2fsis%2fdocs%2fSIS%2dIPO%2fDraft%20Documents&amp;FolderCTID=&amp;View=%7b390C4ADA%2dA69B%2d4E52%2dA0DA%2d50C48F989C4B%7d">&lt;http://cwe.ccsds.org/sis/docs/Forms/AllItems.aspx?RootFolder=%2fsis%2fdocs%2fSIS%2dIPO%2fDraft%20Documents&amp;amp;FolderCTID=&amp;amp;View=%7b390C4ADA%2dA69B%2d4E52%2dA0DA%2d50C48F989C4B%7d&gt;</a>
<br>
&nbsp;<br>
best regards,<br>
&nbsp;<br>
Greg Kazz<br>
Chairman CCSDS SIS-IPO</span><o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>