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

--===============8821775625050220446==
Content-Type: multipart/alternative; boundary=001a1133048a7f972204f477ca46

--001a1133048a7f972204f477ca46
Content-Type: text/plain; charset=ISO-8859-1

Thanks Brian for the quick reply.


On Thu, Mar 13, 2014 at 12:36 PM, Brian F. G. Bidulock <[email protected]
> wrote:

> 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".
>

:)
We are in the process of moving to the new release of the stack provided by
our vendor (right now, the stack uses M3UA in accordance with RFC 3332).

For purely academic purposes, I guess that here too "Notify (AS-ACTIVE)"
would be sent to all the ASPs (as per your reply to my second query, and
RFC-3332 also has the same "Notify Procedures")?





>
>
> >    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.
>


Thanks Brian ... !!!!



Thanks a ton Brian for the clarifications !!




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



-- 
Regards,
Ajay

--001a1133048a7f972204f477ca46
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Brian for the quick reply.<br><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Mar 13, 2014 at 12:36 PM, =
Brian F. G. Bidulock <span dir=3D"ltr">&lt;<a href=3D"mailto:bidulock@opens=
s7.org" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">Ajay,<br>
<br>
Please see comments below:<br>
<br>
Ajay Garg wrote: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(Thu, 13 Ma=
r 2014 12:15:08)<br>
&gt; =A0 =A01)<br>
&gt; =A0 =A0At [1]<a href=3D"https://www.ietf.org/rfc/rfc3332.txt" target=
=3D"_blank">https://www.ietf.org/rfc/rfc3332.txt</a>, in the section<br>
<div class=3D"">&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 5.1.4 Three ASPs in an Application<br>
&gt; =A0 =A0Server (&quot;n+k&quot; sparing, loadsharing case)<br>
&gt; =A0 =A0should not &quot;Notify (AS-ACTIVE)&quot; be sent to ASP1 and A=
SP2 (as against<br>
&gt; =A0 =A0ASP2 and ASP3 as per the diagram), since ASP1 and ASP2 are the =
ones<br>
&gt; =A0 =A0that sent the &quot;ASP Act (Ldshr)&quot; message (and are thus=
 the &quot;n&quot; active<br>
&gt; =A0 =A0ASPs)?<br>
<br>
</div>On the first page of RFC 4666 you will see the line: &quot;Obsoletes:=
 3332&quot;.<br></blockquote><div><br>:) <br></div><div>We are in the proce=
ss of moving to the new release of the stack provided by our vendor (right =
now, the stack uses M3UA in accordance with RFC 3332).<br>
<br></div><div>For purely academic purposes, I guess that here too &quot;No=
tify (AS-ACTIVE)&quot; would be sent to all the ASPs (as per your reply to =
my second query, and RFC-3332 also has the same &quot;Notify Procedures&quo=
t;)?<br>
<br></div><div><br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">
<br>
<br>
&gt; =A0 =A02)<br>
&gt; =A0 =A0At [2]<a href=3D"https://tools.ietf.org/html/rfc4666" target=3D=
"_blank">https://tools.ietf.org/html/rfc4666</a>, in the section<br>
<div class=3D"">&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A05.1.4 Three ASPs in an Application Server<br>
&gt; =A0 =A0(&quot;n+k&quot; sparing, loadsharing case)<br>
&gt; =A0 =A0why will &quot;Notify (AS-ACTIVE)&quot; be sent to ASP3 (since =
only ASP1 and ASP2<br>
&gt; =A0 =A0sent the &quot;ASP Act. (Ldshr)&quot; message, and are thus the=
 &quot;n&quot; active ASPs)?<br>
&gt; =A0 =A0Again, sorry if I am missing something very fundamental.<br>
<br>
</div>RFC 4666 4.3.4.5 Notify Procedures:<br>
<br>
=A0 A Notify message reflecting a change in the AS state MUST be sent to<br=
>
=A0 all ASPs in the AS, except those in the ASP-DOWN state, with<br>
=A0 appropriate Status information and any ASP identifier of the failed<br>
=A0 ASP.<br>
<br>
ASP3 is not in the ASP down state and therefore must be sent the<br>
AS-ACTIVE message.<br></blockquote><div><br><br></div><div>Thanks Brian ...=
 !!!!<br><br><br><br></div><div>Thanks a ton Brian for the clarifications !=
!<br><br></div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">

<span class=3D""><font color=3D"#888888"><br>
--brian<br>
<br>
--<br>
Brian F. G. Bidulock<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"http://www.openss7.org/" target=3D"_blank">http://www.openss7.or=
g/</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><br>-- <br>Regards,<=
br>Ajay<br>
</div></div>

--001a1133048a7f972204f477ca46--


--===============8821775625050220446==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran

--===============8821775625050220446==--