Re: [mif] Five additional problem statements for mif ---- hostrouting
Min Hui <huimin.cmcc@gmail.com> Thu, 19 March 2009 02:25 UTC
Return-Path: <huimin.cmcc@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 787243A695E for <mif@core3.amsl.com>; Wed, 18 Mar 2009 19:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.007
X-Spam-Level:
X-Spam-Status: No, score=-1.007 tagged_above=-999 required=5 tests=[AWL=-1.458, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id daNuYOlmvzD3 for <mif@core3.amsl.com>; Wed, 18 Mar 2009 19:25:34 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by core3.amsl.com (Postfix) with ESMTP id A75CC3A68C6 for <mif@ietf.org>; Wed, 18 Mar 2009 19:25:34 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 24so387898wfg.31 for <mif@ietf.org>; Wed, 18 Mar 2009 19:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=odssZfVjwt68Six7KE9ZjtZIALLiPH1oI6yF/ubLvW8=; b=WwSOzPl+o7fd3sR8MJyUFMXpybaf8TQzR8IzD8OS09pGBrRKUEvewWxtdHbOIqGJRB OrTdyZqwTp4xRVcxs2eSNxjQb87an4IJJKWPf2y1hroMrBTCIvMTcOkgMcrv0TYhadKz XBbIgOA4bhjjb11zsiZkUpV3SdGz+cgY6hWoU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mm6hy5R7uUQbBzACLnVbKxDHRyUy/Ond21NCm8Gk5Kp8j2+XgM6rLoPPQutdjdbdco gHbjFnciTQ4Bx5LAZrS2qh6gyWdDrnQFWoyVBbytCrVrPlkrRm3gxLnT/Y1TI0cpNdQM lolEYCHR4XuRVgf0DfP2b/XPRu0PV4hVsZuxU=
MIME-Version: 1.0
Received: by 10.142.100.1 with SMTP id x1mr740905wfb.256.1237429579596; Wed, 18 Mar 2009 19:26:19 -0700 (PDT)
In-Reply-To: <200903182031271046233@gmail.com>
References: <200903182031271046233@gmail.com>
Date: Thu, 19 Mar 2009 10:26:19 +0800
Message-ID: <5dca10d30903181926k23b85de0r21b3f1801165d7c3@mail.gmail.com>
From: Min Hui <huimin.cmcc@gmail.com>
To: liuyin <liuyin08@gmail.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] Five additional problem statements for mif ---- hostrouting
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 19 Mar 2009 02:25:35 -0000
Hi, Liuyin Thanks for correcting, I'll modify this sentence. Thank you very much. - Hui Min 2009/3/18, liuyin <liuyin08@gmail.com>: > > Hi,hui > I think there is a problem in the description. Please see inline. Thanks. > Best regards. > > liuyin > > > 2009-03-18 ________________________________ > > liuyin ________________________________ > > 发件人: Min Hui > 发送时间: 2009-03-18 11:45:44 > 收件人: mif > 抄送: > 主题: Re: [mif] Five additional problem statements for mif ---- hostrouting > > Hi, everyone > This is the first one: Host routing > The host routing currently follows the default gateway > mechanism, > which will choose the unify gateway among more than one > default routes > ('0.0.0.0'), the detail is described in RFC1122. The > default gateway > guarantees there always has a route to network when the > host can not > find a specific route for a datagram in the route table. > But when it comes to multiple interfaces situation, the > default > gateway mechanism in host routing will let all the IP > flows go out > through one interface except some specific assignment > (e.g. static > routing item). In this case, the applications can’t use > different > interfaces which are the aim of multiple interfaces. > > ==> This sentence makes me confused. I think it should express like this: > In this case, the applications can't use different interfaces, which > against > the aim of multiple interfaces. > > The reason is the > application will not appoint a source address in most > situations > currently. The source address will be determined by host > operating > system after querying the host routing table, if there > is any > available routing item for the destination, the > corresponding source > address of this routing item will be selected. In most > cases, the > routing item of default gateway will be used, so that > every > application will use the same interface. > In conclusion, the above host routing mechanism is one of > problems in > the way to maintain multiple interfaces work > simultaneously. > - Hui Min > 2009/3/18 Min Hui <huimin.cmcc@gmail.com>: > > Hi, all mif fans > > > > I have viewed the agenda of mif bof, and I notice some > problem > > statements for mif are not concluded in the current ps > documents which > > will be discussed in the meeting. > > So I post these additional problems in the mail list for > discussion, > > all of them come from the draft > > "draft-hui-ip-multiple-connections-ps-02" with some > modifications > > according to the comments received recently. > > There are five problems in addition, which will be > proposed in five > > separated mails in order to have sufficient discussion > for each of > > them. > > Five mails will be sent out following this mail, the > structure is: > > 1. Host routing > > 2. DNS selection > > 3. Different metric measurements > > 4. Source address selection for IPv4 > > 5. TOS consideration > > > > Any comment is welcomed, and thanks for your notice. > > > > BR, > > - Hui Min > > > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif