[CESG] FW: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

Tue Nov 17 19:52:39 UTC 2020

Dear CESG members,

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.

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.

Feedback?  Comments?

Thanks, Peter

From: Peter Shames <peter.m.shames at jpl.nasa.gov>
Date: Monday, November 16, 2020 at 3:44 PM
To: Brian Oliver <brian.oliver at btas.com>
Cc: CCSDS Secretariat <secretariat at mailman.ccsds.org>, Dan Smith <danford.s.smith at nasa.gov>, Steve Townes <stephen.a.townes at jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar at jpl.nasa.gov>
Subject: Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

Hi Brian,

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:

  1.  Liaison  entries where there is just a contact name, no address or affiliation.
  2.  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.
  3.  Liaison entries where the liaison org is identified, but there is no corresponding CCSDS org or PoC.
  4.  Liaison entries where there is a partner org, and a CCSDS PoC, but they are two separate entries.
  5.  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.

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.

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?

Heck, we could even add the “Liaison Agreement” files to these entries, wouldn’t that be novel?

Thanks, Peter

From: Brian Oliver <brian.oliver at btas.com>
Date: Monday, November 16, 2020 at 1:55 PM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>
Cc: CCSDS Secretariat <secretariat at mailman.ccsds.org>, Dan Smith <danford.s.smith at nasa.gov>, Steve Townes <stephen.a.townes at jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar at jpl.nasa.gov>
Subject: RE: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

Peter,

Here is a hack that took only an hour’s worth of work.
https://public.ccsds.org/participation/liaisons_new.aspx<https://urldefense.us/v3/__https:/public.ccsds.org/participation/liaisons_new.aspx__;!!PvBDto6Hs4WbVuu7!YZlT0vtt-lR7t350N2vCQoS31kWzlbouzJbARh2xABDupWWOHMBPGeRL_hJbM84QXqoGjgym$>
Take a look.  I can tweak the name from “Other Contact”?

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.
https://sanaregistry.org/r/contacts/records/385<https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/385__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_TNZEsg_$>

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.

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.

Thanks!!
Brian Oliver
CCSDS IT Tech Support
techsupport at mailman.ccsds.org<mailto:techsupport at mailman.ccsds.org>

From: Shames, Peter M (US 312B)<mailto:peter.m.shames at jpl.nasa.gov>
Sent: Monday, November 9, 2020 4:08 PM
To: Oliver Brian (BTAS)<mailto:brian.oliver at btas.com>
Cc: secretariat at mailman.ccsds.org<mailto:secretariat at mailman.ccsds.org>; Dan Smith<mailto:danford.s.smith at nasa.gov>; Townes, Stephen A (US 9000)<mailto:stephen.a.townes at jpl.nasa.gov>; Asmar, Sami W (US 9110)<mailto:sami.w.asmar at jpl.nasa.gov>
Subject: Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

WARNING! This email contains a link!
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.
- BTAS IT Services
________________________________
Hi Brian,

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”.

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:

Org 1:  org entry
Org 1: PoC entry for the org
Org 1: liaison relationship to org 2
Org 1: liaison PoC to org 2
Contact 1 : name 1
Contact 1 : org name 1
Contact 1 : liaison role

Org 2:  org entry
Org 2: PoC entry for the org 2
Org 2: liaison relationship to org 1
Org 2: liaison PoC to org 1
Contact 2 : name 2
Contact 2 : org name 2
Contact 2 : liaison role

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.

Thanks, Peter

From: Brian Oliver <brian.oliver at btas.com>
Date: Monday, November 9, 2020 at 9:40 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>
Cc: CCSDS Secretariat <secretariat at mailman.ccsds.org>, Dan Smith <danford.s.smith at nasa.gov>, Steve Townes <stephen.a.townes at jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar at jpl.nasa.gov>
Subject: RE: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

Peter,

The Liaison’s page has been updated!!
https://public.ccsds.org/participation/liaisons.aspx

