Simple Multihoming Experiment draft-huitema-multi6-experiment-00.txt Christian Huitema, Microsoft David Kessens, Nokia.

Slides:



Advertisements
Similar presentations
Multihoming and Multi-path Routing
Advertisements

Multihoming and Multi-path Routing
Host Centric Multi6 Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
Dual Homing Experiment Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
3G WLAN handover Gabor Bajko Nokia. Experiment Upstream-router DSMIP6-HA V6 V4 V6 Internet WiFi HSPA DSMIP6 Home Agent.
NAT, firewalls and IPv6 Christian Huitema Architect, Windows Networking Microsoft Corporation.
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
Juan F. Rodríguez, Marcelo Bagnulo,
Multihoming in IPV6 Habib Naderi Department of Computer Science University of Auckland.
Implementing IPv6 Module B 8: Implementing IPv6
Enabling IPv6 in Corporate Intranet Networks
17/10/031 Summary Peer to peer applications and IPv6 Microsoft Three-Degrees IPv6 transition mechanisms used by Three- Degrees: 6to4 Teredo.
Dynamic Tunnel Management Protocol for IPv4 Traversal of IPv6 Mobile Network Jaehoon Jeong Protocol Engineering Center, ETRI
Cs/ee 143 Communication Networks Chapter 6 Internetworking Text: Walrand & Parekh, 2010 Steven Low CMS, EE, Caltech.
1 Address Selection, Failure Detection and Recovery in MULTI6 draft-arkko-multi6dt-failure-detection-00.txt Multi6 Design Team -- Jari Arkko, Marcelo Bagnulo,
Copyright © 1999 Telcordia Technologies All Rights Reserved Christian Huitema An SAIC Company IPv6: Connecting 6 billion.
IPv6 Multihoming Support in the Mobile Internet Presented by Paul Swenson CMSC 681, Fall 2007 Article by M. Bagnulo et. al. and published in the October.
Advanced Networks 1. Delayed Internet Routing Convergence 2. The Impact of Internet Policy and Topology on Delayed Routing Convergence.
Presented by Serge Kpan LTEC Network Systems Administration 1.
1 Network Address Translation (NAT) Relates to Lab 7. Module about private networks and NAT.
CSE5803 Advanced Internet Protocols and Applications (7) Introduction The IP addressing scheme discussed in Chapter 2 are classful and can be summarised.
Wi-Fi Structures.
Topics 1.Security options and settings 2.Layer 2 vs. Layer 3 connection types 3.Advanced network and routing options 4.Local connections 5.Offline mode.
CCNA Guide to Cisco Networking Fundamentals Fourth Edition Chapter 9 Network Services.
Routing of Outgoing Packets with MP-TCP draft-handley-mptcp-routing-00 Mark Handley Costin Raiciu Marcelo Bagnulo.
1 IPv6 in CableLabs DOCSIS 3.0 IETF v6ops wg meeting IETF#65 Ralph Droms Alain Durand
Made with OpenOffice.org 1 TCP Multi-Home Options Arifumi Matsumoto Graduate School of Informatics, Kyoto University, Japan
Basic Network Training. Cable/DSL Modem The modem is the first link in the chain It is usually provided by the ISP and often has a coax cable connector.
1 Chapter 6: Proxy Server in Internet and Intranet Designs Designs That Include Proxy Server Essential Proxy Server Design Concepts Data Protection in.
1 IPv6 Deployment Scenarios in (e) Networks draft-ietf-v6ops deployment-scenarios-01 Myung-Ki Shin, ETRI Youn-Hee Han, KUT Sang-Eon Kim, KT.
NETWORKING COMPONENTS AN OVERVIEW OF COMMONLY USED HARDWARE Christopher Johnson LTEC 4550.
1 Chapter 7: NAT in Internet and Intranet Designs Designs That Include NAT Essential NAT Design Concepts Data Protection in NAT Designs NAT Design Optimization.
Default Router Preferences and More-Specific Routes in RAs Richard Draves May 31, 2001 Redmond Interim IPv6 WG Meeting draft-ietf-ipngwg-router-selection-00.
Vytautas Valancius, Nick Feamster, Akihiro Nakao, and Jennifer Rexford.
Routing integrity in a world of Bandwidth on Demand Dave Wilson DW238-RIPE
4.1.4 multi-homing.
An Update on Multihoming in IPv6 Report on IETF Activity RIPE IPv6 Working Group 22 Sept 2004 RIPE 49 Geoff Huston, APNIC.
Approaches to Multi6 An Architectural View of Multi6 proposals Geoff Huston March 2004.
Engineering Workshops 56 Allocation Schemes CIDR representation and IPv6 allocations.
Making SIP NAT Friendly Jonathan Rosenberg dynamicsoft.
Deploying IPv6, Now Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
WEEK 11 – TOPOLOGIES, TCP/IP, SHARING & SECURITY IT1001- Personal Computer Hardware System & Operations.
Network Components Basics!. Network HUB  Used to connect multiple Ethernet devices together  Layer 1 of the OSI model  Not used much today.
1 Extreme Networking at Home Jari Arkko, Ericsson.
+ Routing Concepts 1 st semester Objectives  Describe the primary functions and features of a router.  Explain how routers use information.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Understanding Customer-to-Provider Connectivity.
Site Multihoming for IPv6 Brian Carpenter IBM TERENA Networking Conference, Poznan, 2005.
IPv6 Renumbering, scenarios & requirements Christian Huitema draft-huitema-ipv6-renumber- 00.txt.
59 th IETF – NEMO Working Group 1 NEMO Multi-homing Issues Prepared for 59 th IETF NEMO WG By Chan-Wah NG, Eun-Kyoung PAIK, Thierry ERNST, Julien CHARBON.
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.
© 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.
NT1210 Introduction to Networking
Windows Vista Configuration MCTS : Advanced Networking.
Routing and Addressing in Next-Generation EnteRprises (RANGER)
Default Router Preferences and More-Specific Routes in RAs
Network Address Translation (NAT)
4.1.5 multi-homing.
Ingress Filtering, Site Multihoming, and Source Address Selection
Instructor Materials Chapter 9: NAT for IPv4
Network Address Translation (NAT)
Routing and Switching Essentials v6.0
CCNA v3.1 Student Migration Guidelines
Chapter 26 IPv6 Addressing
PPPoE Internet Point to Point Protocol over Ethernet
Instructor Materials Chapter 9: NAT for IPv4
An Update on Multihoming in IPv6 Report on IETF Activity
BGP Instability Jennifer Rexford
Sheng Jiang(Speaker) Bing Liu
Presentation transcript:

