Re: [arp222] Some concerns about the MOOSE
Malcolm Scott <Malcolm.Scott@cl.cam.ac.uk> Thu, 29 July 2010 09:39 UTC
Return-Path: <Malcolm.Scott@cl.cam.ac.uk>
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 A754C3A696F for <arp222@core3.amsl.com>; Thu, 29 Jul 2010 02:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 uUGprlYFUrnL for <arp222@core3.amsl.com>; Thu, 29 Jul 2010 02:39:49 -0700 (PDT)
Received: from helene.retrosnub.co.uk (helene.retrosnub.co.uk [IPv6:2a01:348:11d:1008:0:ff:fe00:1]) by core3.amsl.com (Postfix) with ESMTP id 80DBE3A698A for <arp222@ietf.org>; Thu, 29 Jul 2010 02:39:48 -0700 (PDT)
Received: from callisto.malc.org.uk (callisto.malc.org.uk [IPv6:2a01:348:11d:2:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: m@lcolm.org.uk) by helene.retrosnub.co.uk (Postfix; Retrosnub mail submission agent) with ESMTPSA id 429304D0C8; Thu, 29 Jul 2010 10:40:10 +0100 (BST)
Date: Thu, 29 Jul 2010 10:40:09 +0100
From: Malcolm Scott <Malcolm.Scott@cl.cam.ac.uk>
X-X-Sender: mas90@callisto.malc.org.uk
To: xuxiaohu 41208 <xuxh@huawei.com>
In-Reply-To: <fdd3b4fc1d7d.1d7dfdd3b4fc@huawei.com>
Message-ID: <alpine.DEB.2.00.1007291039150.30073@callisto.malc.org.uk>
References: <fdd3b4fc1d7d.1d7dfdd3b4fc@huawei.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: arp222@ietf.org
Subject: Re: [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:39:49 -0000
At 17:31 today, xuxiaohu 41208 wrote: > 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 This is not the case. I assume you're in the Bar BOF; I'll explain in my presentation. Malcolm -- Malcolm Scott University of Cambridge Computer Laboratory
- [arp222] Some concerns about the MOOSE xuxiaohu 41208
- Re: [arp222] Some concerns about the MOOSE Malcolm Scott
- [arp222] 回复 :Re: Some concerns about the MOOSE xuxiaohu 41208