Re: [mif] Five additional problem statements for mif----Different metric measurements
Min Hui <huimin.cmcc@gmail.com> Wed, 18 March 2009 03:51 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 9D2CE3A6873 for <mif@core3.amsl.com>; Tue, 17 Mar 2009 20:51:39 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b6j2ZEkdxDlD for <mif@core3.amsl.com>; Tue, 17 Mar 2009 20:51:38 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by core3.amsl.com (Postfix) with ESMTP id B0F933A6802 for <mif@ietf.org>; Tue, 17 Mar 2009 20:51:38 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so465689yxm.49 for <mif@ietf.org>; Tue, 17 Mar 2009 20:52:22 -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=ZAIpkvIyEwxg6Xfhjz8on9GRi+LWkWg8aew/BAA6bm4=; b=hIDVfwsqqcRWYimeaHTWwMn0C0ZnILpa8wEQKqyKz/bylTaxs+lYH19Anv8aTNkWKd 6IjIiXe/7TgZeoqR+WU/Nw3XPygzbEmDPJxObDD2WtC0Lg0xKn9hg81P/MdHK9TcxWG7 cbf40UTfah5jhLAt1uQjrhGrEtfrCtu6aImqs=
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=d3ahtqF3yqnR8dxzUIrSYpNxqBlXnyZr0clgn7H4tRe1AYTdPUvuXv+r6Op8L+VK5d CqaGSU0fTWrumoL0jS1Go5n6MuBbMoaNZuyiEOUh73/7+MjNPEm2kPdEx32ID8De+rfn Hdw5l/p563Wo/TX1HuS3va63fAhkOHsrtIa8A=
MIME-Version: 1.0
Received: by 10.142.162.9 with SMTP id k9mr307032wfe.129.1237348341812; Tue, 17 Mar 2009 20:52:21 -0700 (PDT)
Date: Wed, 18 Mar 2009 11:52:21 +0800
Message-ID: <5dca10d30903172052h16ad160cv99df5f7e0254aedb@mail.gmail.com>
From: Min Hui <huimin.cmcc@gmail.com>
To: mif <mif@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [mif] Five additional problem statements for mif----Different metric measurements
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:51:39 -0000
Hi, all This is the third one: Different metric measurements Metrics are used to measure the performance of routings, the lower metric it owns, the higher priority it has. For example, the default gateway is chosen based on the metric rule as RFC1122 description, The one have the lowest metric value becomes to the default gateway among several connected gateways, and the interface correspond to this gateway turns to be the default interface. Metric rules are different depending on the access technology and routing protocol, if the multiple interfaces connect to multiple access networks which have different measurements of metrics, the comparing of metrics will be meaningless. However, the current operating system really does this to choose routing among several different networks in multiple interfaces situation. For example, current metric rules define the 100M bps Ethernet network card to be 20 and 10M bps to be 30, but the CDMA data card set its metric value as 1, although its speed is lower than 100M bps Ethernet network card, and the host will choose the CDMA data card as the default network card. This problem confuses the selection of routing in multiple interfaces situation. - 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 >