IETF Logo Mail Archive

Re: [MBONED] NVO3 Multicast Framework

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Mon, 16 May 2016 22:54 UTC

Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3827A12DAE7 for <mboned@ietfa.amsl.com>; Mon, 16 May 2016 15:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.218
X-Spam-Level:
X-Spam-Status: No, score=-4.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 i5cXUAyZLhvs for <mboned@ietfa.amsl.com>; Mon, 16 May 2016 15:54:22 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2775612B005 for <mboned@ietf.org>; Mon, 16 May 2016 15:54:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4GMsKGc060184; Mon, 16 May 2016 15:54:20 -0700
Received: from XCH15-06-07.nw.nos.boeing.com (xch15-06-07.nw.nos.boeing.com [137.136.238.213]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4GMsCVm060158 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 16 May 2016 15:54:12 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-07.nw.nos.boeing.com (2002:8988:eed5::8988:eed5) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 16 May 2016 15:54:11 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1178.000; Mon, 16 May 2016 15:54:11 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [MBONED] NVO3 Multicast Framework
Thread-Index: AQHRr8LBgVPAlaGUw025yexDCkSK3J+8KR0g
Date: Mon, 16 May 2016 22:54:11 +0000
Message-ID: <dfb0700c72b4478aa61bfbc87f7f8b93@XCH15-06-11.nw.nos.boeing.com>
References: <20160512144607.T22764@sapphire.juniper.net> <17B47CE8-D558-4748-88D6-FEC17A02357A@gmail.com>
In-Reply-To: <17B47CE8-D558-4748-88D6-FEC17A02357A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/related; boundary="_004_dfb0700c72b4478aa61bfbc87f7f8b93XCH150611nwnosboeingcom_"; type="multipart/alternative"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mboned/EdpJvf35W5yGOGDOUsJtysI-fl4>
Cc: MBONED WG <mboned@ietf.org>, "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, Benson Schliesser <bensons@queuefull.net>
Subject: Re: [MBONED] NVO3 Multicast Framework
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 22:54:24 -0000

Many of these same issues were addressed over 15-20 years ago now, by the Internetworking over NBMA (ION) working group. Might be worth revisiting some of the solutions from those days, including MARS, RFC 2022, which emulated IP multicast over unicast or ATM-layer multicast virtual circuits.

Bert


From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Dino Farinacci
Sent: Monday, May 16, 2016 18:32
To: Leonard Giuliano <lenny@juniper.net>
Cc: MBONED WG <mboned@ietf.org>; Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com>; Benson Schliesser <bensons@queuefull.net>
Subject: Re: [MBONED] NVO3 Multicast Framework

I just have one minor comment. Regarding the second paragraph:

[cid:image002.png@01D1AFA3.3D876AF0]

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<mailto: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<mailto:nvo3@ietf.org>)- all comments will be greatly appreciated by NVO3.

_______________________________________________
MBONED mailing list
MBONED@ietf.org<mailto:MBONED@ietf.org>
https://www.ietf.org/mailman/listinfo/mboned

v2.23.0 | Report a Bug | By Email