Re: M3UA notify message
"nitin" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <000501c63b9b$c60083d0$2c01a8c0@Nitinnew> |
Please consider a scenario :- Configuration of AS ---------> ASP1 + ASP2 in Override Mode Configuration of SG----------> SGP1 + SGP2 ASP1 ASP2 SGP1 SGP2 |-------ASP UP.------------>| | |<-------ASPUP ACK. -------| | |<-------Notify AS Inact. ------| | | | | | |--------ASP UP.----------------------------> |<---------ASP UP. ACK.---------------------| | | ASP UP | | | |----------------> | | |<---ASP UPACK.| | |-------ASP AC.--------------->| | |<--------ASP AC. ACK--------| | | | | | |<----------Who will Send Notify AS Active SGP1 or SGP2------------------ | | | 1. Who will Send notify message in this case and to whom . 1. SGP1 will give notify AS Active to ASP1 and ASP2. 2. SGP2 will given notify to ASP2 and SGP1 to ASP1. 2. This is a simple case , but there can be many cases in which it is difficult to identify who is responsible for sending notify messages. For example , if this case Suppose ASP2 is inactive at SGP2 and not SGP1 , then SGP1 cannot send notify to ASP1 . So is there a general rule to do it or is it implementation dependent ? thanks nitin ----- Original Message ----- From: "Brian F. G. Bidulock" <[email protected]> To: "Tolga Asveren" <[email protected]> Cc: <[email protected]> Sent: Saturday, February 25, 2006 5:54 AM Subject: Re: [Sigtran] M3UA notify message > Tolga, > > Already drawn, see my previous messages on this thread. > > --brian > > Tolga Asveren wrote: (Fri, 24 Feb 2006 18:24:42) > > Brian, > > > > Could you draw the message exchange between ASPs and SGPs you would expect > > for this scenario? > > > > Thanks, > > Tolga > > > > -- > Brian F. G. Bidulock > [email protected] > http://www.openss7.org/ > > _______________________________________________ > Sigtran mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/sigtran > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.375 / Virus Database: 268.1.0/269 - Release Date: 2/24/2006 > >