Multicast Address Request Protocol (MARP)
draft-hanna-marp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Steve Hanna | ||
| Last updated | 1998-01-30 | ||
| 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
The Multicast Address Request Protocol (MARP) serves as a front end to the Multicast Address Allocation Architecture. Any host that wishes to allocate a multicast address may contact a Multicast Address Allocation Server and use MARP to request an address allocation for a specific interval, scope, etc. Later, the host may request an extension of the address allocation or deallocate the address if it is no longer needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)