Re: accepting draft-fedyk-bgp-te-attribute-02.txt as a CCAMP WG document

On Oct 3, 2007, at 3:03 PM, Adrian Farrel wrote:

2. Could you conceive of using your I-D to meet the requirements of the Vasseur I-D?

In order for me to answer this question I'd like to get a clear
description of the requirements of the Vasseur I-D.

I'm not trying to fight JP's battles for him.
Just trying to find out whether we have two problem spaces or one.

I think the abstract of his I-D is relatively clear:

This document proposes MP-BGP protocol extension so as to convey
Traffic Engineering Link characterictics of PE (Provider Edge) - CE
(Customer Edge) links in order to extend the visibility of the
Traffic Engineering Database to those links. This can then be used
to more efficiently compute CE-to-CE Traffic Engineering Label

Yakov, let me know if you need further clarification on the application ... sounds

pretty obvious, extend the TED to some PE-CE links where a CE to CE TE LSP

is needed. The path computation piece is then very much similar to inter-domain

TE (per domain, PCE, ...). My question here is why would you want to redefine

TE TLVs where we could simply reuse the TE TLVs carried in IGPs, in order to

avoid to redefine TLVs for each TE link characteristic of interest.

Note that the current Abstract:

Abstract

This document defines a new BGP attribute, Traffic Engineering

attribute, than enables BGP to carry Traffic Engineering information.

is fairly general ... "carry Traffic Engineering information".

Thanks.

JP.

A