On Mon, Apr 25, 2016 at 9:42 PM, 杨术 <[email protected]> wrote: > Hi, Dear Mohamed, > > Thank for you advices! > >> * This draft covers two cases: IPv4-over-IPv6 and IPv6-over-IPv4. I see a >> potential overlap with draft-ietf-softwire-dslite-multicast (that passed the >> WGLC) for the IPv4-over-IPv6 case. > Our draft focus on the mesh 4over6 case mentioned in rfc 4925. The "hub and > spoke" scenario is different with the ds-lite 4over6 case in rfc 6333.
This seems to be correct. This draft is based on what I call weird definition of mesh problem in RFC 4925. I don't think it was followed up much afterwards. If we look back, I think this draft has taken up the precious multicast space and as a result, no space was left for much more important edge multicast transition protocols. Sigh. Regards, Behcet > >> * The following section points to RFC7371. I think the authors meant >> https://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-06. > We will update the references. > > Shu Yang > > >> ------------------------------------------------------------- >> 发件人：mohamed.boucadair >> 发送日期：2016-04-25 16:27:33 >> 收件人：Ian Farrer; [email protected] >> 抄送： >> 主题：Re: [Softwires] Call for reviewersdraft-ietf-softwire-mesh-multicast >> >> Hi Ian, all, >> >> I have the following comments about this draft: >> >> * This draft covers two cases: IPv4-over-IPv6 and IPv6-over-IPv4. I see a >> potential overlap with draft-ietf-softwire-dslite-multicast (that passed the >> WGLC) for the IPv4-over-IPv6 case. Unless there are some differences between >> these two documents for this case, I suggest to scope >> draft-ietf-softwire-mesh-multicast to focus on the IPv6-over-IPv4 and add a >> pointer to draft-ietf-softwire-dslite-multicast. Otherwise, it would be >> helpful to identify the differences between the two documents. >> >> * The following section points to RFC7371. I think the authors meant >> https://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-06. >> >> == >> 4.2. Group Address Mapping >> >> For IPv4-over-IPv6 scenario, a simple algorithmic mapping between >> IPv4 multicast group addresses and IPv6 group addresses is supported. >> [RFC7371] has already defined an applicable format. Figure 4 is the >> reminder of the format: >> >> >> +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ >> | 0-------------32--40--48--56--64--72--80--88--96-----------127| >> +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ >> | MPREFIX64 |group address | >> +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ >> >> >> Figure 4: IPv4-Embedded IPv6 Multicast Address Format >> >> The MPREFIX64 for SSM mode is also defined in [RFC7371] : >> >> o ff3x:0:8000::/96 ('x' is any valid scope) >> == >> >> Thank you. >> >> Cheers, >> Med >> >> > -----Message d'origine----- >> > De : Softwires [mailto:[email protected]] De la part de Ian >> > Farrer >> > Envoyé : jeudi 7 avril 2016 16:59 >> > À : [email protected] >> > Objet : [Softwires] Call for reviewers draft-ietf-softwire-mesh-multicast >> > >> > Hi, >> > >> > This document has been around for some time, but has not received any >> > substantive reviews. Can I ask for volunteers who are willing to provide >> > reviews? >> > >> > Thanks, >> > Ian >> > >> > >> > _______________________________________________ >> > Softwires mailing list >> > [email protected] >> > https://www.ietf.org/mailman/listinfo/softwires >> >> _______________________________________________ >> Softwires mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/softwires >> . > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
