Re: [pcp] I-D Action: draft-vinapamula-flow-ha-03.txt

<mohamed.boucadair@orange.com> Fri, 19 September 2014 06:08 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612EB1A0690 for <pcp@ietfa.amsl.com>; Thu, 18 Sep 2014 23:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sw_cVuDOvCbd for <pcp@ietfa.amsl.com>; Thu, 18 Sep 2014 23:08:17 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 199D71A883F for <pcp@ietf.org>; Thu, 18 Sep 2014 23:08:17 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 4C3C93B41C9; Fri, 19 Sep 2014 08:08:15 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 2DFB14C069; Fri, 19 Sep 2014 08:08:15 +0200 (CEST)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.127]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0195.001; Fri, 19 Sep 2014 08:08:14 +0200
From: mohamed.boucadair@orange.com
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>, "cheshire@apple.com" <cheshire@apple.com>
Thread-Topic: I-D Action: draft-vinapamula-flow-ha-03.txt
Thread-Index: Ac/TU6bH7pGLI6+MSL2FizvHY3vI8wAe8PHQ
Date: Fri, 19 Sep 2014 06:08:14 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933006B05A@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <913383AAA69FF945B8F946018B75898A2832B5B2@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A2832B5B2@xmb-rcd-x10.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.9.19.45121
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/5lAaTcgEVuWZXLBy7xyUIONaFJA
Subject: Re: [pcp] I-D Action: draft-vinapamula-flow-ha-03.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 06:08:19 -0000

Hi Tiru, 

Please see inline. 

Cheers,
Med

>-----Message d'origine-----
>De : Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com]
>Envoyé : jeudi 18 septembre 2014 17:18
>À : BOUCADAIR Mohamed IMT/OLN; pcp@ietf.org; cheshire@apple.com
>Objet : RE: I-D Action: draft-vinapamula-flow-ha-03.txt
>
>> -----Original Message-----
>> From: mohamed.boucadair@orange.com
>> [mailto:mohamed.boucadair@orange.com]
>> Sent: Thursday, September 18, 2014 11:57 AM
>> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org; cheshire@apple.com
>> Subject: RE: I-D Action: draft-vinapamula-flow-ha-03.txt
>>
>> Hi Tiru,
>>
>> There are two approaches to address this issue:
>> (1) consider a unified priority level: that is all flows associated with
>the option
>> in the draft should be "processed" equally.
>> (2) add another level of granularity among flows that are associated with
>the
>> option in this draft.
>>
>> The current version of the I-D argues that adding another level of
>granularity
>> to signal a priority level (i.e., approach (2)) may not be that helpful
>because
>> applications will be tempted to systematically set the priority level to
>the
>> highest value in order to increase the chance to have the corresponding
>flow
>> check-pointed/protected.
>
>I can think of two to three ways to address this problem
>1)Applications with required authorization can only signal that it's a high
>priority flow.
>2)End User with the help of a web-portal let's say provided by Home Gateway
>or ISP can re-arrange priorities of flows. Applications like uTorrent
>already provide UI so that user can assign priorities for different file
>downloads.
>3)Just like various good background applications use LEDBAT to limit
>congestion, we can except that such applications in future will explicitly
>signal that it's a low priority flow.
>

[Med] Do you mean PCP messages will be modified in path?

>>
>> Wouldn't (1) be sufficient to address the case you mentioned in your
>> message?
>
>I don't think it is sufficient, it does not provide relative priority.

[Med] Do these flows require check-pointing too? Or you only care about prioritizing these flows during congestion events?