Re: [BEHAVE] New Version Notification for draft-nishizuka-cgn-deployment-considerations-00.txt

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Tue, 02 April 2013 16:26 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67F621F8D90 for <behave@ietfa.amsl.com>; Tue, 2 Apr 2013 09:26:24 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUdugRV9lyp4 for <behave@ietfa.amsl.com>; Tue, 2 Apr 2013 09:26:24 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id BC91221F8D8D for <behave@ietf.org>; Tue, 2 Apr 2013 09:26:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5371; q=dns/txt; s=iport; t=1364919983; x=1366129583; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uWgHH0jQpiKKD8bbneKEgqZNJ/d+Q0vfDSbzszIBJSI=; b=XMFFNgHXyzTYJ9HuuJ7fO3rg6UbwyDdg3+/s35xjLdxiIcA71X+OKEBg ZBL48cMqh2WWWlfjPZZjhod3ixM/q19cuhAlEBGV5cVZw6z+iudpqJTdP SUU4Z3LWYjmnxIMmuvzbN85ITlN8otstKf89K3uCLEY+csiM7E47+WdlB E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAIYFW1GtJV2d/2dsb2JhbABDgwc2vz+BBRZ0gh8BAQEDAQEBATctBwkCBQcEAgEIEQECAQEBAQoUCQcnCxQDBggCBAENBQgBiAUGDLFfkBiOaCYLBwaCWWEDmAqPbIFVgTaCKA
X-IronPort-AV: E=Sophos;i="4.87,394,1363132800"; d="scan'208";a="194160148"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 02 Apr 2013 16:26:20 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r32GQJai025206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Apr 2013 16:26:19 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.244]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Tue, 2 Apr 2013 11:26:19 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, kaname nishizuka <kaname@nttv6.jp>
Thread-Topic: [BEHAVE] New Version Notification for draft-nishizuka-cgn-deployment-considerations-00.txt
Thread-Index: AQHOL7w/MAwMiGZq3EC7nspjQ3pgwJjDHAQg
Date: Tue, 02 Apr 2013 16:26:18 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B115C8F7C@xmb-rcd-x06.cisco.com>
References: <20130328141225.16450.37444.idtracker@ietfa.amsl.com> <515A8B2E.9060706@nttv6.jp> <515A98BA.9030409@nttv6.jp> <DAF649E9-03F4-410A-A5E0-3ECC8689F08F@cisco.com>
In-Reply-To: <DAF649E9-03F4-410A-A5E0-3ECC8689F08F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.38.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Shin Miyakawa <miyakawa@nttv6.jp>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] New Version Notification for draft-nishizuka-cgn-deployment-considerations-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 16:26:25 -0000

This document would benefit from including the throughput/capacity discussion a bit along the following lines:

- challenges in spreading the traffic load (100G, say) among the available NAT capacity (distributed intra-chassis or inter-chassis). For ex, NAT entry is created by the upstream traffic, which is negligible to the downstream traffic that can exhaust the NAT capacity.
	For ex, poor usage of NAT capacity by fragmenting the IP pool (both inside and outside)

More inline,

> I like the description of DNS location at http://tools.ietf.org/html/draft-
> nishizuka-cgn-deployment-considerations-00#section-6.3, as this is an
> important mechanism to reduce the transactional load on the CGN.  Have

