[MOIMS-NAV-EXEC] Request to Delete "Conjunction Data Message Originator" Registry

Thu Jul 5 14:26:56 UTC 2018

Dear David,

We will proceed with the update.

Best regards,
Julien Bernard
Space Assigned Numbers Authority

On 2018-06-29 17:55, Berry, David S (3920) wrote:
> 
> Dear SANA:
> 
> Per the "Next Steps" described below, the CCSDS Editor has now applied the required Corrigendum to the CCSDS Conjunction Data Message standard. All other pre-requisite steps have been completed. At this time I am able to make the final request for SANA Action:
> 
> Please remove the "Conjunction Data Message Originator" registry:  https://sanaregistry.org/r/cdm_originator . 
> 
> Thanks for your support!
> David Berry
> 
> 
> 
> On 1/25/18, 2:54 PM, "Space Assigned Numbers Authority" <info at sanaregistry.org> wrote:
> 
>     David,
>     
>     We have updated the organizations following your comments.
>     We will be waiting for your next request to remove the old registry.
>     
>     Thank you!
>     
>     -- 
>     Best regards,
>     Audric Schiltknecht
>     Space Assigned Numbers Authority
>     
>     On 2018-01-24 19:31, Berry, David S (3920) wrote:
>     > 
>     > Audric:
>     > 
>     > Things look great overall! Thanks so much!  
>     > 
>     > Here are a couple of minor corrections/additions (I didn't have a couple of URLs previously):
>     > 
>     > 1. For "JSPOC", the country is currently "Unspecified". This should be "United States of America".
>     > 
>     > 2. For "NASA Johnson Space Center", I suggest the URL https://www.nasa.gov/centers/johnson/home/index.html (symmetric with other NASA centers).
>     > 
>     > 3. For "COMSPOC", I suggest the URL http://www.agi.com/comspoc 
>     > 
>     > 
>     > Next Steps: Are in my court. I need to work with the CCSDS Editor to change the Conjunction Data Message standard to point to the modified "Organizations" registry. That may take a bit of time. For now, the old "CDM Originator" registry should stay in place, but once the CCSDS Editor has published a Corrigendum to the CDM document, I'll request for SANA to delete the old CDM Originator registry.
>     > 
>     > Regards, and Thanks!
>     > David
>     > 
>     > 
>     > 
>     > 
>     > On 1/24/18, 8:02 AM, "Space Assigned Numbers Authority" <info at sanaregistry.org> wrote:
>     > 
>     >     Dear David,
>     >     
>     >     We have added the new organizations from your document into the registry, and given the CDM
>     >     Originator roles to specified entries.
>     >     Can you please review the organization registry (https://sanaregistry.org/r/organizations) to ensure
>     >     these changes reflect what is specified?
>     >     
>     >     Thank you.
>     >     
>     >     -- 
>     >     Best regards,
>     >     Audric Schiltknecht
>     >     Space Assigned Numbers Authority
>     >     
>     >     On 2017-12-19 18:34, Berry, David S (3920) wrote:
>     >     > Dear SANA Operator:
>     >     > 
>     >     > I have attached a revision to the CDM Originator document I sent on 12-December. It has one new entry for the "Commercial Space Operations Center", which also creates Conjunction Data Messages.
>     >     > 
>     >     > Please use this revised document instead of the original document I sent.
>     >     > 
>     >     > Best Regards,
>     >     > David
>     >     > 
>     >     > 
>     >     > 
>     >     > On 12/12/17, 10:34 AM, "MOIMS-NAV-EXEC on behalf of Berry, David S (3920)" <moims-nav-exec-bounces at mailman.ccsds.org on behalf of david.s.berry at jpl.nasa.gov> wrote:
>     >     > 
>     >     >     Dear SANA Operator:
>     >     >     
>     >     >     The Navigation WG is continuing its effort to phase out the "Conjunction Data Message Originator" registry in the SANA (https://sanaregistry.org/r/cdm_originator ). This is being done as part of Peter Shames' re-engineering effort to eliminate the many role-based registries that contain "organization" related information.
>     >     >     
>     >     >     Thank you for creating the "Conjunction Data Message Originator" role in the "Organization Roles" SANA registry https://sanaregistry.org/r/organization-roles (currently a "Candidate Registry"); this was the first step in our plan detailed below.
>     >     >     
>     >     >     The attached document corresponds to Steps 2 and 3 in the plan detailed in the below message from August 2017 (however, I note that the "Organizations" registry, while listed as an "Approved" registry, still has every entry marked as having a Status of "Provisional", and for some organizations there are multiple entries).
>     >     >     
>     >     >     At any rate, there are several requested changes detailed in the attachment, for your consideration. The plan outlined below provides context for these requests.
>     >     >     
>     >     >     Regards,
>     >     >     David Berry
>     >     >     Chair, CCSDS Navigation WG
>     >     >     
>     >     >     
>     >     >     
>     >     >     On 8/20/17, 5:56 AM, "Berry, David S (3920)" <david.s.berry at jpl.nasa.gov> wrote:
>     >     >     
>     >     >         Dear SANA Operator:
>     >     >         
>     >     >         At Peter Shames' suggestion/request, the CCSDS Navigation WG is in the process of phasing out the current "Conjunction Data Message Originator" registry ( https://sanaregistry.org/r/cdm_originator ).
>     >     >         
>     >     >         Phasing out the existing registry will be a multi-step process, and we are not yet ready eliminate it, but one of the necessary preliminary steps is to add a role to the new "Organization Roles" registry ( https://sanaregistry.org/r/organization-roles ). The new role should be something like "Conjunction Data Message Originator". This role is similar in concept to some of the roles currently in that registry, e.g., "D-DOR Service Provider" and "Relay Service Provider". Organizations that are authorized to create CDMs will ultimately have the new attribute added to their entry in the "Organizations" registry (https://sanaregistry.org/r/organizations/ ). 
>     >     >         
>     >     >         For planning purposes, our process involves:
>     >     >         
>     >     >         1. Creating the "Conjunction Data Message Originator" role in Organization Roles.
>     >     >         2. Ensuring that all organizations currently listed in the existing Conjunction Data Message Originator registry have an entry in the Organizations registry.
>     >     >         3. Adding the new "Conjunction Data Message Originator" role to the Organization entries for those entities identified in the preceding step.
>     >     >         4. Filing a Corrigendum to the CDM Blue Book 508.0-B-1 to reference the new registry structure.
>     >     >         5. Eliminate the existing Conjunction Data Message Originator registry. 
>     >     >         
>     >     >         The request in this email applies to Step 1 in this plan. The Navigation WG is currently collecting the information required for Step 2.
>     >     >         
>     >     >         Regards,
>     >     >         David Berry
>     >     >         Chair, CCSDS Navigation WG 
>     >     >         
>     >     >         
>     >     >     
>     >     >     
>     >     >     
>     >     >     
>     >     >     
>     >     >     
>     >     > 
>     >     
>     >     
>     > 
>     
>     
> 