Re: [p2pi] Follow-Up from Comcast Presentation

John Leslie <john@jlc.net> Sat, 07 June 2008 19:15 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 D78383A6BA1; Sat, 7 Jun 2008 12:15:00 -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 5C0493A6B9E for <p2pi@core3.amsl.com>; Sat, 7 Jun 2008 12:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[AWL=0.426, BAYES_00=-2.599]
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 r+QRB7rIAKxz for <p2pi@core3.amsl.com>; Sat, 7 Jun 2008 12:14:58 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id 736593A6B93 for <p2pi@ietf.org>; Sat, 7 Jun 2008 12:14:55 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 2068033C37; Sat, 7 Jun 2008 15:15:09 -0400 (EDT)
Date: Sat, 07 Jun 2008 15:15:09 -0400
From: John Leslie <john@jlc.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <20080607191509.GL8579@verdi>
References: <45AEC6EF95942140888406588E1A6602045CBA5E@PACDCEXCMB04.cable.comcast.com> <3efc39a60806061909n11a65eafnce88df7c73c30639@mail.gmail.com> <4CB75CEA-FE7E-4398-A1B3-A03DBF5063D3@icsi.berkeley.edu> <3efc39a60806070852p49f6a066y27e804fd5d4cf989@mail.gmail.com> <20080607173925.GJ8579@verdi> <484AC9EB.8060501@isi.edu> <20080607175712.GK8579@verdi> <484ACEEC.9070705@joelhalpern.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <484ACEEC.9070705@joelhalpern.com>
User-Agent: Mutt/1.4.1i
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Follow-Up from Comcast Presentation
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

Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> Several of the meeting presentations referred to "Scavenger service".
> 
> As a definition, assuming I am allowed to define using diffserv, how about:
> 
> Unmarked packets, and packets marked for better diffserv classes will 
> receive preferential queueing treatment compared with those marked with 
> Scavenger class service.  To avoid starvatation, the Scavanger queue 
> will be guaranteed a minimal percentage (10%?) of the data capacity even 
> when normal and better services could consume all available bandwidth.
> 
> That is basically the inverse of the simplified EF definition, for 
> achieving essentially the opposite goal.

   Hmm... we really _ought_ to be able to define "scavenger service"...

   To me, "scavenger service" implies that the application is happy to
see some periods -- say ten minutes or more -- where no packets are
getting delivered at all, so long as the connection isn't lost.

   (Of course, this definition starts to fall apart at inter-planetary
distances...)

--
John Leslie <john@jlc.net>
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi