Re: A question on multicast states in non-querier

--===============1856834622==
Content-Type: multipart/alternative; boundary=0016364d29257ec94c049c39699d

--0016364d29257ec94c049c39699d
Content-Type: text/plain; charset=ISO-8859-1

Hi Bharat,

              You are right. DR will use the database. It is necessary
because in LAN DR is seldom the querier. DR election is based on highest ip
address whereas querier election is based on lowest ip address.

Thanks,
Indranil

On Mon, Feb 14, 2011 at 10:31 AM, Bharat Joshi <[email protected]>wrote:

> Hi All,
>
>      If there are two IGMP routers on a LAN, one of them gets elected as
> querier and another as non-querier.
>
>      The querier sends query and hosts on that LAN reply with the reports.
> Querier sees those report and create a database. Non-querier also sees those
> report and would create the same database.
>
>      Question is whether Multicast routing protocol running on
> non-querier's upstream interface should use this database to join/leave the
> multicast group or not?
>
>      IIRC, it is required because the DR for that LAN could be the
> non-querier router and if we do not join upstream, multicast data won't flow
> to this router. Is this a correct thinking?
>
> 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
>

--0016364d29257ec94c049c39699d
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 You are right. DR will use the=
 database. It is necessary because in LAN DR is seldom the=A0querier. DR el=
ection is based on highest ip address whereas querier election is based on =
lowest ip address.</div>

<div>=A0</div>
<div>Thanks,</div>
<div>Indranil=A0<br><br></div>
<div class=3D"gmail_quote">On Mon, Feb 14, 2011 at 10:31 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 =A0If the=
re are two IGMP routers on a LAN, one of them gets elected as querier and a=
nother as non-querier.<br>
<br>=A0 =A0 =A0The querier sends query and hosts on that LAN reply with the=
 reports. Querier sees those report and create a database. Non-querier also=
 sees those report and would create the same database.<br><br>=A0 =A0 =A0Qu=
estion is whether Multicast routing protocol running on non-querier&#39;s u=
pstream interface should use this database to join/leave the multicast grou=
p or not?<br>
<br>=A0 =A0 =A0IIRC, it is required because the DR for that LAN could be th=
e non-querier router and if we do not join upstream, multicast data won&#39=
;t flow to this router. Is this a correct thinking?<br><br>Regards,<br>Bhar=
at<br>
**************** CAUTION - Disclaimer *****************<br>This e-mail cont=
ains PRIVILEGED AND CONFIDENTIAL INFORMATION intended 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>

--0016364d29257ec94c049c39699d--

--===============1856834622==
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

--===============1856834622==--