Re: [armd] address resolution requirement from hosts to overlay edge nodes. Any opinion?
Mike McBride <mmcbride7@gmail.com> Tue, 14 February 2012 21:16 UTC
Return-Path: <mmcbride7@gmail.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 34C8F21F8652 for <armd@ietfa.amsl.com>;
Tue, 14 Feb 2012 13:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.318
X-Spam-Level:
X-Spam-Status: No, score=-3.318 tagged_above=-999 required=5 tests=[AWL=0.281,
BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 rxMyxowj3aAr for
<armd@ietfa.amsl.com>; Tue, 14 Feb 2012 13:16:29 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com
[209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 443E221F8617 for
<armd@ietf.org>; Tue, 14 Feb 2012 13:16:29 -0800 (PST)
Received: by lahl5 with SMTP id l5so441035lah.31 for <armd@ietf.org>;
Tue, 14 Feb 2012 13:16:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
bh=9FV+6VcKYOObSPY8beBzuwZVKRuOuI4WnS5L1pi5okg=;
b=Jt1sCWvzsXlKqFbL6/Q+Gel96NIk+1A5T2gCHCAvosfMwMv21SNw45If58lkMZN7La
3Ii429VeO4uItfnpTffgEOQzA8Im1qCxMCtUCGq1qlpPensV/OXzPx04omP/NiTnY3rm
Ny5l24/fRC/2a5/hMszTyAOhtlVgRqIs4wFkI=
MIME-Version: 1.0
Received: by 10.112.28.169 with SMTP id c9mr7841629lbh.42.1329254188223;
Tue, 14 Feb 2012 13:16:28 -0800 (PST)
Received: by 10.112.45.99 with HTTP; Tue, 14 Feb 2012 13:16:28 -0800 (PST)
In-Reply-To: <CA+-tSzwFWBWd0_QZ4CqgQmjTUaXnBafNVdk8oZvK6oRTCR4Jqg@mail.gmail.com>
References: <CA+-tSzzNeLP4N=Nv1EeBML51KTpmxPP3NWut+vnaWFy8RtUViA@mail.gmail.com>
<7AE6A4247B044C4ABE0A5B6BF427F8E291E1A5@dfweml503-mbx>
<CA+-tSzyvoDfwnKc7Yt65abQWSqMg2jF0iQax=wcYkmwtNGxZng@mail.gmail.com>
<60C093A41B5E45409A19D42CF7786DFD522A9BE1F1@EUSAACMS0703.eamcs.ericsson.se>
<CA+-tSzwZVYyEO62ngYGojwSrkSBBY2SWr93PDQmAp7a3y_7TMQ@mail.gmail.com>
<CAL3FGfy0iyo_TTr-iuSzQuqRm8Li753UFWQsk=RGWh_nCdPMMw@mail.gmail.com>
<CA+-tSzwFWBWd0_QZ4CqgQmjTUaXnBafNVdk8oZvK6oRTCR4Jqg@mail.gmail.com>
Date: Tue, 14 Feb 2012 13:16:28 -0800
Message-ID: <CAL3FGfwx=n9kKjwcARg6-ge2a-t-R+7RmR=d-qRJx=TdzNHMAQ@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Narten <narten@us.ibm.com>, "armd@ietf.org" <armd@ietf.org>,
Igor Gashinsky <igor@yahoo-inc.com>
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: Tue, 14 Feb 2012 21:16:30 -0000
Anoop, On Tue, Feb 14, 2012 at 12:32 PM, Anoop Ghanwani <anoop@alumni.duke.edu> wrote: > On Tue, Feb 14, 2012 at 12:14 PM, Mike McBride <mmcbride7@gmail.com> wrote: >> And what protocol improvements are needed for multicast with overlays? >> The multicast community is ready to help. Multicast makes us happy. Or >> are you solely talking about vendor implementation, s/w release, hw >> support problems? AFAIK multicast works fairly well with VXLAN, TRILL, >> L2VPN... What's missing? > > The whole problem of sending L2 multicast over a campus or data center > backbone, in any sort of significant way, is a new one enabled for the first > time by overlays. There are interesting challenges when pushing large > amounts of multicast traffic through a network, and have thus far been dealt > with using purpose-built networks. While the overlay proposals have > been careful not to impose new protocol requirements, they have not > addressed the issues of performance and scalability, nor the large-scale > availability of these protocols. There are interesting challenges with unicast and multicast in big flat DC networks. That's why we are here. One of the constant themes we hear with multicast is the FUD that it doesn't scale. Especially from vendors who are pushing another solution or who have a crappy multicast implementation. Meanwhile multicast is being deployed in large scale networks without scaling issue. Large L2 overlay networks? I don't know. Would be good to find out from the community about performance and scalability of multicast in the DC. mike
- [armd] address resolution requirement from hosts … Linda Dunbar
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… Mike McBride
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… AshwoodsmithPeter
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… David Allan I
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… David Allan I
- Re: [armd] address resolution requirement from ho… Mike McBride
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… Mike McBride
- Re: [armd] address resolution requirement from ho… Anoop Ghanwani
- Re: [armd] address resolution requirement from ho… AshwoodsmithPeter
- Re: [armd] address resolution requirement from ho… Michael K. Smith - Adhost
- Re: [armd] address resolution requirement from ho… Joel jaeggli
- [armd] Multicast in the data center [was Re: addr… Thomas Narten
- Re: [armd] Multicast in the data center [was Re: … Aldrin Isaac
- Re: [armd] address resolution requirement from ho… AshwoodsmithPeter
- Re: [armd] Multicast in the data center [was Re: … Linda Dunbar
- Re: [armd] Multicast in the data center [was Re: … AshwoodsmithPeter
- Re: [armd] Multicast in the data center [was Re: … David Allan I
- Re: [armd] Multicast in the data center [was Re: … Aldrin Isaac
- Re: [armd] address resolution requirement from ho… Igor Gashinsky
- Re: [armd] address resolution requirement from ho… Dino Farinacci
- Re: [armd] address resolution requirement from ho… Igor Gashinsky
- Re: [armd] address resolution requirement from ho… Linda Dunbar
- Re: [armd] address resolution requirement from ho… Igor Gashinsky
- Re: [armd] address resolution requirement from ho… Linda Dunbar
- Re: [armd] address resolution requirement from ho… Michael K. Smith - Adhost
- Re: [armd] Multicast in the data center [was Re: … thomas.morin