draft-ietf-mboned-multrans-addr-acquisition-02.txt   draft-ietf-mboned-multrans-addr-acquisition-03.txt 
Internet Engineering Task Force T. Tsou Internet Engineering Task Force T. Tsou
Internet-Draft Huawei Technologies (USA) Internet-Draft Huawei Technologies
Intended status: Informational A. Clauberg Intended status: Informational A. Clauberg
Expires: January 06, 2014 Deutsche Telekom Expires: September 5, 2014 Deutsche Telekom
M. Boucadair M. Boucadair
France Telecom France Telecom
S. Venaas S. Venaas
Cisco Systems Cisco Systems
Q. Sun Q. Sun
China Telecom China Telecom
July 05, 2013 March 4, 2014
Address Acquisition For Multicast Content When Source and Receiver Address Acquisition For Multicast Content When Source and Receiver
Support Differing IP Versions Support Differing IP Versions
draft-ietf-mboned-multrans-addr-acquisition-02 draft-ietf-mboned-multrans-addr-acquisition-03
Abstract Abstract
Each IPTV operator has their own arrangements for pre-provisioning Each IPTV operator has their own arrangements for pre-provisioning
program information including addresses of the multicast groups program information including addresses of the multicast groups
corresponding to broadcast programs on the subscriber receiver. corresponding to broadcast programs on the subscriber receiver.
During the transition from IPv4 to IPv6, scenarios can occur where During the transition from IPv4 to IPv6, scenarios can occur where
the IP version supported by the receiver differs from that supported 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 by the source. This memo examines what has to be done to allow the
receiver to acquire multicast address information in the version it receiver to acquire multicast address information in the version it
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 06, 2014. This Internet-Draft will expire on September 5, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Which Problem Are We Solving? . . . . . . . . . . . . . . . . 3 2. Which Problem Are We Solving? . . . . . . . . . . . . . . . . 3
3. Possible Solutions . . . . . . . . . . . . . . . . . . . . . 3 3. Possible Solutions . . . . . . . . . . . . . . . . . . . . . 4
3.1. The Reactive Strategy . . . . . . . . . . . . . . . . . . 4 3.1. The Reactive Strategy . . . . . . . . . . . . . . . . . . 4
3.2. Dynamic Modification . . . . . . . . . . . . . . . . . . 4 3.2. Dynamic Modification . . . . . . . . . . . . . . . . . . 5
3.3. Administrative Preparation . . . . . . . . . . . . . . . 5 3.3. Administrative Preparation . . . . . . . . . . . . . . . 5
4. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. Informative References . . . . . . . . . . . . . . . . . . . 6 8. Informative References . . . . . . . . . . . . . . . . . . . 6
Appendix A. Some Background On Program Guides . . . . . . . . . 7 Appendix A. Some Background On Program Guides . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
skipping to change at page 7, line 4 skipping to change at page 7, line 11
Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., Tsou, T., Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., Tsou, T.,
and Q. Sun, "IPv4-IPv6 Multicast: Problem Statement and and Q. Sun, "IPv4-IPv6 Multicast: Problem Statement and
Use Cases (Work in Progress)", May 2012. Use Cases (Work in Progress)", May 2012.
[ID.softwire-multicast-prefix-option] [ID.softwire-multicast-prefix-option]
Qin, J., Boucadair, M., Tsou, T., and X. Deng, "DHCPv6 Qin, J., Boucadair, M., Tsou, T., and X. Deng, "DHCPv6
Options for IPv6 DS-Lite Multicast Prefix (Work in Options for IPv6 DS-Lite Multicast Prefix (Work in
Progress)", March 2012. Progress)", March 2012.
[MPEG-7_DDL] [MPEG-7_DDL]
, "Information technology - Multimedia content description "Information technology - Multimedia content description
interface - Part 2: Description definition language", ISI/ interface - Part 2: Description definition language", ISI/
IEC 15938-2 (2002), 2002. IEC 15938-2 (2002), 2002.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC4078] Earnshaw, N., Aoki, S., Ashley, A., and W. Kameyama, "The [RFC4078] Earnshaw, N., Aoki, S., Ashley, A., and W. Kameyama, "The
TV-Anytime Content Reference Identifier (CRID)", RFC 4078, TV-Anytime Content Reference Identifier (CRID)", RFC 4078,
skipping to change at page 9, line 10 skipping to change at page 9, line 18
case, the access information including the source and multicast group case, the access information including the source and multicast group
addresses is embedded as an SDP fragment within a larger set of XML- addresses is embedded as an SDP fragment within a larger set of XML-
encoded program metadata. The OMA metadata can be supplied to the encoded program metadata. The OMA metadata can be supplied to the
receiver in multiple segments, through multiple channels. This receiver in multiple segments, through multiple channels. This
complicates the task of intercepting that metadata and modifying it complicates the task of intercepting that metadata and modifying it
in a particular transport network. in a particular transport network.
Authors' Addresses Authors' Addresses
Tina Tsou Tina Tsou
Huawei Technologies (USA) Huawei Technologies
2330 Central Expressway Bantian, Longgang District
Santa Clara, CA 95050 Shenzhen 518129
USA P.R. China
Phone: +1 408 330 4424
Email: Tina.Tsou.Zouting@huawei.com Email: Tina.Tsou.Zouting@huawei.com
Axel Clauberg Axel Clauberg
Deutsche Telekom Deutsche Telekom
Deutsche Telekom AG, GTN-FM4 Deutsche Telekom AG, GTN-FM4
Landgrabenweg 151 Landgrabenweg 151
Bonn 53227 Bonn 53227
Germany Germany
Phone: +4922893618546 Phone: +4922893618546
 End of changes. 11 change blocks. 
14 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/