From owner-freebsd-multimedia Fri Mar 15 12:43:22 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29172 for multimedia-outgoing; Fri, 15 Mar 1996 12:43:22 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29165 for ; Fri, 15 Mar 1996 12:43:20 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14412(5)>; Fri, 15 Mar 1996 12:42:37 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Fri, 15 Mar 1996 12:42:32 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: "Jordan K. Hubbard" cc: multimedia@freebsd.org Subject: Re: Seeking advice on mrouted configuration.. In-reply-to: Your message of "Wed, 28 Feb 1996 13:00:27 PST." <3508.825541227@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Mar 1996 12:42:23 PST From: Bill Fenner Message-Id: <96Mar15.124232pst.177478@crevenia.parc.xerox.com> Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <3508.825541227@time.cdrom.com>you write: >Yes, both pairs are in the same subnets, but that should be OK from a >unicast point of view so why mandate special twisty semantics for >multicast when you don't have to? Is it really so hard to make >mrouted respect this scenario? Rather, "people noticed a long time ago that unicast doesn't break when you break the Internet architecture in this way, so it became accepted practice, so why does mrouted break?" -- well, because you broke the Internet architecture. I'm not saying that I'm not working on "fixing" such things, I'm just saying that it's more complex an issue [in fact, a fundamental architectural issue] than most people realize. Bill