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

🔓Dan Wing <dwing@cisco.com> Mon, 26 October 2015 16:57 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 1B7B01B4D8B for <pcp@ietfa.amsl.com>; Mon, 26 Oct 2015 09:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.01
X-Spam-Level:
X-Spam-Status: No, score=-13.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_62=0.6, 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 r0TNKO9K8d2H for <pcp@ietfa.amsl.com>; Mon, 26 Oct 2015 09:57:14 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EE661B4781 for <pcp@ietf.org>; Mon, 26 Oct 2015 09:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=42462; q=dns/txt; s=iport; t=1445878634; x=1447088234; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=CTulQZByIOfb/DV6vvX6EBTQw7P0MM/Ubk3oMqq0iOw=; b=ZvW0+mlT94Al8I2qBdQg7AVEmXyXE1XkRM1WFalfLU6+B64uxFxCFqmU vj8fvDixTPin5sKc1xQ7SJmNnZ488LE2P7A3j6F2iB9S5G01UPJ+mwViu UaZaXQk/TtUflULA/PLEMNEWv/d5f2m0hA9j4zQoT6eo+rHSbZh8tKUxt g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AzBQCwWi5W/5tdJa1egmlNVG++UoFXAxcBCYV8AoE0OhIBAQEBAQEBgQqEMgEBAQMBAQEBIAooGQsFCwkCBwoDAQIBIAEGAwICJx8JCAYTiBsDCggNlTWdN407GIQ6AQEBAQEBAQEBAQEBAQEBAQEBAQEBGIZ3ghCCboQqCgcBBh4DGAEHBQEEBgGCaTGBFAWHQoZLhFWDVIgMhRaBWYQ/gwGPJoNwKAU2gkSBXx40hU8JF4EpAQEB
X-IronPort-AV: E=Sophos;i="5.20,201,1444694400"; d="scan'208,217";a="202096157"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Oct 2015 16:57:13 +0000
Received: from [10.24.49.217] ([10.24.49.217]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t9QGvBQs019192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Oct 2015 16:57:12 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_201CA6B5-E4B0-4F9B-B11F-15388F382EB4"
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: <70006713F8B28D4F88E17B98E1459AB5A3B8B8B7@nkgeml501-mbs.china.huawei.com>
Date: Mon, 26 Oct 2015 09:57:11 -0700
Message-Id: <C4ED7181-4527-4F6F-8477-FAE84BB9EB98@cisco.com>
References: <70006713F8B28D4F88E17B98E1459AB5A3B8B8B7@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/sZLXyuVBYK-cSO7WYm3KpVUwX34>
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: Mon, 26 Oct 2015 16:57:17 -0000

On 25-Oct-2015 06:54 pm, Chenguohai <chenguohai@huawei.com> wrote: 
>  
>  
> Hi Dan,
>  
> Thank again.
> What is the workflow in nested NATs for internal host?
> 1: the client must judge how many NATs are there in the path and the order;

It doesn't need to perform (1) first.  In fact, it's impossible to determine how many NATs are on the path first.


> 2: nogotiate with the fisrt PCP server(in the most nested NAT) for the exteral IP and port;
> 3:use the negotiated IP and port with the second PCP server;
> 4 do step 2 and 3 until communicating to the most external PCP server.

Correct.  And after doing that, it will have determined how many PCP-supporting NATs are on the path.

>  
> Does this make sense?

Yes.

-d


>  
> BR
> G.Robert  Chen
> -------------------------------------------------------------------------------------------------------------------------------------
>  
> 发件人: 🔓Dan Wing [mailto:dwing@cisco.com] 
> 发送时间: 2015年10月24日 23:54
> 收件人: ChenGuohai
> 抄送: Chenguohai; pcp@ietf.org
> 主题: Re: [pcp] A question: How can an internal client get the external IP and port of the inner NAT
>  
> 
> On 23-Oct-2015 06:04 pm, ChenGuohai <chenguohai67@outlook.com <mailto:chenguohai67@outlook.com>> wrote:
> Hi Dan,
>  
> Many thanks for your explaination.
>  
> Inner NATs are mostly used in residents and external NATs are CGNs is the most common nested NAT case.
>  
> Using PCP means that the CPE(inner NAT) must embed a PCP server.  The PCP client should communicats with two PCP servers.
>  
> Right.
>  
> 
> 
> Using STUN means a STUN server need to be deployed between inner NAT and external NAT. Shall this be common?
>  
> Not that I have seen.
>  
> -d
>  
> 
> 
>  
> Manual configuration is very cost.
>  
>  
> BR
> G.Robert  Chen
>  
> Subject: Re: [pcp] A question: How can an internal client get the external IP and port of the inner NAT
> From: dwing@cisco.com <mailto:dwing@cisco.com>
> Date: Fri, 23 Oct 2015 10:44:15 -0700
> CC: pcp@ietf.org <mailto:pcp@ietf.org>; chenguohai67@outlook.com <mailto:chenguohai67@outlook.com>
> To: chenguohai@huawei.com <mailto:chenguohai@huawei.com>
> 
> On 22-Oct-2015 08:24 pm, Chenguohai <chenguohai@huawei.com <mailto: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 <mailto:pcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/pcp <https://www.ietf.org/mailman/listinfo/pcp>
>  
>  
>  
>