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

Martin Stiemerling <martin.stiemerling@neclab.eu> Wed, 19 June 2013 07:47 UTC

Return-Path: <Martin.Stiemerling@neclab.eu>
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 6DE3421F9C1D for <ppsp@ietfa.amsl.com>; Wed, 19 Jun 2013 00:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.378
X-Spam-Level:
X-Spam-Status: No, score=-103.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 JQ1O6VdNtLQ5 for <ppsp@ietfa.amsl.com>; Wed, 19 Jun 2013 00:47:25 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2E221F9F80 for <ppsp@ietf.org>; Wed, 19 Jun 2013 00:47:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 34AA71045B6; Wed, 19 Jun 2013 09:47:04 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nx-130pyNaRi; Wed, 19 Jun 2013 09:47:04 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 18A431045B3; Wed, 19 Jun 2013 09:46:49 +0200 (CEST)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 19 Jun 2013 09:46:08 +0200
Message-ID: <51C161ED.70303@neclab.eu>
Date: Wed, 19 Jun 2013 09:46:53 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
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"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.99.64]
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: Wed, 19 Jun 2013 07:47:30 -0000

On 05/10/2013 10: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.
>
>     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.

Good to hear but my question is in what time the WG could expect to see 
results?

This isn't about building up pressure, but more about when the peer 
protocol should be going for publication as RFC.

   Martin