MPLS

[Kireeti Kompella <kireeti@juniper.net>]

NAME OF I-D:

  http://search.ietf.org/internet-drafts/draft-kompella-mpls-multiarea-te-01.txt

SUMMARY

  This ID describes several mechanisms to extend Traffic Engineering
  across IGP area boundaries -- current mechanisms are limited to a
  single area.


RELATED DOCUMENTS

  draft-ash-ccamp-multi-area-te-reqmts-00.txt
  draft-dharanikota-interarea-mpls-te-ext-01.txt
  draft-lee-mpls-te-exchange-00.txt
  draft-venkatachalam-interarea-mpls-te-00.txt


WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK

  Belongs in TEWG, currently resides in MPLS.


WHY IS IT TARGETED AT THIS WG

  It deals with Traffic Engineering.


JUSTIFICATION

  Being able to do Traffic Engineering across multiple areas seems
  to be useful if not vital, although there are varying opinions on
  how much SPs want multi-area TE *today*.  However, as networks
  grow, they will probably move to multiple areas (hierarchical IGPs)
  at which point this work will have relevance.  Also, this work is
  important for optical networks, where it is envisioned that the
  optical devices will belong to a different area than the routers
  for various reasons, but one may desire to do TE across the
  entire network.

  Also, there is in place an effort to get a design team going on
  "Hierarchical TE", whose first task should be answering the question,
  "Do we need multi-area TE?"

  Assuming that we do need multi-area TE, this ID proposes a means to
  do this in a scalable fashion (and scalability is generally why one
  would have hierarchical IGPs).

Kireeti.