IETF Logo Mail Archive

Re: [nvo3] [MBONED] NVO3 Multicast Framework

Dino Farinacci <farinacci@gmail.com> Tue, 24 May 2016 19:18 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 040D412D9B9; Tue, 24 May 2016 12:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 MjKJiAL-pKjq; Tue, 24 May 2016 12:18:23 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::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 7051812D0CC; Tue, 24 May 2016 12:18:23 -0700 (PDT)
Received: by mail-pa0-x229.google.com with SMTP id tb2so9439919pac.2; Tue, 24 May 2016 12:18:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NvQQOUcgDq+uI+VvEEBbcvFyt7ri7XwVP/Tzm4cSTlU=; b=0X8sOetTQbazKMWFJH0DNqcmHfdko28zbWdod3DRQfm90n772CnSWuMrzno5iwtwuz B2K+oyradjjK0H/y8MFXg+DOZ2W/F6CfYb6z87LT7r0wQCGsXPFF2ktzV3G6V4ywqjQA sEBbxqeIAEklIkHhyyJksugml2AiXpqO8CODV8f5IKtbHaYc/dwACw44q8FUTVluE7Av vefETi7qB+2XFZsmWfZA6F476Xvpm6eH+qq7u45Hy+YUoOba5vWKxH1EJfjpRdK6iEr+ hGTN9WSmQa0ibmhO2cOrHUSf6462c9EN6gAvY+YP6Zl3oLwCcU5BxCwQ6w77gagUNFjp n8ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NvQQOUcgDq+uI+VvEEBbcvFyt7ri7XwVP/Tzm4cSTlU=; b=HFQ9MtMnRrHCSNtmj9FoDhxcZGQZBQ1ZA+ILjF92feRf6arVp50iJAcNS1i2WclzbQ /VrKDiDXic78L5ek87D/xByNgCHBaEMWRsk9dlquEvkMfH9i0BoRCnFWOWWymmVtLmEb 0rApq+eq7E2bvSeTSHnLFv3b352lbkjhWkgTrU4KkxaU/sK+GROniPrRa/YQrK0xd4Bc 96ah+ziqR5aeSM7cwkSMix2rcnpvhmlIKMWBarLgld5SwiLOIyYIHQomSAPxXDFnjo9U OSRJHVeOWGN/McCA3GbRYuPfTcnNwMaLIMXjGeBthYwog0kuB6wCb5dgrcn9vUog9Y5y 1D+g==
X-Gm-Message-State: ALyK8tJhAK4XSYQkMT+Tsqs8PMCNZBbOX6zkNaca7mhkMpkgP+VE3kiRJ0WjruvgbeXBVQ==
X-Received: by 10.66.83.163 with SMTP id r3mr9345269pay.54.1464117502807; Tue, 24 May 2016 12:18:22 -0700 (PDT)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id lg17sm7043267pab.36.2016.05.24.12.18.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 12:18:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CA+-tSzxeB_35kXTKkhFrUh+B90aiuvSHE500=rsO5nA3t=XV7A@mail.gmail.com>
Date: Tue, 24 May 2016 12:18:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <738778AD-DC10-4639-9892-D5BFCD460A99@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> <CA+-tSzxeB_35kXTKkhFrUh+B90aiuvSHE500=rsO5nA3t=XV7A@mail.gmail.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/gwob08Da1zTafCfJTKKlJGTRxIw>
Cc: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, MBONED WG <mboned@ietf.org>, "<nvo3@ietf.org>" <nvo3@ietf.org>
Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 19:18:35 -0000

I think so Anoop.

Dino

> On May 24, 2016, at 12:17 PM, Anoop Ghanwani <anoop@alumni.duke.edu> wrote:
> 
> Hi Dino,
> 
> Thanks for pointing that out.  Indeed that is not specific to head end replication.  We can move that text to a separate section that is referenced by the sections for all of the multicast methods.  Let me know if that would address the comment.
> 
> Thanks,
> Anoop
> 
> On Tue, May 24, 2016 at 10:20 AM, Dino Farinacci <farinacci@gmail.com> wrote:
> 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>
> 
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>

v2.23.0 | Report a Bug | By Email