<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 15 (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:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 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-top:12.0pt;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:0in;
        margin-bottom:.0001pt;
        text-align:justify;
        line-height:14.0pt;
        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 Char";
        margin-top:12.0pt;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:0in;
        margin-bottom:.0001pt;
        text-align:justify;
        line-height:14.0pt;
        font-size:10.0pt;
        font-family:"Times New Roman",serif;
        mso-fareast-language:X-NONE;}
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";}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.CommentTextChar
        {mso-style-name:"Comment Text Char";
        mso-style-priority:99;
        mso-style-link:"Comment Text";
        font-family:"Times New Roman",serif;
        mso-fareast-language:X-NONE;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle24
        {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:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Acceptable to SIS.<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">                                --keith<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cesg-bounces@mailman.ccsds.org [mailto:cesg-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP]<br>
<b>Sent:</b> Tuesday, September 01, 2015 9:02 AM<br>
<b>To:</b> Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory] <peter.m.shames@jpl.nasa.gov>; Gian.Paolo.Calzolari@esa.int<br>
<b>Cc:</b> cesg-bounces@mailman.ccsds.org; howie.weiss@sparta.com; CCSDS CESG -- <cesg@mailman.ccsds.org><br>
<b>Subject:</b> RE: Unspecified Management System: [CESG] Re: Results of CESG Polls closing 14 August 2015<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:.5in;text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Attached is an update that includes the proposed text in 6.1, a simplified overview drawing in 2.2, and adds the 355.1 Extended Procedures
 book to the informative references.  Please indicate whether these changes are acceptable.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Craig<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (312B) [<a href="mailto:peter.m.shames@jpl.nasa.gov">mailto:peter.m.shames@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Monday, August 31, 2015 9:56 AM<br>
<b>To:</b> <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a><br>
<b>Cc:</b> CCSDS CESG --; <a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>; Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP];
<a href="mailto:howie.weiss@sparta.com">howie.weiss@sparta.com</a><br>
<b>Subject:</b> Re: Unspecified Management System: [CESG] Re: Results of CESG Polls closing 14 August 2015<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="margin-left:.5in;text-align:left"><o:p> </o:p></p>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Dear Gippo,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Just to avoid all confusion, this is what I would find acceptable.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">On pg 6-1, Sec 6.1<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Change:</span></b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Through the use of a management system, management conveys the required information to the service provider.<o:p></o:p></span></p>
<div>
<div>
<p class="MsoCommentText" style="margin-left:.5in"><b><span lang="X-NONE" style="color:black">To:</span></b><span lang="X-NONE" style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-family:"Calibri",sans-serif;color:black">These managed parameters are intended to be included in any service provider system that manages security associations, but no specification for such a management system is provided nor implied.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-family:"Calibri",sans-serif;color:black">Regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<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">Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<b>Date: </b>Monday, August 31, 2015 at 3:05 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, "<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>" <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>>,
 "Biggerstaff, Craig(JSC-CD221)[LOCKHEED MARTIN CORP]" <<a href="mailto:craig.biggerstaff@nasa.gov">craig.biggerstaff@nasa.gov</a>>, "<a href="mailto:howie.weiss@sparta.com">howie.weiss@sparta.com</a>" <<a href="mailto:howie.weiss@sparta.com">howie.weiss@sparta.com</a>><br>
<b>Subject: </b>Re: Unspecified Management System: [CESG] Re: Results of CESG Polls closing 14 August 2015<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Dear Peter,
</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">        it is true that the Space Data documents do not specify a management system.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">It is also true that the Space Data documents never claim that they specify a management system.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">In CCSDS 132.0-B-1.3 the term "</span><span style="font-family:"Calibri",sans-serif;color:black">management system</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">"
 is used twice - always in NOTES; i.e. non normative statements - and the second occurrence makes clear that "These parameters are defined in an abstract sense and are not intended to imply any particular implementation of a management system. " Moreover section
 1.2 states that this book does not specify "the management activities required to configure and control the protocol."</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The same is true for CCSDS 232.0-B-2.2.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The same is true for CCSDS 732.0-B-2.3 with the difference that, dislike 132.0 and 232.0, the mentioning in not in NOTES rather in plain text in the (non normative) section named
 "OVERVIEW OF MANAGED PARAMETERS".</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">The same is true for CCSDS 355.0-B-0  with the difference that, dislike 132.0 and 232.0, the first mentioning in not in a NOTE rather in plain text in the (non normative) section
 named "OVERVIEW" while the second one is a note as for 132.0 and 232.0.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">I think all this consistently does "</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">make clear in this section that these are the set of managed
 parameters that are intended to be included in any system that manages security associations, but that no specification for such a system is provided nor implied.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">"</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">So adding a word (i.e. unspecified) in a single book is not necessary and would not cure the problem you see.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Having said this I do continue supporting the WG in rejecting this particular condition at this point in time.</span><span style="font-size:10.5pt;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:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Gian Paolo</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">PS It may be that in the future the WG's will work and agree to e.g. adding an exhaustive non normative annex that explains with more details the limitations and issues you see
 in the current versions.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<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">"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></span><span style="font-size:10.5pt;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:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>,
</span><span style="font-size:10.5pt;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">"CCSDS CESG --" <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>,
 "<a href="mailto:howie.weiss@sparta.com">howie.weiss@sparta.com</a>" <<a href="mailto:howie.weiss@sparta.com">howie.weiss@sparta.com</a>>, "Biggerstaff,        Craig\(JSC-CD221\)\[LOCKHEED MARTIN CORP\]" <<a href="mailto:craig.biggerstaff@nasa.gov">craig.biggerstaff@nasa.gov</a>></span><span style="font-size:10.5pt;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">29/08/2015 01:41</span><span style="font-size:10.5pt;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">Re: Unspecified Management System: [CESG] Re: Results of CESG Polls        closing
 14 August 2015</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black"><a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a></span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:center;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:left;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Ciao Gippo,</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">The issue I have with how this Management System is specified in these documents is that it is not really specified at all as a system.  It is, instead, described in Sec 6 as
 a set of managed parameters.   This is useful, since it does provide the implementer with some concrete guidance on what is expected to be managed and a possible range of values, but it does not constitute a Management System.  There is no spec for the system,
 no defined behavior for the system, and no interfaces for the system, not even in the abstract.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">I would recommend, therefore, that you make clear in this section that these are the set of managed parameters that are intended to be included in any system that manages security
 associations, but that no specification for such a system is provided nor implied.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">CCSDS does indeed provide service systems, interface, and behavioral specifications.  The most prominent of these are the SLE and CSTS, but even the MOIMS SM&C is starting to
 develop system interfaces.  The RASIM also provided a set of abstract system interfaces.  Specs such as CFDP and AMS have defined the service characteristics of a data management service that is intended to do buffer management within the protocol.  I find
 none of the typical characterizations of a system or service interface in this spec, only a set of data items that consititue managed parameters.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">I would not in any way suggest that we list in every spec all the things that they are not.  That would be foolish.  At the same time I think we need to be careful to be clear
 in describing what it is that we do define and what the limitations are.</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Best regards, Peter</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
<br>
</span><b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Gian Paolo Calzolari <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:10.0pt">Gian.Paolo.Calzolari@esa.int</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Date: </b>Friday, August 28, 2015 at 12:39 AM<b><br>
To: </b>Peter Shames <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:10.0pt">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Cc: </b>"Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP]" <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:craig.biggerstaff@nasa.gov"><span style="font-size:10.0pt">craig.biggerstaff@nasa.gov</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 "</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:10.0pt">howie.weiss@sparta.com</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:10.0pt">howie.weiss@sparta.com</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 CCSDS Engineering Steering Group - CESG Exec <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt">cesg@mailman.ccsds.org</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Subject: </b>Unspecified Management System: [CESG] Re: Results of CESG Polls closing 14 August 2015</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Dear Peter,<br>
       I am extremely reluctant to accept your condition about adding the term "unspecified" in front of "management system".</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
