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

GangChen <phdgang@gmail.com> Thu, 11 April 2013 07:54 UTC

Return-Path: <phdgang@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D84D21F8ECA for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2013 00:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 FMXPtywCHYp2 for <opsawg@ietfa.amsl.com>; Thu, 11 Apr 2013 00:54:48 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5697721F8EC9 for <opsawg@ietf.org>; Thu, 11 Apr 2013 00:54:48 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id k19so587685qcs.27 for <opsawg@ietf.org>; Thu, 11 Apr 2013 00:54:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=01PwSUPc+Fdfuq9RXOuvWZyuumTHE36thzsh9117SKM=; b=L4rRYdw0ZDe4Vjbq+eHdvWCM4QVeZylnL2w6koc+OUhwewgJs3VBCNwxVUjfZnX/b7 Ncw1chY6bPevPVZn2+X2q80n7DhWUq8sCJCaUqMBZ5rzkkYl0wCWv9uQpi0w+qMIErjC FeLAfznED4uX63BwICas0Off2VhBQ1ju0mp/7hIIkpTi3ZWooBEW5JwLMpkYgyicrRAq YBbbZqitgX/TUMaaNG5XM3uhW/Y26BT8iTov3mpzFUfAz+ZRm862GyFgvaN5XCtqZUS9 Hdm+oCbt/eXLkeztLk3HhmJbNirExrY6h/sQ7SYrDgw0Tv/twpOgtEcrn1mROjGem68m Gk9w==
MIME-Version: 1.0
X-Received: by 10.224.181.200 with SMTP id bz8mr6017589qab.68.1365666881012; Thu, 11 Apr 2013 00:54:41 -0700 (PDT)
Received: by 10.49.5.129 with HTTP; Thu, 11 Apr 2013 00:54:40 -0700 (PDT)
In-Reply-To: <5166523A.8000107@nttv6.jp>
References: <20130328141225.16450.37444.idtracker@ietfa.amsl.com> <515A8B2E.9060706@nttv6.jp> <CAM+vMEQArg1vNk+6ZF8THbT4WOno1-h3KNiDVA8VAUVjXRHGNA@mail.gmail.com> <5166523A.8000107@nttv6.jp>
Date: Thu, 11 Apr 2013 15:54:40 +0800
Message-ID: <CAM+vMEQwaA0rVc_vFYr4CJ9nSNK3yKbxbxq3WNJnGtbEK_Zwsg@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: kaname nishizuka <kaname@nttv6.jp>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Fwd: New Version Notification for draft-nishizuka-cgn-deployment-considerations-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 07:54:49 -0000

Kaname-san,

2013/4/11, kaname nishizuka <kaname@nttv6.jp>:
> Thank you for your comments.
>
> (2013/04/11 12:49), GangChen wrote:
>> Hello authors,
>>
>> Thanks for sharing your tests.
>> Some comments are below.
>>
>> Section 5.2 provides two formulas to estimate the address multiplexing.
>> If the formula of static assigment is intended to align with
>> I-D.donley-behave-deterministic-cgn, it may be amended by adding
>> active subscriber's coefficient. CGN may only assign static port block
>> to active users.Meanwhile, log just needs to add one record for each
>> user.
> It is dynamic assignment of port block.

That is correct. In some senses, a bulk of port is *statically*
reserved to a particular user. It's worth to be noted several
implementations are doing deterministic NAT behavior just following
those rules.

> We are describing the static assignment case.
> In that case, the same active subscriber's coefficient can not be used.
>
> There are potential users who have been assigned an internal IP address
> (and thus external address and port range) but are not generating any
> packet.
> In the dynamic assignment of port block, they don't consume external
> ports so they are not active subscribers.
> On the other hand, in the static assignment, they are reserving the
> external address and port range resources.
> If there is a mapping rule, that is the static assignment.
>
>> Section 6.1 states the MCS is highly dependent with retention time of
>> NAT table. It would be intereted to add some discussions if CGN could
>> interact with PCP.
>>
>> BTW, the table shown CGN sets retention time for DNS. would you do DNS
>> filter on CGN to identify DNS package?  I saw you also described DNS
>> bypass CGN. Are those related?
> Thanks for your suggestion.
> Yes, those are related.
> The point is that DNS query almost does not affect the performance of
> the CGN because
> retention time for DNS is sufficiently short (3 sec.).
> I think we need not to bypass DNS queries.

When I read the section at first time, I thought bypass DNS queries is
recommended since there is additional load(e.g. translation and logs)
to CGN. I guess the statement may be more clear if you could add
discussions what is the loss of bypass DNS queires.

Best Regards

Gang


> regards,
> kaname
>
>> Many thanks
>>
>> Gang
>>
>> 2013/4/2, kaname nishizuka <kaname@nttv6.jp>:
>>> Dear all,
>>>
>>> As I mentioned before, 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.
>>> We mentioned Victor's draft "CGN Deployment with BGP/MPLS IP VPNs Draft"
>>> in
>>> introduction
>>> because part of our research shares the same motivations with it.
>>>
>>> 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.
>>> We've just finished writing.
>>>
>>> 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
>
>