RE: BitTorrentvs MBONE
"Hallam-Baker, Phillip" <pbaker@verisign.com> Fri, 16 September 2005 02:34 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG642-0005WO-6X; Thu, 15 Sep 2005 22:34:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG640-0005WG-8o for ietf@megatron.ietf.org; Thu, 15 Sep 2005 22:34:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04291 for <ietf@ietf.org>; Thu, 15 Sep 2005 22:34:53 -0400 (EDT)
Received: from robin.verisign.com ([65.205.251.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EG68u-0005vk-Aa for ietf@ietf.org; Thu, 15 Sep 2005 22:40:01 -0400
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by robin.verisign.com (8.13.1/8.13.1) with ESMTP id j8G2Ylin010246; Thu, 15 Sep 2005 19:34:47 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 15 Sep 2005 19:34:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Sep 2005 19:34:47 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD375A2B46@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Thread-Topic: BitTorrentvs MBONE
Thread-Index: AcW6Sdky5qqcsfW+QDmjoxVvilelBwAG9Mxw
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Michael Thomas <mat@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-OriginalArrivalTime: 16 Sep 2005 02:34:47.0714 (UTC) FILETIME=[349EB020:01C5BA67]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: BitTorrentvs MBONE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> Behalf Of Michael Thomas > Are we to believe that they are largely self-healing problems > as bad p2p apps will eventually correct themselves since it's > in their interest? Is it reasonable to believe that there is > enough general clue that they could be expected to do that? > And the collective clue of the ietf is not really needed to > help this along? Last time I heard that type of talk it was from all those folk who just had to tell us why the network hypertext project we were working on at the time was certain to be a collosal failure. In terms of bandwidth headroom the Internet seems a heck of a lot better off today than in the early days of the Web when people thought a T1 was the ultimate in network connection. Sure bittorrent is probably not great design by many standards. Neither is NNTP, a protocol which used to rip up about half the Internet bandwidth churning bits around that almost nobody would ever read. Pre-emptive flood fill is an 'interesting' strategy to say the least. Many ISPs no longer support it. Comcast charges extra. I think that the reasonable question to ask here is 'does MBONE have a future?' If I was asked to design a new media distribution protocol from scratch I certainly would not choose MBONE as a model. The technical and political problems both appear insoluble to me. To return to the original question. The IETF is certainly capable of solving complex problems. What it does not appear to be capable of is letting go of failed experiments. Take multicast out to the woodshed, its long overdue. _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: BitTorrentvs MBONE Hallam-Baker, Phillip
- Re: BitTorrentvs MBONE Tim Bray
- Re: BitTorrentvs MBONE John Kristoff
- RE: BitTorrentvs MBONE Hallam-Baker, Phillip
- RE: BitTorrentvs MBONE Pekka Savola