[Softwires] I-D Action: draft-ietf-softwire-dslite-multicast-03.txt

2012-08-23 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Softwires Working Group of the IETF. Title : Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network Author(s) : Jacni Qin

[Softwires] draft-ietf-softwire-dslite-multicast-03

2012-08-23 Thread mohamed.boucadair
Dear all, A new version taking into account comments received during the WGLC has been submitted. The main changes are: * change the title * clarify the solution is generic for any 4-6-4 use case and the solution has been designed with DS-Lite in mind * add a discussion about scoping: preserve

Re: [Softwires] draft-ietf-softwire-dslite-multicast-03

2012-08-23 Thread Behcet Sarikaya
Hi Med, Thanks for posting this revision but it seems like it has not solved any problems but instead it created more problems :-). First, please see the two active tickets, ticket #10 and ticket #11 in the issue tracker: http://tools.ietf.org/wg/softwire/trac/report/1 In addition, in

Re: [Softwires] draft-ietf-softwire-dslite-multicast-03

2012-08-23 Thread Lee, Yiu
Hi Stig, Agree we should review this in mboned. We will send a separate message to mboned for review. Thanks very much for all your comments. Thanks, Yiu On 8/23/12 1:45 PM, Stig Venaas s...@venaas.com wrote: On 8/23/2012 7:54 AM, mohamed.boucad...@orange.com wrote: Dear all, A new version

Re: [Softwires] draft-ietf-softwire-dslite-multicast-03

2012-08-23 Thread Jacni Qin
Re-, On 8/24/2012 Friday 1:45 AM, Stig Venaas wrote: On 8/23/2012 7:54 AM, mohamed.boucad...@orange.com wrote: Dear all, A new version taking into account comments received during the WGLC has been submitted. The main changes are: * change the title * clarify the solution is generic for

Re: [Softwires] draft-ietf-softwire-dslite-multicast-03

2012-08-23 Thread mohamed.boucadair
Hi Behcet, I'm ready to record in the document whatever the WG agrees to do. But as far as I know the solution which consists in encapsulating all multicast flows to the unicast AFTR has not been accepted by the working group. The drawbacks are even been documented in this draft. I'm aware