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

Iljitsch van Beijnum <iljitsch@muada.com> Thu, 15 September 2005 23:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG3W1-0007wL-Ud; Thu, 15 Sep 2005 19:51:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EG3Vz-0007wB-1q for ietf@megatron.ietf.org; Thu, 15 Sep 2005 19:51:39 -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 TAA19274 for <ietf@ietf.org>; Thu, 15 Sep 2005 19:51:36 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EG3as-0002gV-Tw for ietf@ietf.org; Thu, 15 Sep 2005 19:56:43 -0400
Received: from [82.192.90.27] (alumange.muada.com [82.192.90.27]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id j8FNp7Eq046255 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 16 Sep 2005 01:51:08 +0200 (CEST) (envelope-from iljitsch@muada.com)
In-Reply-To: <4329FD20.4070208@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> <p062309bdbf4e8f2a8454@[10.20.30.249]> <4329DE80.5040200@cisco.com> <p062309dfbf4f8ffb57d6@[10.20.30.249]> <4329FD20.4070208@cisco.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7C653B03-7D3D-46DC-98B0-CB3AD678BF89@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 16 Sep 2005 01:51:21 +0200
To: Michael Thomas <mat@cisco.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <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 16-sep-2005, at 1:00, Michael Thomas wrote:

>   I'm not sure; maybe it's really a mutual non-admiration
>   society, and everybody's happy? But it's an elephant
>   insofar as it's pretty darn big trafficwise, and the
>   fact that ietf doesn't seem concerned?

Why should the IETF be concerned about traffic?

Now of course that doesn't mean our amateur protocol designers get it  
right every time... For instance, when you become a Gnutella  
"ultrapeer" you'll very likely create some nasty congestion in the  
outgoing direction of your ADSL or cable connection because when you  
receive one request, the program wakes up and sends out copies of  
that request over several dozen TCP sessions at the same time, which  
will invariably overload the buffers at some point between the host  
and the DSL/cable connection.

> we're layering
>   more and more stuff onto the net too -- like voip -- that
>   are pretty sensitive to average expectations (I'm thinking
>   about things like Vonage, not managed services). Is that
>   a danger for the overall internet architecture?

Anyone who thinks he or she is going to meet real time constraints  
over a random path across the internet that spans multiple ASes has  
more problems than the IETF can possibly fix.

And no, I don't think it's reasonable to restrict p2p bulk data  
transfer to accommodate voice over the public internet.

(Maybe at some point people from Apple would like to share the  
results of them setting a DSCP code point / type of service in the IP  
header of voice packets.)

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