In the SANA the role of a liaison is assigned to the “organization” entry and not the “contact” entry.   See here: https://sanaregistry.org/r/organizations/records/new<https://urldefense.us/v3/__https:/sanaregistry.org/r/organizations/records/new__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_aNKmQaQ$>

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.
https://sanaregistry.org/r/contacts/records/157<https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/157__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_bG1ii_g$>

So the only workaround I can see with the current implementation of SANA is to have two Peter Shames.
https://sanaregistry.org/r/contacts/records/385<https://urldefense.us/v3/__https:/sanaregistry.org/r/contacts/records/385__;!!PvBDto6Hs4WbVuu7!fLN-13krwaHnSS6gUXiRSvjaYc8jspEHOH2uliTKHmJn9R1_e7gyLaHg_PiECu6g_TNZEsg_$>

If you see your doppelganger among town.  Be careful!!

Thanks,

Brian

From: Shames, Peter M (US 312B)<mailto:peter.m.shames at jpl.nasa.gov>
Sent: Monday, November 9, 2020 8:53 AM
To: Oliver Brian (BTAS)<mailto:brian.oliver at btas.com>
Cc: secretariat at mailman.ccsds.org<mailto:secretariat at mailman.ccsds.org>; Dan Smith<mailto:danford.s.smith at nasa.gov>; Townes, Stephen A (US 9000)<mailto:stephen.a.townes at jpl.nasa.gov>; Asmar, Sami W (US 9110)<mailto:sami.w.asmar at jpl.nasa.gov>
Subject: Re: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

WARNING! This email contains a link!
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.
- BTAS IT Services
________________________________
Hi Brian,

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.

In  any event,  if it is necessary  to create  a separate “Contact” who will  carry the SC13/SC14 liaison role then make that be pshames at jpl.nasa.gov<mailto:pshames at jpl.nasa.gov>.

Thanks, Peter

From: Brian Oliver <brian.oliver at btas.com>
Date: Sunday, November 8, 2020 at 6:47 PM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>
Cc: CCSDS Secretariat <secretariat at mailman.ccsds.org>, Dan Smith <danford.s.smith at nasa.gov>, Steve Townes <stephen.a.townes at jpl.nasa.gov>, "Asmar, Sami W (US 9110)" <sami.w.asmar at jpl.nasa.gov>
Subject: [EXTERNAL] Re: [Secretariat] CCSDS Liaison page

Peter,

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.

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.

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.

Examples: peter.shames at jpl.nasa.gov<mailto:peter.shames at jpl.nasa.gov> or peter.m.shames at nasa.gov<mailto:peter.m.shames at nasa.gov>.  Not sure if those are valid?

Thanks!!

Brian

On Nov 8, 2020, at 1:12 PM, Shames, Peter M (US 312B) via Secretariat <secretariat at mailman.ccsds.org<mailto:secretariat at mailman.ccsds.org>> wrote:

Hey guys,

I just checked again.  The liaison agreement between CCSDS and ISO TC20/SC14 was approved back on 4/7/2020.

CMC-P-2020-03-003 Approval of a CCSDS - ISO TC20/SC13 to ISO TC20/SC14 Liaison

At this point this is STILL not listed as a liaison relationship.

Please fix this NOW.

Peter

_______________________________________________
Secretariat mailing list
Secretariat at mailman.ccsds.org<mailto:Secretariat at mailman.ccsds.org>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/secretariat<https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/secretariat__;!!PvBDto6Hs4WbVuu7!cZuMxyn7VdczlqqtfH3uPMMKqQBC2hcZCi7ozPjsNaImXbpL9ujVR9EQEsuWozNav4sqQphw$>

________________________________

CONFIDENTIALITY NOTICE: 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.

________________________________

CONFIDENTIALITY NOTICE: 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.

________________________________

CONFIDENTIALITY NOTICE: 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20201117/c69c4cdf/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CCSDS.org - Liaison Organizations & Notes 16Nov20.pdf
Type: application/pdf
Size: 72495 bytes
Desc: CCSDS.org - Liaison Organizations & Notes 16Nov20.pdf
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20201117/c69c4cdf/attachment-0001.pdf>