[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MPLS Inter-area TE requirement draft
- To: Jean Philippe Vasseur <jvasseur@cisco.com>
- Subject: Re: MPLS Inter-area TE requirement draft
- From: Jim Boyle <jboyle@pdnets.com>
- Date: Wed, 31 Dec 2003 19:05:30 -0800 (PST)
- Cc: Jim Boyle <jboyle@pdnets.com>, te-wg@ops.ietf.org, ejk@tech.org, bwijnen@lucent.com, jeanlouis.leroux@francetelecom.com, Raymond_Zhang@infonet.com, Kenji Kumaki <ke-kumaki@kddi.com>, Yuichi Ikejiri <y.ikejiri@ntt.com>, Parantap Lahiri <parantap.lahiri@mci.com>, ting_wo.chung@bell.ca
- In-reply-to: <4.3.2.7.2.20031231100148.0853e4a8@wells.cisco.com>
- References: <4.3.2.7.2.20031230151712.072836a0@wells.cisco.com> <4.3.2.7.2.20031230151712.072836a0@wells.cisco.com> <4.3.2.7.2.20031231100148.0853e4a8@wells.cisco.com>
JP, so you state that both optimality and scalability are
requirements, yet you acknowledge that there will be trade-offs. I
believe it is important to prioritize the requirements, so as to best
guide the discussion on the solution.
regards,
Jim
On Wed, 31 Dec 2003, Jean Philippe Vasseur wrote:
>
> This is a requirement draft, not a solution draft. The requirement to be
> able to compute an optimal end to end path is clearly stated in the draft
> indeed, since it turns out to be a requirement for several SPs. You seem to
> draw the conclusion that scalability yields to optimality which is
> absolutely not an assumption of this requirement draft. Moreover, such a
> debate will obviously take place when discussing the solution in CCAMP,
> here is a *requirement* draft.
>
> Note that the requirement for a scalable solution is clearly highlighted in
> the present draft:
>
> 5.1. Objectives to preserve IGP/RSVP scalability
>
> Being able to achieve the requirements listed in this document MUST be
> performed while preserving the IGP scalability, which is of the utmost
> importance. Hence, the set of mechanisms defined to meet those
> requirements MUST not require IGP extra-load which could compromise the
> IGP scalability. In particular, a solution satisfying those
> requirements MUST require for the IGP to carry some unreasonable amount
> of extra information and MUST not significantly increase the frequency
> of IGP flooding. Likewise, the solution MUST also preserve the
> scalability of RSVP TE ([RSVP-TE]). Moreover, the solution MUST
> preserve the concept of IGP hierarchy (no TE link information flooded
> across areas).
>
<snip>
> >Am I off here? I'm interested to here some feedback from the members of
> >the WG if they feel scalability or optimality is more crucial, or if it
> >is widely felt that they may harmoniously coexist without trade-off.
>
> Do you know any solution without trade-off ? Obviously not ... but I guess
> that the pros and cons of each solution addressing the requirements will be
> discussed in the solution draft.
>
> Thanks.
>
> JP.
>
> >regards,
> >
> >Jim
>