From owner-freebsd-net@FreeBSD.ORG Mon Mar 3 12:58:48 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B883106566C for ; Mon, 3 Mar 2008 12:58:48 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 388878FC2E for ; Mon, 3 Mar 2008 12:58:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 0F1EB17392; Mon, 3 Mar 2008 13:58:47 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJbkutIzQpz9; Mon, 3 Mar 2008 13:58:41 +0100 (CET) Received: from [212.61.27.67] (opteron.digiware.nl [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 9011D173A4; Mon, 3 Mar 2008 13:58:41 +0100 (CET) Message-ID: <47CBF60E.2060704@digiware.nl> Date: Mon, 03 Mar 2008 13:58:54 +0100 From: Willem Jan Withagen Organization: Digiware User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= References: <497111.42659.qm@web63905.mail.re1.yahoo.com> <20080301225727.GA85851@owl.midgard.homeip.net> <47CAADB8.9000202@digiware.nl> <47CC304F.6040006@bromirski.net> <47CBF16C.6020704@digiware.nl> <47CBF503.9060208@bromirski.net> In-Reply-To: <47CBF503.9060208@bromirski.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: Barney Cordoba , Ingo Flaschberger , net@freebsd.org Subject: Re: FBSD 1GBit router? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 12:58:48 -0000 Łukasz Bromirski wrote: >> My experience is that Multicast in nice in theory and experiment, but >> when >> push comes to shove it does not completely deliver. > > I don't know exact requirements and application used, but given IP TV > deployments relying heavily on multicast, and all other "VoD" > technologies also using multicast...I find Your comments disturbing :) Where do you think I'm getting my experience from. ;) Even network owners and techies will admit to this when squeezed. > However, if you don't control the network over which it will be > transported, you need to replicate each stream...and so either > you'll find bandwidth to do it (or pay for it) or be forced to switch > to other design. There can only be one...... And IP TV over closed networks are not going to make it. That is not what the customer really wants. But this is my last remark to this aspect in this list, since it takes us very OT. --WjW