IETF Logo Mail Archive

Re: [mif] IRON as a multiple interface solution

"Hui Deng" <denghui@chinamobile.com> Tue, 20 December 2011 06:54 UTC

Return-Path: <denghui@chinamobile.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 B949C11E80D5 for <mif@ietfa.amsl.com>; Mon, 19 Dec 2011 22:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level:
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RELAY_IS_221=2.222]
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 lFaaq+A2m-nY for <mif@ietfa.amsl.com>; Mon, 19 Dec 2011 22:54:45 -0800 (PST)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id E174311E80D1 for <mif@ietf.org>; Mon, 19 Dec 2011 22:54:44 -0800 (PST)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 0FD0BE619; Tue, 20 Dec 2011 14:54:44 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id DE5F9E616; Tue, 20 Dec 2011 14:54:43 +0800 (CST)
Received: from Hui ([10.2.43.49]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2011122014544095-10350 ; Tue, 20 Dec 2011 14:54:40 +0800
From: Hui Deng <denghui@chinamobile.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Andrew Sullivan' <ajs@anvilwalrusden.com>
References: <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> <20111119220355.GA893@shinkuro.com> <E1829B60731D1740BB7A0626B4FAF0A65C7911EA73@XCH-NW-01V.nw.nos.boeing.com> <CANF0JMB3--o0z7VKD_MvxYZ7APDhNjdWnGr=41NYjYh=x66pRA@mail.gmail.com> <E1829B60731D1740BB7A0626B4FAF0A65C7917B0D5@XCH-NW-01V.nw.nos.boeing.com> <20111128181115.GC45293@shinkuro.com> <01ed01ccbb23$7127e070$5377a150$@com> <E1829B60731D1740BB7A0626B4FAF0A65C792A5383@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C792A5383@XCH-NW-01V.nw.nos.boeing.com>
Date: Tue, 20 Dec 2011 14:54:44 +0800
Message-ID: <009401ccbee4$41104cf0$c330e6d0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acyt+SSiV3nB5GxjQku3toj+zfni4wNKihNgANRZoKAAG9NZ4A==
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2011-12-20 14:54:40, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2011-12-20 14:54:43, Serialize complete at 2011-12-20 14:54:43
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Content-Language: zh-cn
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18594.005
X-TM-AS-Result: No--24.686-7.0-31-10
X-imss-scan-details: No--24.686-7.0-31-10;No--24.686-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No
Cc: 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: Tue, 20 Dec 2011 06:54:45 -0000

Hi Fred,

>From your reply, it says that MIF DNS does resolve the issue compatible with
IRON, not a competing solution. 

If that is what you mean, that's fine. Thanks for discussion

-Hui

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Tuesday, December 20, 2011 1:45 AM
> To: Hui Deng; 'Andrew Sullivan'
> Cc: mif@ietf.org
> Subject: RE: [mif] IRON as a multiple interface solution
> 
> Hi Hui,
> 
> I thought I had addressed Andrew's points in my
> 12/1/2011 post:
> 
> http://www.ietf.org/mail-archive/web/mif/current/msg01506.html
> 
> Does that post clarify things?
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> > -----Original Message-----
> > From: Hui Deng [mailto:denghui@chinamobile.com]
> > Sent: Thursday, December 15, 2011 4:17 AM
> > To: 'Andrew Sullivan'; Templin, Fred L
> > Cc: mif@ietf.org
> > Subject: RE: [mif] IRON as a multiple interface solution
> >
> > I agree that Andrew's argument does make sense. You can't
> > tell which service
> > it belongs to just based on FQDN
> >
> > -Hui
> >
> > > -----Original Message-----
> > > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On
> > Behalf Of
> > > Andrew Sullivan
> > > Sent: Tuesday, November 29, 2011 2:11 AM
> > > To: Templin, Fred L
> > > Cc: mif@ietf.org
> > > Subject: Re: [mif] IRON as a multiple interface solution
> > >
> > > On Mon, Nov 28, 2011 at 09:22:45AM -0800, Templin, Fred L wrote:
> > > > That said, IRON does not preclude the host from accessing
> > > > services within the underlying ISP networks. To do so,
> > > > however, the host would have to use its ISP-delegated
> > > > address(es) and not the VSP-delegated address.
> > > >
> > > > Does this match your understanding?
> > >
> > > The central problem, however, is that if you are looking up the
> > > address for a name, you don't obviously know where it is (i.e. you
> > > don't know what network you need to go to).  What I don't get in the
> > > IRON approach is how you cope with the fact that a user simply types
> > > some name into an application.  We can't hardly ask them
> > which network
> > > they want to use to look up the name.  The MIF approach, as
> > much as it
> > > makes me airsick, does address that issue.
> > >
> > > A
> > >
> > > --
> > > Andrew Sullivan
> > > ajs@anvilwalrusden.com
> > > _______________________________________________
> > > mif mailing list
> > > mif@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mif
> >
> >
> >

v2.23.0 | Report a Bug | By Email