Hi Tina, I agree with Yiu. FYI, we had a discussion between co-authors of the draft whether we maintain http://tools.ietf.org/html/draft-qin-softwire-dslite-multicast-04#section-8 or remove it. You can read in that section:
" Additionally, mechanisms such as MLD Snooping, MLD Proxying, etc., can be introduced into the distributed Access Network Nodes (e.g., Aggregation Switches, xPON devices) which then could behave as MLD Querier and replicate multicast flows as appropriate. Thus, the multicast replication point is moved downward closer to the receivers, so that bandwidth consumption is optimized." What do you think is missing in that text? Cheers, Med ________________________________ De : softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] De la part de Lee, Yiu Envoyé : jeudi 25 août 2011 05:31 À : softwires@ietf.org Objet : 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? Thanks, Yiu From: Tina TSOU <tina.tsou.zout...@huawei.com> Date: Thu, 25 Aug 2011 02:11:18 +0000 To: "softwires@ietf.org" <softwires@ietf.org> 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: _______________________________________________ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