Simple Multihoming Experiment draft-huitema-multi6-experiment-00.txt Christian Huitema, Microsoft David Kessens, Nokia

7/11/2003Simple Multi-Homing Experiment2 Simple dual homing problem statement Simple bridged network 2 routers, 2 ISP ingress filtering No ISP coordination Example T1 + DSL back-up 2 DSL modems DSL + cable Cable + WiFi mesh Several hosts Simple = IPv6 basic Advanced = multi- homing aware It must work! Single link (bridge) H H H R1 R2 ISP1 ISP2 Internet (IPv6)

7/11/2003Simple Multi-Homing Experiment3 IPv4 equivalent: back-up Use for Back-Up Switch R1 on if R2 is down May incur small delay In general, loose TCP connections Typically combined with NAT & DHCP Private addresses, no renumbering Single link (bridge) H H H R1 R2 ISP1 ISP2 Internet (IPv4)

7/11/2003Simple Multi-Homing Experiment4 Broad Lines of the Solution No coordination between ISP Use of Provider Addresses Each ISP allocates a prefix  or each ISP allocates an IPv4 address, and the routers use 6to4 Multi-Addressing Each router advertises a prefix Hosts configure addresses with each prefix Five issues need resolution

7/11/2003Simple Multi-Homing Experiment5 Multi-addressing issues Ingress filtering host pick address from ISP1, send through R2? Dead default exit router, or dead ISP host keeps sending packets through a black hole? Inbound connection through wrong ISP Peers send packet to the black-holes address? Maintaining TCP connections Keep TCP going if the Router or the ISP fails? Use the right exit/entrance Maybe some amount of load balancing

7/11/2003Simple Multi-Homing Experiment6 Ideas, Ingress Filtering Choice by host Host treats multiple “auto-config” prefixes as “sub-interfaces”, associates individual IPv6 address and default router. Easy to implement in “new hosts”. Redirect at routers No need for tunnels in single link network. Guarantees that “old hosts” keep working. There may be other solutions New services, ISP involvement, etc.

7/11/2003Simple Multi-Homing Experiment7 Ideas, dead exit router or dead ISP If the router notices the problem Advertises prefix as “deprecated”, or stop advertising Will not be used for new connections Will work for old and new hosts. If the problem is not really detected New host tries multiple source addresses when establishing a new connection Host may keep track of the quality of each router connection

7/11/2003Simple Multi-Homing Experiment8 Ideas, Peer using dead address If the problem is detected Update the name server? If the problem is not detected DNS advertises multiple addresses Peer tries several addresses  Issue: TCP timers?

7/11/2003Simple Multi-Homing Experiment9 Ideas, Maintaining TCP Connections No good solution for old hosts But there is no solution in a similar IPv4 set-up either Many applications will automatically reconnect New hosts may use MIPv6 See “Application of the MIPv6 protocol to the multi-homing problem”  draft-bagnulo-multi6-mnm-00 SCTP may also be used See “multi-homing issues in SCTP”  draft-coene-sctp-multihome-04.txt

7/11/2003Simple Multi-Homing Experiment10 Idea, Selecting the right exit/entrance Right entrance: DNS tricks In asymmetric scenarios (back-up), only publish the “best address” in the DNS In symmetric scenarios, publish both Right exit: Routing tricks Provide information in router announcement, as in “Default Router Preferences, More-Specific Routes, and Load Sharing “  draft-ietf-ipv6-router-selection-02.txt

7/11/2003Simple Multi-Homing Experiment11 Summary It looks good on paper All issues have plausible solutions No change required to IPv6 standards No need to rewrite the IPv6 address at site exit We would benefit from “mobile IPv6” and “router selection” work But we would like an actual deployment… In theory, there is no difference between theory and practice, but in practice there is!

7/11/2003Simple Multi-Homing Experiment12 Range of solutions Small sites Do as we just explained Medium sites Ask the ISP to cooperate, allow both source addresses in ingress filtering  E.g. add a local route to the other prefix Very large sites Treat as ISP, get their own prefix & AS#