IGMP for user Authentication Protocol (IGAP)
draft-andou-igmp-auth-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daisuke Andou , Takeshi Hayashi | ||
| Last updated | 2002-06-21 | ||
| 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 IGAP, which allows user IP user clients and IP routers or network access servers to verify whether they can participate in a multicast group they hope and transport some information about it. IGAP is derived from IGMPv2, which can make users join a multicast group, who has the claim to participate a multicast group in a service. It's important for service providers to protect their revenue source.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)