|
PowerPoint Presentation Transition to ipv6 why and how
|
bet | 1/2 | Sana | 14.05.2024 | Hajmi | 1,58 Mb. | | #232408 |
Bog'liq plenaryw-2 - Shin Miyakawa , Ph.D.
- NTT Communications Corporation
- miyakawa@nttv6.jp
- You can find the extended version of this presentation at
- http://www.nttv6.jp/~miyakawa/IETF72/
Most conservative access model changes - introducing “Carrier-Grade NAT” - - Access
- Concentrator
- With NAT
- One Private IPv4 address from new “Private” space
It looks v6 is not needed ? - Please do not feel safe. CGN (and any other carrier-grade NAT scheme) has serious restrictions.
- IPv6 is needed !
- Each customer can have only some “limited” numbers of sessions simultaneously.
- How many ? Let say… 50 ? 30 ? Because “port number” is just 2bytes which means 64K
- For example, if 2000 customer shares same Global IPv4 address (please note that this is just for example), only 25 or 30 so sessions can be used by each customer at the worst case.
- Which means that:
Max 20 Connections Max 15 Connections Max 10 Connections Max 5 Connections So, We DO NEED IPv6 Examples of # of concurrent sessions - According to our observations, about 500 sessions are average numbers of concurrent sessions per users.
- To be more realistic, only 8 users per 1 single global IPv4 address is a good ratio to use CGN
Carrier-Grade NAT - Scalability
- >10K users (or contracts)
- 100s of TCP sessions per user (or contract)
- Maximum Transparency is desired
- Like “ideal” SOHO Router, there should be no barrier for application
- So call “Full-CONE” + “Hairpinning” is ideal
- Different from NAT for Enterprise
- draft-nishitani-cgn-00.txt
- Will be presented at SOFTWIRE and BEHAVE WG.
- High Availability
Transition Scenario Simple concept - Customer can be converted one by one
- Customer do not need to purchase any hardware until some stage of conversion
- Especially he/she uses XP, Vista, Leopard, Linux or BSD
- IPv6 will be main stream eventually
- IPv4 will be for backward compatibility
|
| |