The Internet Routing Overlay Network (IRON)
draft-templin-ironbis-10

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2012-03-16 (latest revision 2011-12-19)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Document shepherd None
IESG IESG state AD Evaluation
Telechat date
Responsible AD Ralph Droms
Send notices to fltemplin@acm.org, draft-templin-ironbis@tools.ietf.org
RFC Editor RFC Editor state ISR
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Intended status: Informational                         December 19, 2011
Expires: June 21, 2012

              The Internet Routing Overlay Network (IRON)
                      draft-templin-ironbis-10.txt

Abstract

   Since the Internet must continue to support escalating growth due to
   increasing demand, it is clear that current routing architectures and
   operational practices must be updated.  This document proposes an
   Internet Routing Overlay Network (IRON) architecture that supports
   sustainable growth while requiring no changes to end systems and no
   changes to the existing 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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 21, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Templin                   Expires June 21, 2012                 [Page 1]
Internet-Draft                    IRON                     December 2011

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  The Internet Routing Overlay Network . . . . . . . . . . . . .  7
     3.1.  IRON Client  . . . . . . . . . . . . . . . . . . . . . . .  9
     3.2.  IRON Serving Router  . . . . . . . . . . . . . . . . . . . 10
     3.3.  IRON Relay Router  . . . . . . . . . . . . . . . . . . . . 10
   4.  IRON Organizational Principles . . . . . . . . . . . . . . . . 11
   5.  IRON Control Plane Operation . . . . . . . . . . . . . . . . . 13
     5.1.  IRON Client Operation  . . . . . . . . . . . . . . . . . . 13
     5.2.  IRON Server Operation  . . . . . . . . . . . . . . . . . . 14
     5.3.  IRON Relay Operation . . . . . . . . . . . . . . . . . . . 14
   6.  IRON Forwarding Plane Operation  . . . . . . . . . . . . . . . 15
     6.1.  IRON Client Operation  . . . . . . . . . . . . . . . . . . 15
     6.2.  IRON Server Operation  . . . . . . . . . . . . . . . . . . 16
     6.3.  IRON Relay Operation . . . . . . . . . . . . . . . . . . . 17
   7.  IRON Reference Operating Scenarios . . . . . . . . . . . . . . 17
     7.1.  Both Hosts within Same IRON Instance . . . . . . . . . . . 17
       7.1.1.  EUNs Served by Same Server . . . . . . . . . . . . . . 18
       7.1.2.  EUNs Served by Different Servers . . . . . . . . . . . 19
       7.1.3.  Client-to-Client Tunneling . . . . . . . . . . . . . . 22
     7.2.  Mixed IRON and Non-IRON Hosts  . . . . . . . . . . . . . . 23
       7.2.1.  From IRON Host A to Non-IRON Host B  . . . . . . . . . 23
       7.2.2.  From Non-IRON Host B to IRON Host A  . . . . . . . . . 25
     7.3.  Hosts within Different IRON Instances  . . . . . . . . . . 26
   8.  Mobility, Multiple Interfaces, Multihoming, and Traffic
       Engineering  . . . . . . . . . . . . . . . . . . . . . . . . . 26
     8.1.  Mobility Management and Mobile Networks  . . . . . . . . . 27
     8.2.  Multiple Interfaces and Multihoming  . . . . . . . . . . . 27
     8.3.  Traffic Engineering  . . . . . . . . . . . . . . . . . . . 28
   9.  Renumbering Considerations . . . . . . . . . . . . . . . . . . 28
Show full document text