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

[Dan Wing <[e-mail]>]

On Apr 3, 2013, at 6:57 PM, kaname nishizuka <[e-mail]> wrote:

> Thanks for your comment.
> 
>> 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.
> Unfortunately, we have not yet investigated the proportion of the subscribers who are using provided DNS versus who are using public DNS.
> Before investigating it, the test we managed to do was that all DNS traffic traverse the CGN as the most severe case.
> The proportion could be different in providers,  but the impact of the DNS query traffic is relatively small if DNS timeout is adjusted.

Yeah, and most of the DNS traffic is UDP (until we have larger records) so even if the UDP timers were pretty long I bet the user port limit wouldn't be exhausted.

>> 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.
>> 
> We also should care for port-overlapping behavior.

Yes, I believe it's the same thing using a different term.

-d

> kaname
> 
> (2013/04/03 1:07), Dan Wing wrote:
>> On Apr 2, 2013, at 1:37 AM, kaname nishizuka <[e-mail]> 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:	[e-mail]
>>>> To:	[e-mail]
>>>> 
>>>> 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
>>> [phone]
>>> _______________________________________________
>>> Behave mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/behave
>> 
> 
> 
> -- 
> ----
> Kaname Nishizuka
> Innovative Architecture Center
> NTT Communications Corporation
> [phone]
>