IETF Logo Mail Archive

Re: [mif] IRON as a multiple interface solution

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 19 November 2011 22:04 UTC

Return-Path: <ajs@anvilwalrusden.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 235EB21F85F1 for <mif@ietfa.amsl.com>; Sat, 19 Nov 2011 14:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 3ZlpKEacIM4X for <mif@ietfa.amsl.com>; Sat, 19 Nov 2011 14:03:59 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 8F45B21F849E for <mif@ietf.org>; Sat, 19 Nov 2011 14:03:59 -0800 (PST)
Received: from shinkuro.com (m070f36d0.tmodns.net [208.54.15.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id ACB551ECB424 for <mif@ietf.org>; Sat, 19 Nov 2011 22:03:44 +0000 (UTC)
Date: Sat, 19 Nov 2011 17:03:56 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: mif@ietf.org
Message-ID: <20111119220355.GA893@shinkuro.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> <E1829B60731D1740BB7A0626B4FAF0A65C7911E911@XCH-NW-01V.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C7911E911@XCH-NW-01V.nw.nos.boeing.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Sat, 19 Nov 2011 22:04:00 -0000

On Fri, Nov 18, 2011 at 02:19:39PM -0800, Templin, Fred L wrote:
> 
> 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?

It does, in that it seems to make it pretty hard to solve the multiple
resolution context problem that the DNS server selection draft is
trying to solve.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

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