IETF Logo Mail Archive

Re: [pcp] Question about THIRD_PARTY option in DS-Lite PCP Client (not Proxy)

"Reinaldo Penno (repenno)" <repenno@cisco.com> Wed, 28 August 2013 14:44 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 2930D21F9B94 for <pcp@ietfa.amsl.com>; Wed, 28 Aug 2013 07:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level:
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6, 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 WJhBP-zZVgmS for <pcp@ietfa.amsl.com>; Wed, 28 Aug 2013 07:44:25 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 4550621F9AEF for <pcp@ietf.org>; Wed, 28 Aug 2013 07:44:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1804; q=dns/txt; s=iport; t=1377701065; x=1378910665; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=3qrWlHelasD7dkcZldrE2Tt06YFoEWsX/WmO3Clz+3k=; b=RXf/9XBOGwnu9zqZCByNfAoobHIjBGluRMQELs3L5aNeHzj9bvyN+YAL spjYp3srTPn0h9PRa83lzKT4LGztsQZSTZ/Hohmz4Rbr+NRQqQVlsAC+U ayK/khe/wYzKZx0QYTkl4IyXukfRdjRnYB9iMS+x+EsZ8aoUW0l79FtlM s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAIAMHlKtJXG8/2dsb2JhbABbgwc1UcAqgR8WdIImAQQBAQE3NB0BCA4UFDcLJQIEARIIh3kMuSOPMziDHH0DmR6JAIc0gyCCKg
X-IronPort-AV: E=Sophos;i="4.89,976,1367971200"; d="scan'208";a="252655187"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 28 Aug 2013 14:44:13 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r7SEiCTH017282 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Wed, 28 Aug 2013 14:44:12 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.201]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Wed, 28 Aug 2013 09:44:12 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Tassos Chatzithomaoglou <achatz@forthnetgroup.gr>, "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: [pcp] Question about THIRD_PARTY option in DS-Lite PCP Client (not Proxy)
Thread-Index: AQHOo/0P6RhUbZuSKUOYVEtry6+UPg==
Date: Wed, 28 Aug 2013 14:44:12 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040912A43B@xmb-rcd-x04.cisco.com>
In-Reply-To: <521DE3FD.5050802@forthnetgroup.gr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.253.180]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CA06A761A30AE54C898884A35629D977@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 14:44:30 -0000

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

v2.23.0 | Report a Bug | By Email