[pcp] FW: New Version Notification for draft-wing-pcp-third-party-authz-03.txt

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Wed, 02 April 2014 12:00 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 657CA1A01F8 for <pcp@ietfa.amsl.com>; Wed, 2 Apr 2014 05:00:00 -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 S9uSKVNsqV7C for <pcp@ietfa.amsl.com>; Wed, 2 Apr 2014 04:59:55 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C93BD1A01F9 for <pcp@ietf.org>; Wed, 2 Apr 2014 04:59:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4574; q=dns/txt; s=iport; t=1396439986; x=1397649586; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=9HDRI7qB/SfS2PHZM2cHZsZ2I+EWQbvVUv4d1rJ8Ng4=; b=J7UFEESs1IDvv/94nXbI7qlO2WfFCa1Ds1ebArl2ehgdrNUHXcbvo7N2 /67iZtGbKBaA8KLnoLYZGOqjklrXuxhf0TprO9js/b4/JKsJuaw1oFbQP qyHBPKbfyELyqELQqp5O+pSuI0OQ7U8EQppi4a2vTGmcpGQVKhhqHownH 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An4FAJv6O1OtJA2J/2dsb2JhbABPCoMGO1EGgwrAXRmBBBZ0giUBAQEEIxE6CQ4EAgEIEQQBAQMCBh0DAgICMBQBBgEBBQMCBBMIAYdwCAWsdaI2F4EpjGsrOAaCaTWBFASaCZEGgzCCKw
X-IronPort-AV: E=Sophos;i="4.97,780,1389744000"; d="scan'208";a="314546064"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-7.cisco.com with ESMTP; 02 Apr 2014 11:59:45 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s32Bxibc017016 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Wed, 2 Apr 2014 11:59:45 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.121]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Wed, 2 Apr 2014 06:59:44 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: New Version Notification for draft-wing-pcp-third-party-authz-03.txt
Thread-Index: AQHPTmp/oENGWDqd9UGApl6Rd2RaGZr+OMkA
Date: Wed, 02 Apr 2014 11:59:43 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A242FDE74@xmb-rcd-x10.cisco.com>
References: <20140402115538.32361.89102.idtracker@ietfa.amsl.com>
In-Reply-To: <20140402115538.32361.89102.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.39.66.242]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/BdU4h34NCmSkJBU9dE2rTHpvHCk
Subject: [pcp] FW: New Version Notification for draft-wing-pcp-third-party-authz-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: Wed, 02 Apr 2014 12:00:00 -0000

Revised draft-wing-pcp-third-party-authz-03 has been published. The update incorporates the comments received from the WG.  Also responding to the comments received from Stuart

Comment1> Why would sites use a blocking mechanism that no apps currently support?

Reply> The problem with WebRTC applications is that Enterprises with restrictive Firewall policies are blocking P2P media streams and data channels. In such deployments, PCP can be used to identify the media session initiated using trusted third party WebRTC service providers. PCP requests without third party authorization can be used to identify non-business related media streams and thus these flows can be prioritized accordingly. The goal is not to block, but give differentiated service to these flows. This problem was also discussed in PNTAW ietf mailing list sometime back.

Comment2> Why would app vendors adopt a mechanism to circumvent a blocking mechanism when no sites are currently using the blocking mechanism or supporting the circumvention mechanism?

Reply> This draft solves two problems, that interests application vendors

1) To solve the problems explained in the response to the first comment.
2) This mechanism can also be used by the ISP to identify and prioritize media streams initiated using third party WebRTC service providers that have tie-up with the ISP. Usage of PCP third party authorization in Mobile Networks to prioritize media streams is discussed in http://tools.ietf.org/html/draft-penno-pcp-mobile-qos-00. 

Thanks and Regards,
-Tiru

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Wednesday, April 02, 2014 5:26 PM
To: Prashanth Patil (praspati); Tirumaleswar Reddy (tireddy); Prashanth Patil (praspati); Tirumaleswar Reddy (tireddy); Dan Wing (dwing); Reinaldo Penno (repenno); Dan Wing (dwing); Reinaldo Penno (repenno)
Subject: New Version Notification for draft-wing-pcp-third-party-authz-03.txt


A new version of I-D, draft-wing-pcp-third-party-authz-03.txt
has been successfully submitted by Tirumaleswar Reddy and posted to the IETF repository.

Name:		draft-wing-pcp-third-party-authz
Revision:	03
Title:		PCP Extension for Third Party Authorization
Document date:	2014-04-02
Group:		Individual Submission
Pages:		15
URL:            http://www.ietf.org/internet-drafts/draft-wing-pcp-third-party-authz-03.txt
Status:         https://datatracker.ietf.org/doc/draft-wing-pcp-third-party-authz/
Htmlized:       http://tools.ietf.org/html/draft-wing-pcp-third-party-authz-03
Diff:           http://www.ietf.org/rfcdiff?url2=draft-wing-pcp-third-party-authz-03

Abstract:
   It is often desirable for an application server to permit a flow
   across a firewall, as happens today when a firewall includes an
   Application Layer Gateway (ALG) function.  However, an ALG has
   several weaknesses.

   This document describes a cryptographic technique for an application
   server to permit a flow across a firewall.  This technique uses OAuth
   and a new PCP option.

                                                                                  


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