Re: [pcp] FW: New Version Notification for draft-penno-pcp-asdn-00.txt

"Reinaldo Penno (repenno)" <repenno@cisco.com> Mon, 30 September 2013 14:17 UTC

Return-Path: <repenno@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A645121F9D8B for <pcp@ietfa.amsl.com>; Mon, 30 Sep 2013 07:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.879
X-Spam-Level:
X-Spam-Status: No, score=-9.879 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, J_BACKHAIR_37=1, RCVD_IN_DNSWL_HI=-8]
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 pQ+VMQ+n6KH6 for <pcp@ietfa.amsl.com>; Mon, 30 Sep 2013 07:16:59 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 911B521F9DA9 for <pcp@ietf.org>; Mon, 30 Sep 2013 07:16:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3150; q=dns/txt; s=iport; t=1380550616; x=1381760216; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=QHBqauFsXX4V+yTRKQ65Q/eeRnCMH6DVHrf01pZwO1Y=; b=cdTRuzA60h8nMm9YEbWCE2aEzfjofhPlgPDhQw+L3f1277yGuMufwWGh yXaOQmILfeglYFfuMQ8Xz+4NNDWAWIpaFWHJa3R13ZfWmd0AJadI57rSV VMXLAmAJ0IIRljTvd9Cfticj445QzK3f5QOvnucEZ0Kr5nVw1SNxhYHYN A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFADeHSVKtJXG8/2dsb2JhbABagwc4UsB9gSwWdIIlAQEBBAEBASQTNAkOBgEIEQQBAQEKFAkoBgsUCAEIAgQBEggBEodZAw8Ms10NiWqMZoI6DykGgxmBAwOWFoMYixaFNIMkgio
X-IronPort-AV: E=Sophos;i="4.90,1008,1371081600"; d="scan'208";a="266188510"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-5.cisco.com with ESMTP; 30 Sep 2013 14:16:56 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r8UEGtrb003759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 30 Sep 2013 14:16:55 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.47]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Mon, 30 Sep 2013 09:16:55 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] FW: New Version Notification for draft-penno-pcp-asdn-00.txt
Thread-Index: AQHOvee3P0pxuOof/EuOMEici86fbA==
Date: Mon, 30 Sep 2013 14:16:54 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B71A204@xmb-rcd-x04.cisco.com>
In-Reply-To: <52497938.1010900@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.145.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C274DC9DA90B924B9369F602672BCF2D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] FW: New Version Notification for draft-penno-pcp-asdn-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 30 Sep 2013 14:17:04 -0000

Hi Tom,

In a nutshell, for the scenarios described in the draft, yes. But with
worked to correct or bring differentiators that we believe make this
solution interesting.

Last IETF we presented the draft
(http://tools.ietf.org/html/draft-wing-pcp-flowdata-00) and implementation
of these ideas on both MiniUPnP and Tramsission Bittorrent client.

A more generic app<->network signaling and metadata discussion can be
found in:

http://tools.ietf.org/html/draft-eckert-intarea-flow-metadata-framework-00

Thanks,

Reinaldo

The motivations behind this solution are further discussed in

On 9/30/13 6:14 AM, "Tom Taylor" <tom.taylor.stds@gmail.com> wrote:

>So this is a substitute for RSVP in particular?
>
>On 30/09/2013 1:46 AM, Tirumaleswar Reddy (tireddy) wrote:
>> This document describes an approach where using PCP the application
>>explicitly signals its needs to the network to provide additional
>>network services such as QoS or supplemental bandwidth and the Policy
>>Decision Point (for e.g. SDN controller) programs the network with flow
>>information and its associated metadata to provide differentiated
>>treatment.
>>
>> comments and suggestions are welcome.
>>
>> -Authors.
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Sunday, September 29, 2013 8:36 PM
>> To: Tirumaleswar Reddy (tireddy); Suresh Vinapamula; Reinaldo Penno
>>(repenno); Mohamed Boucadair; Dan Wing (dwing)
>> Subject: New Version Notification for draft-penno-pcp-asdn-00.txt
>>
>>
>> A new version of I-D, draft-penno-pcp-asdn-00.txt
>> has been successfully submitted by Reinaldo Penno and posted to the
>> IETF repository.
>>
>> Filename:	 draft-penno-pcp-asdn
>> Revision:	 00
>> Title:		 Application Enabled SDN (A-SDN)
>> Creation date:	 2013-09-29
>> Group:		 Individual Submission
>> Number of pages: 12
>> URL:            
>>http://www.ietf.org/internet-drafts/draft-penno-pcp-asdn-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-penno-pcp-asdn
>> Htmlized:        http://tools.ietf.org/html/draft-penno-pcp-asdn-00
>>
>>
>> Abstract:
>>     To allow traversal of firewalls or provide additional network
>>     services such as QoS or supplemental bandwidth, it is necessary to
>>     deploy application-aware network elements.  Such network elements
>>are
>>     costly to create, deploy, and are unable to adequately cope with
>>     changes to the application itself, stifling innovation.
>>
>>     This document describes a different approach, where the application
>>     explicitly signals its needs to the network.
>>
>>
>>
>>
>>
>> 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.
>>
>> The IETF Secretariat
>>
>> _______________________________________________
>> 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