IETF Logo Mail Archive

Re: [MBONED] A concern about draft-acg-mboned-multicast-models recommendations

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Thu, 01 March 2018 19:26 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 67AEC12F274 for <mboned@ietfa.amsl.com>; Thu, 1 Mar 2018 11:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 eOYc2fmVWUkH for <mboned@ietfa.amsl.com>; Thu, 1 Mar 2018 11:26:15 -0800 (PST)
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 0E40F12EAF5 for <mboned@ietf.org>; Thu, 1 Mar 2018 11:26:15 -0800 (PST)
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 w21JQEl1031133; Thu, 1 Mar 2018 12:26:14 -0700
Received: from XCH15-01-11.nw.nos.boeing.com (xch15-01-11.nw.nos.boeing.com [137.136.239.187]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w21JQBXi031095 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 1 Mar 2018 12:26:12 -0700
Received: from XCH15-01-07.nw.nos.boeing.com (137.136.239.154) by XCH15-01-11.nw.nos.boeing.com (137.136.239.187) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 1 Mar 2018 11:26:11 -0800
Received: from XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) by XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) with mapi id 15.00.1365.000; Thu, 1 Mar 2018 11:26:10 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] A concern about draft-acg-mboned-multicast-models recommendations
Thread-Index: AQHTsNHfwzeOJIZTOU+7sGf4/A517qO740aA///eioA=
Date: Thu, 01 Mar 2018 19:26:10 +0000
Message-ID: <e16f2a5580ec4e0e8977489680b14b49@XCH15-01-07.nw.nos.boeing.com>
References: <CAH8Jh6DikQa-9Kft0WdyGZYCPjWLScNVtYce2=EyL1q+0rAYVg@mail.gmail.com> <20180227231838.GI67472@cs-it-6805697.local> <CD402244-A3B3-4988-AB45-404B87DBEA94@jisc.ac.uk> <CAH8Jh6CRvvREZXoXH4mw8WecdHCzsvbPt5tHoNQwPGLauCoXOg@mail.gmail.com> <510DB303-A90E-45A8-A2AF-0366FD57122F@jisc.ac.uk>
In-Reply-To: <510DB303-A90E-45A8-A2AF-0366FD57122F@jisc.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/dU1Oiv0xVNXwFg7Q_XkaeQjJ4lk>
Subject: Re: [MBONED] A concern about draft-acg-mboned-multicast-models recommendations
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 01 Mar 2018 19:26:17 -0000

-----Original Message-----
From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Tim Chown

> A side effect of such a document would be to imply where ASM is at least
> currently more suited intra-domain.  It would be interesting to determine
> what those cases actually are.

From my POV, as briefly as possible, those are cases where multiple group members may become the source, and we want to avoid the hassle of having to specifically list each one, or exclude ones. We may not even know what possible sources might crop up. Examples where ASM is exactly what we want, and anything more than that is just added burden for no benefit.

I get that inter-domain, with PIM-SM, that simplicity cannot exist. So inter-domain, SSM is actually simpler. It removes that rendezvous point complication, and then having to find a better route around it, for the multicasts.

Bert

v2.23.0 | Report a Bug | By Email