Multicast Listener Discovery Authentication protocol (MLDA)
draft-hayashi-mlda-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tsunemasa Hayashi | ||
| Last updated | 2004-05-04 | ||
| 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
This memo documents a multicast CDN (Content Delivery Network) issues, and describes requirement and discussion points when we solve them. Here, we need a method of precise user accounting (logging) of a user activity to a multicast group and of user access control to a multicast group to protect to subscribe from an illegal access. In this case, it is needed to authorize a user access to a multicast group on the CDN, and to get information of user action (Join/Leave) to a multicast group. The key is how a control process of group membership synchronizes with an AAA process (authentication, authorization and accounting), because we can get a user access information at an AAA server. This depends on the network model of the multicast CDN service. Last of all, we introduce an example of solution MLDA (Multicast Listener Discovery Authentication protocol).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)