DRTM - Distributed Real Time Mapping for Ivip and LISP
draft-whittle-ivip-drtm-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robin Whittle | ||
| Last updated | 2010-03-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
Distributed Real Time Mapping (DRTM) is intended for Ivip, but may be useful for other Core-Edge Separation solutions to the routing scaling problem, such as LISP. End-user networks - or other organizations they appoint - control the mapping of each or their one or more micronets (ranges of "edge" space with a single mapping) via sending commands to the organizations from whom they lease this space. This is conveyed to all ITRs which need it in "real-time" such as a second or two, globally. There is no need for any single set of servers to handle all the mapping updates, or to store all the mapping databases for all the MABs (Mapped Address Block) of "edge" space. Networks with ITRs use purely caching Resolving query servers (QSRs), in contrast to previous Ivip arrangements which required them to run a query server which contained the real-time updated full mapping database for all MABs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)