<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:"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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.ms-sitemapdirectional
{mso-style-name:ms-sitemapdirectional;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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;}
/* List Definitions */
@list l0
{mso-list-id:360665567;
mso-list-template-ids:732202598;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:2014455408;
mso-list-template-ids:-1438499404;}
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="MsoNormal"><span style="color:#1F497D">Tim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the clarification. That was even easier to do.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> css-csts-bounces@mailman.ccsds.org [mailto:css-csts-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Ray, Timothy J. (GSFC-5830)<br>
<b>Sent:</b> Tuesday, March 31, 2015 5:15 PM<br>
<b>To:</b> CCSDS_CSTSWG (css-csts@mailman.ccsds.org)<br>
<b>Subject:</b> Re: [Css-csts] Updated MD-CSTS and RID status document on CWE<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi John,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Thanks for looking at my suggestion. I wasn’t intending to ask for any decompression (but think it is a good idea). I was asking for a consistency in the ORDER in which the five options are listed.
As I see it, currently the five options are listed in the order “1,2,3,4,5” in one section (2.2.3.2) , but in the order “1,2,3,5,4” (I.e. Options 4 and 5 are reversed) in the other two sections (2.2.3.3 and 2.2.3.4).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Tim<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;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="color:black">From: </span></b><span style="color:black">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><br>
<b>Date: </b>Tuesday, March 31, 2015 at 3:25 PM<br>
<b>To: </b>"Ray, Timothy J. (GSFC-5830)" <<a href="mailto:timothy.j.ray@nasa.gov">timothy.j.ray@nasa.gov</a>>, SLE-CSTS <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>><br>
<b>Subject: </b>RE: [Css-csts] Updated MD-CSTS and RID status document on CWE<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Tim,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’ve had the chance to look at your comments and proposal. I’ll note that the pre-Red-1 version of book in the spring of 2014 had lists similar to what you have recommended, but all but the first one (for Cyclic
Report) were collapsed in response to a comment from the WG saying that the MD-CSTS book was too repetitious of the material in the Framework. In response to that comment, I compressed the material in section 2.2.3.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">However, I may have compressed it too much, and there is certainly merit in helping the reader to compare the three procedures through parallel descriptions. So I have put corresponding lists back into the Notification
and Information Query procedure sections (2.2.3.3 and 2.2.3.4). However, these lists are not as descriptive as the one in the Cyclic Report section, under the theory that the more-elaborate description of each of the data types in the Cyclic Report section
provides adequate information for the reader to understand their purposes in the other two procedures.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">One final comment on this – the lists are not completely parallel across all three procedures. Specifically, the Notification procedure does not mention procedure configuration parameter change events, procedure
types, or procedure instance identifiers because none of the MD-CSTS procedures have dynamically-changeable configuration parameters that would result in an event notification.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m in the process of making other changes resulting from Wolfgang’s comments and a few other things that need to be cleaned up, but I hope to have an updated MD-CSTS book out to the WG sometime next week.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for your review and the good suggestion.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">John</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </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 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> Ray, Timothy J. (GSFC-5830) [<a href="mailto:timothy.j.ray@nasa.gov">mailto:timothy.j.ray@nasa.gov</a>]
<br>
<b>Sent:</b> Sunday, March 22, 2015 11:37 PM<br>
<b>To:</b> John Pietras; CCSDS_CSTSWG (<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>)<br>
<b>Subject:</b> Re: [Css-csts] Updated MD-CSTS and RID status document on CWE</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:10.5pt;color:black">Dear CSTS-WG colleagues,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Please forgive me for putting in input so late in the cycle…</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Sections 2.2.3.2 and 2.2.3.3 of the MD-CSTS Red Book include a list of the possibilities for requesting cyclic reporting of parameters and event notifications, respectively. Both sections list
five possibilities. In section 2.2.3.2, these are labeled ‘a)’ through ‘e)’. In section 2.2.3.3, they are contained within a single sentence near the top of page 2-8.</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">It appears that, for each possibility listed in section 2.2.3.2, there is an analogous possibility in section 2.2.3.3:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.5pt">the names of individual monitored parameters (2.2.3.2a), or the names of event names (2.2.3.3).</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.5pt">The labels of monitored parameter types (2.2.3.2b), or event labels (2.2.3.3).</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.5pt">The name of a list of parameter labels (2.2.3.2c), or an event label list (2.2.3.3).</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.5pt">The name of a Functional Resource type (2.2.3.2e), or a Functional Resource type (2.2.3.3).</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<span style="font-size:10.5pt">The name of a specific Functional Resource instance (2.2.3.2d), or a Functional Resource Name (2.2.3.3). (Page 1-8 of the CSTS SFW defines “Functional Resource Name” as “The unique identifier of an instance of a functional resource.
A Functional Resource Name is made of a Functional Resource Type and a Functional Resource Instance Number.”</span><o:p></o:p></li></ol>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">My comment: (assuming that what I have said so far is correct) can we be consistent in the order that the possibilities are presented? For example, this could be done by changing the following
sentence in section 2.2.3.3 from:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">"The START invocation may subscribe to notifiable events by using the names of events names, event labels, an event label list (named or default), a Functional Resource type, or a Functional Resource
Name.”</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">TO:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">"The START invocation may subscribe to notifiable events by using the names of events names, event labels, an event label list (named or default), a Functional Resource Name, or a Functional Resource
type.”</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Note: Section 2.2.3.4 (Query of Parameters) matches section 2.2.3.3. So if we change 2.2.3.3, we should make a corresponding change to 2.2.3.4. (Or we could swap 2.2.3.2d and 2.2.3.2e, and avoid
any need to change 2.2.3.3 and 2.2.3.4).</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Best regards,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Tim</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </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 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><br>
<b>Date: </b>Thursday, March 12, 2015 at 3:45 PM<br>
<b>To: </b>SLE-CSTS <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>><br>
<b>Subject: </b>[Css-csts] Updated MD-CSTS and RID status document on CWE<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">CSTSWG colleagues ---</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">I have uploaded what I believe to be the final draft update of the MD-CSTS Red Book (MD-CSTS-922x1r1_2-150312) to the CWE in the
<a href="http://cwe.ccsds.org/css">Cross Support Services Area (CSS)</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
Documents</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
CSS-CSTS</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
CWE Private</a> > <span class="ms-sitemapdirectional">2 - MD CSTS RED-1 Review material folder, at URL:</span></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><a href="http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_2-150312.doc">http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_2-150312.doc</a></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">This update includes all Red-1 Review RID resolutions, and is also in compliance with Wolfgang’s current working draft of the CSTS SFW.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">I have also uploaded to the same folder the complete set of MD-CSTS RID resolutions (MD-CSTS-Red1-Proposed_RID_Resolutions-150216), which have now been closed. The RID resolutions can be found
at URL:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"><a href="http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-Red1-Proposed_RID_Resolutions-150216.docx">http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-Red1-Proposed_RID_Resolutions-150216.docx</a></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">I’m looking forward to seeing you in Pasadena.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Best regards, </span>
<span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">John </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:16.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:13.5pt;color:black;background:white">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black;background:white"><br>
<a href="https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=s" target="canit_note">Spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=n" target="canit_note">Not spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01O6PEKGN&m=28a88c27811a&c=f" target="canit_note">Forget previous vote</a></span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:13.5pt;color:black;background:white">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black;background:white"><br>
<a href="https://filter.gst.com/canit/b.php?i=01OaljKWn&m=b08bca07da9f&c=s" target="canit_note">Spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01OaljKWn&m=b08bca07da9f&c=n" target="canit_note">Not spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01OaljKWn&m=b08bca07da9f&c=f" target="canit_note">Forget previous vote</a></span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>