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

Linda Dunbar <dunbar.ll@gmail.com> Fri, 12 December 2014 21:23 UTC

Return-Path: <dunbar.ll@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0E61A8A4B; Fri, 12 Dec 2014 13:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 AN_ggj-LA3Fe; Fri, 12 Dec 2014 13:23:37 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DCB01A8A39; Fri, 12 Dec 2014 13:23:37 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id rd3so7962901pab.14 for <multiple recipients>; Fri, 12 Dec 2014 13:23:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fXWbUCFbcztMa3JTodrwZhjIvZZKqe5X1r9Pmmth+LI=; b=qTSIlKaJrH0QnhyvyDQFGBHMB7dKy/GL4CLv7rOjymFcLcm+fSXQZwC9NWCMzi5Nhr rTnV8egd9535XO7yJyylwI98mHJcZuH9iZG2mCnIHZdIW9tcmTvbTohUiWb5VYZSU2Gc 89Idt2g27EPOrBCCrqqLhbC42P9byblpWQtAjnvak9wKs320a/Hdpc1LIWwykz7LmFI7 Jt8K8nT/aHpsBmGYqEW055pIWpM0YNg3/Mm+b4WHsTAEZ5o4NdqCNdMMtxsDOOKIMYkp Pg5GxMNIG74WtNd8xiUW81DfzcgIDhCxAwnw93Suali+NetGDcNY12H7MIhwF3p+Y/gv zVbA==
MIME-Version: 1.0
X-Received: by 10.68.211.7 with SMTP id my7mr30437212pbc.115.1418419416092; Fri, 12 Dec 2014 13:23:36 -0800 (PST)
Received: by 10.70.18.197 with HTTP; Fri, 12 Dec 2014 13:23:36 -0800 (PST)
In-Reply-To: <D1F36B9B-6883-484C-967E-92B62B1F42C2@Contextream.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645E75398@dfweml701-chm> <B52034D4-AAD1-4070-B24A-52E2A7E4DAFC@gmail.com> <D1F36B9B-6883-484C-967E-92B62B1F42C2@Contextream.com>
Date: Fri, 12 Dec 2014 15:23:36 -0600
Message-ID: <CAP_bo1YBtAY9s2GEMOmmb755xTnM6qvxS-B1jSOVjRvgj_s9cA@mail.gmail.com>
From: Linda Dunbar <dunbar.ll@gmail.com>
To: Sharon Barkai <Sharon@contextream.com>
Content-Type: multipart/alternative; boundary="e89a8ff1c6a4705559050a0b81ac"
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/z5Yy0EfqLqtjD-EPrY676pC-gJk
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, Dino Farinacci <farinacci@gmail.com>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [nvo3] [lisp] Comparing LISP multicast with draft-ghanwani-nvo3-app-mcast-framework-01.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 12 Dec 2014 21:23:41 -0000

Sharon,

Is the "floating anchor in mapping database" same as the "systemic
anchoring"?

Can you send me the draft names that describe the "floating anchoring"?  We
definitely should make it consistent across multiple WGs.

Thanks, Linda


On Mon, Dec 8, 2014 at 8:28 PM, Sharon Barkai <Sharon@contextream.com>
wrote:
>
> I think it's important to point out that all these features which require
> in-network anchoring e.g. multicast replication, mobility/motion, chaining,
> NAT traversal, anycast ... in lisp, use ONE consistent methodology - a
> "floating" anchor in the mapping database can be unambiguously resolved &
> realized dynamically at the network edge Ingres just in time.
> Would really be good if this systemic anchoring approach is carried over
> to nvo3,
> rather then each such feature will be built based on a whole new
> methodology-terminology.
>
> --szb
>
> > On Dec 8, 2014, at 16:14, Dino Farinacci <farinacci@gmail.com> wrote:
> >
> >
> >> 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
> >
> > _______________________________________________
> > lisp mailing list
> > lisp@ietf.org
> > https://www.ietf.org/mailman/listinfo/lisp
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>