[Sis-ams] minor heartbeat-related issue

[Edell, David J.]

I ran into a similar issue when finishing my implementation.  
 
I believe the intent was for the reply method to be inferred from the
transport service in that case--meaning that this is a piece of data
missing in the AMS content itself.  In my case, I think the node-id was
included which I used in the absence of TS specified context to infer
the reply address in the APL implementation for unregistered nodes
(which uses a direct mapping). I don't remember if/how I had addressed
this for an unregistered registrar.  
 
- David
 
 


________________________________

From: sis-ams-bounces at mailman.ccsds.org
[mailto:sis-ams-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J.
(GSFC-583.0)
Sent: Wednesday, July 09, 2008 2:51 PM
To: sis-ams at mailman.ccsds.org
Subject: [Sis-ams] minor heartbeat-related issue



Dear WG members,

 

(Scott:  thanks for posting the latest specs, and for keeping them
up-to-date.)

 

Here's another issue that I've run into.  Perhaps I am missing
something?

 

4.2.7.4.4 - If a server receives a 'heartbeat' from an unregistered
registrar, it is supposed to send back a 'you-are-dead'.  In order to do
that, it will need to know how to contact the registrar (i.e. its
mams-endpoint-name).  That name is not included in the 'heartbeat'.  How
can a server send an MPDU to an unregistered registrar?

 

4.2.7.4.5 - Same as previous, but registrar receives a heartbeat from an
unregistered node.

 

Tim

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-ams/attachments/20080709/6dc1e0dd/attachment.htm