IETF Logo Mail Archive

Re: [armd] address resolution requirement from hosts to overlay edge nodes. Any opinion?

Igor Gashinsky <igor@yahoo-inc.com> Wed, 22 February 2012 23:19 UTC

Return-Path: <igor@yahoo-inc.com>
X-Original-To: armd@ietfa.amsl.com
Delivered-To: armd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E907621F84DC for <armd@ietfa.amsl.com>; Wed, 22 Feb 2012 15:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.599
X-Spam-Level:
X-Spam-Status: No, score=-18.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLulvl3HoyAU for <armd@ietfa.amsl.com>; Wed, 22 Feb 2012 15:19:26 -0800 (PST)
Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by ietfa.amsl.com (Postfix) with ESMTP id 46EB521F84DF for <armd@ietf.org>; Wed, 22 Feb 2012 15:19:26 -0800 (PST)
Received: from netops1.corp.bf1.yahoo.com (netops1.corp.bf1.yahoo.com [98.139.254.110]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q1MN8mJG081111; Wed, 22 Feb 2012 15:08:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1329952133; bh=yzG676lHbDuiDQ70xp0xfGHoDAJmFp7f6pzrO1hywW0=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=qTT3yZPUK7EoThRDQQwdfEt6tcO8KiIiNU+i4404K0enm1IC5IV/CLnMyXX2P8VJu bnYDnfNuTXGhEH2rUqx2zzIlz3p5EcXsbyZjo+qT/SM9ObLq0gKZTuUGNhZtAnholh wcxA94xEiRbzzk4Ngvz/goSfLMGYhwNTekWub3tU=
Date: Wed, 22 Feb 2012 15:08:48 -0800 (PST)
From: Igor Gashinsky <igor@yahoo-inc.com>
X-X-Sender: igor@netops1.corp.bf1.yahoo.com
To: Linda Dunbar <linda.dunbar@huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F632E2223D@dfweml505-mbx>
Message-ID: <alpine.LRH.2.00.1202221506230.24790@netops1.corp.bf1.yahoo.com>
References: <CA+-tSzxP2uruxqCQSBD7O+VurqxziZG3HhzSyfcHSRBeCTVSRg@mail.gmail.com> <7AE6A4247B044C4ABE0A5B6BF427F8E291E2C8@dfweml503-mbx> <D8CD26287252844898B508C40824D8F4830AEE@AD-EXH02.adhost.lan> <4A95BA014132FF49AE685FAB4B9F17F632E2223D@dfweml505-mbx>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Thomas Narten <narten@us.ibm.com>, "armd@ietf.org" <armd@ietf.org>
Subject: Re: [armd] address resolution requirement from hosts to overlay edge nodes. Any opinion?
X-BeenThere: armd@ietf.org
X-Mailman-Version: 2.1.12
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." <armd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/armd>, <mailto:armd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/armd>
List-Post: <mailto:armd@ietf.org>
List-Help: <mailto:armd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/armd>, <mailto:armd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2012 23:19:27 -0000

On Wed, 22 Feb 2012, Linda Dunbar wrote:

:: Michael, 
:: 
:: > -----Original Message-----
:: > Microsoft is configurable for IGMP Multicast and Unicast.  There are
:: > also the other LB protocols such as CARP, VRRP, GLBP, HSRP, etc.
:: > 
:: 
:: Why do you consider VRRP as LB protocols? Hosts are not even aware of if VRRP is used or not, correct?

I actually can easily see VRRP being termed an LB protocol  -- while it's 
true that VRRP and HSRP are first-hop redundancy protocols, by striping 
VRRP/HSRP groups along multiple switches, you can manually achieve 
load-ballancing between multiple gateways, in fact, quite a few people do 
that very thing (and have done it for over a decade).

-igor

--------------------+----------------------+------------------
   Igor Gashinsky   | Network Architecture | Yahoo! Inc.
 igor@yahoo-inc.com |  cell 917.807.2213   | Do You... Yahoo?
--------------------+----------------------+------------------

v2.8.7 | Report a Bug | By Email