Re: [pcp] Question about THIRD_PARTY option in DS-Lite PCP Client (not Proxy)
Tassos Chatzithomaoglou <achatz@forthnetgroup.gr> Wed, 28 August 2013 15:04 UTC
Return-Path: <achatz@forthnetgroup.gr>
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 CD52D21F8DDD for <pcp@ietfa.amsl.com>; Wed, 28 Aug 2013 08:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
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 XXL4hNWMPPRE for <pcp@ietfa.amsl.com>; Wed, 28 Aug 2013 08:04:05 -0700 (PDT)
Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.115]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFE511E8195 for <pcp@ietf.org>; Wed, 28 Aug 2013 08:04:04 -0700 (PDT)
Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-01.forthnet.gr (8.14.4/8.14.4) with ESMTP id r7SF3xdG028648; Wed, 28 Aug 2013 18:03:59 +0300
Received: from MX-IN-05.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.30]) by mx-av-03.forthnet.gr (8.14.3/8.14.3) with ESMTP id r7SF3xR1025297; Wed, 28 Aug 2013 18:03:59 +0300
Received: from [192.168.1.2] (194.219.240.252.dsl.dyn.forthnet.gr [194.219.240.252]) by MX-IN-05.forthnet.gr (8.14.4/8.14.4) with ESMTP id r7SF3wsN023876; Wed, 28 Aug 2013 18:03:59 +0300
Authentication-Results: MX-IN-05.forthnet.gr smtp.mail=achatz@forthnetgroup.gr; spf=pass
Authentication-Results: MX-IN-05.forthnet.gr header.from=achatz@forthnetgroup.gr; sender-id=pass
Message-ID: <521E115A.1040609@forthnetgroup.gr>
Date: Wed, 28 Aug 2013 18:03:54 +0300
From: Tassos Chatzithomaoglou <achatz@forthnetgroup.gr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20
MIME-Version: 1.0
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
References: <45A697A8FFD7CF48BCF2BE7E106F06040912A43B@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040912A43B@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [pcp] Question about THIRD_PARTY option in DS-Lite PCP Client (not Proxy)
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, 28 Aug 2013 15:04:21 -0000
Thanks Reinaldo. That's my understanding too, after reading the case "HTTP-Triggered PCP Client Model" in draft-boucadair-pcp-deployment-cases. Question to draft-ietf-pcp-dslite authors: Although i had asked this in the past, are there any plans to add PCP Client in draft-ietf-pcp-dslite? We surely gonna use this functionality. -- Tassos Reinaldo Penno (repenno) wrote on 28/8/2013 17:44: > Seems right - as assuming your DS-Lite CPE does not apply NAT as well. > > The PCP request created by the CPE will allocated a public IP:port in the > AFTR. When external/incoming packets match this external public IP:port > they will be translated to this internal IP (192.168.1.2) and tunneled > over v6 to the CPE. The CPE will decap the v6 and forward the regular IPv4 > packet to its destination. > > If you DS-Lite CPE also does NAT that's another story. The internal IP > should be the WAN facing IPv4. > > On 8/28/13 8:50 AM, "Tassos Chatzithomaoglou" <achatz@forthnetgroup.gr> > wrote: > >> I'm reading draft-ietf-pcp-dslite-00: >> >> In the plain mode the B4, the customer end-point of the DS-Lite IPv6 >> tunnel, implements a PCP proxy ([I-D.ietf-pcp-proxy >> <http://tools.ietf.org/html/draft-ietf-pcp-dslite-00#ref-I-D.ietf-pcp-prox >> y>]) function and >> uses UDP over IPv6 with the AFTR to send PCP requests and receive PCP >> responses. >> >> The B4 MUST source PCP requests with the IPv6 address of its DS-Lite >> tunnel end-point and MUST use a THIRD PARTY option either empty or >> carrying the IPv4 internal address of the mappings. >> >> I'm testing a DS-Lite CPE running a PCP client (PCP Proxy is disabled) >> and i'm trying to create some manual/static mappings through its >> port-forwarding GUI. >> What i'm seeing inside the MAP request is the THIRD PARTY option using as >> "Internal IP address" the local host ip address i define in the port >> forwarding setup (i.e 192.168.1.2). >> This ip address belongs just to a dummy host (running a web server), >> without any PCP/NAT-PMP/UPnP/etc. functionality. >> >> Is this expected? >> >> -- >> Tassos >> >> _______________________________________________ >> pcp mailing list >> pcp@ietf.org >> https://www.ietf.org/mailman/listinfo/pcp > >
- [pcp] Question about THIRD_PARTY option in DS-Lit… Tassos Chatzithomaoglou
- Re: [pcp] Question about THIRD_PARTY option in DS… Reinaldo Penno (repenno)
- Re: [pcp] Question about THIRD_PARTY option in DS… Tassos Chatzithomaoglou