Re: A new spin on multihoming: multihoming classes.

[Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>]

At/À 09:53 2001-09-05 -0700, Michel Py you wrote/vous écriviez:
>multi6 folks,
>
>I think that one of the problems we are having is that
>we are trying to design a universal solution for a too
>broad topic.
>
>Let's divide multihoming into two classes:
>- Entreprise class.
>- user class.

good classification


>- Entreprise class is for companies that receive a BGP
>feed from two different TLAs and have been allocated a
>centrally managed multihomed block of IPv6 addresses.
>These entreprises run mission-critical web servers
>with large pipes to the Net and want 99.999%
>availability and global load sharing among their
>different connections.
>The multihoming solution for entreprise class must be
>contained at the network or internet layer. My
>personal submission to entreprise class is:
>http://arneill-py.sacramento.ca.us/draft-py-multi6-mhtp-01.txt
>
>- User class is for home/soho setups that dual home
>both to DSL and cable (example). These users might be
>given dynamically assigned IPv6 addresses or prefixes
>and are in potentially very large numbers. These users
>mailnly use their connections for surfing and
>eventually run minimal/personal servers over a slow
>uplink.

However, I would include in this class the "fiber-to-the home" and wireless 
802.11 community networks.
Still a user class, but the "slow uplink" might not be right for those users.

Marc.


>The potentially very large number of user
>class multihomed sites and high volatility of IP
>addresses makes it very difficult to centrally
>administer.
>The multihoming solution for user class could be based
>on transport or higher levels. Survivability and
>availability are nice to have but second to the ease
>of a large scale deployment.
>
>Any comments?
>Michel.
>
>
>__________________________________________________
>Do You Yahoo!?
>Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
>http://im.yahoo.com