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

Scott W Brim <sbrim@cisco.com> Thu, 15 September 2005 22:58 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG2gA-00012v-AL; Thu, 15 Sep 2005 18:58:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG2g8-00012q-OY for ietf@megatron.ietf.org; Thu, 15 Sep 2005 18:58:05 -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 SAA16601 for <ietf@ietf.org>; Thu, 15 Sep 2005 18:58:01 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EG2l1-0001HF-A4 for ietf@ietf.org; Thu, 15 Sep 2005 19:03:08 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 15 Sep 2005 15:57:42 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,115,1125903600"; d="scan'208"; a="9910138:sNHT22380516"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8FMvXTC009982; Thu, 15 Sep 2005 18:57:39 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 15 Sep 2005 18:57:36 -0400
Received: from [10.86.242.148] ([10.86.242.148]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 15 Sep 2005 18:57:35 -0400
Message-ID: <4329FC5E.8080104@cisco.com>
Date: Thu, 15 Sep 2005 18:57:34 -0400
From: Scott W Brim <sbrim@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
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]> <4329DE80.5040200@cisco.com> <p062309dfbf4f8ffb57d6@[10.20.30.249]>
In-Reply-To: <p062309dfbf4f8ffb57d6@[10.20.30.249]>
X-Enigmail-Version: 0.92.1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Sep 2005 22:57:35.0667 (UTC) FILETIME=[DCEA2030:01C5BA48]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: Michael Thomas <mat@cisco.com>, 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

On 09/15/2005 17:09 PM, Paul Hoffman allegedly wrote:
> At 1:50 PM -0700 9/15/05, Michael Thomas wrote:
>> 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?
> 
> Not sure why this is an elephant; who cares? I have seen numbers that
> show that a huge percentage of traffic is P2P of various flavors, but I
> haven't seen anyone saying that this is having any negative effects.

The metaphor I'm trying to use this week is that the IETF is
landscapers and we provide a fertile, beautiful area for people to go
wild and create excellent gardens.  What you're describing is not a
bug, it's feature.  It means the IETF have done their job.  If there
were interoperability problems in the fundamental and/or widespread
technologies being used in the Internet, then there would be a problem
(we're working on those).  Congratulations.

swb

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