Re: [pcp] Fw:I-D Action: New Version Notification for draft-tsou-pcp-natcoord-08.txt
"Dan Wing" <dwing@cisco.com> Fri, 02 November 2012 02:07 UTC
Return-Path: <dwing@cisco.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 0137421F98CE for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 19:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.554
X-Spam-Level:
X-Spam-Status: No, score=-110.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A73F5CVhuLqX for <pcp@ietfa.amsl.com>; Thu, 1 Nov 2012 19:07:41 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id CABCB21F983D for <pcp@ietf.org>; Thu, 1 Nov 2012 19:07:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3741; q=dns/txt; s=iport; t=1351822061; x=1353031661; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=jQ1I7t9bupOlnwRxjNmcSF/WRkXQJPIhvBDCDpQ+I2g=; b=dP7A65G1WBH0yGNNLkyQheheUtFIql28rA1HabSA24QanhSNwtUnemkG pq0c6BYFQCuYtPkd4058LIB0UcBPlTPL50C0K7cRPudjirbPkBRtD0MTo viVvmfE/VLAbyHGrsQP3gHoQWPko4AYSkc5R4AEXba93OUvsO1+hpLg/b A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEIqk1CrRDoG/2dsb2JhbAA6CoYXvRmBCIIeAQEBAwEIAggBEFQCBQgDAgkaAiYCAhk+AgQeBRKHXgUMnHONKZJugSCKa4UYgRMDiFqFF4gHgRuNPYFrgw8
X-IronPort-AV: E=Sophos;i="4.80,696,1344211200"; d="scan'208";a="62850541"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 02 Nov 2012 02:07:32 +0000
Received: from DWINGWS01 ([10.32.240.194]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA227WpP017508; Fri, 2 Nov 2012 02:07:32 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Qiong' <bingxuere@gmail.com>
References: <CAH3bfAAn79BdM+F9G2WkJwvwxo08y89Fa3D6VKRX6cOZu98FYA@mail.gmail.com> <0c8701cdb792$8ee8c4a0$acba4de0$@cisco.com> <CAH3bfABZOjVZqHzZ7PTJfQ5WQT0wUnbZRtMCoJJfVsMw==U8bQ@mail.gmail.com> <01ac01cdb840$0ef753c0$2ce5fb40$@cisco.com> <CAH3bfAD_nreqZ5tEwMDmuY8NO9kOUet6nyiTQ7Ldsdivt150VQ@mail.gmail.com>
In-Reply-To: <CAH3bfAD_nreqZ5tEwMDmuY8NO9kOUet6nyiTQ7Ldsdivt150VQ@mail.gmail.com>
Date: Thu, 01 Nov 2012 19:07:32 -0700
Message-ID: <056301cdb89e$d1826660$74873320$@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNPFg3hnot8iaQn7dMg74vbEf4q5wHPoD1sAYkIPtMBOHUi3AF+2gWqlKKRraA=
Content-Language: en-us
Cc: pcp@ietf.org
Subject: Re: [pcp] Fw:I-D Action: New Version Notification for draft-tsou-pcp-natcoord-08.txt
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, 02 Nov 2012 02:07:42 -0000
> [Qiong] Right, we should make it clear. The PCP server should assign > individual port-set for each MAP_PORT_SET request, rather than an > aggregated one. Yes, that would be good to explain in the document. > This would simpilfy the implementation both for the pcp > server and pcp client, right? Yes, I think so. -d > Thanks for your comments! > > Best wishes > Qiong > > > > > Besides, since the pcp-controlled device can identify each client > with > > the internal address(IPv6 address), I think there will be no > confusion > > in PCP servers to assgin non-overlap port-set to clients. > > > > I will add it explicitly in draft as a requirement to PCP server. > Is it > > ok ? > > > -d > > > > > > > > > > > > > draft-tsou-pcp-natcoord-08 says: > > > > The Client MUST use a different Mapping Nonce for > > different MAP_PORT_SET requests. > > > > This is a MUST, which means there must be something that > breaks if > > it violates that requirement. What breaks? > > > > > > > > [Qiong] This is used when one pcp-natcoord client is allowed to > initiate > > multiple port-set requests in case it has used out all the ports > in one > > port-set. As a result, one pcp client may get multiple mapping > rules > > including the same Internal address, external address and > different > > port-sets. In this case, one mapping rule should have one > corresponding > > mapping nonce, and the server should also keep the Nonce value > for each > > port-set mapping. Otherwise, the pcp server can not get the > distinction > > between a port-set request retransimission when the request is > somehow > > lost and a new port-set request to get another port-set mapping, > since > > the suggested port-set might be zero in both cases and the > Internal > > address, protocol is the same. So when the client is going to > request a > > new port-set, a different Mapping Nonce should be used with the > previous > > port-set request. Does it make sense ? Hope it clarifies -:) > > > > Thanks again for your comments ! > > > > Best wishes > > Qiong > > > > > > > > > > -d > > > > > > > > > BTW, you can also find the opensource project in > sourceforge: > > > http://sourceforge.net/projects/pcpportsetdemo/ > > > > > > > > > Thanks a lot! > > > > > > Best wishes > > > > > > -- > > > ============================================== > > > Qiong Sun > > > China Telecom Beijing Research Institude > > > > > > > > > Open source code: > > > lightweight 4over6: > http://sourceforge.net/projects/laft6/ > > > PCP-natcoord: > http://sourceforge.net/projects/pcpportsetdemo/ > > > =============================================== > > > > > > > > > > > > > > > > > > > > > > -- > > ============================================== > > Qiong Sun > > China Telecom Beijing Research Institude > > > > > > Open source code: > > lightweight 4over6: http://sourceforge.net/projects/laft6/ > > PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/ > > =============================================== > > > > > > > > > > > > -- > ============================================== > Qiong Sun > China Telecom Beijing Research Institude > > > Open source code: > lightweight 4over6: http://sourceforge.net/projects/laft6/ > PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/ > =============================================== > >
- [pcp] Fw:I-D Action: New Version Notification for… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Simon Perreault
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Simon Perreault
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Dan Wing
- Re: [pcp] Fw:I-D Action: New Version Notification… Simon Perreault
- Re: [pcp] Fw:I-D Action: New Version Notification… Zhouqian (Cathy)
- Re: [pcp] Fw:I-D Action: New Version Notification… Qiong
- Re: [pcp] Fw:I-D Action: New Version Notification… Xiaohong Deng