First of all Craig motivated the non addition of this term in his WinWord comment stating <</span><span style="font-size:10.0pt;color:black">Using the word 'unspecified' for management in section 6.1 is not consistent with the language used with the SLP BBs.
  Each of the four standards (SDLS, TC, TM, AOS) contains a statement in section 1.2 where the absence of specification for the management activities is stated.  Otherwise, the word 'unspecified' does not show up a single time in TC, TM and AOS BBs.
<br>
The WG prefers to be consistent with the SLP books, and proposes not to add the word 'unspecified' here.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Moreover if we accept this trend than each CCSDS document will need to add the term unspecified in front of whatever is not specified in that document or outside.<br>
It is also not fully true that the management is unspecified, actually chapter 6 itself contains a number of requirement (not all requirements, indeed) to be used when specifying the (agency specific) management system.<br>
Last but not l;east, CCSDS never specifies systems but rather provide standards to be used for a subset (sometimes large) of the systems specification to be issued by a given Agency/Company.</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
So I do recommend keeping consistency within the documents of the SLS Area and not adding the term "unspecified" in front of "management system" and I kindly ask you to withdraw this specific condition.</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Best regards</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
Gian Paolo</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
<br>
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"Shames, Peter M (312B)" <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP]" <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:craig.biggerstaff@nasa.gov"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">craig.biggerstaff@nasa.gov</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">>,
 "Scott, Keith L (9730-Affiliate)" <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:kscott@mitre.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">kscott@mitre.org</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">>,
 "</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">tomaso.decola@dlr.de</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">tomaso.decola@dlr.de</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">>,
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">howie.weiss@sparta.com</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">howie.weiss@sparta.com</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">>,
 "</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">cesg@mailman.ccsds.org</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">cesg@mailman.ccsds.org</span></a></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">></span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">28/08/2015 02:48</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject:        </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:black">[CESG] Re: Results of CESG Polls closing 14 August 2015</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Sent by:        </span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">cesg-bounces@mailman.ccsds.org</span></a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-align:center;line-height:normal">
