[CNST] Draft CNSA Concept

Kearney, Mike W. (MSFC-EO01) Mike.Kearney at nasa.gov
Thu Jul 26 16:23:14 EDT 2007


Overall, excellent.   Nice to have a policy statement for something.  

 

These are not critical, so I'm sending this out for Adrian's
consideration, rather than tying up the telecon.  

 

1st section item #4 could use a greater emphasis on international
cross-support, and clarify that it's not only at the RF level but at the
level of service management and various data packet levels (SLE, AOS,
IP, etc.).  

 

1st section item #5 should conclude with "sharing with other
organizations and agencies".  

 

2nd section item #3 - should we recognize that it's the NASA section of
an international catalogue?   

 

2nd section item #5 - Not sure this is necessary to spell out in this
document, but it is important to understand that for anything that we
*don't* get plugged into the international catalogue as a core service,
if NASA asks an international party for that service, they'll say "No".
(Like IP in HDLC frames, etc.)  That's why this is important for NASA to
pay attention to.  Sort of a rationale statement.  

 

3rd section item #1 - Should add "...and by which NASA and SCaN
negotiates for services from other agencies".  

 

In the 3rd section, I was thinking that there should be some statement
about where the official list of standards is, for which waivers are
required.  At least say "For any function which is covered by a CCSDS
standard, compliance is required."  Obviously, we can't require
compliance with draft standards or WG activities that aren't settled
yet.  Option 1 is to point to an ISO9000-like online SCaN library or web
page.  Option 2 is to simply say compliance is required for any blue
book on the CCSDS website.  I guess Option 3 is to leave it
intentionally ambiguous and not address it here.  Considering all those,
I lean towards Option 2 (any blue book).  

 

   -=- Mike

 

Mike Kearney

NASA MSFC EO-01

256-544-2029

 

 

-----Original Message-----
From: cnst-bounces at mailman.ccsds.org
[mailto:cnst-bounces at mailman.ccsds.org] On Behalf Of Adrian J. Hooke
Sent: Thursday, July 26, 2007 1:09 PM
To: Fred Brosi
Cc: NASA Consolidated Network Services Team
Subject: Re: [CNST] Draft CNSA Concept

 

Folks: attached for your comment is a  draft policy that would establish
the management basis for SCaN's adoption of the Consolidated Network
Services Architecture approach.

 

If such a policy was in place, the concept paper that was drafted by
Fred and sent out on Monday would then become the "statement of
approach" that outlines the long-term vision, snapshots where we are
now, and identifies how to begin the transition. Please review it as
such and let's discuss on this afternoon's telecon:

 

12:30 PDT/14:30 CDT/15:30 EDT

818-354-3434

MEETING ID: 7226

 

My observation is that we need to do a bang-up job on pages 6, 7 in
terms of identifying what we have now versus what we want soon, so that
people can see the near-term impact.

 

It's clear from my discussions at HQ this week that we will need to
extensively socialize these concepts with the SCaN staff. So I will need
an update of this paper from Fred which very clearly establishes our
approach. I will then update the presentation material, add the draft
policy, and then start briefing the 3-way package.

 

///a

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cnst/attachments/20070726/914aac1b/attachment.htm


More information about the CNST mailing list