[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: draft-ietf-multi6-multihoming-requirements-03.txt



On Wed, 23 Oct 2002, Sean Doran wrote:

> Have you read it?  Do you think it's ready?
> Do you think it's not ready?  Do you have an
> idea you think should be incorporated into
> the draft?

Two changes I recommend:

Insert between 3.1.4 and 3.1.5 (alternative is placing it into the
"3.1.6 transport-layer survivability" section, although that doesn't
completely address the issue:

---
3.1.x Alternate path visibility

  Multihoming solutions must not constrain alternate path visibility to
  the originating host only.  Multihoming solutions should allow
  alternate path visibility to reside within the network infrastructure,
  such that the multihomed site's operator may easily configure policy to
  prefer a given set of paths.  This may include host and
  network-infrastructure interaction to determine the best path.
---

Discussion:  See previous threads.  The goal is to allow network
infrastructure to have visibility into alternate paths for IP traffic, and
not constrain them to the originating host.

An addition to 3.2.6:

---
A multihoming solution must not require cooperation between the
multi-homed site and other transit providers not providing service to
said multi-homed site.
---

Discussion:  A requirement or possibility for a multihomed site to
establish a business relationship with many, or every, transit provider is
unreasonable.  Multihoming solutions should work and provide reachability
to an end-site provided the guidelines are adhered to, without the need
for a site to establish settlement with a significant number of transit
providers to carry any routing information.

/cah

---
Craig A. Huegen, Chief Network Architect      C i s c o  S y s t e m s
IT Transport, Network Technology & Design           ||        ||
Cisco Systems, Inc., 400 East Tasman Drive          ||        ||
San Jose, CA  95134, (408) 526-8104                ||||      ||||
email: chuegen@cisco.com       CCIE #2100      ..:||||||:..:||||||:..