<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.emailstyle21
{mso-style-name:emailstyle21;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:1787966484;
mso-list-type:hybrid;
mso-list-template-ids:291265136 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;}
@list l1
{mso-list-id:1900045982;
mso-list-template-ids:793652280;}
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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear CESG members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is the background on this CCSDS liaison role situation. There is an analysis attached and some suggestions (in the email below) as to how to handle it. We clearly need some sort of clearly stated liaison role documentation defined,
an appropriate registry recognizing that these are interfaces with two parties, and a process for assigning entries and managing them. We have an awful mish-mash right now. I do not think this needs to be a heavy weight activity.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It also occurs to me that we may want to create a new small registry that actually records these liaison arrangements, including the orgs, their point(s) of contact and ours, the CCSDS organization, etc and maybe even the liaison agreement
itself stating what the agreed scope is.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Feedback? Comments?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Monday, November 16, 2020 at 3:44 PM<br>
<b>To: </b>Brian Oliver <brian.oliver@btas.com><br>
<b>Cc: </b>CCSDS Secretariat <secretariat@mailman.ccsds.org>, Dan Smith <danford.s.smith@nasa.gov>, Steve Townes <stephen.a.townes@jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar@jpl.nasa.gov><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Hi Brian,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I guess we can make almost anything work, so that does not give me much “heartburn”. But here is the real issue. After looking at what we now have I find the following:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Liaison entries where there is just a contact name, no address or affiliation.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Liaison entries where a CCSDS PoC is identified, but not the CCSDS organization that they represent. Some are a WG, some and Area, some all of CCSDS.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Liaison entries where the liaison org is identified, but there is no corresponding CCSDS org or PoC.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Liaison entries where there is a partner org, and a CCSDS PoC, but they are two separate entries.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Liaison entries where there is a partner org, and a CCSDS PoC, but they are marked as “Other Contact” in one entry, and not a separate entry.<o:p></o:p></li></ol>
<p class="MsoListParagraph"> <o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">I printed the existing list and marked all of this stuff as I found it. It would be nice if we adopted some simple, straightforward, approach and followed it. Uniformly.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"> <o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">One thing we could do in the future would be to add a “Liaison PoC” role to the Contact role set and then come up with some agreed way to show CCSDS members with their roles, and the CCSDS orgs they are representing.
It does occur to me that maybe we really need a separate “Liaison agreements registry” that covers all of these variants and points to the Orgs, Contacts, & Roles registries?
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"> <o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">Heck, we could even add the “Liaison Agreement” files to these entries, wouldn’t that be novel?<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"> <o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in">Thanks, Peter<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:0in"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Brian Oliver <brian.oliver@btas.com><br>
<b>Date: </b>Monday, November 16, 2020 at 1:55 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Secretariat <secretariat@mailman.ccsds.org>, Dan Smith <danford.s.smith@nasa.gov>, Steve Townes <stephen.a.townes@jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar@jpl.nasa.gov><br>
<b>Subject: </b>RE: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Peter,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Here is a hack that took only an hour’s worth of work.<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://urldefense.us/v3/__https:/public.ccsds.org/participation/liaisons_new.aspx__;!!PvBDto6Hs4WbVuu7!YZlT0vtt-lR7t350N2vCQoS31kWzlbouzJbARh2xABDupWWOHMBPGeRL_hJbM84QXqoGjgym$">https://public.ccsds.org/participation/liaisons_new.aspx</a></b><o:p></o:p></p>
<p class="MsoNormal">Take a look. I can tweak the name from “Other Contact”? <o:p>
</o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal">What I did was add Fred Slane’s contact information into the “Notes” field on your ISO doppelganger (with evil mustache) contact record in SANA.<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/385__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_TNZEsg_$" target="_BLANK翛">https://sanaregistry.org/r/contacts/records/385</a></b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal">I realize that is NOT the best to implement such a solution, but this approach still only gives us 1 bad record (your doppelganger) then 2 bad records (with another e-mail address for Fred). Plus this was the quickest and easiest way for
me to implement with my existing code. My code is not currently setup to have 2 separate SANA contacts under 1 organization.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Long term, perhaps changes should be made to the SANA and CCSDS website. But, I don’t know the complexity of changes and amount of effort that would take on either sides. IMO - Overall the SANA and CCSDS website integration has been a
huge success. The 9 CCSDS Liaisons are one of those strange occurrences when things don’t align as smoothly as they do with the rest of the roles in SANA.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks!!<o:p></o:p></p>
<p class="MsoNormal">Brian Oliver<o:p></o:p></p>
<p class="MsoNormal">CCSDS IT Tech Support<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:techsupport@mailman.ccsds.org">techsupport@mailman.ccsds.org</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From: </b><a href="mailto:peter.m.shames@jpl.nasa.gov">Shames, Peter M (US 312B)</a><br>
<b>Sent: </b>Monday, November 9, 2020 4:08 PM<br>
<b>To: </b><a href="mailto:brian.oliver@btas.com">Oliver Brian (BTAS)</a><br>
<b>Cc: </b><a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>;
<a href="mailto:danford.s.smith@nasa.gov">Dan Smith</a>; <a href="mailto:stephen.a.townes@jpl.nasa.gov">
Townes, Stephen A (US 9000)</a>; <a href="mailto:sami.w.asmar@jpl.nasa.gov">Asmar, Sami W (US 9110)</a><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page<o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div style="border:dotted #003333 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class="MsoNormal" style="background:white"><b><span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#E47833">WARNING! This email contains a link!</span></b><span style="color:black">
</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="text-indent:12.0pt;background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">This email may be a phishing or spoofing scam and may be unsafe. If you do not know the sender, do not open this email
or click on the link as these can open malicious websites or download Trojan viruses. Immediately delete the message from your Inbox, as well as from your Deleted Items folder.
</span><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="text-align:right;background:white"><i><span style="font-size:10.0pt;font-family:"Times New Roman",serif;color:black">- BTAS IT Services</span></i><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div>
<div>
<p class="MsoNormal"><span class="emailstyle21">Hi Brian,</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"> </span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Can we add Fred Slane as the ISO TC20/SC14 PoC as well. It’s an “interface” which means that there are always two sides. I’m guessing you can treat Fred the same as me. He will have his “home” org and his
SC14 “org”.</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"> </span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">And maybe we need to rethink this whole “liaison role” thing being related to Organizations. I think the relationships ought to be something like this:</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"> </span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 1: org entry</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 1: PoC entry for the org</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 1: liaison relationship to org 2</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"><span lang="FR">Org 1: liaison PoC to org 2</span></span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"><span lang="FR">Contact 1 : name 1</span></span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"><span lang="FR">Contact 1 : org name 1</span></span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"><span lang="FR">Contact 1 : liaison role</span></span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"><span lang="FR"> </span></span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 2: org entry</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 2: PoC entry for the org 2</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 2: liaison relationship to org 1</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Org 2: liaison PoC to org 1</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Contact 2 : name 2</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Contact 2 : org name 2</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Contact 2 : liaison role</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"> </span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">You could, I suppose, even extend this to allow one person to have more than one liaison role. This could be discovered by looking in the Org registry to find all of the PoC entries with the “liaison role”
set. There could be more than one.</span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21"> </span><o:p></o:p></p>
<p class="MsoNormal"><span class="emailstyle21">Thanks, Peter</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Brian Oliver <brian.oliver@btas.com><br>
<b>Date: </b>Monday, November 9, 2020 at 9:40 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Secretariat <secretariat@mailman.ccsds.org>, Dan Smith <danford.s.smith@nasa.gov>, Steve Townes <stephen.a.townes@jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar@jpl.nasa.gov><br>
<b>Subject: </b>RE: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Peter,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The Liaison’s page has been updated!!<o:p></o:p></p>
<p class="MsoNormal">https://public.ccsds.org/participation/liaisons.aspx<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In the SANA the role of a liaison is assigned to the “organization” entry and not the “contact” entry. See here:
<a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/organizations/records/new__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_aNKmQaQ$">
https://sanaregistry.org/r/organizations/records/new</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Then each “contact” in the SANA can only be pointed to 1 “organization”. So for instance Peter Shames is pointed to JPL. It’s a 1 to 1 mapping.<o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/157__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_bG1ii_g$">https://sanaregistry.org/r/contacts/records/157</a>
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So the only workaround I can see with the current implementation of SANA is to have two Peter Shames.
<o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/385__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_TNZEsg_$">https://sanaregistry.org/r/contacts/records/385</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">If you see your doppelganger among town. Be careful!! <o:p>
</o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Brian<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From: </b><a href="mailto:peter.m.shames@jpl.nasa.gov">Shames, Peter M (US 312B)</a><br>
<b>Sent: </b>Monday, November 9, 2020 8:53 AM<br>
<b>To: </b><a href="mailto:brian.oliver@btas.com">Oliver Brian (BTAS)</a><br>
<b>Cc: </b><a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>;
<a href="mailto:danford.s.smith@nasa.gov">Dan Smith</a>; <a href="mailto:stephen.a.townes@jpl.nasa.gov">
Townes, Stephen A (US 9000)</a>; <a href="mailto:sami.w.asmar@jpl.nasa.gov">Asmar, Sami W (US 9110)</a><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page<o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div style="border:dotted #003333 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class="MsoNormal" style="background:white"><b><span style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#E47833">WARNING! This email contains a link!</span></b><span style="color:black">
</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="text-indent:12.0pt;background:white"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">This email may be a phishing or spoofing scam and may be unsafe. If you do not know the sender, do not open this email
or click on the link as these can open malicious websites or download Trojan viruses. Immediately delete the message from your Inbox, as well as from your Deleted Items folder.
</span><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="text-align:right;background:white"><i><span style="font-size:10.0pt;font-family:"Times New Roman",serif;color:black">- BTAS IT Services</span></i><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div>
<div>
<p class="MsoNormal">Hi Brian,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I am sorry, but this seems just weird to me. Many of us have more than one role. Just for instance, I am: a JPL person (my home institution), the SEA AD (a role), the SAWG Chair (a role), a member of the CESG (a role), and a NASA
person (a role). I do not know why it should not be possible for me to also have a Liaison role. If we do not have such a liaison role yet we should create one.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In any event, if it is necessary to create a separate “Contact” who will carry the SC13/SC14 liaison role then make that be
<a href="mailto:pshames@jpl.nasa.gov">pshames@jpl.nasa.gov</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Brian Oliver <brian.oliver@btas.com><br>
<b>Date: </b>Sunday, November 8, 2020 at 6:47 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Secretariat <secretariat@mailman.ccsds.org>, Dan Smith <danford.s.smith@nasa.gov>, Steve Townes <stephen.a.townes@jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar@jpl.nasa.gov><br>
<b>Subject: </b>[EXTERNAL] Re: [Secretariat] CCSDS Liaison page</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Peter,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Forgive me for the delay. The dealy was with 1 to 1 mapping of the organization to each contact in the SANA. To map you with a different organization would force me to change your JPL designation. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I reviewed my code on the CCSDS website, and the JSON extracts from SANA, and I see no current way via programming for a workaround. The OIDs from the SANA need to point to one another from the organization to the contact.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I believe the only reasonable workaround (and SANA did this for someone a while back) is to enter another Peter Shames into the SANA contacts, which would point to this Liasion/Organization. We could either use a non-NASA e-mail address
or perhaps abbreviate your current NASA e-mail address.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Examples: <a href="mailto:peter.shames@jpl.nasa.gov">peter.shames@jpl.nasa.gov</a> or
<a href="mailto:peter.m.shames@nasa.gov">peter.m.shames@nasa.gov</a>. Not sure if those are valid? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks!!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Brian<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Nov 8, 2020, at 1:12 PM, Shames, Peter M (US 312B) via Secretariat <<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Hey guys,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I just checked again. The liaison agreement between CCSDS and ISO TC20/SC14 was approved back on 4/7/2020. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:.5in"><b>CMC-P-2020-03-003 Approval of a CCSDS - ISO TC20/SC13 to ISO TC20/SC14 Liaison</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">At this point this is STILL not listed as a liaison relationship.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Please fix this NOW.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Peter<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica">_______________________________________________<br>
Secretariat mailing list<br>
</span><a href="mailto:Secretariat@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:Helvetica">Secretariat@mailman.ccsds.org</span></a><span style="font-size:9.0pt;font-family:Helvetica"><br>
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/secretariat__;!!PvBDto6Hs4WbVuu7!cZuMxyn7VdczlqqtfH3uPMMKqQBC2hcZCi7ozPjsNaImXbpL9ujVR9EQEsuWozNav4sqQphw$"><span style="font-size:9.0pt;font-family:Helvetica">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/secretariat</span></a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p style="margin-bottom:12.0pt;line-height:10.0pt"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:red">CONFIDENTIALITY NOTICE:
</span><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#666666">The contents of this e-mail message may be privileged, confidential, or otherwise protected against disclosure or dissemination. If you are not the intended recipient of this
message, any dissemination, distribution or copying is strictly prohibited. If you have received this message in error, please delete all copies from your computer system.
</span></i><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p style="margin-bottom:12.0pt;line-height:10.0pt"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:red">CONFIDENTIALITY NOTICE:
</span><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#666666">The contents of this e-mail message may be privileged, confidential, or otherwise protected against disclosure or dissemination. If you are not the intended recipient of this
message, any dissemination, distribution or copying is strictly prohibited. If you have received this message in error, please delete all copies from your computer system.
</span></i><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p style="margin-bottom:12.0pt;line-height:10.0pt"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:red">CONFIDENTIALITY NOTICE:
</span><i><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#666666">The contents of this e-mail message may be privileged, confidential, or otherwise protected against disclosure or dissemination. If you are not the intended recipient of this
message, any dissemination, distribution or copying is strictly prohibited. If you have received this message in error, please delete all copies from your computer system.
</span></i><o:p></o:p></p>
</div>
</body>
</html>