[mif] IRON as a multiple interface solution

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 18 November 2011 20:38 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0746921F84C9 for <mif@ietfa.amsl.com>; Fri, 18 Nov 2011 12:38:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.749
X-Spam-Level:
X-Spam-Status: No, score=-6.749 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4mqBi8gTvv2t for <mif@ietfa.amsl.com>; Fri, 18 Nov 2011 12:38:17 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDD921F84C3 for <mif@ietf.org>; Fri, 18 Nov 2011 12:38:17 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id pAIKc7D4027984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <mif@ietf.org>; Fri, 18 Nov 2011 12:38:15 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id pAIKc7eE028025 for <mif@ietf.org>; Fri, 18 Nov 2011 12:38:07 -0800 (PST)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id pAIKc7qu028017 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <mif@ietf.org>; Fri, 18 Nov 2011 12:38:07 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Fri, 18 Nov 2011 12:38:07 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "mif@ietf.org" <mif@ietf.org>
Date: Fri, 18 Nov 2011 12:38:06 -0800
Thread-Topic: IRON as a multiple interface solution
Thread-Index: Acyl47ekZfkZT4I0Tz2nzbp32pI9zwASbcTA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C7911E89A@XCH-NW-01V.nw.nos.boeing.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB78C3C98@GRFMBX704BA020.griffon.local> <916CE6CF87173740BC8A2CE44309696204193417@008-AM1MPN1-053.mgdnok.nokia.com>, <4EC512A2.2060509@gmail.com> <890A58CF-8EAD-4F92-9981-9B5AA07EBF00@nominum.com>, <4EC5B720.8020605@gmail.com> <83A7D27A-9036-4252-AC94-3A89125C961B@nominum.com> <4EC63ECC.8010700@gmail.com>
In-Reply-To: <4EC63ECC.8010700@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mif] IRON as a multiple interface solution
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2011 20:38:18 -0000

Hi,

A new routing and addressing system known as the
Internet Routing Overlay Network (IRON) is available
that (among many other things) supports hosts with
multiple interfaces. IRON (along with its associated
mechanisms VET and SEAL) uses a tunnel virtul interface
to harness the host's ISP interfaces into a "bundle"
that is represented to a server in the Internet. The
tunnel interface assigns a single, stable IP address
that host applications can use regardless of the ISP
connection or connections used to carry traffic.

The server is responsible for representing the host's
stable IP address into the Internet routing system. The
host is responsible for selecting ISP interfaces for
outbound packets, and for providing directions to the
server as to ISP interfaces to use for inbound packets.
Traffic engineering, load balancing, fault tolerance,
asymmetric routing, etc. are all therefore naturally
supported. Mobility and NAT traversal are also naturally
supported. The solution also supports the case of the
host receiving an IP prefix instead of just a singleton
IP address and then beginning to function as a router.

Please see below for the documents and send comments:

http://www.ietf.org/internet-drafts/draft-templin-ironbis-08.txt
http://www.ietf.org/internet-drafts/draft-templin-intarea-vet-31.txt
http://www.ietf.org/internet-drafts/draft-templin-intarea-seal-39.txt

Thanks - Fred
fred.l.templin@boeing.com