Re: [pcp] TR: I-D Action: draft-vinapamula-flow-ha-05.txt
"Reinaldo Penno (repenno)" <repenno@cisco.com> Tue, 21 October 2014 19:22 UTC
Return-Path: <repenno@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 710181A19F9 for <pcp@ietfa.amsl.com>; Tue, 21 Oct 2014 12:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 bhViTb516tbn for <pcp@ietfa.amsl.com>; Tue, 21 Oct 2014 12:22:42 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 029A81A1A93 for <pcp@ietf.org>; Tue, 21 Oct 2014 12:22:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10916; q=dns/txt; s=iport; t=1413919361; x=1415128961; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=TJqQ5rAtI5ZCUlRn08lSK8xPsKFpxhkdrusDYHOfv+4=; b=Hk9mLpKnjZtv6ZfCqRjyHTv/go5VSolMjunqA2e10AlelT5+6r6z5N2y o7DOISWqw5RbpFzZnQPMqaHuEUh1xDEkK9VIRxYx7TMcC3DBlj/FcuOWI DflRSzb7bnijXG8qAnblX7x7HdCA39VBAZ3QPtwbAZnbBfELNM6X3aCN0 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFACSyRlStJV2b/2dsb2JhbABSCoMOU1MFBIMCyW8Kh00CG3sWAX2EAwEBBAEBASAROhsCAQgYAgIJCQEQAwICAiULFAEQAgQBEgmINggFsWCUbQEBAQEBAQQBAQEBAQEBG4EsiSqFJQUKGhgiEgGCZIFUBZIBhEaEN4JcgTA8gwyKVYJXhAGDeGwBgQYBBxcigQMBAQE
X-IronPort-AV: E=Sophos;i="5.04,763,1406592000"; d="scan'208";a="365204325"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 21 Oct 2014 19:22:40 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9LJMdAV015759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Oct 2014 19:22:39 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.20]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Tue, 21 Oct 2014 14:22:39 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Suresh Kumar Vinapamula Venkata <sureshk@juniper.net>, "Prashanth Patil (praspati)" <praspati@cisco.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] TR: I-D Action: draft-vinapamula-flow-ha-05.txt
Thread-Index: AQHP7S3QZRNhohXfuUSkYfgN+OnwDpw6ZceAgABViAD//7otAIAAV2EA
Date: Tue, 21 Oct 2014 19:22:39 +0000
Message-ID: <D06BFE62.47AE%repenno@cisco.com>
References: <D06BF17D.47A1%repenno@cisco.com> <D06BF274.53F30%sureshk@juniper.net>
In-Reply-To: <D06BF274.53F30%sureshk@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.21.95.87]
Content-Type: text/plain; charset="utf-8"
Content-ID: <470B8FA584F59B4F97BAD58DE6538915@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/YREs4suTcLH4t3h-PrwxeSUxVXU
Subject: Re: [pcp] TR: I-D Action: draft-vinapamula-flow-ha-05.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: Tue, 21 Oct 2014 19:22:45 -0000
Thanks Suresh, your examples clear up a few things: 1 - There might be form of quota per PCP Client/Circuit/Subscriber 2 - There might be some form of authorization that needs to built around this functionality. It could be ISP driven (“subscriber A is gold”) or device driven. Personally these examples seem to represent the functionality better than the ones in “typical usages section”. I would suggest incorporating the text. BTW, I agree that keeping the priority option out of the draft was the right decision. It would complicate things needlessly. Thanks, Reinaldo On 10/21/14, 12:09 PM, "Suresh Kumar Vinapamula Venkata" <sureshk@juniper.net> wrote: >Hi Reinaldo, > >It is not application alone, along with application it is also end user >where ever necessary will help in identifying which flows are critical. >Let me give couple of examples. > >Example 1: >Consider Netflix app is the application that has ability to support this >functionality. >The same app is installed in three UEs A B and C. For A it is critical and >doesn’t want interruption and for B it is not, and for C only some >programs are critical. >At the time of installing this App, this can be provisioned. When netflix >starts streaming >1) It may request user for checkpointing only in case of C. >2) Incase of A all flows are critical. Limiting number of flows to >checkpoint will ensure that UE doesn’t exceed his limit. >3) In case of B it is not an issue as none of these flows are critical for >checkpointing. > >Example 2: >Suppose end user is providing a media streaming service. Subscriptions >could be like gold, silver, bronze. >To provide best quality of service, policies are configured such that >1) all the flows associated with gold subscription should be check >pointed. >2) Only some flows associated with silver subscription is check pointed. >3) None of the flows associated with bronze subscription is check pointed. >When a user logs in for streaming service, based on login credentials he >may fall into one of those buckets, and according to the configured >policy, his associated streaming flows are automatically check pointed. > >Example 3: >Similarly a phone app may provide ability to checkpoint flows associated >with phone calls. >No matter what is configured, some calls are always check pointed, say >call to 911. Application has to identify such calls. > >In short the point I wanted to make is, > >1) Application has ability to checkpoint. >2) Application has some default setting and should be programmable. >3) Exposing and enforcing these features is application specific. >4) If applications don’t honor this, they are treated as rogue >applications. >5) To ensure users don’t exceed their quota (knowingly/unknowingly) limits >are enforced. > >Please let me know if the above makes sense. > >Thanks >Suresh > > >On 10/21/14 11:19 AM, "Reinaldo Penno (repenno)" <repenno@cisco.com> >wrote: > >>In all fairness this does not quite answers the question. What precludes >>every single appellation from requesting their flows to be checkpointerd >>and defeating the original purpose of the new option. >> >>On 10/21/14, 11:13 AM, "Suresh Kumar Vinapamula Venkata" >><sureshk@juniper.net> wrote: >> >>>Hi Prashanth, >>> >>>Thanks for your comment. >>> >>>It is not just the application alone, it is application and end user of >>>that application(where ever applicable) decides if a flow associated >>>with >>>that application is business critical. >>>An application may have a default setting, and may be programmable by >>>end >>>user. Way to program the application is application specific, such as, >>> >>>1) Change default settings while installing that application. >>>2) Popup window to confirm when ever an application is launched. >>>3) Some of them are critical and will not be altered. Say for example a >>>call to 911 is critical. >>>Etc... >>> >>>Configuration of these settings are very similar to configuration of >>>location services by various apps in your iPhone, options to handle >>>popup >>>windows in browsers etc... >>> >>>-Suresh >>> >>> >>>On 10/21/14 5:52 AM, "Prashanth Patil (praspati)" <praspati@cisco.com> >>>wrote: >>> >>>>My concern with the proposal is that that an application will always >>>>choose to checkpoint its flows. Why would an application ever consider >>>>otherwise i.e. consider its flow not critical? >>>>The draft suggests "Administration SHOULD restrict the number of >>>>connections that can be elected to be backed up and the rate of >>>>check-pointing on per PCP client.", which doesn¹t really address the >>>>above >>>>problem. >>>> >>>> >>>>-Prashanth >>>> >>>>On 10/21/14 12:22 PM, "mohamed.boucadair@orange.com" >>>><mohamed.boucadair@orange.com> wrote: >>>> >>>>>Dear all, >>>>> >>>>>An updated version is available online. (comments received during the >>>>>interim meeting were addressed in a previous version) >>>>> >>>>>This version is ready for adoption. >>>>> >>>>>Cheers, >>>>>Med >>>>> >>>>>-----Message d'origine----- >>>>>De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de >>>>>internet-drafts@ietf.org >>>>>Envoyé : mardi 21 octobre 2014 08:06 >>>>>À : i-d-announce@ietf.org >>>>>Objet : I-D Action: draft-vinapamula-flow-ha-05.txt >>>>> >>>>> >>>>>A New Internet-Draft is available from the on-line Internet-Drafts >>>>>directories. >>>>> >>>>> >>>>> Title : Application-Initiated Flow High Availability >>>>>Awareness through PCP >>>>> Authors : Suresh Vinapamula >>>>> Senthil Sivakumar >>>>> Mohamed Boucadair >>>>> Tirumaleswar Reddy >>>>> Filename : draft-vinapamula-flow-ha-05.txt >>>>> Pages : 9 >>>>> Date : 2014-10-20 >>>>> >>>>>Abstract: >>>>> This document specifies a mechanism for a host to signal via Port >>>>> Control Protocol (PCP) which connections should be protected >>>>>against >>>>> network failures. These connections will be elected to be subject >>>>>to >>>>> high availability mechanisms enabled at the network side. >>>>> >>>>> This approach assumes that applications/users have more visibility >>>>> about sensitive connections rather than any heuristic that can be >>>>> enabled at the network side to guess which connections should be >>>>> secured. >>>>> >>>>> >>>>> >>>>>The IETF datatracker status page for this draft is: >>>>>https://datatracker.ietf.org/doc/draft-vinapamula-flow-ha/ >>>>> >>>>>There's also a htmlized version available at: >>>>>http://tools.ietf.org/html/draft-vinapamula-flow-ha-05 >>>>> >>>>>A diff from the previous version is available at: >>>>>http://www.ietf.org/rfcdiff?url2=draft-vinapamula-flow-ha-05 >>>>> >>>>> >>>>>Please note that it may take a couple of minutes from the time of >>>>>submission >>>>>until the htmlized version and diff are available at tools.ietf.org. >>>>> >>>>>Internet-Drafts are also available by anonymous FTP at: >>>>>ftp://ftp.ietf.org/internet-drafts/ >>>>> >>>>>_______________________________________________ >>>>>I-D-Announce mailing list >>>>>I-D-Announce@ietf.org >>>>>https://www.ietf.org/mailman/listinfo/i-d-announce >>>>>Internet-Draft directories: http://www.ietf.org/shadow.html >>>>>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >>>>> >>>>>_______________________________________________ >>>>>pcp mailing list >>>>>pcp@ietf.org >>>>>https://www.ietf.org/mailman/listinfo/pcp >>>> >>>>_______________________________________________ >>>>pcp mailing list >>>>pcp@ietf.org >>>>https://www.ietf.org/mailman/listinfo/pcp >>> >>>_______________________________________________ >>>pcp mailing list >>>pcp@ietf.org >>>https://www.ietf.org/mailman/listinfo/pcp >> >
- [pcp] TR: I-D Action: draft-vinapamula-flow-ha-05… mohamed.boucadair
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Prashanth Patil (praspati)
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Suresh Kumar Vinapamula Venkata
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Reinaldo Penno (repenno)
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Suresh Kumar Vinapamula Venkata
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Reinaldo Penno (repenno)
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Suresh Kumar Vinapamula Venkata
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… Tirumaleswar Reddy (tireddy)
- Re: [pcp] TR: I-D Action: draft-vinapamula-flow-h… mohamed.boucadair