<span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" align="left" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;text-align:left;line-height:normal">
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
<br>
Dear Craig, et al, <br>
<br>
I have reviewed the proposed changes to the document.  I find all of them acceptable except for one.  I really believe that this document will better represent its functions if a new, simplified, version of "figure 6-1” is included in sec 2.2.2.  This would
 allow you to introduce in a graphical way exactly what this protocol does relative to the three space data link protocols.   You can then point to the protocol specific versions as you have.<br>
</span><span style="font-family:"Calibri",sans-serif;color:black"><br>
And on pg 6-1, sec 6.1 there was a side note about the "management system” being unspecified.  I propose changing the text to read "</span><span style="color:black">Through the use of an out of band and unspecified management system…"</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
<br>
I think that gets the flavor of what you are describing.  Would you agree?<br>
<br>
There is this further loose end having to do with the “still in work” </span><span style="color:black">CCSDS SDLS Extended Procedures recommendation (reference 355.1-B).  </span><span style="font-family:"Calibri",sans-serif;color:black">It is mentioned twice
 in the document in NOTE and overview text.  Since it is not final this is probably appropriate.  Tom Gannett will probably have an opinion about this, but I think you could insert a reference to the Red Book in the non normative references and mark it as [Future}.
  We did that on the SCCS-ARD and no one screamed, and it at least gets a clear reference to the “to be published” standard into the document.</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-family:"Calibri",sans-serif;color:black"><br>
Best regards, Peter</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">
<br>
<br>
<br>
<b><br>
From: </b>"Biggerstaff, Craig (JSC-CD221)[LOCKHEED MARTIN CORP]" <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:craig.biggerstaff@nasa.gov"><span style="font-size:10.0pt">craig.biggerstaff@nasa.gov</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Date: </b>Thursday, August 27, 2015 at 4:16 PM<b><br>
To: </b>Peter Shames <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:10.0pt">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 Keith Scott <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:kscott@mitre.org"><span style="font-size:10.0pt">kscott@mitre.org</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 "</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:10.0pt">tomaso.decola@dlr.de</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:tomaso.decola@dlr.de"><span style="font-size:10.0pt">tomaso.decola@dlr.de</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:10.0pt">cesg@mailman.ccsds.org</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 Gilles Moury <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:10.0pt">Gilles.Moury@cnes.fr</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">>,
 "</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:10.0pt">howie.weiss@sparta.com</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">"
 <</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:howie.weiss@sparta.com"><span style="font-size:10.0pt">howie.weiss@sparta.com</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">><b><br>
Subject: </b>RE: Results of CESG Polls closing 14 August 2015<br>
<br>
Dear ADs/DADs, <br>
<br>
As the book editor of CCSDS 355.1-B-0 'Space Data Link Security Protocol', I have attached proposed text changes that, the WG believes, will resolve your CESG poll conditions.  Please review these changes and let me know if the changes answer your requirements.
  Thank you. <br>
<br>
<br>
<br>
Best regards, <br>
<br>
Craig Biggerstaff <br>
<br>
At 03:37 PM 8/17/2015, CCSDS Secretariat wrote:<br>
CESG E-Poll Identifier: CESG-P-2015-07-001 Approval to publish CCSDS<br>
355.0-B-1, Space Data Link Security Protocol (Blue Book, Issue 1)<br>
Results of CESG poll beginning 31 July 2015 and ending 14 August 2015:<br>
<br>
                 Abstain:  0 (0%) <br>
 Approve Unconditionally:  6 (66.67%) (Merri, Behal, Calzolari,<br>
Moury, Suess, Barton) <br>
 Approve with Conditions:  3 (33.33%) (Shames, Scott, Cola)<br>
 Disapprove with Comment:  0 (0%) <br>
