[CESG] SANA interface updates in process - FW: [EXTERNAL] short summary for SSA design

Fri Aug 14 18:40:28 UTC 2020

Excellent.  Thanks Mike.  It seemed like such a nice fit.

Regards, Peter

From: Michael Blackwood <MBlackwood at asrcfederal.com>
Date: Friday, August 14, 2020 at 7:49 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov>, David Berry <david.s.berry at jpl.nasa.gov>
Cc: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org>, James Border <james.s.border at jpl.nasa.gov>, "SANA Steering Group (SSG)" <ssg at mailman.ccsds.org>
Subject: RE: SANA interface updates in process - FW: [EXTERNAL] short summary for SSA design

Hi Peter, Marc, et al,

I agree with David that this is a great idea and should be straightforward to implement. I don’t see any problems with this process and registry. I have spoken with Brian Oliver and we are both happy to maintain the contents of the registry.

Best regards,

Michael Blackwood
CCSDS Secretariat
W: 301-837-3901 | michael.blackwood at asrcfederal.com<mailto:michael.blackwood at asrcfederal.com>
7515 Mission Drive, Seabrook, MD 20706
ASRC Federal | Customer-Focused. Operationally Excellent.

From: Secretariat <secretariat-bounces at mailman.ccsds.org> On Behalf Of Shames, Peter M (US 312B) via Secretariat
Sent: Wednesday, August 12, 2020 2:57 PM
To: Berry, David S (US 3920) <david.s.berry at jpl.nasa.gov>
Cc: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org>; CCSDS Secretariat <secretariat at mailman.ccsds.org>; Border, James S (US 335D) <james.s.border at jpl.nasa.gov>; SANA Steering Group (SSG) <ssg at mailman.ccsds.org>
Subject: Re: [Secretariat] SANA interface updates in process - FW: [EXTERNAL] short summary for SSA design

[External Email]
________________________________
Hi David,

Thanks for taking a look at this.  You identified the key "hook" for controlling access and then missed its significance.

Your SANA ID, is exactly ("David Berry [1.3.112.4.2.184]<https://urldefense.proofpoint.com/v2/url?u=https-3A__beta.sanaregistry.org_r_contacts_records_184&d=DwMGaQ&c=Ff2GokX4A_6S-cy_JRNEiQ&r=nsI9dACK1FmwdtL-UmMWiHLWwD3k0OykltBFCmrMSrI&m=qxz4sV9420yPOvBekNbc3b98M6HaHgPRO3M9pbuLar8&s=bm5oWG2zA2bcD6t1CphBUf5xcNbPjhPN3YjBOBpYTgs&e=>").  That OID is associated with you when your "identity" is created in the SANA Contacts registry.   When a SANA login is created, it is tied to that SANA ID and you get a password.  That password is (by intention) different from the CWE password, and it provides access to any SANA functions that require a login.  Once this new WG Registry is created the existence of your name in that registry, associated with the name "Nav WG" is what allows you to login and modify Nav WG controlled registries.

Make sense?

Thanks, Peter

From: David Berry <david.s.berry at jpl.nasa.gov<mailto:david.s.berry at jpl.nasa.gov>>
Date: Wednesday, August 12, 2020 at 11:31 AM
To: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Subject: Re: SANA interface updates in process - FW: [EXTERNAL] short summary for SSA design

Peter:

