Architectural Considerations of IP Anycast
draft-mcpherson-anycast-arch-implications-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Danny R. McPherson , David R. Oran | ||
| Last updated | 2009-01-06 | ||
| 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 discusses architectural implications of IP anycast.
Authors
Danny R. McPherson
David R. Oran
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)