Re: Multi-Area TE Protocol Extensions
Yakov Rekhter <yakov@juniper.net> Tue, 10 December 2002 20:15 UTC
Envelope-to: ccamp-data@psg.com
Delivery-date: Tue, 10 Dec 2002 12:18:08 -0800
Message-Id: <200212102015.gBAKFkS51587@merlot.juniper.net>
To: Dimitri.Papadimitriou@alcatel.be
cc: Jean Philippe Vasseur <jvasseur@cisco.com>, sachin laddha <sachinl@internettrends.co.in>, mpls@UU.NET, ccamp@ops.ietf.org
Subject: Re: Multi-Area TE Protocol Extensions
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <50341.1039551345.1@juniper.net>
Date: Tue, 10 Dec 2002 12:15:46 -0800
From: Yakov Rekhter <yakov@juniper.net>
Dimitri, > > this ID does not propose a mechanism to compute inter-area TE path > > well i would say that either none of them does it, or all of > them, more accurately route exclusions are applicable to any > mpls network where full computation of the ero is not performed > before the LSP is signaled, implying thus a "scope" for computed > path thus among other applicable to multiple areas - nevertheless > i agree that a next version of this i-d should probably include > an applicability section covering this in a bit more details (see > also section 4.1 for an example - > > this said and as for any other input or i-d provided on constraint- > passing (as well as path query, btw) lot of work is still needed to > achieve a decent first step in this effort; On the subject passing constraint, I'd like to mention draft-kompella-mpls-rsvp-constraints-00.txt (expired, but I could provide a copy upon request). It contains a fairly general mechanism for passing constraints in RSVP. Yakov. > > thanks, > - dimitri. > > Jean Philippe Vasseur wrote: > > > > Hi Dimitri, > > > > cc'ing CCAMP - see in line, > > > > At 17:45 10/12/2002 +0100, Dimitri.Papadimitriou@alcatel.be wrote: > > >jp, > > > > > >in fact the below list should simply be as follows for > > >signalling-based methods: 1) constraint-passing 2) loose > > >routing and 3) path query; > > > > > >and the for constraint-passing we have a several i-d's > > >such as, > > > > > >http://www.ietf.org/internet-drafts/draft-lee-ccamp-rsvp-te-exclude-route- 01.txt > > > > > > > this ID does not propose a mechanism to compute inter-area TE path > > > > >constraint passing may also be extended using the crank- > > >back as listed below; the usage scenarios of these methods > > >are described in the following: > > > > > >http://www.ietf.org/internet-drafts/draft-kompella-mpls-multiarea-te-03.tx t > > > > > >now probably it is worth spending some time in considering > > >input coming from the tewg wrt to this effort, most of the > > >input that you see listed above has been produced over the > > >past year (and more) i can't imagine stepping in the protocol > > >details without a clear consensus on what do we want to cover > > >within the ccamp wg & w/o taking into account the tewg rec's > > >(probably better to discuss this on the ccamp mailing list) > > > > Fully agree with you. Hopefully multi-area TE should be soon part of the > > CCAMP charter. > > > > JP. > > > > >thanks, > > >- dimitri. > > > > > >Jean Philippe Vasseur wrote: > > > > > > > > Hi, > > > > > > > > At 13:53 10/12/2002 +0530, sachin laddha wrote: > > > > >Hi, > > > > >'draft-ash-multi-area-te-reqmts-01.txt' stated in section 5 as > > > > >"Initial requirements are given here for protocol support of the > > > multi-area > > > > >TE methods, which include needs to support > > > > > > > > > >* path-computation-server (PCS) functionality [kompella, lee, > > > vasseur, > > > > >te-qos-routing], > > > > >* query functionality [query, vasseur], > > > > >* crankback functionality [crankback], > > > > > > > > > >and, optionally, > > > > > > > > > >* TE feedback functionality [feedback], and > > > > >* summary-LSA functionality [summary_lsa]." > > > > >. > > > > >I want to know whether cisco/juniper routers (standard ones) supports > > > all of > > > > >the above extension. > > > > >or if not,how many.......or Whether router is supposed to support how many > > > > >... > > > > > > > > I do not think any vendor supports all the method mentioned above, but just > > > > a subset. If you are running a network, your feed-backs on your preferr ed > > > > method is very welcome. > > > > > > > > JP. > > > > > > > > >Regards, > > > > >---Sachin > > > > > >-- > > >Papadimitriou Dimitri > > >E-mail : dimitri.papadimitriou@alcatel.be > > >Private: http://www.rc.bel.alcatel.be/~papadimd/index.html > > >E-mail : dpapadimitriou@psg.com > > >Public : http://psg.com/~dpapadimitriou/ > > >Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium > > >Phone : Work: +32 3 2408491 - Home: +32 2 3434361 > > -- > Papadimitriou Dimitri > E-mail : dimitri.papadimitriou@alcatel.be > Private: http://www.rc.bel.alcatel.be/~papadimd/index.html > E-mail : dpapadimitriou@psg.com > Public : http://psg.com/~dpapadimitriou/ > Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium > Phone : Work: +32 3 2408491 - Home: +32 2 3434361 >
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Cheng-Yin Lee
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Jean Philippe Vasseur
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Jean Philippe Vasseur
- Re: Multi-Area TE Protocol Extensions Cheng-Yin Lee
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Cheng-Yin Lee
- Re: Multi-Area TE Protocol Extensions Yakov Rekhter
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Yakov Rekhter
- Re: Multi-Area TE Protocol Extensions Dimitri.Papadimitriou
- Re: Multi-Area TE Protocol Extensions Jean Philippe Vasseur