Skip to main content

Light-weight Multicast Address Discovery Protocol
draft-williamson-mboned-madp-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Beau Williamson
Last updated 2007-11-13
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

Light-weight, multicast address discovery mechanisms that can be used by large scale client-server application deployments have been virtually non-existent in the past. This has resulted in many multicast client-server applications being deployed with "hard-coded" multicast addresses within the client workstations in order to provide "zero-configuration" operation of the application. Unfortunately, many of these hard-coded multicast addresses are often picked at random by the application developers resulting in multicast address collisions with other protocols/applications or conflicts with the multicast scoping plans of a network administrator. This document describes a "light-weight" multicast address discovery protocol that can be used by application clients to locate their nearest application server using well-known scope relative multicast addresses. Once located, the server can then communicate the multicast address(es) that have been configured on the server by the network administrator for use by the application. This permits applications be written to operate in a flexible "near-zero" configuration mode without having to use "hard-coded" addresses or rely on any other network service other than multicast and the existence of a nearby application server.

Authors

Beau Williamson

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)