<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Assi Friedman wrote:
<blockquote cite="mid006101c74bbc$382126a0$800101df@AssiLaptop"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 11 (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: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";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{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";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<div class="Section1">
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">I would like
to point out that a lot of
discussion needs to go into the physical/link layers of this migration.
CCSDS as-is
is has its history significantly influenced from the STDN era. This
history
does not make it very conducive to IP in space.</span></font></p>
</div>
</blockquote>
Hi, Assi. Can you go into a little more detail on why the CCSDS
link-layer protocols are not very conducive to IP in space?<br>
<br>
Since they were designed for use in -- and are heavily (and very
successfully) used in -- space, and are the international standard link
protocols for communication with spacecraft, I'm guessing it's not the
"in space" part of the problem that you think the protocols are not
suitable for. So I'm concluding that you think that they are not a
suitable medium for carrying IP packets, right? Is there something
about IP packets that makes them okay to carry in Ethernet frames, PPP,
SONET, etc. but not okay to carry in, say AOS frames?<br>
<blockquote cite="mid006101c74bbc$382126a0$800101df@AssiLaptop"
type="cite">
<div class="Section1">
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">Migrating to
IP will require us
to address the physical/link layers.</span></font></p>
</div>
</blockquote>
"Require" is kind of a strong word to use here. Are you saying that
it's impossible to convey IP traffic over the CCSDS link protocols? Or
are you saying that it's just operationally more expensive to convey IP
traffic to and from spacecraft over CCSDS link protocols than over some
other link protocols? In either case, can you point to some published
studies that demonstrate the deficiencies of the CCSDS links?<br>
<br>
Scott<br>
</body>
</html>