Re: [MBONED] [nvo3] NVO3 Multicast Framework
Anoop Ghanwani <anoop@alumni.duke.edu> Tue, 24 May 2016 19:35 UTC
Return-Path: <ghanwani@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C242A12D113; Tue, 24 May 2016 12:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPtnKNyVx5v2; Tue, 24 May 2016 12:35:05 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E505112D0CC; Tue, 24 May 2016 12:35:04 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id t145so17283597qke.2; Tue, 24 May 2016 12:35:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=R0yW4uB/PjI52i0c/WQchQ4Elr3Nm/qC/GR1is8/qUc=; b=mAOkFNUI9flSvpKVPZWRZrZ57RzBKq7xhr+xIlR5qp7spNKXs5jEXaaWGdDQh8q6D9 OjWrya+OhM6d3YQ3JoPF6fKFjJrYP7MB6XOmgExd/RgnihYZUfVXxrPmpZc225Gm8h5o vvDbMVy895afJEpcGQC0fy1HM+50ZHJ2sfGq3yyUvtfVYHpPrX8b6wuP/ihN1DWNn6Me 8Ys3hktwqL+4E0bchteuyjGdhXGHQ0YOWig2+IhFnG4nb8pa3XovrA1em5g3ik+CEuyj YNSoknQwC5SDIFKbLKIqCxAxpjtQTBFfJ6Me51I+DJpTfGvuTfD+osHPHV/ro5hVHRnt /cbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=R0yW4uB/PjI52i0c/WQchQ4Elr3Nm/qC/GR1is8/qUc=; b=U+l7UozVsyZq8Dj9gmru6OWWLOwu4FSBMo/67Ow+Yfe1S7ZtX0AWiNW7HFX3l4wHIv aTZhH0EJvN6KVFFmbF7Mcl3qBygZJTrS1nKyy8uj90o0otSWXr0FDpbTKjzTKCQyd8vn nDu3mUvJ61Lp3MXdf/WI14s/nYjvSRdAEVrrGQtdFSzmFIgk0mKh2XRYBW64PyYwr7I5 Adtx4PFk5oVVD2WxPcHOyinALqzrJ3KZ1TcJOmdejzL/2RwqDUo8BpGwa/E8ylU3M7TM eLrR08cEB3BmE092ybcf+Ja0WWVD7PgLvqBT6JtQs3Z9JS73C50d+Qoii/dKTazq9zU4 6DRQ==
X-Gm-Message-State: ALyK8tL5eLpx3gZMRyKmcIhGq/gaE0IC1p/5C5sEC+ozBTsLYPKoXdr52+Qo4lM7zySiJ+iTwhKDwUYn9vapRQ==
MIME-Version: 1.0
X-Received: by 10.55.80.131 with SMTP id e125mr5038230qkb.155.1464118503966; Tue, 24 May 2016 12:35:03 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.55.135.199 with HTTP; Tue, 24 May 2016 12:35:03 -0700 (PDT)
In-Reply-To: <F0088019-8A54-47B6-B600-303996B58C99@gmail.com>
References: <20160512144607.T22764@sapphire.juniper.net> <17B47CE8-D558-4748-88D6-FEC17A02357A@gmail.com> <D36A11E1.9BBC8%matthew.bocci@nokia.com> <429D0BE5-C6A5-4AEE-975E-2A5C7ED65631@gmail.com> <807243401bcc4ca3a7e014690a920f96@PRDMSEXCH002.gsm1900.org> <F0088019-8A54-47B6-B600-303996B58C99@gmail.com>
Date: Tue, 24 May 2016 12:35:03 -0700
X-Google-Sender-Auth: GW1JwPN2K8oUJ4Fs8hg8Tp1v158
Message-ID: <CA+-tSzxH9OfUasUXssJRfP1ijXZYbAugeoSBGVErZ-smmtF1ww@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: Dino Farinacci <farinacci@gmail.com>
Content-Type: multipart/alternative; boundary="001a114a9ad056915905339ba75f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mboned/EhwpC4-GGIBmTUB4U0kFoIQt6MI>
Cc: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, MBONED WG <mboned@ietf.org>, "<nvo3@ietf.org>" <nvo3@ietf.org>
Subject: Re: [MBONED] [nvo3] NVO3 Multicast Framework
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 19:35:08 -0000
Thanks Beau & Dino. We'll add a reference to RFC 6831 and a brief discussion of SSM. Anoop On Tue, May 24, 2016 at 11:42 AM, Dino Farinacci <farinacci@gmail.com> wrote: > If a reference to RFC6831 is provided, then there are many details on how > an underlay can support ASM, Bidir, and SSM. > > Dino > > > On May 24, 2016, at 11:35 AM, Williamson, Beau > <Beau.Williamson@T-Mobile.com> wrote: > > > > I'd like to see Section 3.4, "IP multicast in the underlay" expanded a > bit. > > > > The section mentions the use of BIDIR for a scalable underlay. The sad > fact is that many vendors still do not fully support BIDIR in their devices > (after how many years?) or have limitations on its use that preclude it as > a viable option. I'm no expert in these Underlay sort of DC to DC networks > but it seems that SSM would not have that issue since it is basically a > subset (and much simpler to implement and configure) of the PIM protocol > and would therefore be available in pretty much all vendor devices that > support multicast. The problem is one of Source Discovery of the VTEPs > (or, in the case of this draft I think the term is NVE) which would be the > sources of the multicast traffic in each TS. > > > > At the very least, I'd like to see a paragraph discussing the possible > use of SSM as an alternative to BIDIR if the VTEP/NVE devices had a way to > learn of each other's IP address so that they could join all SSM SPT's to > create/maintain an underlay SSM IP Multicast tunnel solution. This would > greatly simplify the configuration and management of the underlay IP > Multicast environment. > > > > I realize that the VTEP/NVE Source Discovery problem is beyond the scope > of this Framework document but I'd like to see the above mentioned to > possibly encourage more work in this area if it is not already underway. > > > > > > Beau Williamson > > CCIE #1346 R/S Emeritus > > Principal Member of Technical Staff > > Corporate Engineering > > metroPCS/T-Mobile > > Internal: 314982 > > Office: 469.330.4982 > > Mobile: 972.679.4334 > > > > > > -----Original Message----- > > From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Dino > Farinacci > > Sent: Tuesday, May 24, 2016 12:21 PM > > To: Bocci, Matthew (Nokia - GB) > > Cc: MBONED WG; <nvo3@ietf.org> > > Subject: Re: [MBONED] NVO3 Multicast Framework > > > > Sorry, I thought I had. NVo3, see my comments below. > > > > Dino > > > >> On May 24, 2016, at 6:14 AM, Bocci, Matthew (Nokia - GB) < > matthew.bocci@nokia.com> wrote: > >> > >> Hi Dino > >> > >> Could you copy NVO3 on your comments, please? > >> > >> Thanks > >> > >> Matthew > >> > >> From: EXT Dino Farinacci <farinacci@gmail.com> > >> Date: Monday, 16 May 2016 at 23:31 > >> To: Leonard Giuliano <lenny@juniper.net> > >> Cc: MBONED WG <mboned@ietf.org>, Matthew Bocci < > matthew.bocci@alcatel-lucent.com>, Benson Schliesser < > bensons@queuefull.net> > >> Subject: Re: [MBONED] NVO3 Multicast Framework > >> > >> I just have one minor comment. Regarding the second paragraph: > >> > >> <PastedGraphic-2.png> > >> > >> Using LISP-signal-free does not mean the head-end must do replication. > The draft indicates that a mapping system is used to decide where packets > go. If the mapping database indicates that packets are encapsulated to > multicast RLOCs, or unicast RLOCs, or both in one set, so be it. > >> > >> And note if there is a single multicast RLOC, then there is no > replication happening at the head-end, just one packet encapsulting > multicast in multicast. > >> > >> So what is written above is true, but it may be associated with an > incorrect section title. > >> > >> Dino > >> > >>> On May 12, 2016, at 2:52 PM, Leonard Giuliano <lenny@juniper.net> > wrote: > >>> > >>> MBONED, > >>> > >>> The following draft recently went through WG last call in the NVO3 > working group: > >>> > >>> https://datatracker.ietf.org/doc/draft-ietf-nvo3-mcast-framework/ > >>> > >>> This doc covers multicast in data center overlay networks. As you > know, it is part of our charter in MBONED to provide feedback to other > relevant working groups. Please review and send any comments to the NVO3 > WG mailing list (nvo3@ietf.org)- all comments will be greatly appreciated > by NVO3. > >>> > >>> _______________________________________________ > >>> MBONED mailing list > >>> MBONED@ietf.org > >>> https://www.ietf.org/mailman/listinfo/mboned > >> > >> <PastedGraphic-2.png> > > > > _______________________________________________ > > MBONED mailing list > > MBONED@ietf.org > > https://www.ietf.org/mailman/listinfo/mboned > > _______________________________________________ > nvo3 mailing list > nvo3@ietf.org > https://www.ietf.org/mailman/listinfo/nvo3 >
- [MBONED] NVO3 Multicast Framework Leonard Giuliano
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Manfredi, Albert E
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Leonard Giuliano
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Williamson, Beau
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Truman Boyes
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Bocci, Matthew (Nokia - GB)
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Olufemi Komolafe
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Behcet Sarikaya
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar