Re: [pcp] What's the final conclusion?答复: [Technical Errata Reported] RFC6887 (3887)

Dan Wing <dwing@cisco.com> Thu, 13 February 2014 02:22 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 7940E1A00C9 for <pcp@ietfa.amsl.com>; Wed, 12 Feb 2014 18:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.76
X-Spam-Level:
X-Spam-Status: No, score=-8.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, 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 Q9c9JlZKKvv2 for <pcp@ietfa.amsl.com>; Wed, 12 Feb 2014 18:22:46 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id AC35C1A00CB for <pcp@ietf.org>; Wed, 12 Feb 2014 18:22:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3319; q=dns/txt; s=iport; t=1392258166; x=1393467766; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=27za/TbmOeOOom/RY+ZTVfQHInP490UBe+KfpG27TN0=; b=m5TuU02ryvuMugvAVo6SDfLjEAX5gbTeq1USnvVfD3ECfwndvYuMw9cG 6rKZZAaxvOgDPLJ35JUP1TyeFgVIjxCBKjEqCgEMw2XLubWYJVQA4ugT+ NVDvozgiWzI+7SAzRW8NjC9pZfz3T/5nLNxI6x0TkWDkqKaX63H1EOe81 k=;
X-IronPort-AV: E=Sophos;i="4.95,836,1384300800"; d="scan'208";a="102328145"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 13 Feb 2014 02:22:45 +0000
Received: from [10.85.165.242] ([10.85.165.242]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1D2MgXP025702; Thu, 13 Feb 2014 02:22:43 GMT
Content-Type: text/plain; charset="GB2312"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <1DA8CEC3F3E989439069663C05A865D334F97B15@nkgeml508-mbx.china.huawei.com>
Date: Wed, 12 Feb 2014 18:22:42 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <315A4314-038C-4304-BB90-8DC75FFFF9B3@cisco.com>
References: <20140212033032.D4F0A7FC395@rfc-editor.org> <B5316AA3-9CFD-4E25-822B-401F9DE36765@cisco.com> <F8F3C26A-FC50-486A-8EFF-DA2C08178524@nominum.com> <1DA8CEC3F3E989439069663C05A865D334F97AE6@nkgeml508-mbx.china.huawei.com> <B12D7908-1773-4DC9-8474-90532F328E21@cisco.com> <1DA8CEC3F3E989439069663C05A865D334F97B15@nkgeml508-mbx.china.huawei.com>
To: Zhangzhan <channy.zhang@huawei.com>
X-Mailer: Apple Mail (2.1510)
Cc: Stuart Cheshire <cheshire@apple.com>, Brian Haberman <brian@innovationslab.net>, PCP Working Group <pcp@ietf.org>
Subject: Re: [pcp] What's the final conclusion?答复: [Technical Errata Reported] RFC6887 (3887)
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: <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: Thu, 13 Feb 2014 02:22:49 -0000

On Feb 12, 2014, at 5:29 PM, Zhangzhan (Channy) <channy.zhang@huawei.com> wrote:

> Maybe you misunderstand me.
> There is only one router for NAT and PCP.
> If the NAT gateway device (such as CGN) is PCP Server and has two or more out interfaces to internet were doing different nat conversion in the ISP. 
> Maybe using NAT address pool A, B, C... And the routing entries to internet on NAT gateway is equivalent default route. In this case, the out interface is uncertain, fully in accordance with the equivalent route selection.
> If no PCP, service traffic can be selected out interface according to the destination address and do different NAT conversion.
> But the PCP message is in before the normal service traffic. And PCP MAP mode message does not include the destination address, the NAT gateway device how to choose the out interfaces and the different NAT address pools? 
> Based on the current PCP protocol, I think that can't be solved. Or what I understand something wrong?

With such a network topology, you are correct that the current MAP opcode doesn't work.  We need something different.  Would http://tools.ietf.org/html/draft-penno-pcp-zones be a viable solution?

-d


> 
> -----邮件原件-----
> 发件人: Dan Wing [mailto:dwing@cisco.com] 
> 发送时间: 2014年2月13日 9:02
> 收件人: Zhangzhan (Channy)
> 抄送: Ted Lemon; PCP Working Group; Stuart Cheshire; mohamed.boucadair@orange.com Boucadair; Reinaldo Penno; pselkirk@isc.org; Brian Haberman; Dave Thaler
> 主题: Re: What's the final conclusion?答复: [Technical Errata Reported] RFC6887 (3887)
> 
> 
> On Feb 12, 2014, at 4:49 PM, "Zhangzhan (Channy)" <channy.zhang@huawei.com> wrote:
> 
>> "Indeed, it has been discussed."
>> 
>> What's the final conclusion to the discussion? 
>> 
>> How PCP applies in the Dual-Egress NAT scene?
>> 
>> Could you please share it? 
> 
> I removed the RFC Editor from the thread.
> 
> PCP client needs to communicate to both of the NATs independently.  Which the same host (the PCP client) needs to know how to do anyway to send its TCP SYN to one ISP or the other ISP -- to send its TCP SYNs to different networks, the host must have routing entries.  The PCP client can use those same routing entries to know there are two routers on the network, and send PCP messages to those two routers separately.
> 
> -d
> 
> 
>> 
>> -----邮件原件-----
>> 发件人: Ted Lemon [mailto:ted.lemon@nominum.com] 
>> 发送时间: 2014年2月13日 0:13
>> 收件人: Dan Wing
>> 抄送: RFC Errata System; Zhangzhan (Channy); Stuart Cheshire; mohamed.boucadair@orange.com Boucadair; Reinaldo Penno; pselkirk@isc.org; Brian Haberman; Dave Thaler; PCP Working Group
>> 主题: Re: [Technical Errata Reported] RFC6887 (3887)
>> 
>> On Feb 12, 2014, at 10:15 AM, Dan Wing <dwing@cisco.com> wrote:
>>> It seems appropriate to discuss this question on the PCP mailing list, pcp@ietf.org.
>> 
>> Indeed, it has been discussed.   This isn't really an appropriate topic for an erratum.
>> 
>