Re: M3UA notify message

Nitin,

Haresign Lincoln wrote:                                           (Thu, 23 Feb 2006 10:19:46)
> Nitin,
> 
> For the first scenario, I would think that the ASP is either:
> 
> 1) Configured at the SG (perhaps with IP addresses)
> 2) Is sending an ASPID to the SG. 
> 
> In this way, the SG can see that the ASUP/ACPAC are coming from the same
> ASP as the ASPID MUST be unique within the AS.  Therefore, the SG
> properly manages the state of the AS and ASP.

I agree with Lincoln here.  This scenario was already discussed on the list.
The SG in scenario 1 is plain behaving incorrectly.

> 
> For the second scenario, I would say the data message should be dropped
> and an error return since the ASP/SGP2 state machine has not been
> properly completed.

The spec says that an ASP should not send data from an AS before it has
received ASP Active Ack for the AS or it will risk message loss.  The
ASP is risking message loss because it has not done so.  The SG can drop
or process the message at its discretion.

> 
> For scenario three, once one ASP is active to one SGP, the AS is active.

The third case depends on the value of n and k, which you did not provide.
If n is 1 and k is 1 then the AS is active.

In general I don't think that these flows (except perhaps the last one)
illustrate AS/ASP state coordination, but, instead, other provisions
in the RFC (such as ASP Id).

--brian


-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/