IETF Logo Mail Archive

Re: [BEHAVE] Home NAPT44 - How many ports?

kaname nishizuka <kaname@nttv6.jp> Wed, 05 June 2013 18:16 UTC

Return-Path: <kaname@nttv6.jp>
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 133B621F9B3F; Wed, 5 Jun 2013 11:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.11
X-Spam-Level: *
X-Spam-Status: No, score=1.11 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_33=0.6, J_CHICKENPOX_83=0.6]
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 DZvU-ToUZH5O; Wed, 5 Jun 2013 11:16:17 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.148]) by ietfa.amsl.com (Postfix) with ESMTP id BAE5221F9B09; Wed, 5 Jun 2013 11:16:17 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:208::212]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 3F00FBDC21; Thu, 6 Jun 2013 03:15:59 +0900 (JST)
Received: from [IPv6:::1] (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id C1D9DE1E27; Thu, 6 Jun 2013 03:15:58 +0900 (JST)
Message-ID: <51AF805D.4000101@nttv6.jp>
Date: Thu, 06 Jun 2013 03:15:57 +0900
From: kaname nishizuka <kaname@nttv6.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090A0A82@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F0604090A0A82@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "behave@ietf.org" <behave@ietf.org>, "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>, "Softwires-wg list (softwires@ietf.org)" <softwires@ietf.org>, "Erik Kline (ek@google.com)" <ek@google.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Subject: Re: [BEHAVE] Home NAPT44 - How many ports?
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: Wed, 05 Jun 2013 18:16:22 -0000

With regard to the DNS packets, shortening the time-out of NAT table is 
another good solution.

In larger environment, we tested that when the time-out of DNS was 
shortened to 3sec, the impact of such DNS requests was much smaller than 
TCP sessions.
3 sec is sufficient  round-trip time in general situation.
I don't think it's necessary to place a recursive DNS server inside the CGN.

Though there are differences between Home NAPT44 and CGN, it will work 
well in both case.
That is because there are many devices in home and those seldom access 
the web site within a short time simultaneously.

regards,
--
kaname

(2013/06/06 1:27), Reinaldo Penno (repenno) wrote:
>
> On 6/5/13 1:23 PM, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:
>
>>>>>>> "repenno" == repenno  <Reinaldo> writes:
>>     repenno> On the other hand, as Rajiv captured,the number of
>>     repenno> UDP sessions can be much larger than the number of
>>     repenno> TCP. Because the way
>>     repenno> dynamic webpages are constructed today, there are sometimes
>>     repenno> literally 100s
>>     repenno> of DNS requests to download a single page.
>>
>> If one is doing CGN, wouldn't it be reasonable to point customers' at
>> a recursive DNS server with an interface inside the CGN?
> Yes. That's what I suggest. But some people use, say, Google's
> DNS/OpenDns/etc and in some other cases the network is not setup correctly.
>
>> This seems to also suggest that having a *caching* recursive DNS(SEC,
>> HOMENET+, mDNS+) server inside the customer router is also a big win.
> Yes, it is.
>
>> -- 
>> ]               Never tell me the odds!                 | ipv6 mesh
>> networks [
>> ]   Michael Richardson, Sandelman Software Works        | network
>> architect  [
>> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails
>>    [
>> 	
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


-- 
----
Kaname Nishizuka
Innovative Architecture Center
NTT Communications Corporation
+81-50-3812-4704

v2.23.0 | Report a Bug | By Email