[pcp] Comments on draft-tsou-pcp-natcoord-08
"Reinaldo Penno (repenno)" <repenno@cisco.com> Wed, 28 November 2012 13:47 UTC
Return-Path: <repenno@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 905FA21F857B for <pcp@ietfa.amsl.com>; Wed, 28 Nov 2012 05:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 yCN3cPiHGOTD for <pcp@ietfa.amsl.com>; Wed, 28 Nov 2012 05:47:39 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id C7D0221F8573 for <pcp@ietf.org>; Wed, 28 Nov 2012 05:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1609; q=dns/txt; s=iport; t=1354110459; x=1355320059; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=DC1JhAf1qAeCYBtYcz3DBPy2LSV7xE/tS5jQc+jrVis=; b=ShfAZSDHJtmnXiBLCxPPm3/jerHK25jXiNcrPmo3IWXbvbcwgj9QvlBm N1Z952OsETF3IFNLbVlIEmdR5HNaD0lLj+QlvCjlvgYSIs4MlRAsR/X0Z +Dg6oGHMu1CnSGiXrQI2EQvSqP8mKxRj164ZTmidKD173W4fJFeQpKJgY 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQLADQVtlCtJXG8/2dsb2JhbABFwBUWbAeCIAEEOlEBKhRCJwQbE4d0nS6hSYxUg0thA6ZFgnCBYz4
X-IronPort-AV: E=McAfee;i="5400,1158,6909"; a="147128075"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 28 Nov 2012 13:47:39 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id qASDldQ1018137 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <pcp@ietf.org>; Wed, 28 Nov 2012 13:47:39 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.66]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.001; Wed, 28 Nov 2012 07:47:39 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "pcp@ietf.org" <pcp@ietf.org>
Thread-Topic: Comments on draft-tsou-pcp-natcoord-08
Thread-Index: AQHNzW7tUdQudtqM2EefCyX9WZI71g==
Date: Wed, 28 Nov 2012 13:47:38 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604177EF0@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.148.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <02433E4E1B582249AC2E542E6D1489AC@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pcp] Comments on draft-tsou-pcp-natcoord-08
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: Wed, 28 Nov 2012 13:47:40 -0000
Hello Authors, I reviewed this draft and my general comments are below, mostly related to the motivation and proposed solution. The draft states the following: " 1. Application Scenario PCP can be used to control an upstream device to achieve the following goals: 1. A plain IP address (i.e., a non-shared) can be assigned to a given subscriber because it subscribed to a service which uses a protocol that don't embed a transport number or because the NAT is the only deployed platform to manage IP addresses. 2. An application (e.g., sensor) does not need to listen to a whole range of ports available on a given IP address. Only a limited set of ports are used to bind its running services. For such devices, the external port(s) and IP address can be delegated to that application and therefore avoid enforcing NAT in the network side for its associated flows. The NAT in the PCP- controlled device should be bypassed. 3. A device able to restrict its source ports can be delegated an external port restricted IP address. The PCP- controlled device should be instructed to by-pass the NAT when handling flows destined/issued to that device. " In both 2 and 3 NAT could be performed by PCP controlled device. There is no discussion of this aspect (maybe due to Lw4o6 drivers) but if the mechanism is to be generic, we need to define how it would work. As I think about it , it seems there are quite a few issues to be ironed out. Thanks, Reinaldo
- [pcp] Comments on draft-tsou-pcp-natcoord-08 Reinaldo Penno (repenno)
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Zhouqian (Cathy)
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Simon Perreault
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Reinaldo Penno (repenno)
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Qiong
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Reinaldo Penno (repenno)
- Re: [pcp] Comments on draft-tsou-pcp-natcoord-08 Qiong