<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Meh ran</div><div>What happens if you have a DTN node at a Ground Station?</div><div>And it is a Ground Station from other Agency in an ABA configuration?</div><div>If the DTN NM info is encapsulated in a TM packet, I do not see any issue</div><div>But if you have a node at the Ground Station there are issues with CSS</div><div>That we need to address</div><div>My suggestion, as CESG Chair,</div><div>Is "discuss the issues"</div><div>Not " do not do it"</div><div>And Meteron is an enabler but does not represent all cases</div><div>And by no way the most complex configurations</div><div>Ciao</div><div>Nestor<br><br>Sent from my iPhone</div><div><br>On 14.10.2014, at 09:17, Mehran Sarkarati <<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>> wrote:<br><br></div><blockquote type="cite"><div>Hi Nestor,<br>
<br>
How does this relate to the question asked by Scott? If I understand correctly, he is asking if they can use the SM&C application layer M&C services (Parameter and Aggregation Service) for retrieving TM items, which are related to DTN-management (e.g. the status of each node, the ping time to the next node, ...)<br>
<br>
I guess at communication layer, for each scenario (deep space or not) an appropriate DTN protocol and convergence layer will be selected but if you want to transfer DTN management telemetry items, it means you are using DTN in the first place, right? As far as the MO services are concerned, what you need to do is to define a communication protocol binding for MAL to whatever DTN protocol you use (e.g. BP or another).<br>
<br>
The METERON case is the proof of concept of how such binding works. For a different deployment a different binding (or encoding) may be needed but the concept is the same.<br>
<br>
So, I think the answer is: Yes you can use the MO Parameter or Aggregation service for doing what you want to do and yes you can bind it to whatever DTN protocol suitable for your deployment, similar to what we have done for METERON.<br>
<br>
But I may be missing something here.<br>
<br>
Kind regards<br>
Mehran<br>
<div class="domino-section"><div class="domino-section-head"><span class="domino-section-title"><font color="#424282">Nestor Peccia---14/10/2014 13:32:46---From: Nestor Peccia/esoc/ESA To: Mehran Sarkarati/esoc/ESA@esa,</font></span></div><div class="domino-section-body"><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2">Nestor Peccia/esoc/ESA</font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2">Mehran Sarkarati/esoc/ESA@esa, </font><br>
<font size="2" color="#5F5F5F">Cc: </font><font size="2">Mario Merri/esoc/ESA@esa, "<a href="mailto:moims-sc-bounces@mailman.ccsds.org">moims-sc-bounces@mailman.ccsds.org</a>" <<a href="mailto:moims-sc-bounces@mailman.ccsds.org">moims-sc-bounces@mailman.ccsds.org</a>>, "Barkley, Erik J (317H)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>, "Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>, "<a href="mailto:moims-sc@mailman.ccsds.org">moims-sc@mailman.ccsds.org</a>" <<a href="mailto:moims-sc@mailman.ccsds.org">moims-sc@mailman.ccsds.org</a>></font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">14/10/2014 13:32</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [Moims-sc] Re: Would SM&C have a few hours to discuss network management?</font><br>
<hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; "><br>
<br>
<br>
<font size="4">We must analyze potential issues with SIS and CSS</font><br>
<font size="4">Meteron configuration is not similar to a deep space or L2 cross support scenario<br>
<br>
Sent from my iPhone</font><br>
<font size="4"><br>
On 14.10.2014, at 06:37, </font><a href="mailto:Mehran.Sarkarati@esa.int"><u><font size="4" color="#0000FF">Mehran.Sarkarati@esa.int</font></u></a><font size="4"> wrote:<br>
</font>
<ul>
<ul>Hi Scott, Mario,<font size="4"> <br>
</font><br>
If I may add one more detail, which may be of interest to Scott:<font size="4"> <br>
</font><br>
In the context of the METERON project, ESA has already implemented, deployed and operationally validated some of the MO M&C services to publish a various set of TM parameters (which were not Spacecraft related but for instance related to the health status of a laptop and even the status of a button on particular software running on that laptop on the ISS) using DTN BP at communication layer (we used ION 2.3 and are currently updating to ION 3.2).<font size="4"> <br>
</font><br>
We have also implemented a so called BPPing Agent, which was deployed on each DTN node and periodically pinged other nodes. The results of the BPPings were then published to all intersted listeners (our M&C system instances) using again the related MO M&C Parameter service.<font size="4"> <br>
</font><br>
In practice, the mentioned M&C service were used to publish and receive the TM parameters encoded in binary over BP over Channel Protocol (the convergence layer below BP) from ISS to the ground. The exact same implementation of these services (same code at run-time) had published a second endpoint to provide the same functionality via a different protocol (XML encoding over HTTP) on the ground.<font size="4"> <br>
</font><br>
So basically two set of different consumers have used the same services to retrieve the TM, using the communication protocol of their choice. If you are interested, I can prepare a presentation for the discussion session. I have added Sebastian in cc, who is our DTN expert, in case of DTN specific questions.<font size="4"> <br>
</font><br>
Kind Regards<font size="4"> </font><br>
Mehran<font size="4"> <br>
<br>
<br>
</font><font size="2" color="#5F5F5F"><br>
From: </font><a href="mailto:Mario.Merri@esa.int"><u><font size="2" color="#0000FF">Mario.Merri@esa.int</font></u></a><font size="4"> </font><font size="2" color="#5F5F5F"><br>
To: </font><font size="2">"Scott, Keith L." <</font><a href="mailto:kscott@mitre.org"><u><font size="2" color="#0000FF">kscott@mitre.org</font></u></a><font size="2">>, </font><font size="2" color="#5F5F5F"><br>
Cc: </font><font size="2">"Barkley, Erik J \(317H\)" <</font><a href="mailto:erik.j.barkley@jpl.nasa.gov"><u><font size="2" color="#0000FF">erik.j.barkley@jpl.nasa.gov</font></u></a><font size="2">>, </font><a href="mailto:moims-sc@mailman.ccsds.org"><u><font size="2" color="#0000FF">moims-sc@mailman.ccsds.org</font></u></a><font size="4"> </font><font size="2" color="#5F5F5F"><br>
Date: </font><font size="2">14/10/2014 11:21</font><font size="4"> </font><font size="2" color="#5F5F5F"><br>
Subject: </font><font size="2">[Moims-sc] Re: Would SM&C have a few hours to discuss network management?</font><font size="4"> </font><font size="2" color="#5F5F5F"><br>
Sent by: </font><a href="mailto:moims-sc-bounces@mailman.ccsds.org"><u><font size="2" color="#0000FF">moims-sc-bounces@mailman.ccsds.org</font></u></a><font size="4"> <br>
</font><hr width="100%" size="2" align="left" noshade=""><font size="4"><br>
<br>
</font><font face="Arial"><br>
Hi Keith,</font><font size="4"> </font><font face="Arial"><br>
<br>
I have earmarked a 2h joint meeting with SIS-DTN in the agenda of SM&C WG starting at 13:30 of Thu 13Nov. Is that OK?</font><font size="4"> </font><font face="Arial"><br>
<br>
Without pre-emptying the discussion, the MO SM&C Services provide a coherent set of services to monitor and control *any* remote (controllable) object, not necessarily only as spacecraft. The operations of these services are defined in an abstract manner (via the MAL). For a specific deployment, and here I am touching on your question on "how those parameters are encoded and transported, the abstract services need to be mapped to a concrete encoding/transport. This is achieved by a dedicated blue book at the level of MAL.</font><font size="4"> </font><font face="Arial"><br>
<br>
The bottom line is that</font><font size="4"> </font><font face="Arial"><br>
- one can use the MO M&C services to monitor and control any remote object</font><font size="4"> </font><font face="Arial"><br>
- one can select the most appropriate encoding/transport for its deployment of these services.</font><font size="4"> </font><font face="Arial"><br>
<br>
I hope the above helps. How do you want to play the joint meeting? For instance, would you like to send us in advance a set of questions that you would like to be addressed?</font><font size="4"> </font><font face="Arial"><br>
<br>
Thanks</font><font size="4"> </font><font face="Arial"><br>
<br>
__Mario</font><font size="4"> <br>
<br>
</font><font size="2" color="#5F5F5F"><br>
<br>
From: </font><font size="2">"Scott, Keith L." <</font><a href="mailto:kscott@mitre.org"><u><font size="2" color="#0000FF">kscott@mitre.org</font></u></a><font size="2">></font><font size="4"> </font><font size="2" color="#5F5F5F"><br>
To: </font><font size="2">"</font><a href="mailto:Mario.Merri@esa.int"><u><font size="2" color="#0000FF">Mario.Merri@esa.int</font></u></a><font size="2">" <</font><a href="mailto:Mario.Merri@esa.int"><u><font size="2" color="#0000FF">Mario.Merri@esa.int</font></u></a><font size="2">>, "Barkley, Erik J (317H)" <</font><a href="mailto:erik.j.barkley@jpl.nasa.gov"><u><font size="2" color="#0000FF">erik.j.barkley@jpl.nasa.gov</font></u></a><font size="2">>, </font><font size="2" color="#5F5F5F"><br>
Cc: </font><font size="2">"</font><a href="mailto:roger.thompson@scisys.co.uk"><u><font size="2" color="#0000FF">roger.thompson@scisys.co.uk</font></u></a><font size="2">" <</font><a href="mailto:roger.thompson@scisys.co.uk"><u><font size="2" color="#0000FF">roger.thompson@scisys.co.uk</font></u></a><font size="2">></font><font size="4"> </font><font size="2" color="#5F5F5F"><br>
Date: </font><font size="2">13/10/2014 20:09</font><font size="4"> </font><font size="2" color="#5F5F5F"><br>
Subject: </font><font size="2">Would SM&C have a few hours to discuss network management?</font><font size="4"> <br>
</font><hr width="100%" size="2" align="left" noshade=""><font size="4"><br>
</font><font size="5" face="Calibri"><br>
<br>
The SIS-DTN working group is about to start doing some work in the network management for the BP layers of the stack. Would it be possible for us to get a few hours together with SM&C to talk about the interaction between the monitor and control services and what we (think we) need for DTN network management? I’m thinking just an hour or two for the two WGs to exchange their views of what’s going on would be really helpful to us.</font><font size="4"> <br>
</font><font size="5" face="Calibri"><br>
>From my interpretation of the 522.1-R-3 book, the MO SM&C Services provides a framework for (general-purpose) monitor and control, which is tailored towards spacecraft. *</font><b><font size="5" face="Calibri">IF</font></b><font size="5" face="Calibri">* I understand correctly, a way for e.g. Bundle Protocol network management could ‘plug in’ to SM&C with a set of ‘drivers’ for the spacecraft to monitor / control the various BP parameters of interest according to the various SM&C services. [Is that a completely broken characterization?] There’s then a question of how those parameters are encoded and transported.</font><font size="4"> <br>
</font><font size="5" face="Calibri"><br>
Sometime Thursday (PM?) of the CCSDS meetings would be best for the SIS-DTN WG, but we’re meeting Thursday and Friday and if that wouldn’t work, I’ll find some other time.</font><font size="4"> <br>
</font><font size="5" face="Calibri"><br>
I know that Erik and the CSS groups are interested in talking with you as well, and that would be a good time for them.</font><font size="4"> <br>
<br>
</font><font size="5" face="Calibri"><br>
--keith</font><font size="4"> <br>
</font><tt><font size="4"><br>
This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.</font></tt><tt><br>
_______________________________________________<br>
Moims-sc mailing list</tt><tt><u><font color="#0000FF"><br>
</font></u></tt><a href="mailto:Moims-sc@mailman.ccsds.org"><tt><u><font color="#0000FF">Moims-sc@mailman.ccsds.org</font></u></tt></a><u><font size="4" color="#0000FF"><br>
</font></u><a href="http://mailman.ccsds.org/mailman/listinfo/moims-sc"><tt><u><font color="#0000FF">http://mailman.ccsds.org/mailman/listinfo/moims-sc</font></u></tt></a><font size="4"><br>
</font><br>
<tt><font size="4">This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</font></tt><br>
<tt><font size="4">_______________________________________________<br>
Moims-sc mailing list<br>
</font></tt><a href="mailto:Moims-sc@mailman.ccsds.org"><tt><u><font size="4" color="#0000FF">Moims-sc@mailman.ccsds.org</font></u></tt></a><tt><font size="4"><br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/moims-sc"><tt><u><font size="4" color="#0000FF">http://mailman.ccsds.org/mailman/listinfo/moims-sc</font></u></tt></a><tt><font size="4"><br>
</font></tt></ul>
</ul>
</div></div></div></blockquote><PRE>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.
</PRE></body></html>