Re: [BEHAVE] Fwd: New Version Notification for draft-nishizuka-cgn-deployment-considerations-00.txt
kaname nishizuka <kaname@nttv6.jp> Wed, 15 May 2013 04:21 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 E919621F8B33 for <behave@ietfa.amsl.com>; Tue, 14 May 2013 21:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 g7vFylVY7nub for <behave@ietfa.amsl.com>; Tue, 14 May 2013 21:20:54 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:144::148]) by ietfa.amsl.com (Postfix) with ESMTP id 519B421F8B18 for <behave@ietf.org>; Tue, 14 May 2013 21:20:54 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [115.69.228.212]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 1F308BDC21; Wed, 15 May 2013 13:20:53 +0900 (JST)
Received: from [IPv6:2402:c800:ff06:0:14a9:c723:77c7:2791] (unknown [IPv6:2402:c800:ff06:0:14a9:c723:77c7:2791]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 233A1E0D9C; Wed, 15 May 2013 13:20:53 +0900 (JST)
Message-ID: <51930D20.2050809@nttv6.jp>
Date: Wed, 15 May 2013 13:20:48 +0900
From: kaname nishizuka <kaname@nttv6.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <B14A62A57AB87D45BB6DD7D9D2B78F0B1167BCA4@xmb-rcd-x06.cisco.com> <5190D29B.9070805@viagenie.ca>
In-Reply-To: <5190D29B.9070805@viagenie.ca>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "behave@ietf.org" <behave@ietf.org>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Subject: Re: [BEHAVE] Fwd: 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: Wed, 15 May 2013 04:21:03 -0000
Yes. Based on the port consumption trend, we figured out that the sharing ratio of dynamic assignment is 10 times of that of static assignment. However, I'm not intended to conclude that which is preferable in the draft. That depends on the provider's choice. I would carefully remove confusing representations. regards, kaname (2013/05/13 20:46), Simon Perreault wrote: > Le 2013-05-09 14:19, Rajiv Asati (rajiva) a écrit : >>> An ISP is running out of addresses. It considers two options: static >>> CGN >>> vs dynamic CGN. Static allows, let's say, 32 users per public IPv4 >>> address. Given the 1:10 figure from the draft, it follows that dynamic >>> allows 320 users per public IPv4 address. >> >> 1:32 (dynamic assignment) on top of 1:10 (static assignment)? Did you >> intend to nest? >> >> Could you please clarify? > > The draft says that the achievable address sharing ratio for dynamic > is 10x that of static. So if you have 1:32 for static (a made up > figure), it follows you would have 1:320 for dynamic. > > Simon > _______________________________________________ > 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
- [BEHAVE] Fwd: New Version Notification for draft-… kaname nishizuka
- Re: [BEHAVE] New Version Notification for draft-n… Dan Wing
- Re: [BEHAVE] New Version Notification for draft-n… Rajiv Asati (rajiva)
- Re: [BEHAVE] Fwd: New Version Notification for dr… Senthil Sivakumar (ssenthil)
- Re: [BEHAVE] New Version Notification for draft-n… Simon Perreault
- Re: [BEHAVE] Fwd: New Version Notification for dr… Simon Perreault
- Re: [BEHAVE] Fwd: New Version Notification for dr… Senthil Sivakumar (ssenthil)
- Re: [BEHAVE] Fwd: New Version Notification for dr… Simon Perreault
- Re: [BEHAVE] Fwd: New Version Notification for dr… Senthil Sivakumar (ssenthil)
- Re: [BEHAVE] Fwd: New Version Notification for dr… Howard, Lee
- Re: [BEHAVE] New Version Notification for draft-n… kaname nishizuka
- Re: [BEHAVE] New Version Notification for draft-n… Dan Wing
- Re: [BEHAVE] Fwd: New Version Notification for dr… kaname nishizuka
- Re: [BEHAVE] Fwd: New Version Notification for dr… Simon Perreault
- Re: [BEHAVE] New Version Notification for draft-n… Dan Wing
- Re: [BEHAVE] Fwd: New Version Notification for dr… Rajiv Asati (rajiva)
- Re: [BEHAVE] Fwd: New Version Notification for dr… Simon Perreault
- Re: [BEHAVE] Fwd: New Version Notification for dr… kaname nishizuka
- Re: [BEHAVE] Fwd: New Version Notification for dr… Rajiv Asati (rajiva)