<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=utf-8">
<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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{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;}
/* List Definitions */
@list l0
{mso-list-id:1626233887;
mso-list-type:hybrid;
mso-list-template-ids:1535392668 2129291492 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Scott & Keith,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Just to confirm, is this your
(DTN WG) request to add the following PIDs to Space Link Identifiers Blue Book to
support DTN:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>1 new CCSDS Encapsulation
Service PID for “Bundle Protocol i.e., BP”<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>1 new CCSDS
Encapsulation Service PID for “Linklidder Transport Protocol i.e., LTP”<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>When do you need these PIDs
assigned? <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Note that there will be a
discussion at the SLS area plenary on this Friday afternoon, to consider more
frequent updates (more frequent than the traditional 5-year cycle) of the Space
Link Identifiers. I am a strong proponent of more frequent updates. In fact, it
is my opinion that the Space Link Identifier values should be controlled by
SANA in a database.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Greg<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </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"'> Burleigh, Scott C
(313B) <br>
<b>Sent:</b> Tuesday, October 27, 2009 6:15 AM<br>
<b>To:</b> Scott, Keith L.; Kazz, Greg J (313B); Hooke, Adrian J (9000)<br>
<b>Cc:</b> 'sls-slp@mailman.ccsds.org'<br>
<b>Subject:</b> RE: Encapsulation PIDs for DTN, LTP, etc<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>More precise than “direct DTN”,
I think, would be “BP”, but I agree, we’d want at least those two. And
yes, the client service ID would be used to distinguish between LTP segments
that are to be delivered to a Bundle Protocol agent versus those that are to be
delivered other potential LTP users.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Scott<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<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"'> Scott, Keith L.
[mailto:kscott@mitre.org] <br>
<b>Sent:</b> Tuesday, October 27, 2009 4:25 AM<br>
<b>To:</b> Kazz, Greg J (313B); Burleigh, Scott C (313B); Hooke, Adrian J
(9000)<br>
<b>Cc:</b> 'sls-slp@mailman.ccsds.org'<br>
<b>Subject:</b> Re: Encapsulation PIDs for DTN, LTP, etc<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>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</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></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"'>: 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 </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<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>
</div>
</body>
</html>