<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.templin-ironbis" target="https://datatracker.ietf.org/doc/html/draft-templin-ironbis-12">
   <front>
      <title>The Intradomain Routing Overlay Network (IRON)</title>
      <author initials="F." surname="Templin" fullname="Fred Templin">
         </author>
      <date month="October" day="22" year="2012" />
      <abstract>
	 <t>   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 proposes
   an Intradomain Routing Overlay Network (IRON) architecture that
   supports sustainable growth within 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-templin-ironbis-12" />
   
</reference>
