Re: [M3UA] AS state machine sharing between SGPs

"Brian F. G. Bidulock" <[email protected]>
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
Tolga,

Here is one quote.

Asveren, Tolga wrote:                                             (Tue, 15 May 2001 15:06:09)
> Hi,
>  
> I think the below discussion is about whether we need SGP concept or not. Unless we say that they are sharing AS states, I don't see any reason to have the SGP concept (According to me, practically it is the same to say there is no SGP concept or to say every SG consist of one SGP).
> But I believe on the importance of sharing AS states between SGPs.In fact it is for sure, that some information should be shared, on SG level or on ASP level or on both. If as an ASP, which is functioning as standby for some ASs, I receive some AS-DOWN notification message there are two choices. If I know, that all of SGP, I am connected (and also the active ASP for this AS, is connected to) are sharing AS state, then I am sure, the active ASP is not reachable via any of these SGPs (otherwise I wouldn't receive ASDOWN message). So, I don't need to check anything with the other ASP and can send an ASPAC. 
> But, if SGPs are not sharing AS state, then after receiving the ASDOWN, I should check with active ASP to see, whether it is reachable via another SG or not, i.e. this time we should share SG-ASP connectivity per AS basis between ASPs.
> So, I think it is unavoidable sharing states at some level. When I think conceptually, SG is functioning like a router on IP domain, so all of the message routing responsibility should be there, i.e. every SGP, which is serving the same AS should share the AS states. I also agree, that for practical purposes, this will bring more complications to SG-developers. 
>  
>    Regards,
>    Tolga
>  
> 

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.