Re: Question about IGMP host implementation

--===============2912125196654431018==
Content-Type: multipart/alternative; boundary=001485f6d9fedcb3ef04af1aca0a

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

Hi Bharat,

              I was thinking on the line of cat3k switches where we can
configure SVIs.

Thanks,
Indranil

On Wed, Oct 12, 2011 at 4:53 PM, Bharat Joshi <[email protected]>wrote:

> How is a switch has two different subnets on its two ports? Typically
> switch divides the broadcast domain. Right?
>
> Regards,
> Bharat
> ________________________________________
> From: [email protected] [[email protected]] On Behalf Of
> Indranil Bhattacharya [[email protected]]
> Sent: Wednesday, October 12, 2011 2:05 PM
> To: Kunal Shah
> Cc: [email protected]
> Subject: Re: [magma] Question about IGMP host implementation
>
> Hi Kunal,
>
>             Yes it should. The scenario that I have in mind is a switch
> whose mrouter interface is in vlanA and igmp joins are received on an
> interface in vlanB. In this case, query coming from vlanA(different subnet)
> has to be answered by hosts in vlanB.
>
> Thanks,
> Indranil
>
> On Wed, Oct 12, 2011 at 6:08 AM, Kunal Shah <[email protected]
> <mailto:[email protected]>> wrote:
> Hi all,
>
> Can an IGMPv2 host respond to a general query originated from a subnet
> other then its own?? RFC 2236 states:
>
> ""query received" occurs when the host receives either a valid
>     General Membership Query message, or a valid Group-Specific
>     Membership Query message.  To be valid, the Query message must be
>     at least 8 octets long, and have a correct IGMP checksum.  The
>     group address in the IGMP header must either be zero (a General
>     Query) or a valid multicast group address (a Group-Specific Query)"
>
> There is no requirement for the source address to be on the same subnet as
> the host.
>
> Thanks,
> Kunal
>
>
> _______________________________________________
> magma mailing list
> [email protected]<mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/magma
>
>
>
> **************** 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***
>

--001485f6d9fedcb3ef04af1aca0a
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 I was thinking on the line of =
cat3k switches where we can configure SVIs.</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Indranil<br><br></div>
<div class=3D"gmail_quote">On Wed, Oct 12, 2011 at 4:53 PM, Bharat Joshi <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">bharat_josh=
[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">How is a switch has two differen=
t subnets on its two ports? Typically switch divides the broadcast domain. =
Right?<br>
<br>Regards,<br>Bharat<br>________________________________________<br>From:=
 <a href=3D"mailto:[email protected]">[email protected]</a> [<a h=
ref=3D"mailto:[email protected]">[email protected]</a>] On Behalf=
 Of Indranil Bhattacharya [<a href=3D"mailto:[email protected]">myse=
[email protected]</a>]<br>
Sent: Wednesday, October 12, 2011 2:05 PM<br>
<div class=3D"im">To: Kunal Shah<br>Cc: <a href=3D"mailto:[email protected]">m=
[email protected]</a><br></div>Subject: Re: [magma] Question about IGMP host im=
plementation<br>
<div class=3D"im"><br>Hi Kunal,<br><br>=A0 =A0 =A0 =A0 =A0 =A0 Yes it shoul=
d. The scenario that I have in mind is a switch whose mrouter interface is =
in vlanA and igmp joins are received on an interface in vlanB. In this case=
, query coming from vlanA(different subnet) has to be answered by hosts in =
vlanB.<br>
<br>Thanks,<br>Indranil<br><br></div>
<div class=3D"im">On Wed, Oct 12, 2011 at 6:08 AM, Kunal Shah &lt;<a href=
=3D"mailto:[email protected]">[email protected]</a>&lt;mailto:<=
a href=3D"mailto:[email protected]">[email protected]</a>&gt;&g=
t; wrote:<br>
Hi all,<br><br>Can an IGMPv2 host respond to a general query originated fro=
m a subnet other then its own?? RFC 2236 states:<br><br>&quot;&quot;query r=
eceived&quot; occurs when the host receives either a valid<br>=A0 =A0 Gener=
al Membership Query message, or a valid Group-Specific<br>
=A0 =A0 Membership Query message. =A0To be valid, the Query message must be=
<br>=A0 =A0 at least 8 octets long, and have a correct IGMP checksum. =A0Th=
e<br>=A0 =A0 group address in the IGMP header must either be zero (a Genera=
l<br>=A0 =A0 Query) or a valid multicast group address (a Group-Specific Qu=
ery)&quot;<br>
<br>There is no requirement for the source address to be on the same subnet=
 as the host.<br><br>Thanks,<br>Kunal<br><br><br>__________________________=
_____________________<br>magma mailing list<br></div><a href=3D"mailto:magm=
[email protected]">[email protected]</a>&lt;mailto:<a href=3D"mailto:[email protected]">=
[email protected]</a>&gt;<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/magma" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/magma</a><br>
<div>
<div></div>
<div class=3D"h5"><br><br><br>**************** CAUTION - Disclaimer *******=
**********<br>This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION =
intended solely<br>for the use of the addressee(s). If you are not the inte=
nded 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>
</div></div></blockquote></div><br>

--001485f6d9fedcb3ef04af1aca0a--

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

--===============2912125196654431018==--