________________________________
From: Lee, Yiu [mailto:[email protected]]
Sent: Thursday, August 25, 2011 11:31 AM
To: [email protected]
Subject: Re: [Softwires] Comments on
draft-qin-softwire-dslite-multicast-04
Hi Tina,
What do you see new here in this scenario? mAFTR is a logical
function, it would perform MLD PIMv4-Join interworking. This has been
captured. If a vendor wants to make mAFTR also a L2 device, it would
perform standard MLD snooping. What else is missing?
Xiaohong: Exactly. I also wonder what's missing to your eyes? ;)
Cheers,
Xiaohong
Thanks,
Yiu
From: Tina TSOU <[email protected]>
Date: Thu, 25 Aug 2011 02:11:18 +0000
To: "[email protected]" <[email protected]>
Subject: [Softwires] Comments on
draft-qin-softwire-dslite-multicast-04
Hi all,
One more comment on Section 7.4.2.
This document only covers IGMP-MLD and PIMv6-PIMv4 scenarios. We
also need to consider the scenario where it is layer 2 network between
mAFTR and mB4. The architecture is as below:
------------
/ \
| IPv4 network |
\ /
------------
: | ^
IPv4 Multicast : | : PIMv4 Join
v | :
+-------------+
| mAFTR |
+-------------+
|:| | ^
IPv6 Multicast |:| | : (MLD Report)
(IPv4 embedded) |.| ... .
+-----------+
| MLD proxy/|
| snooping |
+-----------+
|:| | : MLD Report
|v| | :
+-----------+
| mB4 |
+-----------+
: | ^
IPv4 Multicast : | : IGMP Report
v | :
+-----------+
| IPv4 |
| Receiver |
+-----------+
B. R.
Tina
_______________________________________________ Softwires
mailing list [email protected]
https://www.ietf.org/mailman/listinfo/softwires
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
