Hi Woj, DS-Lite terminology is used in the sense that an IPv4 receiver is delivered (IPv4) multicast content (from an IPv4 source) over an IPv6 network.
The generic use case as described in http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#section-3.1 is called 4-6-4. I personally agree to change the title to reflect this. The document does not make any assumption about the location of AFTR and mAFTR: deployment considerations are out of scope. FWIW, mAFTR is defined as follows: o Multicast AFTR (mAFTR): is a functional entity which supports IPv4-IPv6 multicast interworking function (refer to Figure 3). It receives and encapsulates the IPv4 multicast packets into IPv4-in- IPv6 packets and behaves as the corresponding IPv6 multicast source for the encapsulated IPv4-in-IPv6 packets. If you still think mAFTR terminology is confusing, we can change it to mBR (for multicast Border Router), 64mBR (IPv6/IPv4 Multicast Border Router), mIXF (multicast Interconnection Function), etc. Cheers, Med ________________________________ De : [email protected] [mailto:[email protected]] De la part de Wojciech Dec Envoyé : mercredi 6 juin 2012 15:43 À : Simon Perreault Cc : [email protected]; Yong Cui Objet : Re: [Softwires] WG last call on draft-ietf-softwire-dslite-multicast-02 In addition a general observation: This draft appears to have very little in common with DS-Lite (nothing except use of IPinIP on my reading), and using that reference and the AFTR terms is confusing. The fact that technically it features an address family mapped multicast transport, which alongside with the IGMP/MLD translation makes it anything but transparent tunneling. A change of title would be also useful, as well as general decoupling from the ds-lite architecture: The mAFTR device can, and likely will be a often a dedicated multicast device that plays no part in unicast forwarding. -Woj.
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
