Re: [pcp] A question: How can an internal client get the external IP and port of the inner NAT

🔓Dan Wing <dwing@cisco.com> Fri, 23 October 2015 17:44 UTC

Return-Path: <dwing@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 DDD8E1A88CA for <pcp@ietfa.amsl.com>; Fri, 23 Oct 2015 10:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.229
X-Spam-Level:
X-Spam-Status: No, score=-13.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 8LZNqAn_t3Rd for <pcp@ietfa.amsl.com>; Fri, 23 Oct 2015 10:44:18 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED1DF1A88C8 for <pcp@ietf.org>; Fri, 23 Oct 2015 10:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11980; q=dns/txt; s=iport; t=1445622257; x=1446831857; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=pm/IqKaHaH87L4Ay2lMd1sw1Y+ZM77qa+n/aiP51XLo=; b=nENC8nmLr2KtSMuPGgbmdL1z0h/eqxdGY9MRX7QhKCB90rw+WXpIi1Dd JpHAfiwGD6TXsCtzDDbf6g7dKpQMG2exWOhgU02LnM2pukqO0l1IWLL10 QMa12k3j5Nga8XYhWH8K8Aj53ys8ZLUeo0jn8dgkuiKdUMH63dxbtdN7X E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D7AQDicCpW/4gNJK1egmlNVG++LAENgVkXAQmFfAKBPTgUAQEBAQEBAYEKhDIBAQEDAQEBASAKKBkLBQsJAgcRKgICJzAGE4goCA2WBp03kl0BAQEBAQEBAQEBAQEBAQEBAQEBAQEYhneCEIJuhCoKBwEGRgUHgmkxgRQFh0CGSYgijR6BWIQ/lg8fAQFCgkSBXx40hHoJF4EpAQEB
X-IronPort-AV: E=Sophos; i="5.20,187,1444694400"; d="scan'208,217"; a="40444336"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-6.cisco.com with ESMTP; 23 Oct 2015 17:44:16 +0000
Received: from dhcp-10-155-84-107.cisco.com (dhcp-10-155-84-107.cisco.com [10.155.84.107]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t9NHiGO0020950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Oct 2015 17:44:16 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_D30B4761-3ECA-4D16-8251-BC8BBB1D9A02"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <70006713F8B28D4F88E17B98E1459AB5A3B8B47A@nkgeml501-mbs.china.huawei.com>
Date: Fri, 23 Oct 2015 10:44:15 -0700
Message-Id: <B3CC94E1-A9DF-45F2-99ED-5CA519920B3D@cisco.com>
References: <70006713F8B28D4F88E17B98E1459AB5A3B8B47A@nkgeml501-mbs.china.huawei.com>
To: Chenguohai <chenguohai@huawei.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/TTcPY-EpPm5KINQ2M8x1vGRw7NQ>
Cc: ChenGuohai <chenguohai67@outlook.com>, "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] A question: How can an internal client get the external IP and port of the inner NAT
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 23 Oct 2015 17:44:21 -0000

On 22-Oct-2015 08:24 pm, Chenguohai <chenguohai@huawei.com> wrote: 
>  
>  
> Hi all,
> I am new to PCP and reading RFC6887.I have a question about section 8.1. On the upper part of page 22 writing following,
> the PCP-controlled NAT creating pointless non-functional mappings.
>    When such an intervening non-PCP-aware inner NAT is detected,
>    mappings must first be created by some other means in the inner NAT,
>    before mappings can be usefully created in the outer PCP-controlled
>    NAT.  Having created mappings in the inner NAT by some other means,
>    the PCP client should then use the inner NAT’s external address as
>    the client IP address, to signal to the outer PCP-controlled NAT that
>    the client is aware of the inner NAT, and has taken steps to create
>    mappings in it by some other means, so that mappings created in the
>    outer NAT will not be a pointless waste of resources.
>  
> My question is that how an interal client could get the external IP and port of the inner NAT.

PCP, UPnP IGD, STUN, manual configuration.

> Should there be server between the inner NAT and the external one? How could it be assured that the inner NAT does not change external port?

Hopefully whatever mechanism the client used (PCP, UPnP IGD, STUN, manual configuration) would tell the client of such a change.

-d



>  
> BR
> G.Robert  Chen
> -------------------------------------------------------------------------------------------------------------------------------------
> G.Robert  Chen (Chen Guohai  陈国海). Network Research Department, Huawei Technologies Co., Ltd. Telephone: 0086-25-56624606;   http://www.huawei.com <http://www.huawei.com/>
> -------------------------------------------------------------------------------------------------------------------------------------
> This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the  information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
> ----------------------------------------------------------------------------------------------------------------------------------------
>  
>  
>  
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp