[Smwg] Service Management - Standard Header.

[Tuttle, Karen L. (GRC-MSC0)]

Will do.
Karen
-- 
Karen L. Tuttle
NASA GRC Space Communications & Navigation (SCaN) Standards Manager
216 308-6922 (Cell)





On 11/18/14 11:31 AM, "Barkley, Erik J (3970)"
<erik.j.barkley at jpl.nasa.gov> wrote:

>Colin,
>
>I will take a better look at this (multi-tasking at CESG meeting), but my
>quick comments are:
>
>1) There may not be an end time?   For example,  would it make sense to
>have an end time for configuration profile?
>2) Status sounds/looks good but maybe we want to run through all the
>information entities methodically to see if there is some other status
>needed?   Conversely maybe there are some restrictions...e.g, not sure
>that provisional accountability data makes the most sense (why publish
>the data if you don' mean it) -- so that might actually be "corrected"
>status (if a mistake was made in the output).
>
>
>With regard to srvMessageType, it seems reasonable to register that as an
>overall extensibility consideration  with the first 19 types (info
>entities in green book) as the first set.  But lets start tracking the
>various registry types we have?
>
>Karen,
>
>Perhaps that can be added to the inter-recommendation tracking
>spreadsheet.
>
>Best regards,
>
>-Erik
>
>
>-----Original Message-----
>From: smwg-bounces at mailman.ccsds.org
>[mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Colin.Haddow at esa.int
>Sent: Tuesday, November 18, 2014 8:09 AM
>To: CCSDS Service Mgmt WG
>Subject: [Smwg] Service Management - Standard Header.
>
>
>Dear all,
>                 please find attached the first pass at the Service
>Management Standard Header for your comments. In defining this I've found
>myself with a couple of points;
>
>   Do we want to have a SANA registry holding the values permitted for
>   the"srvMgtMessageType", or is it better just to define the required
>values
>   where the messages are defined (NOTE I'm using message in the widest
>sense
>   here such that it can be taken to encompass files). ?
>   Do we just want one generalised description of the Standard Header
>   somewhere or do we want to tailor the description for each message ?
>
>Cheers for now,
>
>Colin
>
>(See attached file: SM Standard Header i0r0DraftA.doc)
>
>--------------------------------------------------------------------------
>-------------------------------
>
>Dr. Colin R. Haddow,
>HSO-GI, European Space Agency,
>European Space Operations Centre,
>Robert-Bosch-Str 5,
>64293 Darmstadt,
>Germany.
>
>Phone; +49 6151 90 2896
>Fax;      +49 6151 90 3010
>E-Mail;  colin.haddow at esa.int
>--------------------------------------------------------------------------
>-------------------------------
>
>This message and any attachments are intended for the use of the
>addressee or addressees only.
>The unauthorised disclosure, use, dissemination or copying (either in
>whole or in part) of its content is not permitted.
>If you received this message in error, please notify the sender and
>delete it from your system.
>Emails can be altered and their integrity cannot be guaranteed by the
>sender.
>
>Please consider the environment before printing this email.
>
>
>_______________________________________________
>Smwg mailing list
>Smwg at mailman.ccsds.org
>http://mailman.ccsds.org/mailman/listinfo/smwg