Re: [lisp] Comparing LISP multicast with draft-ghanwani-nvo3-app-mcast-framework-01.txt

Dino Farinacci <farinacci@gmail.com> Tue, 09 December 2014 00:14 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77E961A1A62; Mon, 8 Dec 2014 16:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 7dA6IAG9wncr; Mon, 8 Dec 2014 16:14:40 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8091B1A02BE; Mon, 8 Dec 2014 16:14:40 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id lj1so6183563pab.19 for <multiple recipients>; Mon, 08 Dec 2014 16:14:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=w/zwQfvgrRk7bEjZfQaN4CV32xYW8Cy4EOhBOK32Z5k=; b=ckOUxgKIabS4JyRiAGWcMhSRdxdZsx+jzA0f84vQnxzRuDsKv/MH3xNorKuEVI/6bN YCZi37a/wGj/QY6QpmymDyHJIi/lG0GOSkKzU423sIMmzlymlUzB5Uj+yWXYD5UnNTwc u0dllyiWFYUIJ/fNk7as2HiRXJh+0AU1WTNCl2UFvSTMr9aWe2iJs8yAYlt5ZUi2ErdK BWgeP2yr5ekbW4iawsBD2BhhlC5sCqtEwT+/8Yu4mRYvMl8zh+Xl31BGV4rqxEOggBGC koA+8San0TwWEhPfu5px4T5qPSFpenPpht9nhqo3qx4wShK0UijGh6Wh1q/8rF1+MXID 70sw==
X-Received: by 10.68.131.133 with SMTP id om5mr55927pbb.41.1418084079756; Mon, 08 Dec 2014 16:14:39 -0800 (PST)
Received: from [192.168.1.79] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPSA id fy4sm37287849pbb.42.2014.12.08.16.14.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 16:14:39 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645E75398@dfweml701-chm>
Date: Mon, 8 Dec 2014 16:14:37 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B52034D4-AAD1-4070-B24A-52E2A7E4DAFC@gmail.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645E75398@dfweml701-chm>
To: Linda Dunbar <linda.dunbar@huawei.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/hrM9Vyw_xzREULe2yIwwqzgUo6k
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] Comparing LISP multicast with draft-ghanwani-nvo3-app-mcast-framework-01.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 00:14:42 -0000

> RFC 6831 (LISP for Multicast) states: 
> "The fundamental multicast forwarding model is to encapsulate a multicast packet into another multicast packet"

Right, the fundamental model so we have the most efficient form of multicast delivery.

> So LISP assumes that the underlay network supports some sort of IP multicast scheme. 

No, LISP does not, just this RFC does. If you look at the other LISP multicast related RFCs, you will see that you can encapsulate multicast packets inside of unicast packets.

And you can use PIM signaling specified in RFC 6831 to instruct an ETR to encapsulate in unicast.

> In NVO3 environment, especially in data center environment, the underlay network may not necessarily support IP multicast. draft-ghanwani-nvo3-app-mcast-framework-01 describes various mechanisms for forwarding tenant multicast traffic without the underlay network supporting the multicast protocols. 

Right, see draft-farinacci-lisp-signal-free-multicast-01. It can simplify the control-plane as well as encapsulate in either unicast or multicast.

Dino

> 
> We appreciate your feedback. 
> 
> Linda 
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: Monday, December 08, 2014 4:17 PM
> To: Vinay Bannai; Linda Dunbar; Vinay Bannai; Ram (Ramki) Krishnan; Linda Dunbar; Anoop Ghanwani; Ram Krishnan; Anoop Ghanwani
> Subject: New Version Notification for draft-ghanwani-nvo3-app-mcast-framework-01.txt
> 
> 
> A new version of I-D, draft-ghanwani-nvo3-app-mcast-framework-01.txt
> has been successfully submitted by Linda Dunbar and posted to the IETF repository.
> 
> Name:		draft-ghanwani-nvo3-app-mcast-framework
> Revision:	01
> Title:		Framework of Supporting Applications Specific Multicast in NVO3
> Document date:	2014-12-08
> Group:		Individual Submission
> Pages:		16
> URL:            http://www.ietf.org/internet-drafts/draft-ghanwani-nvo3-app-mcast-framework-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ghanwani-nvo3-app-mcast-framework/
> Htmlized:       http://tools.ietf.org/html/draft-ghanwani-nvo3-app-mcast-framework-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ghanwani-nvo3-app-mcast-framework-01
> 
> Abstract:
>   This draft discusses the framework of supporting applications
>   specific multicast traffic, i.e. the non ARP/ND related
>   multicast/broadcast traffic, in a network that uses Network
>   Virtualization using Overlays over Layer 3 (NVO3). It describes the
>   various mechanisms and considerations that can be used for
>   delivering those application specific multicast traffic in networks
>   that use NVO3.
> 
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>