[Css-csts] Re: CCSDS - CSTS - SANA Object Identifier Registration

[Yves.Doat at esa.int]

That's correct for the update.

Apart from the update we have to clarify who allocate numbers directly under:
iso.identified-organization.standards-producing-organization.ccsds
Does this need to be addressed with SEA?

Regards
Yves



                                                                                                                                   
  From:       Marc Blanchet <marc.blanchet at viagenie.ca>                                                                            
                                                                                                                                   
  To:         Yves.Doat at esa.int                                                                                                    
                                                                                                                                   
  Cc:         css-csts at mailman.ccsds.org                                                                                           
                                                                                                                                   
  Date:       20/05/2011 09:15                                                                                                     
                                                                                                                                   
  Subject:    Re: CCSDS - CSTS - SANA Object Identifier Registration                                                               
                                                                                                                                   





Le 11-05-20 09:06, Yves.Doat at esa.int a écrit :
> Dear Marc,
>
> To limit the scope of responsibility looks ok to me but we should also
> include the SLE branch which is also under CSTS responsibility.

ok. therefore, the
iso.identified-organization.standards-producing-organization.ccsds.csts
and the
iso.identified-organization.standards-producing-organization.ccsds.space-link-extension

will be under the policy that you described below. correct?

>
> Having said that, we should also be clear who is responsible for the other
> branches.

There are currently no other branches than csts and
space-link-extension. So the remaining question is for the parent space
and this would be a CCSDS level discussion. correct?

Regards, Marc.


>
> Best regards
> Yves
>
>
>
>    From:       Marc Blanchet<marc.blanchet at viagenie.ca>
>
>    To:         Yves.Doat at esa.int
>
>    Cc:         css-csts at mailman.ccsds.org
>
>    Date:       19/05/2011 15:54
>
>    Subject:    Re: CCSDS - CSTS - SANA Object Identifier Registration
>
>
>
>
>
>
> actually, I would change a bit:
> - the approval by the CSTS wg chair should be for the sub-tree that the
> CSTS maintains, not the whole CCSDS tree.
> - Therefore, the policy you are proposing should be for the
>
> iso.identified-organization.standards-producing-organization.ccsds.csts
> sub-tree?
> - the iso.identified-organization.standards-producing-organization.ccsds
> tree would be CCSDSblue for now until the CCSDS says otherwise.
>
> Do you agree?
>
> Regards, Marc.
>
> Le 11-05-19 15:33, Yves.Doat at esa.int a écrit :
>> Dear Marc,
>>
>> The Working Group reviewed the registration policy and the text on the
SANA
>> site.
>> Please find below the proposed text for the Web site under "registration
>> policy".
>>
>> The current text states:
>>     Requests to add, change or delete assignments to this registry must
come
>>     from a Blue book recommendation produced by the Consultative Committee
> for
>>     Space Data Systems(CCSDS).
>>
>> The new proposed text would be:
>>     Requests to add assignments to this registry shall be submitted to
SANA
> and
>>     come from
>>          a member Agency, or
>>          an observer Agency,  or
>>          a CCSDS Associates, or
>>          an industry partner supported by a member Agency
>>     The request shall be related to a cross support activity.
>>     After evaluation of the request and approval by the CSTS WG chair or a
>>     person duly authorized by her/him, a new Object Identifier will be
>>     allocated and added to the existing list.
>>
>> The link on the page "http://sanaregistry.org/c/oid/oid.html" should be
>> rephrased from "CCSDSblue" to "Object Identifier registration"
>>
>> Please let us know if the proposal is agreeable to you.
>>
>> Best regards
>> Yves
>
>
> --
> =========
> 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
>


--
=========
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