<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.tsou-multrans-use-cases" target="https://datatracker.ietf.org/doc/html/draft-tsou-multrans-use-cases-00">
   <front>
      <title>Use Cases For Multicast Transition From IPv4 to IPv6</title>
      <author initials="C." surname="Zhou" fullname="Cathy Zhou">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="R." surname="Maglione" fullname="Roberta Maglione">
         <organization>Telecom Italia</organization>
      </author>
      <author initials="T." surname="Tsou" fullname="Tina Tsou (Ting ZOU)">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="T." surname="Taylor" fullname="Tom Taylor">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="August" day="24" year="2011" />
      <abstract>
	 <t>   Like other internet activities, multicast is affected by the fact
   that the transition from IPv4 to IPv6 is occurring over a period of
   years, via multiple transition paths.  As a result, mechanisms need
   to be added to the basic multicast architecture to assist in specific
   transition scenarios.  This document describes detailed use cases so
   that the requirements for the multicast transition mechanisms can be
   better understood.

   The considered opinion in discussions to date on multicast transition
   requirements has been that the two most important transition
   scenarios in the near future will be the &quot;4-6-4&quot; and &quot;6-4&quot; network
   scenarios.  These scenarios are described in detail below, in their
   several possible variants, showing the new issues that IPv6
   transition raises for multicast operation.

   There is further general agreement that Any-Source Multicast (ASM)
   (the service, not necessarily the technology) is no longer an
   important use case.  As a result, this document restricts itself to
   scenarios where the set of multicast sources is separate from the set
   of multicast receivers.  As a final restriction, it assumes a single
   administrative provider domain.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-tsou-multrans-use-cases-00" />
   
</reference>