It is certainly desirable trait to let the DNS server not exhaust the CGN capacity. However, such a trait is not attainable when the number of users is too high to avoid overlapping (of private address space). This ends up moving DNS behind the CGN. :(

Cheers,
Rajiv


> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing (dwing)
> Sent: Tuesday, April 02, 2013 12:08 PM
> To: kaname nishizuka
> Cc: Shin Miyakawa; behave@ietf.org
> Subject: Re: [BEHAVE] New Version Notification for draft-nishizuka-cgn-
> deployment-considerations-00.txt
> 
> 
> On Apr 2, 2013, at 1:37 AM, kaname nishizuka <kaname@nttv6.jp> wrote:
> 
> 
> 	Dear all,
> 
> 	I'm kaname from NTT communications in Japan.
> 	We are testing CGN under the support of Japanese Government.
> 	Now, we've uploaded a new draft based on the result of our
> verification.
> 	The useful information about the average consumption of the ports
> are available on the document.
> 	Please look through it, and all kind of feedback are welcome.
> 
> Thanks for publishing this document.
> 
> I like the description of DNS location at http://tools.ietf.org/html/draft-
> nishizuka-cgn-deployment-considerations-00#section-6.3, as this is an
> important mechanism to reduce the transactional load on the CGN.  Have
> you analyzed the number of subscribers that over-ride the ISP-provided
> DNS servers to use other DNS servers (e.g., Google, OpenDNS), as that DNS
> query traffic will traverse the CGN.
> 
> http://tools.ietf.org/html/draft-nishizuka-cgn-deployment-considerations-
> 00#section-5.3.2 would benefit from some discussion of the privacy impact
> of an ISP storing destination information, and should also describe memory
> impact (in the CGN) if the subscriber uses the same source port to visit many
> different destinations (if CGN does not store the list of destinations, CGN
> will generate a log for every packet sent to a new destination).  Applications
> such as bittorrent can consume a lot of memory in a CGN that is configured
> for destination logging.
> 
> -d
> 
> 
> 
> 	By conducting realistic experiment, this draft is answering to "draft-
> ietf-behave-lsn-requirements-10" which will be the newest RFC very soon.
> 
> 	The document is *NOT* intended to be Standards Track. It's for
> Informational.
> 	The wrong description is just mere mistake, so we'll soon correct it
> in the next revision.
> 
> 	The full report of our work will be available soon on the Web in
> English.
> 	I'll also announce it when it's available to this mailing-list.
> 
> 	Best regards,
> 
> 	kaname
> 
> 
> 
> 
> 
> 		-------- Original Message --------
> Subject: 	New Version Notification for draft-nishizuka-cgn-
> deployment-considerations-00.txt
> Date: 	Thu, 28 Mar 2013 07:12:25 -0700
> From: 	internet-drafts@ietf.org
> To: 	kaname@nttv6.jp
> 
> 
> 		A new version of I-D, draft-nishizuka-cgn-deployment-
> considerations-00.txt
> 		has been successfully submitted by Kaname Nishizuka and
> posted to the
> 		IETF repository.
> 
> 		Filename:	 draft-nishizuka-cgn-deployment-
> considerations
> 		Revision:	 00
> 		Title:		 Carrier-Grade-NAT (CGN) Deployment
> Considerations.
> 		Creation date:	 2013-03-29
> 		Group:		 Individual Submission
> 		Number of pages: 16
> 		URL:             http://www.ietf.org/internet-drafts/draft-
> nishizuka-cgn-deployment-considerations-00.txt
> 		Status:          http://datatracker.ietf.org/doc/draft-nishizuka-
> cgn-deployment-considerations
> 		Htmlized:        http://tools.ietf.org/html/draft-nishizuka-cgn-
> deployment-considerations-00
> 
> 
> 		Abstract:
> 		   This document provides deployment considerations for
> Carrier-Grade-
> 		   NAT (CGN) based on the verification result include the
> investigation
> 		   of the number of sessions of applications.  The verification
> was
> 		   conducted in StarBED which is one of the largest scale
> network
> 		   experiment environment in Japan.  A million of subscribers
> was
> 		   emulated and it revealed the realistic behavior of CGN.
> 
> 
> 
> 
> 		The IETF Secretariat
> 
> 
> 
> 
> 
> 
> 	--
> 	----
> 	Kaname Nishizuka
> 	Innovative Architecture Center
> 	NTT Communications Corporation
> 	+81-50-3812-4704
> 	_______________________________________________
> 	Behave mailing list
> 	Behave@ietf.org
> 	https://www.ietf.org/mailman/listinfo/behave
> 
>