Re: MLDv2 router in the presence of MLDv1 Multicast Address Listeners

--===============1124031581==
Content-Type: multipart/alternative; boundary=001636426cd766e7550491379c43

--001636426cd766e7550491379c43
Content-Type: text/plain; charset=ISO-8859-1

Hi Kiyoaki Kawaguchi,

                                Yes, I would think so. Otherwise there is a
possibility of some sources getting deleted. When MLDv1 receiver is present
in the LAN, this will not be acceptable.

Thanks,
Indranil

On Mon, Sep 27, 2010 at 8:46 AM, K.Kawaguchi <[email protected]> wrote:

> Hi all,
>
> I have a simple question for MLDv2 interoperation with MLDv1.
>
>
> RFC3810
> ---
> 8.3.  Multicast Router Behavior
>
> 8.3.2.  In the Presence of MLDv1 Multicast Address Listeners
>
>   MLDv2 BLOCK messages are ignored, as are source-lists in TO_EX()
>   messages (i.e., any TO_EX() message is treated as TO_EX( {} )).  On
>   the other hand, the Querier continues to send MLDv2 queries,
>   regardless of its Multicast Address Compatibility Mode.
> ---
>
>
> Is the follwing a correct right too?
>
>   "Any IS_EX() message is treated as IS_EX( {} )."
>
>
> Best Regards
> --
> Kiyoaki Kawaguchi
>
>
> _______________________________________________
> magma mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/magma
>

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

<div>Hi Kiyoaki Kawaguchi,</div>
<div>=A0</div>
<div>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 Yes, I would think so. Otherwise there is a possib=
ility of some sources getting deleted. When MLDv1 receiver is present in th=
e LAN, this will not be acceptable.</div>
<div>=A0</div>
<div>Thanks,</div>
<div>Indranil<br><br></div>
<div class=3D"gmail_quote">On Mon, Sep 27, 2010 at 8:46 AM, K.Kawaguchi <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">kawaguti@ysknet=
.co.jp</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>I have a simple q=
uestion for MLDv2 interoperation with MLDv1.<br><br><br>RFC3810<br>---<br>
8.3. =A0Multicast Router Behavior<br><br>8.3.2. =A0In the Presence of MLDv1=
 Multicast Address Listeners<br><br>=A0 MLDv2 BLOCK messages are ignored, a=
s are source-lists in TO_EX()<br>=A0 messages (i.e., any TO_EX() message is=
 treated as TO_EX( {} )). =A0On<br>
=A0 the other hand, the Querier continues to send MLDv2 queries,<br>=A0 reg=
ardless of its Multicast Address Compatibility Mode.<br>---<br><br><br>Is t=
he follwing a correct right too?<br><br>=A0 &quot;Any IS_EX() message is tr=
eated as IS_EX( {} ).&quot;<br>
<br><br>Best Regards<br><font color=3D"#888888">--<br>Kiyoaki Kawaguchi<br>=
<br><br>_______________________________________________<br>magma mailing li=
st<br><a href=3D"mailto:[email protected]">[email protected]</a><br><a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/magma" target=3D"_blank">https://www.ie=
tf.org/mailman/listinfo/magma</a><br>
</font></blockquote></div><br>

--001636426cd766e7550491379c43--

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

--===============1124031581==--