[lisp] Multicast agonostic NVE described by draft-ghanwani-nvo3-app-mcast-framework

Linda Dunbar <linda.dunbar@huawei.com> Wed, 29 October 2014 22:14 UTC

Return-Path: <linda.dunbar@huawei.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 6BF3B1A90AD; Wed, 29 Oct 2014 15:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 IbAXEhsQz23h; Wed, 29 Oct 2014 15:14:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079361A9121; Wed, 29 Oct 2014 15:14:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOE78297; Wed, 29 Oct 2014 22:14:03 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 29 Oct 2014 22:14:03 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Wed, 29 Oct 2014 15:13:50 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: Multicast agonostic NVE described by draft-ghanwani-nvo3-app-mcast-framework
Thread-Index: Ac/EhQABYHv1vOWVT6W+msem4gUujQA8Tj+AABShKyAAHorjAAtfJh7A
Date: Wed, 29 Oct 2014 22:13:49 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645E26636@dfweml701-chm>
References: <4A95BA014132FF49AE685FAB4B9F17F645DDEAFB@dfweml701-chm> <D16FFD82-DF25-4944-81D9-A43C9A57426E@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F645DDEEE2@dfweml701-chm> <99FD9369-6E14-4FCB-99D9-46EE39F6E0C3@gmail.com>
In-Reply-To: <99FD9369-6E14-4FCB-99D9-46EE39F6E0C3@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.144.39]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645E26636dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/vfQeh18oj7NL2-DAfcqcYXRjt94
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Subject: [lisp] Multicast agonostic NVE described by draft-ghanwani-nvo3-app-mcast-framework
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: Wed, 29 Oct 2014 22:14:07 -0000

We are looking for feedback on a scheme to enable TSs multicast in NVO3 environment without NVE doing extra work for IGMP/MLD messages (to be added to the Section 3.3: Replication at a Multicast Service Node). This approach will be very useful for Server based NVEs that don't support IGMP/MLD:


      "Multicast Service Node" can send VN scoped broadcast "IGMP query", that are encapsulated in overlay header. The overlay header has the following property.
       Inner Source = Multicast Service Node
       Inner Dest Addr = IGMP multicast address

       Outer Source = the NVE module embedded in (or attached to) Multi-Service Node
       Outer Dest Addr = NVEs that participate in the VN.

      The NVEs perform the same procedure as other data frames: i.e. decapsulate and forwarded to the attached TSs.

      If the NVEs perform real time learning of inner-outer address mapping, the NVE should have learned the following mapping:
       Inner: the Multicast Service Node Address ==>   Outer: Multicast Service Node NVE address.

      NVEs can also get their Multicast Service Node  to its NVE address mapping from NVA.

      When the reply (IGMP report) from the targeted TSs arrives at the NVEs, the normal encapsulation by the NVEs will have the outer DA as the Multicast Service Node NVE address.


Your comments are appreciated.

Linda