|
At the beginning: Global v4 only service
|
| bet | 2/2 | | Sana | 14.05.2024 | | Hajmi | 1,58 Mb. | | #232408 |
Bog'liq plenaryw-2At the beginning: Global v4 only service - Nationwide / International Back bone (v4 only)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
Dual Stack backbone (it’s easy) - Nationwide / International Back bone (v4/v6)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
Introducing CGN - Nationwide / International Back bone (v4/v6)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
- One Private IPv4 address
- From New “Private” space
Introducing Softwire (v6 over v4 L2TP) - Nationwide / International Back bone (v4/v6)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
- One (new) Private
- IPv4 address
- SOFTWIRE Client
- (v6 over v4 L2TP)
- If softwire client has v6 routing
- function, delegated IPv6 is here
Softwire termination on CPE router looks tricky but in-expensive - Nationwide / International Back bone (v4/v6)
- CPE Router (v4 NAT /v6 softwire)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
- One Private IPv4 address
- From New “Private” space
- SOFTWIRE Client
- (v6 over v4 L2TP)
- Nationwide / International Back bone (v4/v6)
- Access Concentrator (v4/v6)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
- One Private IPv4 address
- From New “Private” space
- SOFTWIRE Client
- (v6 over v4 L2TP)
- If softwire client has v6 routing
- function, delegated IPv6 is here
Replace CPE router to IPv6 compatible - Nationwide / International Back bone (v4/v6)
- Access Concentrator (v4/v6)
- RFC1918 Based Private address
- (typically 192.168.0.0/24)
- IPv6 traffic is
- Bypassed CGN
Pure v6 world - Nationwide / International Back bone (v6)
- IPv6 address + Prefix delegation
We will do - Actually, NTT group already has commercialized walled garden IPv6 service for VoIP, IPTV and so on for 5+ millions of customers
- We are now constructing a beta testing ISP facility for complete dual stack with CGN environment in a data center in down town Tokyo
- Our new service with CGN is planned to start by year 2010 Spring
- We are really happy if we could help ISPs especially in Asia Pacific area (but not limited too) that will be facing same problems
Enterprises - We already have some requests from ASPs, usual enterprises, governmental organizations and schools for IPv6 deployment support especially for their out side system like web and E-mails first
- Eventually, their internal system will follow
These are important things to be considered - We think that we still need
- Simple security scheme for IPv6 should be nailed down
- draft-ietf-v6ops-cpe-simple-security-02
- New “private” address space allocation for carrier / provider access network behind CGN
- draft-shirasaki-shared-adrs-00.txt
- And some more…
- Also we need implementations
- IPv6 DNS deployment should be more popular
- MPLS support
- Firewall
- Load Balancer
|
| |
