[Isis-wg] RE: FYI Draft Metrics and Resource Classes for TE

[Don Fedyk]

> -----Original Message-----
> From: Tony Przygienda [mailto:prz@siara.com]
> Sent: Thursday, October 21, 1999 9:30 PM
> To: Fedyk, Don [BL3:2001-I:EXCH]
> Cc: Chiu, Angela L, ALSVC; awduche@UU.NET; te-wg@UU.NET;
> isis-wg@external.juniper.net
> Subject: Re: [Isis-wg] RE: FYI Draft Metrics and Resource 
> Classes for TE
> > _______________________________________________
> > Isis-wg mailing list  -  Isis-wg@external.juniper.net
> > http://external.juniper.net/mailman/listinfo/isis-wg
stuff deleted

> 
> first, I think that the draft is dearly missing the reference 
> to the QoSR
> RFC 2386 by Raj & Bala that does much more thorough (and error-free) 
> job of explaining the problem and well-known research results 
> in terms of 
> algorithmic complexities and available design space and would 
> make some of it
> superfluous. 

We will add the reference. Thank you.

It is evident that there is some confusion. We are only addressing 
connection oriented traffic engineering metrics not 
connectionless metrics. I will try to be more clear.

In my experience I have effectively used multiple connection
oriented TE metrics. I believe this is worthwhile going forward. 
We have customers that request it. The multiple metrics we ask 
for are for traffic engineering MPLS not IGP. 

> second, it may be better to aim for a presentation at the 
> routing area meeting
> rather than in ISIS and OSPF & other groups disjointly since 
> the interested parties
> will be there and this is not a draft asking for specific TLVs / LSA 
> additions but somehow for extensions to the generic scope of 
> the work. As well,
> presenting to 4 groups is kind of a strain ;-)

We only asked for MPLS TE and IS-IS at this point.

> 
> third, IMHO I'd be reluctant to put into the protocol metrics 
> that are a 
> "network administrative decision". An IGP is _not_ a network 
> management tool.
> Metrics have crisp meanings. Otherwise issues of metric 
> translation, ranges,
> consistent computation algorithms and so on will be an 
> interesting albeit
> not very constructive exercise on a live network.

I am confused. The IS-IS draft has TE metrics and resources
this is what we were trying to address.

> 
> fourth, Tony Li's name is misspelled until he changed his 
> name with his job ;-)
Yes, Henk Smit pointed this out already. I apologized to Tony Li. 
I will update the document. 

> 
> 
> 		thanks 
> 
> 		- tony
>
Thanks, 
Don