To Be Multihomed: Requirements and Definitions

2/8/98


Click here to start


Table of Contents

To Be Multihomed: Requirements and Definitions

Why this topic?

A Gap (1)

A Gap (2)

Useful Web Pages

IETF References

Target audience for this info

Goal 1: Server availability to arbitrary users

The User You Hate to Want

That’s all very nice. Clearly, you aren’t able to do what I want to pay for. Can you refer me to whoever is in charge of the Internet?

Key Points to Educate this Customer

Goal 2: User connectivity to arbitrary servers

Key Points to Educate this Customer

Goal 3: Enterprise connectivity to selected partners

Key Points to Educate this Customer

Goal 4: Enterprise WAN Outsourcing

Key Points to Educate this Customer

Planning & Budgeting

Customers need to think about technical tradeoffs

Solution Family 1: Application/Transport/Name Multihoming

Solution Family 2: Layer 3/2 Multihoming

Solution Family 3: Medium/Transmission Multihomng

Multiple server addresses in DNS

Application caching

DNS-routing linkage

AIIIEEE! A Black Hole!

Multiple defaults advertised into IGP

Customer Advertising to You with Interior Routing Protocol

End User RIP Intended Usage

End User RIP Problems

End User RIP Enterprise and ISP Protective Measures

Provider Filtering

BGP tunnel over multiple media

BGP primary/backup

Full BGP

Transmission System Protection

Actions

Return to Notes Page

Author: Howard C. Berkowitz

Email: hcb@clark.net

Home Page: http://www.clark.net