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

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Fri, 19 September 2014 09:06 UTC

Return-Path: <tireddy@cisco.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 B82CC1A0049 for <pcp@ietfa.amsl.com>; Fri, 19 Sep 2014 02:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.153
X-Spam-Level:
X-Spam-Status: No, score=-16.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 gVJAfFPITGpn for <pcp@ietfa.amsl.com>; Fri, 19 Sep 2014 02:06:48 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFE271A0052 for <pcp@ietf.org>; Fri, 19 Sep 2014 02:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2998; q=dns/txt; s=iport; t=1411117608; x=1412327208; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=pKVcLlFfOGJYlhBEYk5/Q10WSYtFFAjxXQjDfrtBB7M=; b=h+84eN74WAcmJcwP5iC4A0aiE5rUro/3+T/2AV/XBDlnmh0oQf9mrude 6pHytsg1S9jNweEFlHdMovTGRm3WCQ88qR5UqkeUSkoW86psq4+NpopdU 2izePb1r6myQj4FEAPNERQD4/Qe1T/CQdeLT6CyPcvcWeVVQqh9uc3pFD g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFANXwG1StJA2H/2dsb2JhbABggw2BKgTRKQGBAhYBeYQDAQEBBIEFBAIBCBEEAQELHQcyFAkIAQEEARIIiDbCXAEXjyAmOAaDKIEdBYsEhkqGdJoSg15sgQdBgQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,553,1406592000"; d="scan'208";a="356307389"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP; 19 Sep 2014 09:06:47 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s8J96lkW020985 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Sep 2014 09:06:47 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.68]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Fri, 19 Sep 2014 04:06:47 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.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+MSL2FizvHY3vI8wAe8PHQAAY97gA=
Date: Fri, 19 Sep 2014 09:06:47 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A2832BF02@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A2832B5B2@xmb-rcd-x10.cisco.com> <787AE7BB302AE849A7480A190F8B933006B05A@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933006B05A@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.39.66.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/4RuMizzGT9up1WTr7eOrRqLBy2I
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 09:06:50 -0000

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Friday, September 19, 2014 11:38 AM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org; cheshire@apple.com
> Subject: RE: I-D Action: draft-vinapamula-flow-ha-03.txt
> 
> 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?

No, I meant there will be some applications that will declare that they have low-priority flows just like applications that declare  that HA is not required.

> 
> >>
> >> 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?

These flows could care about both check-pointing and prioritization or care about only one of them.

-Tiru

>