Re: [pcp] section 8

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Tue, 18 October 2011 13:23 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.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 8B75621F8B1C for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 06:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.152
X-Spam-Level:
X-Spam-Status: No, score=-3.152 tagged_above=-999 required=5 tests=[AWL=-0.756, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 iuDB-+SBaVbM for <pcp@ietfa.amsl.com>; Tue, 18 Oct 2011 06:23:56 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 9A83F21F8B08 for <pcp@ietf.org>; Tue, 18 Oct 2011 06:23:55 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT9003UVJVSOL@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 18 Oct 2011 21:23:53 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LT9006S4JVSFI@szxga03-in.huawei.com> for pcp@ietf.org; Tue, 18 Oct 2011 21:23:52 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEN14071; Tue, 18 Oct 2011 21:23:52 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 18 Oct 2011 21:23:48 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.58]) by szxeml403-hub.china.huawei.com ([10.82.67.35]) with mapi id 14.01.0270.001; Tue, 18 Oct 2011 21:23:42 +0800
Date: Tue, 18 Oct 2011 13:23:41 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <A6A061BEE5DDC94A9692D9D81AF776DF0AAED8F6@szxeml527-mbs.china.huawei.com>
X-Originating-IP: [10.212.244.143]
To: "pcp@ietf.org" <pcp@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C1985E9@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="gb2312"
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] section 8
Thread-index: AQHMizBr13yvB88tzkaCmzhKkDKJiJV/zDkAgABdyQCAAfEzkA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: "14 Oct 2011 23:17:43 -0000." <C0E0A32284495243BDE0AC8A066631A80C19635B@szxeml526-mbx.china.huawei.com> <201110151147.p9FBljtN031911@givry.fdupont.fr> <A6A061BEE5DDC94A9692D9D81AF776DF0AAED7C8@szxeml527-mbs.china.huawei.com> <A6A061BEE5DDC94A9692D9D81AF776DF0AAED8F6@szxeml527-mbs.china.huawei.com>
Subject: Re: [pcp] section 8
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: Tue, 18 Oct 2011 13:23:56 -0000

Francis,
Reply inline:
________________________________________
发件人: pcp-bounces@ietf.org [pcp-bounces@ietf.org] 代表 Francis Dupont [Francis.Dupont@fdupont.fr]
发送时间: 2011年10月15日 19:47
到: Tina TSOU
Cc: pcp@ietf.org
主题: Re: [pcp] section 8

 In your previous mail you wrote:

   Hi,
   In section 8, it reads:
     "It is REQUIRED that the PCP-controlled device assign the same
      external IP address to PCP-created explicit dynamic mappings and to
      implicit dynamic mappings for a given Internal Host.  In the absence
      of a PCP option indicating otherwise, it is REQUIRED that PCP-created
      explicit dynamic mappings be assigned the same external IP address."
   It is not consistent with what we have discussed in the mailing list below. And i
  t is a bit ambiguous in reading.

   How about changing the second sentence from on of the 4 candidates as below?

   Alternative 1:
   PCP client should request same external IP address for an application if there is
   already any existing explicit mapping for that application.

=> the section 8 rule is per subscriber+host so the alternative should be too.
[TT] Do you mean that section 8 has defined the same external IP address per subscriber+host, and we don't need to propose the alternative texts? 
If so, could you please point out the texts for me? Thanks.

   Alternative 2:
   PCP client should request the same external IP address if there are existing expl
  ict mappings, unless there is explicit reasons of not doing so, e.g. http://tools.
  ietf.org/html/draft-penno-pcp-zones-00

=> same issue

   Alternative 3:
   It is indicated by the PCP client that PCP-created explicit dynamic mappings be a
  ssigned the same external IP address, unless there are explicit reasons of not doi
  ng so, e.g. http://tools.ietf.org/html/draft-penno-pcp-zones-00"

=> same issue

   Alternative 4:
   It is indicated by the PCP client that PCP-created explicit dynamic mappings be a
  ssigned the same external IP address, unless a PCP option indicates different exte
  rnal IP address

=> same issue

I can't see the problem, the text says all mappings (even there is nothing
about static mappings, is there a problem to add them?) get the same external
IP address if there is no option indicating otherwise.

[TT] From the current texts, it is easily understood that the address is allocated by PCP server.
However,  the same external IP address for one application is required by the PCP client.



BTW IWFs work far better if the affinity is per subscriber.

IMHO the best should be to make the affinity larger, i.e., per subscriber
and for all mappings, but at a lower level, i.e., with a RECOMMEND/SHOULD
in place of the current REQUIRE/MUST.

[TT] Agree.

Regards

Francis.Dupont@fdupont.fr
_______________________________________________
pcp mailing list
pcp@ietf.org
https://www.ietf.org/mailman/listinfo/pcp