Re: LMP revision 04

[Kireeti Kompella <kireeti@juniper.net>]

On Wed, 7 Aug 2002, Wijnen, Bert (Bert) wrote:

> I have reviewed this document with my AD hat on.
>
> Here are my comments/question
>
> - My biggest question is:
>
>   How does this fit in CCAMP in terms of providing a
>   COMMON control protocol and/or COMMON measurement protocol.
>
>   Remember our architecure, which is as follows:
>
>   --- pictorial overview of work in the sup-IP area --------------
>
>   The Working Groups at the top are those that will use the
>   Common Control and Measurement Protocols that we're
>   defining in the CCAMP WG.
>
>
>   Applications         +-------+  +-------+        (new) Hour glass
>   that use CCAMP: \    | TE-WG |  | PPVPN |  ...           /
>                    \   +-------+  +-------+               /
>                     \     +----------------------+       /
>                      \    |         CCAMP        |      /
>                       \   |-----------+----------|     /
>                       /   |     C     |    M   --|------ IGP LSA ext
>            LMP ======/====|= control  | measure  |     \
>                     /     +----------------------+      \
>   Technologies to  / +----+ +----+ +----+ +----+ +----+  \
>   measure/control:/  |MPLS| |OPT | |RPR | |ATM | | FR |...\
>                      +----+ +----+ +----+ +----+ +----+
>
>   The technologies at the bottom allow us to create paths and so those
>   are the ones we want to measure and control via the Common Control
>   and Measurement Protocols coming out of CCAMP. One of those
>   technologies (MPLS) is defined by IETF, others are (have been) defined
>   in other standards organisations. However, we want to focus mainly on
>   the use of such technologies for IP.
>
>   So for example the IPO and IPORPR WGs are assumed to be active at
>   the bottom because we want to focus on the IP use of such technologies.

Here's my view on how LMP fits into the Sub-IP "hourglass":

   LMP provides a valuable addition to the control plane that allows
   nodes in a network to establish and maintain control channels,
   exchange properties of links, abstract groups of such links into a
   "TE link", map such TE links to their respective control channels,
   and manage faults on these links.  The information gathered by LMP
   feeds into the IGP extensions to provide a fuller picture of the
   network topology, as well as into signaling protocols for mapping of
   control channels to data links, and fault recovery.  LMP operation
   is COMMON across a variety of control channel instantiations, and TE
   link types.  TE link types may be ATM, Frame Relay, SONET/SDH,
   Ethernet, OEO, lambdas, or fibers.

Kireeti.