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

"Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com> Fri, 19 September 2014 12:16 UTC

Return-Path: <Lyle.T.Bertz@sprint.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 4F7751A00F1 for <pcp@ietfa.amsl.com>; Fri, 19 Sep 2014 05:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-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 8vCm0P2LCWNZ for <pcp@ietfa.amsl.com>; Fri, 19 Sep 2014 05:16:17 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0744.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:744]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5C961A00B0 for <pcp@ietf.org>; Fri, 19 Sep 2014 05:16:17 -0700 (PDT)
Received: from BL2FFO11FD014.protection.gbl (10.173.160.31) by BL2FFO11HUB038.protection.gbl (10.173.160.242) with Microsoft SMTP Server (TLS) id 15.0.1029.15; Fri, 19 Sep 2014 12:15:54 +0000
Received: from pdaasdm2.corp.sprint.com (144.229.32.57) by BL2FFO11FD014.mail.protection.outlook.com (10.173.160.222) with Microsoft SMTP Server (TLS) id 15.0.1029.15 via Frontend Transport; Fri, 19 Sep 2014 12:15:54 +0000
Received: from plsasen1.corp.sprint.com (default-server.local [144.226.201.28]) by pdaasdm2.corp.sprint.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s8JCFqBE030274 (version=TLSv1/SSLv3 cipher=ADH-AES256-SHA bits=256 verify=NO); Fri, 19 Sep 2014 07:15:53 -0500
Received: from PREWE13M07.ad.sprint.com (prewe13m07.corp.sprint.com [144.226.128.26]) by plsasen1.corp.sprint.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s8JCFpNc007559 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Sep 2014 07:15:52 -0500
Received: from PLSWE13M07.ad.sprint.com (2002:90e5:d61a::90e5:d61a) by PREWE13M07.ad.sprint.com (2002:90e2:801a::90e2:801a) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 19 Sep 2014 08:15:51 -0400
Received: from PLSWE13M07.ad.sprint.com ([fe80::b8a7:9769:a6fe:384c]) by PLSWE13M07.ad.sprint.com ([fe80::b8a7:9769:a6fe:384c%15]) with mapi id 15.00.0847.030; Fri, 19 Sep 2014 07:15:50 -0500
From: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "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/TU6bHi/y5qfc1ykmPZBIvV68iagAplrcAAAY8XYAAAG6RgAADCIAAAAejZlA=
Date: Fri, 19 Sep 2014 12:15:50 +0000
Message-ID: <62f870a31458456d81aeb9adc5cb5484@PLSWE13M07.ad.sprint.com>
References: <913383AAA69FF945B8F946018B75898A2832B5B2@xmb-rcd-x10.cisco.com> <787AE7BB302AE849A7480A190F8B933006B05A@OPEXCLILM23.corporate.adroot.infra.ftgroup> <913383AAA69FF945B8F946018B75898A2832BF02@xmb-rcd-x10.cisco.com> <787AE7BB302AE849A7480A190F8B933006B24F@OPEXCLILM23.corporate.adroot.infra.ftgroup> <913383AAA69FF945B8F946018B75898A2832BF59@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A2832BF59@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.123.104.25]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:144.229.32.57; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(438002)(189002)(199003)(55784002)(13464003)(51704005)(377454003)(83322001)(81342003)(99396002)(6806004)(81542003)(230783001)(64706001)(76482002)(90102001)(74502003)(108616004)(74662003)(77982003)(15975445006)(95666004)(19580395003)(50466002)(47776003)(79102003)(80022003)(2501002)(44976005)(93886004)(85306004)(4396001)(77096002)(20776003)(2656002)(46102003)(19580405001)(85852003)(2201001)(87936001)(107886001)(31966008)(92566001)(86362001)(21056001)(23756003)(83072002)(33646002)(76176999)(106466001)(50986999)(107046002)(54356999)(26826002)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2FFO11HUB038; H:pdaasdm2.corp.sprint.com; FPR:; MLV:ovrnspm; PTR:smtpda2.sprint.com; MX:1; A:1; LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;UriScan:;
X-Forefront-PRVS: 0339F89554
Received-SPF: Pass (protection.outlook.com: domain of sprint.com designates 144.229.32.57 as permitted sender) receiver=protection.outlook.com; client-ip=144.229.32.57; helo=pdaasdm2.corp.sprint.com;
Authentication-Results: spf=pass (sender IP is 144.229.32.57) smtp.mailfrom=Lyle.T.Bertz@sprint.com;
X-OriginatorOrg: sprint.com
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/D8gfZL-L5NznflUdVRC74dokLNw
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 12:16:20 -0000

ARP is applied at the radio bearer level which often represents multiple IP flows.

A user who is congested because their demand exceeds the radio resources they can receive, e.g. coverage challenge, from the network may never see ARP come into play if the radio network is not itself congested.

-----Original Message-----
From: pcp [mailto:pcp-bounces@ietf.org] On Behalf Of Tirumaleswar Reddy (tireddy)
Sent: Friday, September 19, 2014 5:46 AM
To: mohamed.boucadair@orange.com; pcp@ietf.org; cheshire@apple.com
Subject: Re: [pcp] I-D Action: draft-vinapamula-flow-ha-03.txt

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Friday, September 19, 2014 2:49 PM
> To: Tirumaleswar Reddy (tireddy); pcp@ietf.org; cheshire@apple.com
> Subject: RE: I-D Action: draft-vinapamula-flow-ha-03.txt
>
> Re-,
>
> Please see inline.
>
> Cheers,
> Med
>
> >-----Message d'origine-----
> >De : Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com] Envoyé :
> >vendredi 19 septembre 2014 11:07 À : 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: 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
> >> >
> >> >
> >> >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.
>
> [Med] OK. If we assume a priority level was added, what will be the
> behavior of the server when it receives a request for high-priority
> flow but there is no resources to honor the request? Should it remove
> entries with low-priority from the check-pointing table? I'm afraid
> this will induce more complexity at the server side.

I thought servers already have such complexity, for example Mobile Networks already use techniques like ARP (Allocation and Retention priority) to accommodate high-priority flow by penalizing low-priority flows.

>
> >
> >>
> >> >>
> >> >> 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.
>
> [Med] I can understand the priority level for flows that are subject
> to check- pointing, but I have an issue to generalize this draft to
> address the prioritization purpose ** only **. The problems are not
> the same. If prioritization is needed as a requirement in its own
> (which I understand since I'm for a mean to indicate at least DSCP),
> then a dedicated option can be defined for that purpose.

Works for me.

-Tiru

_______________________________________________
pcp mailing list
pcp@ietf.org
https://www.ietf.org/mailman/listinfo/pcp

________________________________

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.