Re: [pcp] pcp-base-19

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Fri, 23 December 2011 08:51 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 A104B21F8B39 for <pcp@ietfa.amsl.com>; Fri, 23 Dec 2011 00:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.943
X-Spam-Level:
X-Spam-Status: No, score=-6.943 tagged_above=-999 required=5 tests=[AWL=-0.344, BAYES_00=-2.599, 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 zTGz4+Ae1L-w for <pcp@ietfa.amsl.com>; Fri, 23 Dec 2011 00:51:50 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 9485321F8B37 for <pcp@ietf.org>; Fri, 23 Dec 2011 00:51:48 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWN0088IFA4JH@szxga04-in.huawei.com> for pcp@ietf.org; Fri, 23 Dec 2011 16:51:40 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWN00C8KFA4EY@szxga04-in.huawei.com> for pcp@ietf.org; Fri, 23 Dec 2011 16:51:40 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFX13987; Fri, 23 Dec 2011 16:51:40 +0800
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 23 Dec 2011 16:51:38 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.37]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Fri, 23 Dec 2011 16:51:31 +0800
Date: Fri, 23 Dec 2011 08:51:30 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <022201ccc03c$0a4226e0$1ec674a0$@com>
X-Originating-IP: [10.212.246.34]
To: Dan Wing <dwing@cisco.com>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C2377D8@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-US
Content-transfer-encoding: 7bit
Accept-Language: en-US, zh-CN
Thread-topic: [pcp] pcp-base-19
Thread-index: AQHMvshLlgQo2yg0SuKgPIbgmlIgJZXmCNUggACR36CAAEr20IAABvqqgAALjYCAAicg8A==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <C0E0A32284495243BDE0AC8A066631A80C233F2F@szxeml526-mbx.china.huawei.com> <020201ccc033$b75e08c0$261a1a40$@com> <9E33FE0C-91D4-4440-AD18-13819470EEFF@huawei.com> <022201ccc03c$0a4226e0$1ec674a0$@com>
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] pcp-base-19
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: Fri, 23 Dec 2011 08:51:51 -0000

Dan,
In line...

- Tina

-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com] 
Sent: Wednesday, December 21, 2011 3:56 PM
To: Tina TSOU
Cc: pcp@ietf.org
Subject: RE: [pcp] pcp-base-19

> -----Original Message-----
> From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
> Sent: Wednesday, December 21, 2011 3:06 PM
> To: Dan Wing
> Cc: pcp@ietf.org
> Subject: Re: [pcp] pcp-base-19
...
> 		2. P28, section 9
> 
> 
> 		"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 Address. In
> the absence
> 		of a PCP option indicating otherwise, it is REQUIRED that
> all
> 		PCP-created explicit dynamic mappings be assigned the same
> external
> 		IP address."
> 
> 
> 
> 		How about replace "In the absence of a PCP option
> indicating otherwise,
> 		it is REQUIRED that all PCP-created explicit dynamic
> mappings be
> 		assigned the same external IP address."
> 
> 		with
> 
> 		"It is indicated by the PCP client that PCP-created
> explicit dynamic
> 		mappings be assigned the same external IP address, unless
> there are
> 		explicit reasons of not doing so, e.g.
> 		http://tools.ietf.org/html/draft-penno-pcp-zones-00"?
> 
> 
> 		Because "It is REQUIRED that the PCP" give the requirement
> from the
> 
> 
> 		server's point of view, I think we should also give the
> requirement
> 
> 
> 		from the client's point of view.
> 
> 
> 		This is more or less what Dan suggested before, perhaps an
> oversight.
> 
> 
> 
> 	I don't understand the nuance between the wording.  Can you give
> an
> 	example of what the existing text prohibits / breaks / disallows?
> 
> The existing text disallows client to request same external IP
> proactively.


The client can request the address it wants in the Suggested 
External Address field, which exists for both MAP and PEER.
[Tina: Excellent! So some descriptive text is needed here to describe these protocol operations before digging into the messages and fields.]

> You agreed my comments earlier before.

I recall a discussion on this previously, yes.  I don't recall any
definitive conclusion.  Here are pointers to the end of two
threads related to the previous discussion:

http://www.ietf.org/mail-archive/web/pcp/current/msg01632.html
http://www.ietf.org/mail-archive/web/pcp/current/msg01627.html


If there was a definitive conclusion previously please provide 
a pointer and accept my apologies for my oversight.

[Tina:
http://www.ietf.org/mail-archive/web/pcp/current/msg01391.html
You said in Date: Tue, 7 Jun 2011 11:26:39 -0700
"I think see what you're wanting the document to say.  

How about this proposed text, instead:


  If there is already an active explicit dynamic mapping,
  it will be mapped to a certain external IP address.
  When the PCP client makes another explicit dynamic mapping,
  it SHOULD place the external IP address of the existing
  mapping into the Requested External Address of the MAP 
  request.  By doing this, all of the PCP client's explicit
  dynamic mappings will be on the same external address.


Does that say the same thing?

Is it acceptable?

-d"

I answer now "Yes, it is." Sorry for the very laaate answer from summer till X'mas. Merry X'mas!
]

-d

-d