datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Address Acquisition For Multicast Content When Source and Receiver Support Differing IP Versions
draft-ietf-mboned-multrans-addr-acquisition-03

Document type: Active Internet-Draft (mboned WG)
Document stream: IETF
Last updated: 2014-03-04
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Internet Engineering Task Force                                  T. Tsou
Internet-Draft                                       Huawei Technologies
Intended status: Informational                               A. Clauberg
Expires: September 5, 2014                              Deutsche Telekom
                                                            M. Boucadair
                                                          France Telecom
                                                               S. Venaas
                                                           Cisco Systems
                                                                  Q. Sun
                                                           China Telecom
                                                           March 4, 2014

   Address Acquisition For Multicast Content When Source and Receiver
                     Support Differing IP Versions
             draft-ietf-mboned-multrans-addr-acquisition-03

Abstract

   Each IPTV operator has their own arrangements for pre-provisioning
   program information including addresses of the multicast groups
   corresponding to broadcast programs on the subscriber receiver.
   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 what has to be done to allow the
   receiver to acquire multicast address information in the version it
   supports in such scenarios.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 5, 2014.

Tsou, et al.            Expires September 5, 2014               [Page 1]
Internet-Draft        Multicast Address Acquisition           March 2014

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Which Problem Are We Solving? . . . . . . . . . . . . . . . .   3
   3.  Possible Solutions  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  The Reactive Strategy . . . . . . . . . . . . . . . . . .   4
     3.2.  Dynamic Modification  . . . . . . . . . . . . . . . . . .   5
     3.3.  Administrative Preparation  . . . . . . . . . . . . . . .   5
   4.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Some Background On Program Guides  . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Discussion of the multicast transition problem has focussed on the
   case of broadcast delivery of program content.  Within this scenario,
   the operation of viewing a program follows a well-defined sequence.
   For the sake of reducing channel switching delay, the list of
   multicast addresses is generally pre-provisioned to the receiver as
   part of the program guide.  Each operator has their own solution for
   achieving this delivery, despite the attempts at standardization
   recounted in Appendix A.

   At some later time, after the program guide is delivered, the user
   chooses to view a program, possibly by selecting it from a displayed
   program listing, or simply by selecting a channel.  The receiver uses
   its pre-acquired information to signal to the network to receive the

[include full document text]