<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)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@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><font size=2 color=navy face=Arial>
Greg,<br><br>We've been thinking about the following:<br><br>1) DTN directly over Encap (e.g. When used over prox-1 reliable packet service.)<br><br>2) DTN over LTP over encap over (tc/tm or aos)<br><br>Thus, would it make sense to have encap pids for each (ltp and 'direct DTN') (how many ids are available)?<br><br>Scott - I'm assuming that ltp would use the Client Service ID to identify dtn vs. Other ltp users.<br><br> --keith<br></font></div>
<br><div><hr size=2 width="100%" align=center tabindex=-1>
<font face=Tahoma size=2>
<b>From</b>: Kazz, Greg J (313B) <greg.j.kazz@jpl.nasa.gov>
<br><b>To</b>: Scott, Keith L.; Burleigh, Scott C (313B) <scott.c.burleigh@jpl.nasa.gov>; Hooke, Adrian J (9000) <adrian.j.hooke@jpl.nasa.gov>
<br><b>Cc</b>: sls-slp@mailman.ccsds.org <sls-slp@mailman.ccsds.org>
<br><b>Sent</b>: Tue Oct 27 06:58:42 2009<br><b>Subject</b>: Encapsulation PIDs for DTN, LTP, etc
<br></font><br></div>
<div class=Section1>
<p class=MsoNormal>Keith et al,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>SLS-SLP WG would like to know if the DTN WG needs to define
Encapsulation Protocol IDs (PIDs) for LTP blocks, or DTN Bundles, or something
else?<o:p></o:p></p>
<p class=MsoNormal>The actual value of these PIDs would go into the Space Link Identifiers
Blue Book. <o:p></o:p></p>
<p class=MsoNormal>SLS-SLP WG is advancing the Space Link Identifiers Blue Book
to a new version as a result of our meeting today.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Please let me know if you want to comment on this issue.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Greg<o:p></o:p></p>
</div>
</body>
</html>