[arp222] Some concerns about the MOOSE

xuxiaohu 41208 <xuxh@huawei.com> Thu, 29 July 2010 09:31 UTC

Return-Path: <xuxh@huawei.com>
X-Original-To: arp222@core3.amsl.com
Delivered-To: arp222@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA4B03A6989 for <arp222@core3.amsl.com>; Thu, 29 Jul 2010 02:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.105
X-Spam-Level: *
X-Spam-Status: No, score=1.105 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 wlo3Zf7u4wgw for <arp222@core3.amsl.com>; Thu, 29 Jul 2010 02:31:24 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6E9A33A6971 for <arp222@ietf.org>; Thu, 29 Jul 2010 02:31:17 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6B00K24BSIVU@szxga03-in.huawei.com> for arp222@ietf.org; Thu, 29 Jul 2010 17:31:31 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6B000O1BSHWZ@szxga03-in.huawei.com> for arp222@ietf.org; Thu, 29 Jul 2010 17:31:29 +0800 (CST)
Received: from [172.24.1.3] (Forwarded-For: [130.129.116.197]) by szxmc04-in.huawei.com (mshttpd); Thu, 29 Jul 2010 17:31:29 +0800
Date: Thu, 29 Jul 2010 17:31:29 +0800
From: xuxiaohu 41208 <xuxh@huawei.com>
To: arp222@ietf.org
Message-id: <fdd3b4fc1d7d.1d7dfdd3b4fc@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
Subject: [arp222] Some concerns about the MOOSE
X-BeenThere: arp222@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion of issues associated with large amount of virtual machines being introduced in data centers and virtual hosts introduced by Cloud Computing." <arp222.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/arp222>, <mailto:arp222-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/arp222>
List-Post: <mailto:arp222@ietf.org>
List-Help: <mailto:arp222-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arp222>, <mailto:arp222-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 09:31:26 -0000

Hi,

If I understood the MOOSE correctly, the major contribution of MOOSE is to reduce the MAC forwarding table size by rewriting flat MAC addresses (i.e., source MAC addresses) to hierarchical MAC addresses on the ingress MOOSE switches. However, to introduce the address aggegation capability of IP into Ethernet, the forwarding behavior on Ethernet switch chips would have to be changed from full-matching algorithm to longest-mataching algorithm
. IMHO, this is a big obstacle for MOOSE.

Xiaohu