<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR>
<STYLE>@font-face {
        font-family: MS Mincho;
}
@font-face {
        font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
P.StyleParagraph4Kernat14pt {
        FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
LI.StyleParagraph4Kernat14pt {
        FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
DIV.StyleParagraph4Kernat14pt {
        FONT-SIZE: 12pt; MARGIN: 12pt 0in 0pt; LINE-HEIGHT: 14pt; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
SPAN.EmailStyle18 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
        page: Section1
}
OL {
        MARGIN-BOTTOM: 0in
}
UL {
        MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2>I agree that this is an area that can use some further
refinement. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2>My interpretation was that any receipt of a
valid 'YOU_ARE_DEAD' packet, regardless of status, would be to process it
and cease all AMS activity pending a reconnect command from the
user-application. It's description in 3.1.24 and 4.2.7.4.4 seems to
support this. The "I_AM_STOPPING" message I had viewed as only being valid
during the normal messaging mode. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2>I think the usage of the "I_AM_STOPPING" message being sent
to the node that is inferred to be inactive should be deprecated in favor of
directly sending a 'YOU_ARE_DEAD' message. Any receipt of 'YOU_ARE_DEAD'
from its registrar should then be interpreted as valid.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2>On this topic, re-reading section 4.2.7.4.3, it does
not seem to explicitly state that a message should be transmitted to the
terminated node itself, but rather to every "other" node. Catching up on
my old messages thoug, I see that you already caught this one.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=118005318-10092008><FONT face=Arial
color=#0000ff size=2>- David</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sis-ams-bounces@mailman.ccsds.org
[mailto:sis-ams-bounces@mailman.ccsds.org] <B>On Behalf Of </B>Ray, Timothy J.
(GSFC-583.0)<BR><B>Sent:</B> Wednesday, September 10, 2008 2:02 PM<BR><B>To:</B>
sis-ams@mailman.ccsds.org<BR><B>Subject:</B> [Sis-ams] clarification
needed?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Dear WG members,</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">From an AMS node point-of-view,
there are two incoming MPDUs that tell it to reset to an ‘unregistered’
condition:</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
You-are-dead</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
i-am-stopping (with my own node-id)</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have found it difficult to
determine (with confidence) whether those MPDUs *<B><SPAN
style="FONT-WEIGHT: bold">always</SPAN></B>* cause the reset, or are
context-dependent. For example, suppose a node receives a ‘you-are-dead’
but has not sent a ‘reconnect’? (My interpretation says “ignore it”)
Conversely, suppose a node sends a ‘reconnect’ and then receives an
‘i-am-stopping’ (with its own node-id)? (My interpretation says “reset to
unregistered condition”).</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">My suggestion is that we discuss
this in Berlin and perhaps tighten up the spec.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Tim</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P></DIV></BODY></HTML>