The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Jul> msg00389



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

IGPs and MPLS

  • From: Vivek Venkatraman <v_vivek@yahoo.com>
  • Date: Tue, 25 Jul 2000 14:38:21 -0700 (PDT)


Hi,

I have a few questions regarding IGPs (e.g., OSPF) and
MPLS TE and would appreciate any answers.

1. When an LSP is established and IGP traffic
engineering is being performed, should the LSP be
informed as a (logical) Router link and/or a TE LSA
link into OSPF? If not, how is traffic engineering for
IGP destinations performed, is it completely internal
to the Ingress node?

2. If the available/unreseved bandwidth or some other
TE parameter on a link changes when a new LSP is
established, should the change be made known
immediately to OSPF and OSPF originate a new TE LSA?

3. Should CSPF path computations occur as a result of
an updated TE LSA or are they done only when a new LSP
is to be setup or existing LSPs optimized etc.?
 
4. Should a LSP be specifically designated as an
FA-LSP (draft-kompella-lsp-hierarchy-00.txt) or can
any LSP established function as an FA-LSP if the LSP
is advertised into OSPF?

5. Sec 4.2 of draft-kompella-lsp-hierarchy-00.txt
mentions how a FA-LSP/forwarding adjacency can be
restricted to allow its usage only for MPLS TE LSPs.
So, is there an Internet draft which defines how an
LSP should be advertised as a regular LSA into OSPF?


Vivek


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/