Carrier-Grade-NAT (CGN) Deployment Considerations.
draft-nishizuka-cgn-deployment-considerations-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kaname Nishizuka , Daigo Natsume | ||
| Last updated | 2014-03-31 (Latest revision 2013-09-27) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides deployment considerations for Carrier-Grade- NAT (CGN). Due to emerging new web technologies such as Websocket, SPDY and HTTP2.0, the trend of the Internet traffic has been changing. The number of sessions of commonly-used applications were investigated to estimate the efficiency of IPv4 address sharing of CGN. Based on the result of the average number of sessions of subscribers, the verification of CGN was conducted in the large scale network experiment environment with one million emulated subscribers. It revealed that CGN can be used in more centralized location of a provider's network and it arose many considerations.
Authors
Kaname Nishizuka
Daigo Natsume
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)