IPv6 Routing Considerations Masaru Mukai / POWERDCOM Kuniaki Kondo / IIJ.

Slides:



Advertisements
Similar presentations
Multihoming and Multi-path Routing
Advertisements

Multihoming and Multi-path Routing
Economics of stub network multihoming and link load balancing INTERIM RESULTS AND NEXT STEPS Henna Warma Aalto University - COMNET December, 7 th 2011.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Policy Meeting Address Policy (Procedures) SIG 1 March 2001.
Routing Basics.
Multihoming in IPV6 Habib Naderi Department of Computer Science University of Auckland.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Introduction to IPv4 Introduction to Networks.
Chapter 19 Network Layer: Logical Addressing Stephen Kim.
The need for BGP AfNOG Workshops Philip Smith. “Keeping Local Traffic Local”
Best Practices for ISPs
CSE5803 Advanced Internet Protocols and Applications (7) Introduction The IP addressing scheme discussed in Chapter 2 are classful and can be summarised.
Kae Hsu Communication Network Dept. Redundant Internet service provision - customer viewpoint.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Considering the Advantages of Using BGP.
MPLS L3 and L2 VPNs Virtual Private Network –Connect sites of a customer over a public infrastructure Requires: –Isolation of traffic Terminology –PE,
TDC365 Spring 2001John Kristoff - DePaul University1 Interconnection Technologies Routing I.
Border Gateway Protocol (BGP4) Rizwan Rehman, CCS, DU.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—7-1 Integrating Internet Access with MPLS VPNs Implementing Internet Access as a Separate VPN.
© 2009 Cisco Systems, Inc. All rights reserved.ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Planning the Enterprise-to-ISP Connection.
IAB/IESG Recommendations on IPv6 Address Allocation Bob Hinden at RIPE Sept Brian Carpenter at ARIN Oct Alain Durand at APNIC Oct
1 Chapter Overview Subnet. What is a subnet When you break a network into a few smaller networks, you have created several subnets Like IP address where.
IAB/IESG Recommendations on IPv6 Address Allocation Bob Hinden at RIPE Sept Brian Carpenter at ARIN Oct Alain Durand at APNIC Oct
1 The Geography and Governance of Internet Addresses Paul Wilson APNIC.
IP Addressing. Dotted Decimal Notation IP addresses are written in a so-called dotted decimal notation Each byte is identified by a decimal number in.
4: Addressing Working At A Small-to-Medium Business or ISP.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Planning the Addressing Structure Working at a Small-to-Medium Business or ISP – Chapter.
BGP Best Current Practices
Proposal of “Time-Limited” IPv4 Address Allocation Policy Project leader : Jun Murai Project officiers: –Hiroshi Esaki –Akira Kato –Osamu Nakamura –Masaki.
CRIO: Scaling IP Routing with the Core Router-Integrated Overlay Xinyang (Joy) Zhang Paul Francis Jia Wang Kaoru Yoshida.
IP Addressing Introductory material. An entire module devoted to IP addresses.
1 Chapter 27 Internetwork Routing (Static and automatic routing; route propagation; BGP, RIP, OSPF; multicast routing)
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Internet Registry allocation and assignment Policies.
Desired IRR Operational Model ~IRR/Whois Interaction~ Kuniaki Kondo (JPNIC IRR Workshop/IIJ) Ikuo Nakagawa (Intec) Takashi Arano (Asia Global Crossing)
Introduction to The Internet ISP Workshops 1 Last updated 24 April 2013.
David Wetherall Professor of Computer Science & Engineering Introduction to Computer Networks Hierarchical Routing (§5.2.6)
Address planning. Introduction Network-Level Design Considerations Factors affecting addressing scheme Recommended practices Case studies 6/4/20162.
The necessity of 4-over-6 stateless address sharing mechanism Satoru Matsushima Jie Jiao Chunfa Sun 0.
Routing integrity in a world of Bandwidth on Demand Dave Wilson DW238-RIPE
JPNIC Open Policy Meeting Update Yuka Suzuki IP Department Japan Network Information Center (JPNIC) NIR Meeting Aug. 21st, 2003.
LISP Deployment Scenarios Darrel Lewis and Margaret Wasserman IETF 76, Hiroshima, Japan.
Guidance for Running Multiple IPv6 Prefixes (draft-liu-v6ops-running-multiple-prefixes-02) Bing Liu, Sheng Jiang (Speaker), Yang Bo IETF91
Network Architecture Protection (draft-vandevelde-v6ops-nap-01.txt) Brian Carpenter, Ralph Droms, Tony Hain, Eric L Klein, Gunter Van de Velde.
An Update on Multihoming in IPv6 Report on IETF Activity RIPE IPv6 Working Group 22 Sept 2004 RIPE 49 Geoff Huston, APNIC.
IPv6 Operation Study Group in Japan March 5, 2002 Akihiro Inomata/Fujitsu Limited Chair of IPv6 Operation Study Group.
Guidance of Using Unique Local Addresses draft-liu-v6ops-ula-usage-analysis-05 draft-liu-v6ops-ula-usage-analysis-05 Bing Liu(speaker), Sheng Jiang, Cameron.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—6-1 Scaling Service Provider Networks Scaling IGP and BGP in Service Provider Networks.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Understanding Customer-to-Provider Connectivity.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—1-1 Course Introduction.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—3-1 Route Selection Using Policy Controls Using Multihomed BGP Networks.
17/10/031 Euronetlab – Implementation of Teredo
IETF #58 in Minneapolis1 IPv6 Address Assignment and Route Selection for End-to-End Multihoming Kenji Ohira Kyoto University draft-ohira-assign-select-e2e-multihome-02.txt.
Expectation for IPv6 Dec.19th, 2000 Noriyuki Kishikawsa NEC Corporation.
6to4
Internet Traffic Engineering Motivation: –The Fish problem, congested links. –Two properties of IP routing Destination based Local optimization TE: optimizing.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Connecting a Multihomed Customer to Multiple Service.
CCNA4-1 Chapter 7-1 IP Addressing Services Scaling Networks With Network Address Translation (NAT)
CCNA4-1 Chapter 7-1 NAT Chapter 11 Routing and Switching (CCNA2)
1 Requirements of Carrier Grade NAT (CGN) draft-nishitani-cgn-00.txt draft-shirasaki-isp-shared-addr-00.txt NTT Communications Corporation Shin Miyakawa.
Deploying Dual-Stack Lite in IPv6 Network draft-boucadair-dslite-interco-v4v6-04 Mohamed Boucadair
1 APNIC Open Address Policy Meeting Special Interest Group Session March 2nd, Korea, Seoul.
Routing and Addressing in Next-Generation EnteRprises (RANGER)
BGP 1. BGP Overview 2. Multihoming 3. Configuring BGP.
Keeping local stuff local
Border Gateway Protocol
Planning the Addressing Structure
An IPv4 address is a 32-bit address that uniquely and universally defines the connection of a device (for example, a computer or a router) to the Internet.
IPv6-only in an Enterprise Network
BGP Overview BGP concepts and operation.
Consideration on IPv6 Address Management
An Update on Multihoming in IPv6 Report on IETF Activity
Planning the Addressing Structure
Presentation transcript:

