IETF Logo Mail Archive

Re: [mif] IRON as a multiple interface solution

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 18 November 2011 22:19 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 D0D9621F8AEA for <mif@ietfa.amsl.com>; Fri, 18 Nov 2011 14:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.741
X-Spam-Level:
X-Spam-Status: No, score=-6.741 tagged_above=-999 required=5 tests=[AWL=-0.142, 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 Towxy+1Oe4iz for <mif@ietfa.amsl.com>; Fri, 18 Nov 2011 14:19:46 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id E144921F8AE6 for <mif@ietf.org>; Fri, 18 Nov 2011 14:19:46 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id pAIMJf6r016829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 18 Nov 2011 14:19:42 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id pAIMJfrZ029629; Fri, 18 Nov 2011 14:19:41 -0800 (PST)
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id pAIMJexW029597 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 18 Nov 2011 14:19:41 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Fri, 18 Nov 2011 14:19:40 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 18 Nov 2011 14:19:39 -0800
Thread-Topic: [mif] IRON as a multiple interface solution
Thread-Index: AQHMpj1koMqud6He1Eq9rIfXAKsZZJWzMgAQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C7911E911@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>, <E1829B60731D1740BB7A0626B4FAF0A65C7911E89A@XCH-NW-01V.nw.nos.boeing.com> <D24D78CD-CDB8-4DDE-9D08-CE747443440B@nominum.com>
In-Reply-To: <D24D78CD-CDB8-4DDE-9D08-CE747443440B@nominum.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
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [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 22:19:47 -0000

Hi Ted, 

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Sent: Friday, November 18, 2011 2:00 PM
> To: Templin, Fred L
> Cc: mif@ietf.org
> Subject: Re: [mif] IRON as a multiple interface solution
> 
> On Nov 19, 2011, at 4:38 AM, "Templin, Fred L" 
> <Fred.L.Templin@boeing.com> wrote:
> > A new routing and addressing system known as the
> > Internet Routing Overlay Network (IRON) is available
> 
> Correct me if I am wrong, but doesn't this depend on all 
> provisioning domains being in the same administrative domain?

If you consider "the Internet" as a singe administrative
domain then, yes, the IRON tunnel virtual interface is
configured over a single administrative domain. So, the
tunnel virtual interface is configured over all of the
host's ISP interfaces.

If the host also connects to a home enterprise network
via a VPN, then that would be a separate administrative
domain and a separate tunnel virtual interface. Does
this help?

Thanks - Fred

v2.46.0 | Report a Bug | By Email | System Status