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

Michael Thomas <mat@cisco.com> Thu, 15 September 2005 20:50 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG0gm-0000Ua-TE; Thu, 15 Sep 2005 16:50:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG0gk-0000UV-E5 for ietf@megatron.ietf.org; Thu, 15 Sep 2005 16:50:34 -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 QAA09764 for <ietf@ietf.org>; Thu, 15 Sep 2005 16:50:31 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EG0lb-0006Qf-Nv for ietf@ietf.org; Thu, 15 Sep 2005 16:55:37 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 15 Sep 2005 13:50:10 -0700
X-IronPort-AV: i="3.97,114,1125903600"; d="scan'208"; a="212237816:sNHT1557118958"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8FKo3KC014440; Thu, 15 Sep 2005 13:50:03 -0700 (PDT)
Received: from [171.71.193.183] (dhcp-171-71-193-183.cisco.com [171.71.193.183]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j8FL2bvY017433; Thu, 15 Sep 2005 14:02:37 -0700
Message-ID: <4329DE80.5040200@cisco.com>
Date: Thu, 15 Sep 2005 13:50:08 -0700
From: Michael Thomas <mat@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
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> <p062309bdbf4e8f2a8454@[10.20.30.249]>
In-Reply-To: <p062309bdbf4e8f2a8454@[10.20.30.249]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1301; t=1126818157; x=1127250357; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=mat@cisco.com; z=Subject:Re=3A=20BitTorrent=20(Was=3A=20Re=3A=20[Isms]=20ISMS=20charter=20broken- =20onus=20should=0A=20be=20on=20WG=20to=20fix=20it)| From:Michael=20Thomas=20<mat@cisco.com>| Date:Thu,=2015=20Sep=202005=2013=3A50=3A08=20-0700| Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=Ug2C7diVbZ7aeNAX2GHXSHHsF0ctqNJKjDVVCQImj9UM2mrv8er/i7IzHffRGsiWi7EaOvb5 AdsyN8Y7CtKO+QjlRmLYxPUtTRC0fvlSvVnsT1tBMfV6UAGQgGg7QuFa7L+D5LeoLjowLRaECp8 kazBojAazOjLpRx4REAUezno=
Authentication-Results: imail.cisco.com; header.From=mat@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: 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

Paul Hoffman wrote:
> At 5:32 PM -0700 9/14/05, Michael Thomas wrote:
>> 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>.

Always the risk when one is being flippant, but I only
meant that the world outside of ietf seems to be taking
on a lot of these issues without ietf's advice and consent.

> 
>>         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.

Which is pretty much the elephant in the room, I'd say. How
much of the net traffic these days is, essentially, not in
any way standardized, and in fact probably considers ietf
old and in the way?

I'll note that many protocols -- good and bad -- spring from
somebody's head. Some of them become successful too. Very
successful. And ietf has no say about them at all. Is this
the new reality? Sure seems like it to me. Should we be
concerned? Might there be film at 11 at some point because
of it?

		Mike, or is it too soon for another
		 ietf ossification thread?

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