<br>
CONDITIONS/COMMENTS: <br>
<br>
Peter Shames (Approve with Conditions): We need this document to be<br>
published, and soon, but there are still a few inconsistencies that<br>
I believe should be fixed before that happens. There are marked in<br>
the attached text, but I will summarize them here:<br>
<br>
1) The document is missing a really good overview description and<br>
figure showing the relationship of the user provided transfer frame<br>
data field to the secured field. Such figures are in docs like CCSDS 232x0b.<br>
<br>
What you are asking for was originally in the SDLS Red Book but was moved to the TC/TM/AOS Pink Books.  The WG would prefer to reference those books instead of duplicating the overview information.<br>
<br>
<br>
2) related to 1), the term "payload" is defined in sec 1.6, but it<br>
is then not used in any consistent way within the rest of the<br>
document. And the definition of the word "payload" is disjoint from<br>
other CCSDS usage. The word "package" or "user provided data" might be better.<br>
<br>
The use of "Payload" in this document follows its common use within cryptography.  Its meaning within the context of this document has been defined in 1.8, and it is now capitalized as a proper name throughout.  The WG believes this will clear up any confusion.<br>
<br>
<br>
3) The Security Association Management Service, sec 3.4, reads like<br>
Green Book material, not Blue Book. There is not even an abstract<br>
service spec provided and as such it appears to be non-normative<br>
content. The related "Primitives" are not even sketched out, which<br>
makes this section look even more "unfinished".<br>
<br>
The WG's consensus was that specifying only the required Security Association managed parameters was sufficient for 355.0, which the WG wanted to keep 'lightweight'.  The WG did originally consider a set of service primitives covering SA management, but decided
 that including them in the 355.0 core protocol would unduly constrain operations centers to a particular state model for operational key changes and recovery from spacecraft failures, where is not now any consensus to reverse agency-specific approaches.  Those
 subjects were deemed material for the Green Book or else for the SDLS Extended Procedures Blue Book.<br>
<br>
<br>
4) There is a repeated description of "Rollover of the sequence<br>
number could be used to signal the end of the acceptable lifetime of<br>
a cryptographic key", which sounds like specific guidance, but<br>
always appears in a NOTE. This might be better expressed in a real<br>
requirement as a "may". <br>
<br>
The NOTEs have been modified to eliminate any guidance and to refer to the GB.<br>
<br>
<br>
Keith Scott (Approve with Conditions): I concur with Tomaso that a<br>
note stating the non-applicability of this specification to<br>
Proximity-2 communications would be quite helpful.<br>
<br>
Tomaso de Cola (Approve with Conditions): As the book relates to<br>
security implemented in the data link layer of CCSDS protocol stack,<br>
I would expect a note or comment in Section 1 to state that the<br>
scope of the book is limited to AOS, TM, and TC and does not address<br>
Proximity. Finding no mention of proximity leaves some uncertainty<br>
on the overall security implementation in SDLP.<br>
<br>
A statement to this effect has been added to paragraph 2.1.<br>
<br>
<br>
<br>
Note for future book amendments, the green book CCSDS 350.0-G-2 (THE<br>
APPLICATION OF CCSDS PROTOCOLS <br>
TO SECURE SYSTEMS ) will probably require some minor revision to<br>
reflect the changes provided in this blue book, once published.<br>
<br>
<br>
Total Respondents: 9 <br>
No response was received from the following Area(s):<br>
<br>
CSS <br>
<br>
SECRETARIAT INTERPRETATION OF RESULTS:  Approved with Conditions<br>
PROPOSED SECRETARIAT ACTION:            Generate CMC poll after<br>
conditions have been addressed <br>
_______________________________________________<br>
CESG mailing list</span><u><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:blue"><br>
</span></u><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:CESG@mailman.ccsds.org"><span style="font-size:10.0pt">CESG@mailman.ccsds.org</span></a></span><u><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:blue"><br>
</span></u><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="http://mailman.ccsds.org/mailman/listinfo/cesg"><span style="font-size:10.0pt">http://mailman.ccsds.org/mailman/listinfo/cesg</span></a></span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</span><tt><span style="font-size:10.0pt;color:black">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New";color:black"><br>
<tt>CESG mailing list</tt><br>
<tt><a href="mailto:CESG@mailman.ccsds.org">CESG@mailman.ccsds.org</a></tt><br>
</span><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"><a href="http://mailman.ccsds.org/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">http://mailman.ccsds.org/mailman/listinfo/cesg</span></tt></a><o:p></o:p></span></p>
<pre style="margin-left:.5in"><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 style="margin-left:.5in"><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 style="margin-left:.5in"><span style="color:black">content is not permitted.<o:p></o:p></span></pre>
<pre style="margin-left:.5in"><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 style="margin-left:.5in"><span style="color:black">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></span></pre>
<pre style="margin-left:.5in"><span style="color:black"><o:p> </o:p></span></pre>
<pre style="margin-left:.5in"><span style="color:black">Please consider the environment before printing this email.<o:p></o:p></span></pre>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>