Multicast Geo-Distribution Control
draft-rekhter-geo-distribution-control-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Huajin Jeng , Jeffrey Haas , Yakov Rekhter , Zhaohui (Jeffrey) Zhang | ||
| Last updated | 2013-07-04 (Latest revision 2012-12-31) | ||
| RFC stream | (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
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.
Authors
Huajin Jeng
Jeffrey Haas
Yakov Rekhter
Zhaohui (Jeffrey) Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)