220 likes | 362 Views
Introduction to CNGI-6IX. Tsinghua Univ./CERENET 2008-10-21. Outline. Background Topology Equipment Addressing and Routing Services Traffic Problems. 1. Background. CNGI-6IX China Next Generation Internet Exchange Center Started to provide service in the end of 2005 Location
E N D
Introduction to CNGI-6IX Tsinghua Univ./CERENET 2008-10-21
Outline • Background • Topology • Equipment • Addressing and Routing • Services • Traffic • Problems
1. Background • CNGI-6IX • China Next Generation Internet Exchange Center • Started to provide service in the end of 2005 • Location • Beijing (Tsinghua University) • Hong Kong (Mega-iAdvantage)
Participants • CNGI participants • CERNET2 (AS23910) • China Telecom (AS4134) • China Unicom (AS9800) • China Netcom (AS18344) • China Mobile (AS24311) • China Tailcom (AS24425)
Domestic peers • CERNET (AS4538) • NSFCNet (AS9406) • CJ-IPv6 (AS23912) • Google-China (AS24424) • …
External peers • TEIN2-North (AS24489) • APAN-JP (AS7660) • KREONet2 (AS17579) • HK-IX2 (AS4635) • CUHK (AS3661) • Google (AS15169) • Cable & Wireless (AS1273) • Hurricane (AS6939) • …
3. Equipment • Beijing • 6 CNGI participants’ edge routers • 2 CNGI-6IX core routers • 2 CNGI-6IX core switches • Hong Kong • 1 CNGI-6IX core router
Equipments (Beijing) • CNGI participants’ edge router • CERNET2: Juniper T640 • China Telecom: Huawei NE80E • China Unicom: Juniper T320 • China Netcom: Juniper T640 • China Mobile: Huawei NE80E • China Tailcom: Huawei NE5000E
Equipments (Beijing) • CNGI-6IX core router • Cisco CRS-16 • Juniper T640 • CNGI-6IX core switch • Cisco 7609 • Force10 E600
Equipments (Hong Kong) • CNGI-6IX core router • Cisco GSR-12410
4. Addressing and Routing • IPv6 block • 2001:252::/32 • 2001:7fa:5::/48 (obsolete) • IPv4 block • 210.25.189.0/24 • Just for MPLS/L2VPN service provisioning
Policy • Principle of IPv6 peering policy • Open to receive all the IPv6 prefixes from CNGI participants and external peers • Conservative to advertise IPv6 prefixes based on agreed peering policy • No transit service for external peers • Community-based
Community List • CNGI participant • CERNET2: 23911:23910 • China Telecom: 23911:4134 • China Unicom: 23911:9800 • China Netcom: 23911:18344 • China Mobile: 23911:24311 • China Tailcom: 23911:24425
Community List • Domestic peer • CERNET: 23911:4538 • NSFCNet: 23911:9406 • CJ-IPv6: 23911:23912 • Google-China: 23911:24424
Community List • External peers • TEIN2-North: 23911:24489 • APAN-JP: 23911:7660 • KREONet2: 23911:17579 • HK-IX2: 23911:4635 • CUHK: 23911:3661 • Google: 23911:15169 • Cable & Wireless: 23911:1273 • Hurricane: 23911:6939
5. Service • Primary service • IPv6 exchange center • CNGI participants • Domestic peers • R&E • Commercial • External peers • R&E • Commercial • Advanced service • IPv6 Multicast • MPLS/L2VPN (IPv4-based)
6. Traffic • Total traffic of CNGI participants and domestic peers (since Jan 1, 2008)
Traffic • Total traffic of CNGI external peers (since Jan 1, 2008)
7. Problems • IPv6 flow analysis (netflow v9) • Some equipments can’t support netflow-based IPv6 flow data collecting/exporting • IPv6 prefix length filtering • Quite a number of organizations have applied small IPv6 block (/36-/48), which should not be globally routable according to certain historical document. • Should we accept such IPv6 prefixes from external peers? • IPv6 R&E routes vs. IPv6 commercial routes • How to distinguish IPv6 R&E routes from IPv6 commercial routes?