[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D ACTION:draft-palet-multi6-scenarios-00.txt
- To: Multi6 <multi6@ops.ietf.org>
- Subject: Re: I-D ACTION:draft-palet-multi6-scenarios-00.txt
- From: Brian E Carpenter <brc@zurich.ibm.com>
- Date: Thu, 22 Jul 2004 11:43:12 +0200
- In-reply-to: <200407131926.PAA06716@ietf.org>
- Organization: IBM
- References: <200407131926.PAA06716@ietf.org>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Personal comments:
Obviously this still needs quite a lot of work, and I suggest
merging in section 3 of draft-ietf-multi6-v4-multihoming-01.txt.
Just one direct comment today:
3.1 Internet Service Provider (ISP)
An ISP is naturally multihomed when connected to two or more upstream
providers. Actually this is a very common case, especially for
medium and large ISPs.
But why should we care? Once we get into BGP4+ territory, multihoming just
becomes part of routing. There isn't a scaling problem at this level.
Brian