RADIUS Extension for Multicast Router Authentication
draft-yamanouchi-radius-ext-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nagatsugu Yamanouchi , Osamu Takahashi , Norihiro Ishikawa | ||
| Last updated | 1998-03-18 | ||
| 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 describes an extension of RADIUS authentication protocol (RFC2138) and RADIUS accounting protocol (RFC2139) to provide authentication service about multicast receivers and senders to the ingress and egress routers, and to keep track of the receiving and sending clients for multicast data feed service management. New services and attributes are added to the RADIUS definitions while the authentication transaction mechanisms are preserved. The authentication server authenticates the multicast receiver/sender by using the CHAP-based mechanism. The account server logs the start and stop points of multicast route usage. This extension is intended to be used in conjunction with the IGMP extension for multicast receiver and sender authentication.
Authors
Nagatsugu Yamanouchi
Osamu Takahashi
Norihiro Ishikawa
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)