IPv6 Routing Considerations Masaru Mukai / POWERDCOM Kuniaki Kondo / IIJ

APNIC SIG-IPv /03/05 Background This talk shows the result of “IPv6 Operation Study Group(IPv6-OPS)” discussion in Japan IPv6-OPS was held twice over night meeting and BoF in JANOG8 Meeting last year.  JANOG = Japan Network Operators’ Group IPv6-OPS has “Routing Sub-Group”.  This group focuses “ISP Backbone Routing Issues”.

APNIC SIG-IPv /03/05 IPv6-OPS Routing Sub-Group Motivation  Address architecture will change in IPv6. Address Length is 128 bit Address allocation scheme will change  We would like to know what is difference between IPv6 and IPv4. Goal  This group survey how IPv6 address architecture influences IPv6 routing?  If possible, this group hopes to make typical IPv6 network models.

APNIC SIG-IPv /03/05 Agenda Multi-homing EGP IGP

APNIC SIG-IPv /03/05 Multi-Homing Overview  There are some techniques to do multi- homing such as using BGP, using NAT, etc..  In IPv4, some ISPs use to connect inter-ISP or between ISP and customer for redundant.  Customer want to have redundant line and to do load-balancing same as IPv4 network, when IPv6 come.

APNIC SIG-IPv /03/05 IPv4 Multi-Homing One AS announces a part of address block which was allocated for other AS by registry. It makes to increase number of full routes.  One AS customer want to do multi-homing, but their network scale does not so large as getting AS number.  ISPs probably allow this configuration based on customer requires. To increase number of full routes makes some problems.  For example, if number of full routes increase continuously, then BGP convergence time also increase.

APNIC SIG-IPv /03/05 Category of Multi-Homing BGP based (A organization has AS number and PA address)  Anything will not change. Announcing PI address  Currently, Registries do not allocate IPv6 PI address. punching hole  The number of IPv6 punching holed routes are unknown. Multi prefix  Some prefixes are assigned by each upstreams.  Source address selection can be used This behavior is different each implementation. RFC3178 model  This is possible solution, but it needs more costs such as operation cost, line cost, etc.

