[Cesg-all] SANA Registry status

Thu May 19 10:40:58 EDT 2011

follow up:
- spacecraftid copy at SANA site 
(http://sanaregistry.org/c/spacecraftid) is now synched and updated 
based on the source (WDC).
- the copy will now be kept synched as the source is modified.

Regards, Marc.

Le 11-05-12 23:30, Marc Blanchet a écrit :
> Le 11-05-12 16:23, John Garrett a écrit :
>> Hi Peter,
>>
>> I think the version of the GSCID list that is out there is still the
>> same one that was out there at the last meeting and was out of date
>> then.
>
> right. like all candidate registries, no need to keep updates if the
> registry is still a candidate and is waiting for blessing. If we move it
> to a confirmed registry (but with the pointer as today saying that it is
> just a copy and the original is at the url displayed), then we will
> update it with any new data since the time it was put as candidate and
> then keep it in sync moving forward. normal staging policy for registry
> operators.
>
> Marc.
>
> What was there was mostly reasonable, but the actual GSCID
>> register is usually updated several times a month. My understanding was
>> that SANA operator would monitor the authoritative list and would update
>> their lists on their site on a regular basis. I still think it is
>> sufficient for SANA to just point to the authoritative version.
>>
>> See you next week when we can discuss this more.
>>
>> Cheers,
>> -JOhn
>>
>> On 5/12/2011 12:22 PM, Shames, Peter M (313B) wrote:
>>> John,
>>>
>>> This is all true and is what is documented in the SANA Yellow Book.
>>> The SANA has pointers to those registries, and it also has, in one
>>> searchable and identifiable location, the information contained in
>>> those registries. This is as was agreed.
>>>
>>> Please take the time to review the SANA registries and ensure that all
>>> of the information, including the pointers to the authoritative
>>> sources, is accurate. Then approve these registries so that they are
>>> listed in the Approved set.
>>>
>>> Thanks, Peter
>>>
>>>
>>> From: John Garrett <John.G.Garrett at nasa.gov
>>> <mailto:John.G.Garrett at nasa.gov>>
>>> Date: Thu, 12 May 2011 09:18:11 -0700
>>> To: Peter Shames <peter.m.shames at jpl.nasa.gov
>>> <mailto:peter.m.shames at jpl.nasa.gov>>
>>> Cc: CCSDS Engineering Steering Group - CESG All
>>> <cesg-all at mailman.ccsds.org <mailto:cesg-all at mailman.ccsds.org>>, Mike
>>> Kearney <Mike.Kearney at nasa.gov <mailto:Mike.Kearney at nasa.gov>>, "SANA
>>> Steering Group (SSG)" <ssg at mailman.ccsds.org
>>> <mailto:ssg at mailman.ccsds.org>>
>>> Subject: Re: [Cesg-all] SANA Registry status
>>>
>>> Hi Peter,
>>>
>>> As was agreed when we created the SANA, a couple of the registries
>>> were grandfathered in and NSSDC will continue to be the register
>>> for those. The SANA registry is supposed to point to those.
>>>
>>> The two top-level registries grandfathered in are the Spacecraft
>>> ID assignment and the Control Authority Office Assignments
>>> (including the several different pieces that the single registry
>>> was broken up into, such as Member Agency Control Authority Office
>>> Registry and Control Authority Organization Contacts, etc.).
>>>
>>> Cheers,
>>> -JOhn
>>>
>>> On 5/12/2011 11:20 AM, Shames, Peter M (313B) wrote:
>>>> Dear CESG Colleagues,
>>>>
>>>> During the last CCSDS working meetings in London we announced
>>>> that the SANA operator was in place, that the SANA web site now
>>>> exists (http://www.sanaregistry.org) and that there was a set of
>>>> what we called "Candidate Registries" that had been created.
>>>> These candidate registries contain information culled from the
>>>> existing Blue Books in each of your areas. The purpose of the
>>>> SANA, as you know, is to provide a single point of reference for
>>>> all of the CCSDS managed numbers, namespaces, and XML schema. A
>>>> primary intent of the SANA is to provide "one stop shopping" for
>>>> our users as to where to go looking for this information, and
>>>> also to remove the need to produce a Blue Book update, with all
>>>> of the review overhead that entails, in order to update some
>>>> numbers in a table.
>>>>
>>>> This is the list of candidate registries that are now on the web
>>>> site:
>>>>
>>>> Bundle Protocol Compressed Bundle Header Encoding Node Numbers
>>>> <http://www.sanaregistry.org/c/bp_cbhe_node_numbers>
>>>> Bundle Protocol
>>>> <http://www.sanaregistry.org/c/bp_cbhe_service_numbers>Compressed
>>>> Bundle Header Encoding Service Numbers
>>>> <http://www.sanaregistry.org/c/bp_cbhe_service_numbers>
>>>> CCSDS File Delivery Protocol (CFDP) Entity Identifier
>>>> <http://www.sanaregistry.org/c/cfdp_entity_id>
>>>> CCSDS Glossary <http://www.sanaregistry.org/c/glossary>
>>>> CCSDS Object Identifiers (OID) <http://www.sanaregistry.org/c/oid>
>>>> CLCW Version Number
>>>> <http://www.sanaregistry.org/c/clcw_version_number>
>>>> Control Authority Organizations <http://www.sanaregistry.org/c/cao>
>>>> Control Authority Organizations Contacts
>>>> <http://www.sanaregistry.org/c/cao_contacts>
>>>> Extended Protocol Identifiers
>>>> <http://www.sanaregistry.org/c/extended_protocol_id>
>>>> Frame Secondary Header Version Number
>>>> <http://www.sanaregistry.org/c/frame_secondary_header_version_number>
>>>> Internet Protocol Extension Header
>>>> <http://www.sanaregistry.org/c/ipe_header>
>>>> Licklider Transmission Protocol Engine Identifiers
>>>> <http://www.sanaregistry.org/c/ltp_engineid>
>>>> Licklider Transmission Protocol Service Identifiers
>>>> <http://www.sanaregistry.org/c/ltp_serviceid>
>>>> MAP Identifier (MAP ID) <http://www.sanaregistry.org/c/map_id>
>>>> Member Agency Control Authority Office Registries
>>>> <http://www.sanaregistry.org/c/macao>
>>>> Packet Version Number
>>>> <http://www.sanaregistry.org/c/packet_version_number>
>>>> Port Identifier <http://www.sanaregistry.org/c/port_id>
>>>> Protocol Identifier <http://www.sanaregistry.org/c/protocol_id>
>>>> Radio Sources <http://www.sanaregistry.org/c/radio_sources>
>>>> SCPS-NP Domain Identifier (D-ID)
>>>> <http://www.sanaregistry.org/c/scps_np_domain_id>
>>>> SCPS-NP End System Identifier (ES-ID)
>>>> <http://www.sanaregistry.org/c/scps_np_end_system_id>
>>>> SCPS-NP Path Identifier (P-ID)
>>>> <http://www.sanaregistry.org/c/scps_np_path_id>
>>>> SCPS-NP Transport Protocol Identifier (TP-ID)
>>>> <http://www.sanaregistry.org/c/scps_np_transport_protocol_id>
>>>> SCPS-TP Connection Identifier
>>>> <http://www.sanaregistry.org/c/scps_tp_connection_id>
>>>> Space Agencies <http://www.sanaregistry.org/c/agencies>
>>>> Spacecraft Identifiers <http://www.sanaregistry.org/c/spacecraftid>
>>>> Space Link Identifiers Registries
>>>> <http://www.sanaregistry.org/c/space_link_id>
>>>> Space Packet Protocol Application
>>>> <http://www.sanaregistry.org/c/space_packet_protocol_application_process_id>
>>>>
>>>> Process Identifier(APID)
>>>> <http://www.sanaregistry.org/c/space_packet_protocol_application_process_id>
>>>>
>>>>
>>>> Transfer Frame Version Number
>>>> <http://www.sanaregistry.org/c/transfer_frame_version_number>
>>>> Virtual Channel Identifier (VCID)
>>>> <http://www.sanaregistry.org/c/virtual_channel_id>
>>>>
>>>> The SANA operator has done the hard work of combing the CCSDS
>>>> documents to identify those items that should be registered and
>>>> creating these candidate registries. It is the assigned task of
>>>> the Area Directors and individual working groups to review these
>>>> for accuracy and to approve them for release on the SANA web
>>>> site. It will eventually be necessary to provide some sort of WG
>>>> policy statement as to how these registries are to be managed,
>>>> but that is less important at this point than reviewing and
>>>> approving the registries.
>>>>
>>>> And please note, of all of the registries that were identified
>>>> since last fall only one (1) is now an Approved Registry. That is
>>>> the:
>>>>
>>>> Navigation Data Messages XML Schema
>>>> <http://www.sanaregistry.org/r/ndmxml>
>>>>
>>>> Go take a look at this (just click on the link) to see a good
>>>> example of how an XML schema registry may be organized. The XML
>>>> schema that have been standardized in MOIMS SM&C, CSS SM, and
>>>> MOIMS XFDU should be similarly documented and registered. This is
>>>> a task that these working groups will have to take up, but the
>>>> SANA operator will provide assistance. At a minimum at least the
>>>> whole schema should be registered so that our users can reference
>>>> them in one well identified, easy to find, on-line, repository.
>>>>
>>>> Please take some time during this coming week of working meetings
>>>> to at least go look at these candidate registries and make some
>>>> assignments to get them reviewed and approved by the working
>>>> group. It is important to get this done and it is your
>>>> responsibility.
>>>>
>>>> Best regards, Peter
>>>>
>>>> ________________________________________________________
>>>>
>>>> Peter Shames
>>>> CCSDS System Engineering Area Director
>>>>
>>>> Jet Propulsion Laboratory, MS 301-490
>>>> California Institute of Technology
>>>> Pasadena, CA 91109 USA
>>>>
>>>> Telephone: +1 818 354-5740, Fax: +1 818 393-6871
>>>>
>>>> Internet: Peter.M.Shames at jpl.nasa.gov
>>>> ________________________________________________________
>>>>
>>>> We must recognize the strong and undeniable influence that our
>>>> language exerts on our ways of thinking and, in fact, delimits
>>>> the abstract space in which we can formulate - give form to - our
>>>> thoughts.
>>>>
>>>> Niklaus Wirth
>>>>
>>>>
>>
>>
>> _______________________________________________
>> CESG-all mailing list
>> CESG-all at mailman.ccsds.org
>> http://mailman.ccsds.org/mailman/listinfo/cesg-all
>
>

-- 
=========
IETF81 Quebec city: http://ietf81.ca
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN Implementation: http://postellation.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
Space Assigned Number Authority: http://sanaregistry.org