ATMARP Client Autoconfiguration
draft-marcinik-ipatm-auto-arp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fong-Ching Liaw , Carl Marcinik | ||
| Last updated | 1995-11-22 | ||
| 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 to RFC 1577 [1] that allows an ATMARP client to automatically locate its ATMARP server. This procedure is facilitated through the use of ATM anycast addressing [2]. ATMARP clients use a LIS-specific anycast address to locate their LIS-designated ATMARP Server. Both an ATMARP client and an ATMARP server algorithmically determine their LIS-specific anycast address upon restart. The use of this procedure will significantly relieve the administrative burden currently required to (re)configure a Classical IP network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)