Re: Re: M3UA : How to deal whit Unexpected ASPSM/ASTM Message (Jacky Chen)

Thanks,brain
your anser:

1) Quite simply, when the ASP receives an unsolicited ASP Inactive Ack
message
it places the ASP in the ASP-INACTIVE State for the AS indicated in the ASP
Inactive Ack message.  If the ASP was not already in the ASP-INACTIVE State
for the AS indicated in the unsolicited ASP Inactive Ack message, then the
ASP should initiate steps to return the ASP to the previous state for the
AS.
If that previous state was ASP-DOWN (for _all_ AS), the way to initiate
returning the ASP to the appropriate state for the AS is to send an ASP
Down
message.

 my question:
    jack chen:if do as you say,Then One unsolicited ASP Inactive Ack(for
one AS) message will affet all AS(s)'s
status,it is good idea?

2)  Completely reasonable: the SGP is required to send ASP Up Ack in
response to ASP Up, in which case the ASP Up Ack is always expected
by the ASP, cf. RFC 4666 4.3.4.1.  The only reason for an unexpected
ASP Up Ack is some sort of error, in which case the procedure will
attempt to properly resynchronize state.

   my question:
    jack chen:because it is unexpected message,we can not think it is
expected message just only of sort ?!

    maybe because of the error of the sgp' softward code.
       so I think ASP should make itself stronger and not to  affect all
AS's Status.