<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 14 (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: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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char1";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-fareast-language:ZH-CN;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
font-family:"Calibri","sans-serif";}
span.CommentTextChar1
{mso-style-name:"Comment Text Char1";
mso-style-priority:99;
mso-style-link:"Comment Text";
mso-fareast-language:ZH-CN;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:713426868;
mso-list-type:hybrid;
mso-list-template-ids:-1456151798 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="WordSection1">
<p class="MsoCommentText"><o:p> </o:p></p>
<p class="MsoCommentText">Massimo, I sorry you didn’t put me on your distribution, because I can provide you the rationale for the assumptions in USLP. Your comments are enumerated blow in Black,
<span style="color:red">My response is in RED.</span> <o:p></o:p></p>
<p class="MsoCommentText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]> As discussed in the past, with a variable frame size, as intended by USLP, C&S would have a very hard time delimiting the frames, a much cleaner solution would be to have USLP itself to take care of the delimiting (while C&S would do
the same for the codewords). Currently in the TC books (most similar to USLP with variable frame size) the behavior is that the protocol sublayer performs frame delimiting while the coding sublayer performs delimiting of data units (consisting of one or more
Transfer Frames).<o:p></o:p></p>
<p class="MsoNormal"> It results that the functions actually performed in USLP may/shall adapt to the setting for variable or fixed length frames.<o:p></o:p></p>
<p class="MsoNormal"> <span style="color:red"> I have no problem moving frame sync to data services sublayer, except the sublayer below is called coding and sync. It provides sync and coding for code block and should provide sync and CRC coding for
the frame. GP has been adamant about the interface to the C&S sublayer be the frame: this requires the C&S to delimit the received frame adding CRC is totally in line with C&S.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Is this really the case? Undetected error rate with BCH is rather good (even w/o the use of optional CRC), as can be seen in CCSDS230.1-G, sec 9.5.3<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">This is only true if the SNR is above 10**-3, if it is below that and in anomalous conditions it may very well be. Another is if you get false sync you have significant error problems.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>As of today, the security of the TC is apparently a concern for NE (LEO) missions, not so much for DS (or NE not LEO), so it’s difficult to accept that everything should change because of this requirement. This seems to be Green
material, more than (future) Blue, in any case.<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">This is a leading STD hopefully for many years. Are you sure who your allies will be?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>While this is true for (TM) transmitters (modulators), I believe it is still a bit premature for transponders<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">NASA is already working on a universal transceiver, can ESA be far behind?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">5)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:red">A) </span>I would recommend avoiding this sort of grand and general statements. Especially for FPGAs, a number of Agencies are still facing very serious issues with qualification, preventing effective
use of the most recent and powerful devices (for critical units as transponders or transmitters) for a number of years to come. Besides, this seems Green Book material more than (future) Blue.<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">B) </span>Possibly software-defined radio transponders…but certainly not “software transponders”<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">NASA is already working on a universal transceiver, can ESA be far behind? Can Transponders be far behind?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">6)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>It’s not up to USLP to indicate which codes should be used<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:red">We were not putting down SCCC. LDPC was an example.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:red"><span style="mso-list:Ignore">7)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>--As far as USLP is concerned, it is enough to mention coding and sync functions. This part should be deleted altogether.<span style="color:red"><o:p></o:p></span></p>
<p class="MsoListParagraph">--Not clear why a new book would be required (when USLP is still so far away from needing it, anyway)<o:p></o:p></p>
<p class="MsoListParagraph"><span style="color:red">USLP is being designed for all links, It would be nice to have a C&S for all links. You are forward looking and are pushing SCCC. We are trying to be forward looking for Link Layer as well.<o:p></o:p></span></p>
<p class="MsoCommentText" style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="background:yellow;mso-highlight:yellow"><span style="mso-list:Ignore">8)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="background:yellow;mso-highlight:yellow">Why C&S operations should be specified in a protocol book? This is leading to an increase confusion, against the protocol segregation principle. I’m very much against it. If
anything, refer to the existing coding books.<o:p></o:p></span></p>
<p class="MsoListParagraph"><b><span style="color:red">Note that every Blue book describes the services provided by the layers above and below. That is why C&S is included. IT would be much easier to say that the interface between the data services sublayer
and C&S is a Frame!!!! And today we only have C&S for TC or TM/AOS or Prox…..We need something for all links so that an orbiter needs only 1 link layer protocol.
<o:p></o:p></span></b></p>
<p class="MsoListParagraph"><b><span style="color:red"><o:p> </o:p></span></b></p>
<p class="MsoListParagraph"><b><span style="color:red">Thanks for your review. It is important to get comments from all the WGs. If C&S has yet to address these issue I think that it might be time to do so. <o:p></o:p></span></b></p>
<p class="MsoListParagraph"><span style="color:red"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span style="color:red"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span style="color:red"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span style="color:red"><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""> Kazz, Greg J (312B)
<br>
<b>Sent:</b> Thursday, July 09, 2015 9:46 AM<br>
<b>To:</b> Greenberg, Edward (312B)<br>
<b>Cc:</b> Sank, Victor J. (GSFC-560.0)[AS and D, Inc.]<br>
<b>Subject:</b> FW: Updated Draft USLP White Book for SLP WG and interested parties review<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">Ed,<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">Reading though Massimo’s comments for the most part, I guess we really gave him major hemorrhoids on this one. Did you find anything of value in what he commented
on ?<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 0in 0in 0in">
<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">"<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>><br>
<b>Date: </b>Tuesday, July 7, 2015 at 7:08 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>"Hamkins, Jon (3320)" <<a href="mailto:jon.hamkins@jpl.nasa.gov">jon.hamkins@jpl.nasa.gov</a>>, "Andrews, Kenneth S (332B)" <<a href="mailto:kenneth.s.andrews@jpl.nasa.gov">kenneth.s.andrews@jpl.nasa.gov</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>>, "Sank, Victor J. (GSFC-560.0)[AS and D, Inc.]" <<a href="mailto:victor.j.sank@nasa.gov">victor.j.sank@nasa.gov</a>>, "<a href="mailto:Marco.Rovatti@esa.int">Marco.Rovatti@esa.int</a>"
<<a href="mailto:Marco.Rovatti@esa.int">Marco.Rovatti@esa.int</a>><br>
<b>Subject: </b>Re: Updated Draft USLP White Book for SLP WG and interested parties review<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:10.0pt;font-family:"Arial","sans-serif";color:black">Greg,</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">please find a few comments specifically on the interface USLP-C&S.</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">On the point 3 below, I'm afraid I'm completely against the approach taken: unless you are suggesting to disband the C&S WG, I don't see how SLP can propose a new C&S book at
all, without having even discussed this</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">in the C&S WG.
</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Best regards,</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Massimo</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
<br>
<br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">"Kazz, Greg J (312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>></span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">"<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>>,
</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">"Sank, Victor J. (GSFC-560.0)[AS and D, Inc.]" <<a href="mailto:victor.j.sank@nasa.gov">victor.j.sank@nasa.gov</a>>,
"<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>>, "Hamkins, Jon (3320)" <<a href="mailto:jon.hamkins@jpl.nasa.gov">jon.hamkins@jpl.nasa.gov</a>>, "Andrews,
Kenneth S (332B)" <<a href="mailto:kenneth.s.andrews@jpl.nasa.gov">kenneth.s.andrews@jpl.nasa.gov</a>></span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">07/07/2015 01:14</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">Updated Draft USLP White Book for SLP WG and interested parties review</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:15.0pt"><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
<br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">All,</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">Please find an updated USLP White Book in the SLP WG area of the CWE under this URL for the Fall CCSDS meeting in Darmstadt, Germany:</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
<a href="http://tinyurl.com/nuu9xt8"><b><span style="font-size:13.5pt">http://tinyurl.com/nuu9xt8</span></b></a><br>
<br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">I would very much appreciate it if you would please review this document and send me back you comments. Ideally I would like you to do this before August 1. Note that this
draft white book contains references to several new draft books under construction below:</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">1. </span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">COP-U (a draft specification that attempts to create a COP for both Proximity and
Telecommand Applications). See </span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><a href="http://tinyurl.com/q4d5fyy"><b><span style="font-size:13.5pt">http://tinyurl.com/q4d5fyy</span></b></a><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">2. </span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">SOM – Session Operations Management Sublayer of USLP – Currently our thought is
to make this separate from the USLP White Book. (Note that the USLP White Book is modeled based upon the existing TC, TM, AOS Space Data Link Layer books and NOT the Proximity-1 Space Data Link Book which doesn’t conform as well to the other three.) See
</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><a href="http://tinyurl.com/p55g3oj"><b><span style="font-size:13.5pt">http://tinyurl.com/p55g3oj</span></b></a><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">3. </span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">C&S-USLP (a draft specification to gather our thoughts about the interactions between
USLP and the C&S sublayer). Clearly this work will eventually be done by the C&S WG, when the time comes to undertake it.
</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black"><a href="http://tinyurl.com/od43f9t"><b><span style="font-size:13.5pt">http://tinyurl.com/od43f9t</span></b></a><br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">Best regards,</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
<br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">Greg Kazz</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<br>
</span><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:black">Chairman SLS-SLP WG</span><span style="font-size:15.0pt;font-family:"Calibri","sans-serif";color:black">
<o:p></o:p></span></p>
<pre><span style="color:black">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></span></pre>
<pre><span style="color:black">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></span></pre>
<pre><span style="color:black">content is not permitted.<o:p></o:p></span></pre>
<pre><span style="color:black">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></span></pre>
<pre><span style="color:black">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Please consider the environment before printing this email.<o:p></o:p></span></pre>
</div>
</div>
</div>
</body>
</html>