I don't have any issues with this arrangement. It seems fine to me. At first I had a question as to what login would be used (email address? CWE ID?), but then I saw that there's a way to create a "SANA ID". There also does not appear to be a way in the Working Group registry to associate the named user ("David Berry [1.3.112.4.2.184]<https://urldefense.proofpoint.com/v2/url?u=https-3A__beta.sanaregistry.org_r_contacts_records_184&d=DwMGaQ&c=Ff2GokX4A_6S-cy_JRNEiQ&r=nsI9dACK1FmwdtL-UmMWiHLWwD3k0OykltBFCmrMSrI&m=qxz4sV9420yPOvBekNbc3b98M6HaHgPRO3M9pbuLar8&s=bm5oWG2zA2bcD6t1CphBUf5xcNbPjhPN3YjBOBpYTgs&e=>" in my case) to a SANA ID (unless there's something under the covers that we can't see in the record's details).

Conceptually, though, I like this.

David

From: "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Date: Tuesday, August 11, 2020 at 1:36 PM
To: "SANA Steering Group (SSG)" <ssg at mailman.ccsds.org<mailto:ssg at mailman.ccsds.org>>, CCSDS Secretariat <secretariat at mailman.ccsds.org<mailto:secretariat at mailman.ccsds.org>>, CESG <cesg-bounces at mailman.ccsds.org<mailto:cesg-bounces at mailman.ccsds.org>>, David Berry <david.s.berry at jpl.nasa.gov<mailto:david.s.berry at jpl.nasa.gov>>, "Border, James S (US 335D)" <james.s.border at jpl.nasa.gov<mailto:james.s.border at jpl.nasa.gov>>
Subject: SANA interface updates in process - FW: [EXTERNAL] short summary for SSA design

Dear SSG, CCSDS Secretariat, CESG, and key CCSDS leads,

As was mentioned a while back, the SANA Operator has been funded specifically to develop a new interfaces for certain registries that were designed to be updated by Area Directors or WG chairs.  We have a few of these registries already, such as those in the CSS area, or some of the Nav WG registries.  What we do not yet have is a good way for the SANA Operator to associate a designation, such a "updated by Nav WG chair" with the person who currently has that role.  In the RMP we created Roles for Contacts that allowed us to indicate that a given Contact had the WG Chair role, but not which WG that was for.

Now we are fixing that.

Please review this description and ensure that you see no problems.  This is in Google Docs, but you can download a read-only copy and make any needed edits using MS Word.  Please review and provide feedback no later than a week from now, 18 Aug.  This does the following:

1)      Creates a new WG Chair registry, identifying the WG name and the Contact name that currently holds that WG Chair (or deputy) role.

2)      There will be entries in this registry for other "chair" roles like SSG and any other special groups or SIGS.

3)      Creates a new CESG registry, identifying the Area name and the Contact name that currently holds that AD role.

4)      There will be entries in this registry for other "chair" roles like CESG chair and deputy.

5)      The entries in this registry will be made by the Secretariat staff, since they already manage the polling machinery that approves these positions and must manage that info on the CCSDS website.

There is a separate doc relating to the SS&A registry, and access by the authorized Agency Representatives, that will follow shortly.

Thanks, Peter

From: Marc Blanchet <marc.blanchet at viagenie.ca<mailto:marc.blanchet at viagenie.ca>>
Date: Tuesday, August 11, 2020 at 12:58 PM
To: Peter Shames <peter.m.shames at jpl.nasa.gov<mailto:peter.m.shames at jpl.nasa.gov>>
Cc: Space Assigned Numbers Authority <info at sanaregistry.org<mailto:info at sanaregistry.org>>
Subject: Re: [EXTERNAL] short summary for SSA design

On 11 Aug 2020, at 14:36, Shames, Peter M (US 312B) wrote:

Hi Marc and team,

Sorry for the delay in getting back to you.  I have been swamped with
other stuff.  That said, I did look at what you wrote and it generally
seems to be headed in exactly the right direction.  I did download the
two docs and provide some mark-ups.

updated the WG-Area one. New link to be shared to anybody you want to
get comments:

https://docs.google.com/document/d/1EiQHTSPbnEAIIKKYxfYm2tFXWSc8e-h-YYkmbqOvcgo/edit?usp=sharing<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1EiQHTSPbnEAIIKKYxfYm2tFXWSc8e-2Dh-2DYYkmbqOvcgo_edit-3Fusp-3Dsharing&d=DwMGaQ&c=Ff2GokX4A_6S-cy_JRNEiQ&r=nsI9dACK1FmwdtL-UmMWiHLWwD3k0OykltBFCmrMSrI&m=qxz4sV9420yPOvBekNbc3b98M6HaHgPRO3M9pbuLar8&s=Hrd0457jPwJ830LWKxqz-JLE99l6wRtGsNRnVNE069c&e=>

The SS&A one, in particular, needs some work, but that should not be a
surprise.

will look into this one.

________________________________

The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20200814/ea1db123/attachment-0001.htm>