APNIC SIG-IPv /03/05 RFC3178 Model ISP AISP B PA(A) + PA(B) RouterBRouterA PA(A) PA(B) PA(A)

APNIC SIG-IPv /03/05 Problems of RFC3178 Model Problems of using tunnel  To separate responsible area is difficult.  Responsible area can not separate clearly.  There is security problem why traffic might through unwilled ISPs.  There are no-method to limit bandwidth of tunnel lines. If this model does not use tunnel, then it needs more leased lines. It means that it needs more line costs.

APNIC SIG-IPv /03/05 punching hole ISP AISP B User X A The Internet P(A) B A B

APNIC SIG-IPv /03/05 Problems of punching hole Increasing number of routes  Increasing route convergence time  Needs more powerful routers  It makes more cost to provide ISP services

APNIC SIG-IPv /03/05 Multi prefix P(A) P(B) ISP AISP B P(A) P(B) AB host

APNIC SIG-IPv /03/05 Problems of Multi Prefix There are some implementations, but behavior is different each implementations.  Every host must be cared which prefix is better for sending packets. Every host must select source address. Both of backup and load-balance are defective in multi-prefix situation. A router which can do policy routing must be more generic.

APNIC SIG-IPv /03/05 Agenda Multihoming EGP IGP

APNIC SIG-IPv /03/05 EGP Overview  People needs a solution for IPv6 traffic control  Announced prefix will decrease. It makes that traffic will be concentrated to some of routers in ISP.

APNIC SIG-IPv /03/05 Problems of Traffic Control In IPv6 network, ISPs can not control traffic using separated prefixes.  If ISPs announce more specific routes, then number of full routes increase tremendously. In some cases, inter-AS traffic might concentrate specific border routers.

APNIC SIG-IPv /03/05 Traffic Control Solutions for IPv6 Upstream ISPs control traffic  prepend, community New Method  To use MPLS  To propose BGP-5 ISPs announce more specific routes.  Number of full routes increase tremendously.

APNIC SIG-IPv /03/05 Agenda Multi-Homing EGP IGP

APNIC SIG-IPv /03/05 IGP Our discussion summary  Networks might have more number of internal routes than number of external routes.  We would like to consider new network design for IPv6 which is considered aggregation of IP blocks.  If we design network same as IPv4, then IPv6 networks probably have more number of internal routes than IPv4 network. It depends on network design

APNIC SIG-IPv /03/05 Problems of IGP Aggregating prefixes is necessary for decreasing number of internal routes. One of possible way is that prefixes aggregate for each POPs.  Address blocks are assigned to POPs according to number of lines or forecast of number of customers.

APNIC SIG-IPv /03/05 Conclusion Much Much bigger address spaces  Potential number of external routes in future Multi-homing  No PI(Provider Independent) address for enterprises  Punching hole allowed? Any criteria? Aggregation  /48 static assignment per a customer needs special design consideration about aggregation in ISP internal networks.  How can address policy supports this? Traffic engineering  Less external routes to be announced make TE harder.

Acknowledgements

APNIC SIG-IPv /03/05 discussion member(1/2) Akihiro InomataFujitsuChair Masaru MukaiPowerdComCo-Chair Kuniaki KondoIIJ Tomohiko KurahashiIIJ Rie ShimadaPanasonic Toshihiro ArakiJapan Telecom Yasushi EndoJapan Telecom Tomohide NagashimaJapan Telecom Tsuyoshi TomochikaNTT Communications Hiroyuki TanahashiNTT Communications Yasuhiro ShirasakiNTT Communications Akira NagakawaPowerdCom Ryuuichi TakashimaPowerdCom Teruo WatanabePowerdCom Toshio TachibanaAni&Company

APNIC SIG-IPv /03/05 discussion member(2/2) Tomohiro FujisakiNTT Communications Takashi AranoAsia Global Crossing Kazuhiko NakaharaNEC/BIGLOBE Koichiro FujimotoNEC Corporation Hiroki IshiharaNEC Corporation Ikuo NakagawaIntec Web & Genome Informatics Tomohiko KusudaIntec Web & Genome Informatics Kenichi NagamiToshiba Masahito OmoteSapporo Medical University Masamichi Miyaji Sapporo Medical University Satoshi KobayasiNextec Shiro NiinobeNTT West Hirotaka AsaiNTT West Yoshiyuki EzuraIRI Akinori MaemuraEquant

Questions?