Re: [pcp] Issue Analysis of PCP in Mobile Network was (Fwd: New Version Notification for draft-chen-pcp-mobile-deployment-01.txt)

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Wed, 22 August 2012 12:10 UTC

Return-Path: <tireddy@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 8C36321F86A3 for <pcp@ietfa.amsl.com>; Wed, 22 Aug 2012 05:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.878
X-Spam-Level:
X-Spam-Status: No, score=-7.878 tagged_above=-999 required=5 tests=[AWL=2.421, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lrXX0AJUxhP for <pcp@ietfa.amsl.com>; Wed, 22 Aug 2012 05:10:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD6421F8489 for <pcp@ietf.org>; Wed, 22 Aug 2012 05:10:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tireddy@cisco.com; l=1465; q=dns/txt; s=iport; t=1345637406; x=1346847006; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=8lE6L3Xn6DCClgD94+RtOPsg+z72MdUiVA6mkfMzQSs=; b=WKse8eJMSte4FA8BCOElXA2I4Z9dWVY8tbDJQuSbP7tIGA442AhaW/vH ileulqnmzRa70XG9XgnTlzg9ok4aPlV65GaORThgmFrYx5ViWsUnS8yrq 518gD38HhXUqvtrdEGb/ot1zdZ93+xsDjwuoS2ZxjUQRvO4c7ycWogQ2r 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EANDKNFCtJV2b/2dsb2JhbABFukCBB4IgAQEBAwESAWQHBwQCAQgRBAEBCxkEBzIUCQgCBAESCBqHZQaZKqBQiwiGPGADo3+BZoJh
X-IronPort-AV: E=Sophos;i="4.77,808,1336348800"; d="scan'208";a="114166787"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 22 Aug 2012 12:10:06 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q7MCA52k028947 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Aug 2012 12:10:06 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.216]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0298.004; Wed, 22 Aug 2012 07:10:05 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Vízdal Aleš <ales.vizdal@t-mobile.cz>, GangChen <phdgang@gmail.com>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Issue Analysis of PCP in Mobile Network was (Fwd: New Version Notification for draft-chen-pcp-mobile-deployment-01.txt)
Thread-Index: AQHNY4V3euq9CB4dPEON9BKc/XznjpdYtExggA0GZ8CAAA7kIA==
Date: Wed, 22 Aug 2012 12:10:04 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A1478FB54@xmb-rcd-x10.cisco.com>
References: <CAM+vMETn-vSQOP3_+ixq_iSeiXGsKUGO0LT_Q5m31wXhBKNxcQ@mail.gmail.com> <913383AAA69FF945B8F946018B75898A14782FFE@xmb-rcd-x10.cisco.com> <1808340F7EC362469DDFFB112B37E2FCC681D9234A@SRVHKE02.rdm.cz>
In-Reply-To: <1808340F7EC362469DDFFB112B37E2FCC681D9234A@SRVHKE02.rdm.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.39.28.67]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19130.005
x-tm-as-result: No--44.455800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pcp] Issue Analysis of PCP in Mobile Network was (Fwd: New Version Notification for draft-chen-pcp-mobile-deployment-01.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: Wed, 22 Aug 2012 12:10:10 -0000

> -----Original Message-----
> From: Vízdal Aleš [mailto:ales.vizdal@t-mobile.cz]
> Sent: Wednesday, August 22, 2012 2:24 PM
> To: Tirumaleswar Reddy (tireddy); GangChen; pcp@ietf.org
> Subject: RE: [pcp] Issue Analysis of PCP in Mobile Network was (Fwd:
> New Version Notification for draft-chen-pcp-mobile-deployment-01.txt)
> 
> Hi Tiru,
> 
> > -----Original Message-----
> > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> Tirumaleswar
> > Reddy (tireddy)
> > Sent: Tuesday, August 14, 2012 11:05 AM
> > To: GangChen; pcp@ietf.org
> > Subject: Re: [pcp] Issue Analysis of PCP in Mobile Network was (Fwd:
> New Version
> > Notification for draft-chen-pcp-mobile-deployment-01.txt)
> >
> > Hi -
> >
> > 1. Section 2.1
> > Can you please clarify what kind of applications on Mobile devices
> would require port
> > range on Firewall ?
> > MAP/PEER cannot be used to request Firewall to open a range of ports
> (other than "all
> > ports")
> 
> Do you mean that PCP cannot be used to open up a port on the Firewall

PCP can be used to open port on firewall.

> or are you
> pointing out that a port range cannot be opened ? The latter could be
> achieved by
> a request per port to open up a port range.

using single request/response port range cannot be opened, but agreed it can be achieved using multiple request/responses.

--Tiru.

> 
> > --Tiru.
> 
> Cheers,
> Ales