Re: [ppsp] AD review of draft-ietf-ppsp-peer-protocol-06

Wesley Eddy <wes@mti-systems.com> Fri, 10 May 2013 17:18 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6086821F89FF for <ppsp@ietfa.amsl.com>; Fri, 10 May 2013 10:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r80FyED0TIPi for <ppsp@ietfa.amsl.com>; Fri, 10 May 2013 10:17:59 -0700 (PDT)
Received: from atl4mhob04.myregisteredsite.com (atl4mhob04.myregisteredsite.com [209.17.115.42]) by ietfa.amsl.com (Postfix) with ESMTP id 899E521F8746 for <ppsp@ietf.org>; Fri, 10 May 2013 10:17:59 -0700 (PDT)
Received: from mail.hostingplatform.com ([10.30.71.211]) by atl4mhob04.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r4AHHwi5019593 for <ppsp@ietf.org>; Fri, 10 May 2013 13:17:58 -0400
Received: (qmail 28207 invoked by uid 0); 10 May 2013 17:17:58 -0000
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.45.109.70) by 0 with ESMTPA; 10 May 2013 17:17:58 -0000
Message-ID: <518D2BB7.3060101@mti-systems.com>
Date: Fri, 10 May 2013 13:17:43 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Riccardo Petrocco <r.petrocco@gmail.com>
References: <517F8C7B.20106@neclab.eu> <518C4D3C.1040302@mti-systems.com> <CAN6E5EejCzyhb-K6igvUnyF1iiDuqmq8iijDoHV9z4yh38T7FA@mail.gmail.com>
In-Reply-To: <CAN6E5EejCzyhb-K6igvUnyF1iiDuqmq8iijDoHV9z4yh38T7FA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] AD review of draft-ietf-ppsp-peer-protocol-06
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 17:18:04 -0000

On 5/10/2013 4:16 AM, Riccardo Petrocco wrote:
> Dear Wesley and All,
> 
>     Maybe someone can comment on whether alternatives like TFRC
>     were investigated or not?  TFRC is Standards Track, and intended
>     for providing a smoother rate like we talked about in the
>     past (LEDBAT may not be good for relatively rate-inelastic
>     flows), but I don't know if the feedback it requires would be
>     compatible with what the PPSPP framing provides or not.
> 
> 
> We are currently looking into alternatives to LEDBAT for the PPSPP.
> The majority of CCs will require some small modifications to the content
> of the DATA and ACK messages as defined in the draft.


That is good to hear.  I don't know if it's helpful or not, but
one example of how to implement TFRC in a non-DCCP UDP-based
protocol is:
http://tools.ietf.org/html/draft-eddy-tsvwg-saratoga-tfrc-03
I don't think it necessarily has to be as painful as some have
found in the past.


>     I also would not think it wise to change to something else
>     that doesn't match the implemented and deployed base, unless
>     the people implementing and deploying agree that something
>     else is clearly better and will be implemented and deployed
>     by them.
> 
> 
> We will also run some large experiments in a controlled environment to
> evaluate the effect and feasibility of the different solutions.


Excellent!


-- 
Wes Eddy
MTI Systems