Internet Engineering Task Force H. Jeng
Internet-Draft AT&T
Intended status: Standards Track J. Haas
Expires: January 15, 2014 Y. Rekhter
J. Zhang
Juniper Networks
July 14, 2013
Multicast Geo-Distribution Control
draft-rekhter-geo-distribution-control-03
Abstract
Consider a content provider that wants to deliver a particular
content to a set of customers/subscribers, where the provider and the
subscribers are connected by an IP service provider. This document
covers two areas needed to accomplish this:
1. Providing the content provider with the information of whether it
can use the multicast connectivity service provided by the IP
service provider to deliver a particular content to a particular
set of subscribers, and
2. Providing the content provider with a mechanism to restrict
delivery of a given content to a particular set of the
subscribers.
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 January 15, 2014.
Copyright Notice
Jeng, et al. Expires January 15, 2014 [Page 1]
Internet-Draft Multicast Geo Distribution Control July 2013
Copyright (c) 2013 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. Specification of Requirements . . . . . . . . . . . . . . . . . 3
1.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Overview of Operations . . . . . . . . . . . . . . . . . . 4
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
5. Normative References . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Jeng, et al. Expires January 15, 2014 [Page 2]
Internet-Draft Multicast Geo Distribution Control July 2013
1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1.1. Introduction
Consider a content provider that wants to deliver a particular
content to a set of customers/subscribers, where the provider and the
subscribers are connected by an IP service provider. This document
covers two areas needed to accomplish this:
1. Providing the content provider with the information of whether it
can use the multicast connectivity service provided by the IP
service provider to deliver a particular content to a particular
set of subscribers, and
2. Providing the content provider with a mechanism to restrict
delivery of a given content to a particular set of the
subscribers.
For the purpose of this document we assume that a content provider
consists of one or more Content Servers, and one or more Content
Distribution Controllers. While this document assumes communication
between Content Servers and Content Distribution Controllers, the
procedures for implementing such communication is outside the scope
of this document.
Content Servers are connected to one or more IP service provider
(ISP) that can offer both multicast and unicast connectivity service
to the subscribers of the content provider. Content provider uses
this ISP(s) to deliver content to its subscribers.
Subscribers are connected to the Edge Routers (ERs) of the ISP. Note
that the multicast connectivity service provided by the ISP extends
all the way to the ERs. Such service could be provided by either
deploying IP multicast natively, or with some tunneling mechanism
like AMT, or by a combination of both within the ISP. However,
between the ERs and the subscribers there may, or may not be
multicast connectivity.
In the case where a particular subscriber of a given content provider
does not have multicast connectivity to its ER, the content provider
would use IP unicast service provided by the ISP to transmit the
particular content to that subscriber.
A subscriber may want to access a particular content that is not
Jeng, et al. Expires January 15, 2014 [Page 3]
Internet-Draft Multicast Geo Distribution Control July 2013
available to that subscriber due to policy reasons. When that
subscriber would have received that content via unicast connectivity,
the Content Distribution Controller, or the Content Servers, or both
may enforce the policy to not deliver the content. However, when the
content would be delivered via multicast connectivity it may be
possible for the subscriber to receive the content by illicitly
participating in the multicast signaling for that content.
To prevent a subversion of the intent of this content delivery
policy, a mechanism is provided to make this policy available to
devices participating in multicast signaling.
1.2. Overview of Operations
An ISP, using the procedures described in Multicast Distribution
Reachability Signaling [MDRS], provides a content provider, and
specifically Content Distribution Controller(s) of that content
provider, with the information of whether a particular subscriber of
that content provider has multicast connectivity to an ER of that ISP
with the information of whether a particular group of subscribers can
receive multicast content.
For each content provided by a content provider, the content provider
maintains a list of subscribers who are either excluded or allowed to
receive the content. For the purpose of maintaining this list this
document assumes that subscribers are grouped into "zones" based on
IP addresses, so that exclusion/inclusion uniformly applies to all
the subscribers within a given zone. Procedures by which subscribers
are grouped into zones are outside the scope of this document.
However, this document assumes that this grouping is done
consistently by both the content provider and the ISP(s) that the
content provider uses for delivering its content.
To enforce the exclusion/inclusion policies, the content provider
uses procedures described in Multicast Distribution Control Signaling
[MDCS].
For each content provided by a content provider, the content provider
selects a particular multicast channel (S, G) for distributing this
content using multicast connectivity service. Procedures by which
the content provider selects a particular multicast channel, and
maintains the mapping are outside the scope of this document.
Subscribers are connected to the Edge Routers (ERs) of the ISP. Note
that when multicast connectivity service provided is by the ISP, that
service extends all the way to the ERs. Such service could be
provided by either deploying IP multicast natively, or with some
tunneling mechanism like AMT, or a combination of both within the
Jeng, et al. Expires January 15, 2014 [Page 4]
Internet-Draft Multicast Geo Distribution Control July 2013
ISP. However, between the ERs and the subscribers there may, or may
not be multicast connectivity.
When a subscriber wants to receive the particular content from its
content provider, the subscriber issues a request for this content to
the Content Distribution Controller of the provider. When the
Content Distribution Controller receives the request, the Content
Distribution Controller uses the information carried in the request
(e.g., IP address of the subscriber) to determine the zone of the
subscriber, and based on that zone to determine whether the
subscriber can receive this content.
If the Content Distribution Controller determines that the subscriber
can receive the content, then based on the information provided by
the multicast distribution reachability signaling the Content
Distribution Controller determines whether the subscriber can receive
this content using multicast connectivity service, and if yes, then
returns to the subscriber the multicast channel selected for
distributing the content.
If the Content Distribution Controller determines that the subscriber
can receive the content, but can not receive the content using
multicast connectivity service, the Content Distribution Controller
returns to the subscriber the information needed to receive this
content using unicast connectivity service.
If the content would have been delivered to the subscriber via
multicast connectivity, but the Content Distribution Controller had
determined the subscriber was not permited access to this content,
then this policy may need to be enforced by the Edge Routers or
upstream multicast routers to prevent illicit access of this content.
This policy is enforced by utilizing filtering information
distributed using Multicast Distribution Control Signaling [MDCS].
Specification of the procedures for communication between subscribers
and Content Distribution Controllers are outside the scope of this
document.
2. IANA Considerations
This document introduces no IANA Considerations.
3. Security Considerations
TBD
Jeng, et al. Expires January 15, 2014 [Page 5]
Internet-Draft Multicast Geo Distribution Control July 2013
4. Acknowledgements
The authors would like to thank Han Nguyen for his contributions to
this document.
5. Normative References
[MDCS] Jeng, H., Haas, J., Rekhter, Y., and J. Zhang, "Multicast
Distribution Control Signaling", draft-rekhter-mdcs-00.txt
(work in progress), 2013.
[MDRS] Jeng, H., Haas, J., Rekhter, Y., and J. Zhang, "Multicast
Distribution Reachability Signaling",
draft-rekhter-mdrs-00.txt (work in progress), 2013.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Authors' Addresses
Huajin Jeng
AT&T
Email: hj2387@att.com
Jeffrey Haas
Juniper Networks
1194 N. Mathida Ave.
Sunnyvale, CA 94089
US
Email: jhaas@juniper.net
Yakov Rekhter
Juniper Networks
1194 N. Mathida Ave.
Sunnyvale, CA 94089
US
Email: yakov@juniper.net
Jeng, et al. Expires January 15, 2014 [Page 6]
Internet-Draft Multicast Geo Distribution Control July 2013
Jeffrey (Zhaohui) Zhang
Juniper Networks
1194 N. Mathida Ave.
Sunnyvale, CA 94089
US
Email: zzhang@juniper.net
Jeng, et al. Expires January 15, 2014 [Page 7]