Re: [pcp] Will PCP do it?
"Dan Wing" <dwing@cisco.com> Tue, 29 March 2011 11:50 UTC
Return-Path: <dwing@cisco.com>
X-Original-To: pcp@core3.amsl.com
Delivered-To: pcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08A3A28C15E for <pcp@core3.amsl.com>; Tue, 29 Mar 2011 04:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.49
X-Spam-Level:
X-Spam-Status: No, score=-110.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Sp-Kr8ejIJi for <pcp@core3.amsl.com>; Tue, 29 Mar 2011 04:50:28 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 776A228C158 for <pcp@ietf.org>; Tue, 29 Mar 2011 04:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=7886; q=dns/txt; s=iport; t=1301399526; x=1302609126; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=7ZexUasZ4/8fIh2GhTKRZDdOhDAYI6nmWWUEP/XyNmE=; b=d+Rn3UGAX7aijymtwFap/btCGBnuD6fVNYy+kUIHhtJl/qaJiMJRa1mn eCTwCWd0ad+/i68AzWNa6NI/VufbMOjMOeRRNpCYftBV1dXjwaVXjBlGF aA6r2EeMHoMOynlnyQpthib94N5oQTlQyC2E257csy/ATdwBVFUjt7Kw8 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAF7HkU2rRDoH/2dsb2JhbACYD4Fji1N3iHmff5xQhWoE
X-IronPort-AV: E=Sophos;i="4.63,262,1299456000"; d="scan'208";a="326587943"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 29 Mar 2011 11:52:06 +0000
Received: from dwingWS ([10.21.70.165]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2TBq4aq030726; Tue, 29 Mar 2011 11:52:05 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Tina Tsou' <tena@huawei.com>, pcp@ietf.org
References: <6D908227-5221-4336-B6C3-530BFB474DE7@huawei.com> <1fd001cbde91$0f065ad0$2d131070$@com> <004701cbde93$7fe9d220$7fbd7660$@com> <202701cbde95$65763490$30629db0$@com> <007401cbde9f$ff965640$fec302c0$@com> <218301cbdeb2$feb60dc0$fc222940$@com> <016f01cbdf61$79cad9b0$6d608d10$@com> <26ff01cbdf6c$786220f0$692662d0$@com> <015c01cbedf8$4a078430$de168c90$@com>
In-Reply-To: <015c01cbedf8$4a078430$de168c90$@com>
Date: Tue, 29 Mar 2011 13:52:04 +0200
Message-ID: <095501cbee07$b9cc3220$2d649660$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvfYYljRHQVEdCvTsG01QjobsohnQACqvOgA6KevnAABCCywA==
Content-Language: en-us
Subject: Re: [pcp] Will PCP do it?
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 29 Mar 2011 11:50:30 -0000
Nope, PCP doesn't tell an external server the internal IP address + port, because PCP is only listening on the internal-facing interface (not on the Internet-facing external interface) and the existing OpCodes can't express the internal IP address or port. The GET OpCode is close to what you're looking for, draft-boucadair-pcp-failure. However, the security model for your scenario would be different, too -- it is important to prevent server "A" from discoverying how many subscribers had a connection to server B; consider for example the case where two competing content providers queried a NAT to determine market share of their competitor. -d > -----Original Message----- > From: Tina Tsou [mailto:tena@huawei.com] > Sent: Tuesday, March 29, 2011 12:02 PM > To: 'Dan Wing'; pcp@ietf.org > Subject: RE: [pcp] Will PCP do it? > > Hi Dan, > Sorry for the late response. The use cases about real-time query to > the NAT > and non-real-time query to the log server have the same need - mapping > the > external IP address, transport protocol and port # to the > internal/private > IP address and port #. > > > We keep our promises with one another - no matter what! > > Best Regards, > Tina TSOU > http://tinatsou.weebly.com/contact.html > > > -----Original Message----- > From: Dan Wing [mailto:dwing@cisco.com] > Sent: Thursday, March 10, 2011 10:45 PM > To: 'Tina Tsou'; pcp@ietf.org > Subject: RE: [pcp] Will PCP do it? > > > -----Original Message----- > > From: Tina Tsou [mailto:tena@huawei.com] > > Sent: Thursday, March 10, 2011 12:27 PM > > To: 'Dan Wing'; pcp@ietf.org > > Subject: RE: [pcp] Will PCP do it? > > > > The use case is to allow mobile location to be provided to web > portals. > > Ok. And the mobile has a connection (TCP?) that same web portal? If > so, it sounds like exactly the sort of thing that > draft-chen-intarea-v4-uid-header-option, draft-zhang-v6ops-cgn-source- > trace, > or draft-wing-nat-reveal-option could help with. > > Or is this for something like AT&T's existing FamilyMap service, > https://familymap.wireless.att.com/finder-att- > family/helpContent.htm?topic=1 > , > where the phone does not have a connection to the web portal. In which > case, there would not be a PCP mapping. > > -d > > > > > > > We keep our promises with one another - no matter what! > > > > Best Regards, > > Tina TSOU > > http://tinatsou.weebly.com/contact.html > > > > > > -----Original Message----- > > From: Dan Wing [mailto:dwing@cisco.com] > > Sent: Wednesday, March 09, 2011 3:38 PM > > To: 'Tina Tsou'; pcp@ietf.org > > Subject: RE: [pcp] Will PCP do it? > > > > > -----Original Message----- > > > From: Tina Tsou [mailto:tena@huawei.com] > > > Sent: Wednesday, March 09, 2011 1:22 PM > > > To: 'Dan Wing'; pcp@ietf.org > > > Subject: RE: [pcp] Will PCP do it? > > > > > > It is not related to source-trace. > > > > I am out of guesses. > > > > What is the use case? > > > > -d > > > > > > > > > > We keep our promises with one another - no matter what! > > > > > > Best Regards, > > > Tina TSOU > > > http://tinatsou.weebly.com/contact.html > > > > > > > > > -----Original Message----- > > > From: Dan Wing [mailto:dwing@cisco.com] > > > Sent: Wednesday, March 09, 2011 12:06 PM > > > To: 'Tina Tsou'; pcp@ietf.org > > > Subject: RE: [pcp] Will PCP do it? > > > > > > > -----Original Message----- > > > > From: Tina Tsou [mailto:tena@huawei.com] > > > > Sent: Wednesday, March 09, 2011 11:52 AM > > > > To: 'Dan Wing'; pcp@ietf.org > > > > Subject: RE: [pcp] Will PCP do it? > > > > > > > > My understanding about PCP is that it allows the PCP client to > > > instruct > > > > the > > > > PCP server to allocate a port number with a transport protocol > > > > (pinhole) so > > > > that the PCP client can send the NAT's public IP address, > transport > > > > protocol > > > > and port number to the application server outside the NAT to > allow > > > that > > > > application server to send information to the device with the PCP > > > > client. > > > > > > Yes, that covers two of the use-cases described in draft-ietf-pcp- > > base, > > > " Operating a Server" (Section 7.1) and "Operating a Symmetric > > > Client/Server" (Section 7.3). > > > > > > > A PCP client already has the public IP address, transport port > > > protocol > > > > and > > > > port number What I described does not involve the device behind > > the > > > > NAT but > > > > another entity that is interested in knowing which private IP > > address > > > > is > > > > assigned with a specific port number for a transport protocol and > > > NAT's > > > > public IP address. Is it in your opinion that PCP can be > enhanced > > to > > > > support this type of inquiry? Just ask. > > > > > > It could be. I'm asked "what is the use case" to understand why > > > you're wanting this functionality. > > > > > > > If not, I will go for another > > > > candidate protocol. > > > > > > > > In the mobile operator network, two interfaces are needed if > mobile > > > GW > > > > and > > > > NAT are separate: > > > > 1. with NAT: request contains the NAT's public IP address, > > transport > > > > protocol and port number; response contains the private IP > address > > > and > > > > the > > > > port number. > > > > 2. with mobile GW: request contains the private IP address and > > > response > > > > contains the mobile identities (e.g. IMSI, MSISDN, etc.) > > > > > > > > If the mobile GW is integrated with the NAT, one interface is > > needed. > > > > The > > > > request contains the mobile GW's/NAT's public IP address, > transport > > > > protocol > > > > and port number, and the response contains the mobile identities. > > > > > > Sorry, I still don't understand the use case. > > > > > > Is the use case to allow an external entity to perform user > > > identification, > > > akin to draft-chen-intarea-v4-uid-header-option or > > > draft-zhang-v6ops-cgn-source-trace or draft-wing-nat-reveal-option > ?? > > > > > > -d > > > > > > > > > > We keep our promises with one another - no matter what! > > > > > > > > Best Regards, > > > > Tina TSOU > > > > http://tinatsou.weebly.com/contact.html > > > > > > > > > > > > -----Original Message----- > > > > From: Dan Wing [mailto:dwing@cisco.com] > > > > Sent: Wednesday, March 09, 2011 11:35 AM > > > > To: 'Tina TSOU'; pcp@ietf.org > > > > Subject: RE: [pcp] Will PCP do it? > > > > > > > > > -----Original Message----- > > > > > From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On > > Behalf > > > Of > > > > > Tina TSOU > > > > > Sent: Tuesday, March 08, 2011 7:36 AM > > > > > To: pcp@ietf.org > > > > > Subject: [pcp] Will PCP do it? > > > > > > > > > > Hi, > > > > > NAT has the private IP address, transport protocol and port # > on > > > the > > > > > "internal" side and the public IP address, transport protocol > and > > > > port > > > > > # on the "external" side. I'm looking for to allow an entity > > > (e.g., > > > > > not the PCP client who uses PCP to request a port number > > assignment > > > > on > > > > > the "external" side) to know the private IP address on the > > > "internal" > > > > > side for the given public IP address, transport protocol and > port > > # > > > > on > > > > > the "external" side. > > > > > Will PCP do it? > > > > > > > > No. > > > > > > > > What is the use case? > > > > > > > > -d > > > > > > > > > > > > > > > > > > B. R. > > > > > Tina > > > > > http://tinatsou.weebly.com > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > pcp mailing list > > > > > pcp@ietf.org > > > > > https://www.ietf.org/mailman/listinfo/pcp > > > > > >
- [pcp] Will PCP do it? Tina TSOU
- Re: [pcp] Will PCP do it? Dan Wing
- Re: [pcp] Will PCP do it? Tina Tsou
- Re: [pcp] Will PCP do it? Dan Wing
- Re: [pcp] Will PCP do it? Tina Tsou
- Re: [pcp] Will PCP do it? Dan Wing
- Re: [pcp] Will PCP do it? Tina Tsou
- Re: [pcp] Will PCP do it? Dan Wing
- Re: [pcp] Will PCP do it? Tina Tsou
- Re: [pcp] Will PCP do it? Dan Wing
- Re: [pcp] Will PCP do it? Francis Dupont