Skip to main content

Provider-Managed IRON

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Fred Templin
Last updated 2011-05-23
RFC stream (None)
Intended RFC status (None)
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:


The Internet Routing Overlay Network (IRON) is a new internetworking architecture based on encapsulation of inner network layer packets within outer network layer headers using a non-broadcast, multiple access (NBMA) virtual interface model. IRON suggests a third-party global deployment of servers and relays to achieve a Provider- Independent (PI) routing and addressing framework, but there may be instances in which an Internet Service Provider (ISP) wishes to manage its own IRON deployment. This document presents a Provider- Managed IRON framework that offers a fast path alternative for deployment of a long term solution.


Fred Templin

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