Re: [p2pi] [tana] [tsv-area] TANA proposed charter

Reinaldo Penno <rpenno@juniper.net> Wed, 22 October 2008 09:26 UTC

Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 586C93A6B63; Wed, 22 Oct 2008 02:26:30 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA3533A699D; Wed, 22 Oct 2008 02:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.366
X-Spam-Level:
X-Spam-Status: No, score=-6.366 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbDdJEHYdOGD; Wed, 22 Oct 2008 02:26:24 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id AA6603A692F; Wed, 22 Oct 2008 02:26:24 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP; Wed, 22 Oct 2008 02:26:21 PDT
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Oct 2008 02:26:34 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by emailwf1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Oct 2008 05:26:33 -0400
Received: from 172.23.1.75 ([172.23.1.75]) by proton.jnpr.net ([10.10.2.37]) with Microsoft Exchange Server HTTP-DAV ; Wed, 22 Oct 2008 09:26:33 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Wed, 22 Oct 2008 02:26:29 -0700
From: Reinaldo Penno <rpenno@juniper.net>
To: Roland Bless <bless@tm.uka.de>
Message-ID: <C5243FD5.132DE%rpenno@juniper.net>
Thread-Topic: [tana] [tsv-area] TANA proposed charter
Thread-Index: Ack0KENY03Ka+RMOwk2MeimttWguAw==
In-Reply-To: <48FEEFDB.6000801@tm.uka.de>
Mime-version: 1.0
X-OriginalArrivalTime: 22 Oct 2008 09:26:33.0286 (UTC) FILETIME=[45E6CE60:01C93428]
Cc: tsv-area@ietf.org, tana@ietf.org, p2pi@ietf.org, Michael Welzl <michael.welzl@uibk.ac.at>
Subject: Re: [p2pi] [tana] [tsv-area] TANA proposed charter
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org



On 10/22/08 2:18 AM, "Roland Bless" <bless@tm.uka.de> wrote:

> Hi Reinaldo,
> 
> Reinaldo Penno wrote:
>> I'm not sure I'm reading the semantics of "Less than Best Effort" like other
>> folks. 
> 
> Maybe RFC 3662 defines this more clearly.
> 
>> 'Best Effort' has a well-defined semantics in the scope of Diffserv,
>> including a code point of its own. Less than best effort seems we are
>> defining a code point for such applications. Are we? The charter talks about
>> 'end-to-end Diffserv'.
> 
> See RFC 3662

Thanks Roland. I remember some of these discussions. Is there any effort to
make it standard, particularly the DSCP so the algorithm can use it?

> 
>> End-to-end diffserv is a challenge on its own given ISP policies, etc.
>> 
>> If the link is not saturated, are such application also treated as 'less
>> than best effort' by still being DSCP marked and treated differently within
>> routers? 
> 
> Usually lower effort (LE) packets will go into a different queue
> and served only if no other BE packets are waiting. So if
> the BE queue is empty, LE packets will get the same treatment as BE
> packets. Only in case of congestion, LE packets will be treated
> differently.
> 
>> I would like if possible to decouple the 'less than best effort', as in
>> diffserv, from the algorithm per se.
>> 
>> Besides, there are ISPs that are worried about the effect that P2P have on
>> other applications when the link is saturated, but otherwise they do not
>> care. P2P would be treated like best effort in non-saturated situations (a
>> more ECN type approach).
> 
> Yes, and that's exactly where LE helps: an ISP can be sure that
> LE traffic will not harm other BE traffic at any time. In case
> of congestion BE traffic will preempt LE traffic. If the
> link is not saturated, LE will be treated like BE.
> 
> Regards,
>  Roland
> 

_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi