Re: [p2pi] Follow-Up from Comcast Presentation

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Mon, 09 June 2008 20:59 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 9E5A03A6A48; Mon, 9 Jun 2008 13:59:36 -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 89FA13A6A48 for <p2pi@core3.amsl.com>; Mon, 9 Jun 2008 13:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level:
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 KP2RbwC6GzSk for <p2pi@core3.amsl.com>; Mon, 9 Jun 2008 13:59:34 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 4F1D23A69A7 for <p2pi@ietf.org>; Mon, 9 Jun 2008 13:59:34 -0700 (PDT)
Received: from ([24.40.15.118]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.4980545; Mon, 09 Jun 2008 16:59:33 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Jun 2008 16:59:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 09 Jun 2008 16:58:34 -0400
Message-ID: <74CCBBDF76102846AFA7B29F3A98D3F60107BE32@PACDCEXCMB06.cable.comcast.com>
In-Reply-To: <dfa4ab960806090223t65a9833eq36931439e9957b12@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [p2pi] Follow-Up from Comcast Presentation
thread-index: AcjKEootrlHZmUbTThqTM/OrNYZNVAAYIsBg
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><F75C1C69-2110-4949-B8D6-D5726E679302@nokia.com> <dfa4ab960806090223t65a9833eq36931439e9957b12@mail.gmail.com>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Stanislav Shalunov <shalunov@bittorrent.com>, Lars Eggert <lars.eggert@nokia.com>
X-OriginalArrivalTime: 09 Jun 2008 20:59:33.0013 (UTC) FILETIME=[B7956450:01C8CA73]
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

And RFC 4594 (e.g. section 4.10) introduces the term 'Low-Priority Data'
-- which had been called Scavenger in the QBSS reference below.

-----Original Message-----
From: p2pi-bounces@ietf.org [mailto:p2pi-bounces@ietf.org] On Behalf Of
Stanislav Shalunov
Sent: Monday, June 09, 2008 5:24 AM
To: Lars Eggert
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Follow-Up from Comcast Presentation

See also http://qos.internet2.edu/wg/wg-documents/qbss-definition.txt

On Mon, Jun 9, 2008 at 2:15 AM, Lars Eggert <lars.eggert@nokia.com>
wrote:
> RFC3662?
>
> On 2008-6-7, at 20:09, ext Joel M. Halpern 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.
>
> _______________________________________________
> p2pi mailing list
> p2pi@ietf.org
> https://www.ietf.org/mailman/listinfo/p2pi
>



-- 
Stanislav Shalunov
http://shlang.com/
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi