Use Cases For Multicast Transition From IPv4 to IPv6
draft-tsou-multrans-use-cases-00

Document Type Expired Internet-Draft (individual)
Last updated 2011-08-24
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-tsou-multrans-use-cases-00.txt

Abstract

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 "4-6-4" and "6-4" 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.

Authors

Cathy Zhou (cathy.zhou@huawei.com)
Roberta Maglione (roberta.maglione@telecomitalia.it)
Tina Tsou (tina.tsou.zouting@huawei.com)
Tom Taylor (tom111.taylor@bell.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)