Address Acquisition For Multicast Content When Source and Receiver Support Differing IP Versions
draft-tsou-multrans-addr-acquisition-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tina Tsou (Ting ZOU) | ||
| Last updated | 2012-06-13 (Latest revision 2011-12-11) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In a typical IP television (IPTV) system, the receiver acquires information about available program content, the subscriber selects a program to watch, and the receiver signals to the network to begin receiving the program in the form of multicast content. The program content information is typically XML-encoded, can be transmitted in multiple segments, possibly over multiple channels, but includes media stream descriptions for the individual program descriptions that may also be XML-encoded or may use the Session Description Protocol (SDP, RFC 4566). The media stream descriptions provide multicast group and unicast source addresses that are used in the subsequent signalling to the network. During the transition from IPv4 to IPv6, scenarios can occur where the IP version supported by the receiver differs from that supported by the source. This memo examines and evaluates alternative strategies for allowing the receiver to acquire addresses in such scenarios in the version it supports.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)