Re: Query on querier version in IGMPv3

--===============1638502714==
Content-Type: multipart/alternative; boundary=001485e98b36fefdc1048bb92584

--001485e98b36fefdc1048bb92584
Content-Type: text/plain; charset=ISO-8859-1

Hi Bharat,

              Do not lower the querier version. Let the v2 updates's it
querier timer from v3 query or let it use it's configured query interval.
Otherwise, the reselection can happen after every General query.

Thanks,
Indranil

On Mon, Jul 19, 2010 at 10:39 AM, Bharat Joshi <[email protected]>wrote:

> Hi All,
>
>      I was re-reading RFC 3376 for handling compatibility for lower version
> of querier.
>
>      In section 7.3.1, it is mentioned that a querier configured to run in
> V3 mode
>      should lower its version when it sees a lower version query on the
> same
>      network. From that time onwards, a router should send the lower
> version
>      queries.
>
>      Now the question is, when this router should revert back to its
> configured higher
>      version? The text in section 7.3.1 or elsewhere does not talk about
> this.
>
>      Should a timer 'lower_version_querier' be started and updated as and
> when lower
>      version queries are removed? Please note this is not same as
> other-querier-present
>      timer.
>
>      Can someone, who has implemented IGMPv3, let me know how this
> particular case
>      has been handled in their implementation?
>
> Regards,
> Bharat
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely
> for the use of the addressee(s). If you are not the intended recipient,
> please
> notify the sender by e-mail and delete the original message. Further, you
> are not
> to copy, disclose, or distribute this e-mail or its contents to any other
> person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has
> taken
> every reasonable precaution to minimize this risk, but is not liable for
> any damage
> you may sustain as a result of any virus in this e-mail. You should carry
> out your
> own virus checks before opening the e-mail or attachment. Infosys reserves
> the
> right to monitor and review the content of all messages sent to or from
> this e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> _______________________________________________
> magma mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/magma
>

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

<div>Hi Bharat,</div>
<div>=A0</div>
<div>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Do not lower the querier versi=
on. Let the v2 updates&#39;s it querier timer from v3 query or let it use i=
t&#39;s configured query interval. Otherwise, the reselection can happen af=
ter every General query.</div>

<div>=A0</div>
<div>Thanks,</div>
<div>Indranil<br><br></div>
<div class=3D"gmail_quote">On Mon, Jul 19, 2010 at 10:39 AM, Bharat Joshi <=
span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">bharat_jos=
[email protected]</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Hi All,<br><br>=A0 =A0 =A0I was =
re-reading RFC 3376 for handling compatibility for lower version of querier=
.<br>
<br>=A0 =A0 =A0In section 7.3.1, it is mentioned that a querier configured =
to run in V3 mode<br>=A0 =A0 =A0should lower its version when it sees a low=
er version query on the same<br>=A0 =A0 =A0network. From that time onwards,=
 a router should send the lower version<br>
=A0 =A0 =A0queries.<br><br>=A0 =A0 =A0Now the question is, when this router=
 should revert back to its configured higher<br>=A0 =A0 =A0version? The tex=
t in section 7.3.1 or elsewhere does not talk about this.<br><br>=A0 =A0 =
=A0Should a timer &#39;lower_version_querier&#39; be started and updated as=
 and when lower<br>
=A0 =A0 =A0version queries are removed? Please note this is not same as oth=
er-querier-present<br>=A0 =A0 =A0timer.<br><br>=A0 =A0 =A0Can someone, who =
has implemented IGMPv3, let me know how this particular case<br>=A0 =A0 =A0=
has been handled in their implementation?<br>
<br>Regards,<br>Bharat<br>**************** CAUTION - Disclaimer ***********=
******<br>This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION inte=
nded solely<br>for the use of the addressee(s). If you are not the intended=
 recipient, please<br>
notify the sender by e-mail and delete the original message. Further, you a=
re not<br>to copy, disclose, or distribute this e-mail or its contents to a=
ny other person and<br>any such actions are unlawful. This e-mail may conta=
in viruses. Infosys has taken<br>
every reasonable precaution to minimize this risk, but is not liable for an=
y damage<br>you may sustain as a result of any virus in this e-mail. You sh=
ould carry out your<br>own virus checks before opening the e-mail or attach=
ment. Infosys reserves the<br>
right to monitor and review the content of all messages sent to or from thi=
s e-mail<br>address. Messages sent to or from this e-mail address may be st=
ored on the<br>Infosys e-mail system.<br>***INFOSYS******** End of Disclaim=
er ********INFOSYS***<br>
_______________________________________________<br>magma mailing list<br><a=
 href=3D"mailto:[email protected]">[email protected]</a><br><a href=3D"https://ww=
w.ietf.org/mailman/listinfo/magma" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/magma</a><br>
</blockquote></div><br>

--001485e98b36fefdc1048bb92584--

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

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

--===============1638502714==--