Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-framework-02.txt
"Saumya Dikshit (sadikshi)" <sadikshi@cisco.com> Fri, 12 February 2016 07:42 UTC
Return-Path: <sadikshi@cisco.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 2B0461B4115 for <nvo3@ietfa.amsl.com>; Thu, 11 Feb 2016 23:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 9ID2cglmnPNS for <nvo3@ietfa.amsl.com>; Thu, 11 Feb 2016 23:42:28 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0746D1B4113 for <nvo3@ietf.org>; Thu, 11 Feb 2016 23:42:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15944; q=dns/txt; s=iport; t=1455262948; x=1456472548; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=xGJvWgYJ6XA/vaixRD5AxjfMW8+J7OoHH8tcHL0krUw=; b=GhLpo0ADIMWHGLXCyhJcfsUGRxycvT/4otnC5fQ+zBiPOTBKn3+v95FC dthG/1+SMJCsxBz5UETK870z4gvWAbFVPpOdq2ggMjJ7zmnPu0kOABzhz U/Ji3JowCFZ7RfynJk6FZSCD6CPgFedI8BrLPwtxsJ+35wwhxBZtAk9Kn g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQBHjL1W/5tdJa1eDoJgTFJtBohVsTEBDYFnFwELhWoCgTY4FAEBAQEBAQGBCoRBAQEBBAEBAWsbAgEIEQMBAigHJwsUCQgCBAESiBoOwRQBAQEBAQEBAQEBAQEBAQEBAQEYhhEBhDWEAFINCYQEBY1fiRgBhU+IBYFeSoN5iFWOPQEPDwEBQoIogQE7agGGZT18AQEB
X-IronPort-AV: E=Sophos;i="5.22,435,1449532800"; d="scan'208,217";a="236210124"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Feb 2016 07:42:26 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u1C7gQGC000809 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 12 Feb 2016 07:42:26 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 12 Feb 2016 01:42:25 -0600
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1104.009; Fri, 12 Feb 2016 01:42:26 -0600
From: "Saumya Dikshit (sadikshi)" <sadikshi@cisco.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] I-D Action: draft-ietf-nvo3-mcast-framework-02.txt
Thread-Index: AQHRZJ4Lb1l22/HEo0+soCla7PAJzZ8m2CWAgAHxOAA=
Date: Fri, 12 Feb 2016 07:42:25 +0000
Message-ID: <D2E239F2.5F70D%sadikshi@cisco.com>
References: <20160211072908.10127.59125.idtracker@ietfa.amsl.com> <CA+-tSzx6EtjKfJoW+f62p1D6-qw2E5fto6CABRmaNUrE19y8qg@mail.gmail.com>
In-Reply-To: <CA+-tSzx6EtjKfJoW+f62p1D6-qw2E5fto6CABRmaNUrE19y8qg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.78.174]
Content-Type: multipart/alternative; boundary="_000_D2E239F25F70Dsadikshiciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/GwmRnyDHz18Z5-kgg0xZsRpcrOc>
Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-framework-02.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: <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: Fri, 12 Feb 2016 07:42:32 -0000
Hi Anoop I have few queries regarding the following texts from the (kindly bear with if these were taken up earlier or should be posted against different literature): >>>>In the case of ARP/ND, an NVA can be used for distributing the mappings of IP address to MAC address to all NVEs, and the NVEs can respond to ARP messages from the TSs that are attached to it in a way that is similar to proxy-ARP. * NVA here can distribute and ALSO withdraw the IP/MAC mappings, OR the deletion of entries can be delegated to NVE implementation OR based on native ARP/ND functionality (of refreshes and timeouts). * Does the "mapping distribution" generalizes "both local and remote TS credentials" and "remote NVE's" as well or connected TS credentials are expected to be learnt the native ARP/ND way * Proxy-ARP is different in a way wherein the Proxying-router can proxy for destination-hosts which are in different subnets as there may be no default gateway connected to sending-host. In this case local and remote Vteps will map same vni to same-subnet routes, to put them under the same bridging-domain. >>>> In sectin "3.1<https://tools.ietf.org/html/draft-ietf-nvo3-mcast-framework-02#section-3.1>. No multicast support" " All of the application traffic in the network is unicast traffic and the only multicast/broadcast traffic is from ARP/ND protocols." Does this section implies that bridging/switching is not supported on the NVE devices, which will perform broadcast for all L2 packets (either multicast or broadcast) received from connected TS. If not, then case all link-local multicast packets at least can be bridged/switched by the devices in this case. >>>>In section "3.2<https://tools.ietf.org/html/draft-ietf-nvo3-mcast-framework-02#section-3.2>. Replication at the source NVE" In multi-homing environments, i.e. more than one NVE can reach a specific TS, the NVA would be expected to provide all the NVEs that can reach the given TS. I think the above sentence is incomplete and needs to be rephrased, wherein "the credentials of ALL NVEs which are directly connected to TSs should be provided by NVA to other NVEs in it's authoritative domain" From: Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>> Date: Thursday, February 11, 2016 at 1:02 PM To: "nvo3@ietf.org<mailto:nvo3@ietf.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>> Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-framework-02.txt This version addresses the comments received during WGLC. Please let us know if there are any additional comments. Thanks, Anoop On Wed, Feb 10, 2016 at 11:29 PM, <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Virtualization Overlays of the IETF. Title : A Framework for Multicast in NVO3 Authors : Anoop Ghanwani Linda Dunbar Mike McBride Vinay Bannai Ram Krishnan Filename : draft-ietf-nvo3-mcast-framework-02.txt Pages : 15 Date : 2016-02-10 Abstract: This document discusses a framework of supporting multicast traffic in a network that uses Network Virtualization Overlays over Layer 3 (NVO3). Both infrastructure multicast and application-specific multicast are discussed. It describes the various mechanisms that can be used for delivering such traffic as well as the data plane and control plane considerations for each of the mechanisms. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-nvo3-mcast-framework/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-nvo3-mcast-framework-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-mcast-framework-02 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<http://tools.ietf.org>. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ nvo3 mailing list nvo3@ietf.org<mailto:nvo3@ietf.org> https://www.ietf.org/mailman/listinfo/nvo3
- [nvo3] I-D Action: draft-ietf-nvo3-mcast-framewor… internet-drafts
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Anoop Ghanwani
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Saumya Dikshit (sadikshi)
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Anoop Ghanwani
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Saumya Dikshit (sadikshi)
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Anoop Ghanwani
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Saumya Dikshit (sadikshi)
- Re: [nvo3] I-D Action: draft-ietf-nvo3-mcast-fram… Anoop Ghanwani