<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=iso-8859-1">
<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;}
@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:0cm;
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;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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="FR" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Greg and all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I concur with the clarifications that you have introduced in section 6.3 and 6.4. Your proposed figures 6-c and 6-d are less ambiguous than the preceding ones
and they clearly rule out the possibility of interfacing SDLS function with "All Frames Generation/Reception" function. The text modifications you propose in coherence with those new figures are OK.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For the modifications introduced in 4.2.1.1.2 and 4.2.1.10 which aim at defining an optional "SDLS Error Flag" to be transmitted in the CLCW, I do not concur
since we concluded at our Feb telecon on SDLS-COP interaction that we should keep SDLS and COP decoupled. The rationale being :<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">- COP is dealing with transmission errors exclusively, so COP-FARM and COP-FOP should only be informed of detected transmission errors<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">- SDLS detects and passivate security errors (discarding impacted frames). SDLS informs associated SLP protocol of security errors, SLP protocol should in
turn inform SLP user. In all cases, security errors management will require analysis and action by human operators. Therefore, I do not see what an automated procedure like the COP could do with this SDLS error flag that you would like to introduce in the
CLCW. Security errors reporting will be defined as part of the SDLS extended procedures which include an SDLS Monitoring & Control service. A real-time SDLS reporting status word will be defined. It could be transmitted either in line in the frame as a newly
defined OCF for TM/AOS, or as a normal TM packet to be carried in the data field of TM/AOS transfer frames. What do you think of the possibility to define a specific type of OCF for SDLS real-time reporting ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For your last point : "ApplySecurity" and "ProcessSecurity" functions are mentionned in SDLS book. So the coherency is insured. We could still add in SLP books
that "ApplySecurity" and "ProcessSecurity" functions are virtual functions that provide security services of SDLS.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gilles<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Gilles MOURY</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">CNES Toulouse</span><span style="color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kazz, Greg J (313B) [mailto:greg.j.kazz@jpl.nasa.gov]
<br>
<b>Envoyé :</b> mardi 19 mars 2013 20:08<br>
<b>À :</b> Moury Gilles<br>
<b>Cc :</b> sls-sea-dls@mailman.ccsds.org; sls-slp@mailman.ccsds.org<br>
<b>Objet :</b> Re: [Sls-sea-dls] Re: Order of Processing between TC-SDLP, COP-1 and SDLS<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">All,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Attached is my attempt to clarify the known interface points between the TC protocol and SDLS. Most of my redlines are confined to the following sections:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">4.2.1.1.2<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">4.2.1.10<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">6.3<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">6.4<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"> I tried to clarify at what channel level (individual VC, MC, Physical Channel – meaning multiplexed Mcs) the TC user can interface with SDLS. To this end, I
provided a diagram that attempts to show this relationship replacing Marjorie's in Section 6.3 and 6.4, which didn't define the interface but rather showed typically examples of where the interface might be. I also introduced text that would aide the TC user
in choosing the appropriate interface point to SDLS within TC. You will see this new text also in sections 6.3 and 6.4.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Most controversially perhaps is the addition of an optional new flag, that SDLS should consider supporting, called "SDLS Error Flag" which enables a reporting
mechanism of security errors from SDLS through the CLCW to COP-1. My concern is that without it, there is no mechanism to inform the COP-1 that the in-order, without duplicate or omission delivery guarenteed by the COP-1 may have been compromised due to actions
taken by SDLS but unknown to the COP-1. I encourage the SDLS WG to consider it. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Finally to ensure that both the SDLS book and the SLP books are coherent, should there be some mention in the SDLS book about the virtual functions I.e., "ApplySecurity"
and "ProcessSecurity" mentioned in TC (which will also be mentioned in AOS and TM as well). Or should we simply say in the SLP books, that this is a virtual function that represents the security services provided in SDLS? It is another open issue.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">This attached version of the TC book is now in the SLP WG CWE under: <b><a href="http://tinyurl.com/ck48ckr">http://tinyurl.com/ck48ckr</a></b><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Your comments are welcome!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Greg Kazz<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Chairman SLP WG<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><Kazz>, "Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<b>Date: </b>Thursday, March 14, 2013 1:22 PM<br>
<b>To: </b>Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Cc: </b>"<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>>, "<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>><br>
<b>Subject: </b>[Sls-sea-dls] Re: Order of Processing between TC-SDLP, COP-1 and SDLS<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Bonjour Gilles,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Thank you for contribution. Essentially you are saying that the green box in both Figures 6c and 6d should shrink so that it does not expand beyond either the
Master Channel Multiplexing Function or the MC Demultiplexing Function. In other words, there is no interface point for SDLS with either the TC-SDLP 'All frames generation' or 'All Frames receiption' functions. This makes sense. However, Figures 6c and 6d
are very nebulous in the sense that there is this "SDLS ApplySecurity Function" seemingly floating around in space that shows an anchor at the port of "Virtual Channel Multiplexing/Demultiplexing" only for example. The text says it could be in Virtual Channel
Generation Function or in the Virtual Channel Multiplexing function. No text talks about the possibility in the MC Multiplexing function. Also the COP management Function is called out in 6c, but no such reciprocal function exists in 6d. I think we are still
lacking a clear explanation of these figures in the text. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">We still need a better way to convey the relationships between the protocols involved including the order of overall processing to the user I.e., between SDLS,
COP-1, TC-SDLP. I think some kind of high order diagram and text that shows the order of processing between them is needed. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">We also need to modify the TC Sync & CC Green book so that we capture the rationale behind our decisions on the order of processing of SDLS, COP-1, TC-SDLP (much
of which you have already captured in the meeting minutes of our last TIM, but some business is yet to be completed).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Comments anyone ?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Greg<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Date: </b>Thursday, March 14, 2013 10:06 AM<br>
<b>To: </b>"Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<b>Cc: </b>"Greenberg, Edward (313B)" <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>>, "Biggerstaff, Craig (JSC-DD12)[LOCKHEED MARTIN CORP]" <<a href="mailto:craig.biggerstaff-1@nasa.gov">craig.biggerstaff-1@nasa.gov</a>>,
"<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>" <<a href="mailto:sls-sea-dls@mailman.ccsds.org">sls-sea-dls@mailman.ccsds.org</a>>, "<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>><br>
<b>Subject: </b>RE: Order of Processing COP-1 and SDLS<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Greg,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Please find attached the additions I propose to the TC-SDLP book to avoid users implementing the wrong order of processing between SDLS and "frame error detection"
by TC-SDLP. In fact, the only forbidden configuration for interfacing SDLS function with TC-SDLP functions is interfacing SDLS with "All Frame Generation" at the sending end and "All Frame Reception" at the receiving end. This guarantee that, at the receiving
end, transmission errors are detected and impacted frames discarded first , before SDLS processes the frames, which satisfies our security requirement that transmission errors should be unambiguously separated from security errors.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I have therefore introduced an additional text in sections 6.3.1 and 6.4.1 to forbid this configuration (see attached redlined file). I think it covers the
point. All comments are welcome.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gilles</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Gilles MOURY</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">CNES Toulouse</span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Kazz, Greg J (313B) [<a href="mailto:greg.j.kazz@jpl.nasa.gov">mailto:greg.j.kazz@jpl.nasa.gov</a>]
<br>
<b>Envoyé :</b> lundi 11 mars 2013 23:02<br>
<b>À :</b> Moury Gilles<br>
<b>Cc :</b> Greenberg, Edward (313B); Biggerstaff, Craig (JSC-DD12)[LOCKHEED MARTIN CORP]<br>
<b>Objet :</b> Order of Processing COP-1 and SDLS</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Gilles,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Correct me if I am wrong, but I did not see a response from you regarding this action item below:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">We do not have text in the TC SLP section 6 document which deals with this issue yet.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">- best regards,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">Greg</span><span style="color:black"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="502" style="width:376.5pt;border-collapse:collapse">
<tbody>
<tr>
<td width="115" valign="top" style="width:86.4pt;border:solid windowtext 1.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">SDLS0213/01</span><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"> <o:p></o:p></p>
</td>
<td width="96" valign="top" style="width:72.0pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt">G. Moury</span><o:p></o:p></p>
</td>
<td width="363" valign="top" style="width:272.25pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="font-size:11.0pt">Propose a solution to explicitly specify the order of processing at the receiving end between TC-COP and SDLS (if not already present in section 6 of TC-SLP)
</span><o:p></o:p></p>
</td>
<td width="95" valign="top" style="width:70.9pt;border:solid windowtext 1.0pt;border-left:none;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt"> March 8, 2013</span><o:p></o:p></p>
<p class="MsoNormal" align="center" style="text-align:center"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>