Re: [mif] Five additional problem statements for mif ---- host routing
Min Hui <huimin.cmcc@gmail.com> Wed, 18 March 2009 03:44 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 71CAC3A6873 for <mif@core3.amsl.com>; Tue, 17 Mar 2009 20:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
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 8TkRtN08FE4P for <mif@core3.amsl.com>; Tue, 17 Mar 2009 20:44:56 -0700 (PDT)
Received: from mail-gx0-f160.google.com (mail-gx0-f160.google.com [209.85.217.160]) by core3.amsl.com (Postfix) with ESMTP id 81EA03A6802 for <mif@ietf.org>; Tue, 17 Mar 2009 20:44:56 -0700 (PDT)
Received: by gxk4 with SMTP id 4so567020gxk.13 for <mif@ietf.org>; Tue, 17 Mar 2009 20:45:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=5BuKAjx7l/W00uXB5F6qksb9MtSzVa5ivUFhAQKHJEg=; b=DeNpc/fay0+SSBXNkWhVzf1IPcU7sKGbCmhW51vdXGJ9oSVwC4H/S6NenvIa7CzNn1 91s0EaxPBysvqVZ+W6HXxCw2Zk0m3dl1Jvft/36IFZba6q/zean8Wi4j210kWfB1AAm+ vXRMbxoQl4yT3MdEETeYXyhfKh0hhUpZeuaws=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=g+R6Baio7B0hjqY7/IklQDIZNYc/jOuT05INkq0o1QqHv3PyE+/2EKJB0nZUGhQEJH Epoyl5XGMEGTHJqOCk9UtWKk43czhw0/D9SC5kolqCGL8/Z659HRM4QRPVLVgQ71LONK 7Vz9dJRoXvTSutpVa3S/1fbtyZ5USKDV0uL0s=
MIME-Version: 1.0
Received: by 10.143.10.15 with SMTP id n15mr291421wfi.319.1237347939309; Tue, 17 Mar 2009 20:45:39 -0700 (PDT)
Date: Wed, 18 Mar 2009 11:45:39 +0800
Message-ID: <5dca10d30903172045g6bb8f43u3980dbc021a32932@mail.gmail.com>
From: Min Hui <huimin.cmcc@gmail.com>
To: mif <mif@ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [mif] Five additional problem statements for mif ---- host routing
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: Wed, 18 Mar 2009 03:44:57 -0000
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. 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 >