Re: [Sigtran] State-machines wrong in the RFC-3332 and RFC-4666 ??!!

["Brian F. G. Bidulock" <[e-mail]>]

Ajay,

Please see comments below:

Ajay Garg wrote:                        (Thu, 13 Mar 2014 12:15:08)
>    1)
>    At [1]https://www.ietf.org/rfc/rfc3332.txt, in the section
>                                   5.1.4 Three ASPs in an Application
>    Server ("n+k" sparing, loadsharing case)
>    should not "Notify (AS-ACTIVE)" be sent to ASP1 and ASP2 (as against
>    ASP2 and ASP3 as per the diagram), since ASP1 and ASP2 are the ones
>    that sent the "ASP Act (Ldshr)" message (and are thus the "n" active
>    ASPs)?

On the first page of RFC 4666 you will see the line: "Obsoletes: 3332".


>    2)
>    At [2]https://tools.ietf.org/html/rfc4666, in the section
>                                  5.1.4 Three ASPs in an Application Server
>    ("n+k" sparing, loadsharing case)
>    why will "Notify (AS-ACTIVE)" be sent to ASP3 (since only ASP1 and ASP2
>    sent the "ASP Act. (Ldshr)" message, and are thus the "n" active ASPs)?
>    Again, sorry if I am missing something very fundamental.

RFC 4666 4.3.4.5 Notify Procedures:

  A Notify message reflecting a change in the AS state MUST be sent to
  all ASPs in the AS, except those in the ASP-DOWN state, with
  appropriate Status information and any ASP identifier of the failed
  ASP.

ASP3 is not in the ASP down state and therefore must be sent the
AS-ACTIVE message.

--brian

-- 
Brian F. G. Bidulock
[e-mail]
http://www.openss7.org/