The Interior Routing Overlay Network (IRON)
draft-templin-ironbis-15
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2013-11-04 (Latest revision 2013-05-03) | ||
| RFC stream | Independent Submission | ||
| Formats | |||
| Reviews | |||
| Additional resources | |||
| Stream | ISE state | In ISE Review | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Telechat date | (None) | ||
| Responsible AD | Ralph Droms | ||
| Send notices to | fltemplin@acm.org, draft-templin-ironbis@tools.ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Since large-scale Internetworks such as the public Internet must continue to support escalating growth due to increasing demand, it is clear that Autonomous Systems (ASes) must avoid injecting excessive de-aggregated prefixes into the interdomain routing system and instead mitigate de-aggregation internally. This document describes an Interior Routing Overlay Network (IRON) architecture that supports sustainable growth within AS-interior routing domains while requiring no changes to end systems and no changes to the exterior routing system. In addition to routing scaling, IRON further addresses other important issues including mobility management, mobile networks, multihoming, traffic engineering, NAT traversal and security. While business considerations are an important determining factor for widespread adoption, they are out of scope for this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)