BitTorrent (Was: Re: [Isms] ISMS charter broken- onus should be on WG to fix it)

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 15 September 2005 02:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFjk8-0007tc-Oo; Wed, 14 Sep 2005 22:44:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFjk6-0007tX-WD for ietf@megatron.ietf.org; Wed, 14 Sep 2005 22:44:55 -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 WAA28929 for <ietf@ietf.org>; Wed, 14 Sep 2005 22:44:52 -0400 (EDT)
Received: from above.proper.com ([208.184.76.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFjon-0000ZB-Pc for ietf@ietf.org; Wed, 14 Sep 2005 22:49:48 -0400
Received: from [10.20.30.249] (dsl2-63-249-92-231.cruzio.com [63.249.92.231]) (authenticated bits=0) by above.proper.com (8.12.11/8.12.9) with ESMTP id j8F2ikSr080631 for <ietf@ietf.org>; Wed, 14 Sep 2005 19:44:47 -0700 (PDT) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062309bdbf4e8f2a8454@[10.20.30.249]>
In-Reply-To: <4328C102.2010201@cisco.com>
References: <200509131506.j8DF664A016810@pacific-carrier-annex.mit.edu> <tslhdcokeed.fsf@cz.mit.edu> <20050913204555.GA14153@boskop.local> <tslbr2wk78f.fsf@cz.mit.edu> <3C03BDBD60783D559EDAE652@sirius.fac.cs.cmu.edu> <01LSZP7AGR0Y000092@mauve.mrochek.com> <432886C4.9040606@cisco.com> <01LT0ZC5UEV8000092@mauve.mrochek.com> <4328C102.2010201@cisco.com>
Date: Wed, 14 Sep 2005 19:44:44 -0700
To: ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: BitTorrent (Was: Re: [Isms] ISMS charter broken- onus should be on WG to fix it)
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

At 5:32 PM -0700 9/14/05, Michael Thomas wrote:
>Ned Freed wrote:
>>Such a third party would act as a repository for update information 
>>provided by
>>vendors. Applications would then "call home" to one of these repositories
>>rather than directly to the vendor. Various anonymyzing tricks could be
>>employed to minimize information leakage even if the third party was
>>compromised.
>
>You mean we could invent Bitorrent? :)

BitTorrent (note the spelling) does a lot of very nice things, but 
not those. For those interested, the BitTorrent protocol is described 
at <http://www.bittorrent.com/protocol.html>.

>		Mike, doesn't it strike others as odd
>		 that ietf is completely outside of the
>		 p2p bizness?

In this case, there is no advantage to the developer of the protocol 
to have it worked on in the IETF, nor even published as an RFC. It 
came out of one person's head, he was able to experiment with it live 
on the net, and he retains the ability to tweak the specs whenever he 
feels like it. It has worked remarkably well, given the variety of 
clients and servers available for the protocol, and the huge amount 
of traffic that is moved daily over it.

--Paul Hoffman, who shares a lot of legal music and OSs with BitTorrent

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf