[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CCAMP draft-ietf-mpls-lmp-02.txt




NAME OF I-D:

  Write it down as a URL so we can click on it to see it.  e.g. 

  http://www.ietf.org/internet-drafts/draft-ietf-mpls-lmp-02.txt


SUMMARY

   This draft specifies a link management protocol (LMP) that runs
   between neighboring nodes and is used to manage traffic engineering
  (TE) links.  Specifically, LMP will be used to maintain control
   channel connectivity, verify the physical connectivity of the
   data-bearing channels, correlate the link property information
   (e.g., local/remote Interface ID mappings), and manage link
   failures.  A unique feature of the fault management technique is
   that it is able to localize failures in both opaque and transparent
   networks, independent of the encoding scheme used for the data.

RELATED DOCUMENTS

  Related documents:
      http://www.ietf.org/internet-drafts/draft-dubuc-lmp-mib-01.txt
      http://www.ietf.org/internet-drafts/draft-fredette-lmp-wdm-01.txt
      http://www.ietf.org/internet-drafts/draft-kompella-mpls-bundle-05.txt
 
http://www.ietf.org/internet-drafts/draft-many-gmpls-architecture-00.txt
 
http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-04
.txt
 
http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-rsvp-te-03.t
xt
 
http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-cr-ldp-03.tx
t
 
http://www.ietf.org/internet-drafts/draft-ietf-isis-gmpls-extensions-02.txt
 
http://www.ietf.org/internet-drafts/draft-kompella-ospf-gmpls-extensions-01.
txt

   various OIF documents on neighbor discovery, link management, and the OIF
UNI 1.0 (link not included as it requires company membership).

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

      LMP is a fits in the Control part of the sub-ip work.

WHY IS IT TARGETED AT THIS WG

LMP addresses the following CCAMP work items:

- Define measurement protocols such that they support multiple physical path
and tunnel technologies (e.g. O-O and O-E-O optical switches, ATM and Frame
Relay switches, MPLS, GRE) using input from technology-specific working
groups such as MPLS, IPO, etc.

- Abstract link and path properties needed for link and path protection.
Define signalling mechanisms for path protection, diverse routing and fast
path restoration. Ensure that multi-layer path protection and restoration
functions are achievable using the defined
signalling and measurement protocols, either separately or in combination.

- Define the properties of network resources gathered by the measurement
protocol that can be distributed in existing routing protocols, such as OSPF
and IS-IS.

- Define a set of protocol-independent metrics and parameters for describing
links that can be carried in protocols.

JUSTIFICATION

  We believe LMP is justified for the CCAMP working group because it
provides essential link management functionality to support multiple
physical path technologies.  Furthermore, the features provided by LMP are
required to manage links where the control plane is physically diverse from
the data plane.  For example, LMP provides the correlation between nodes for
physical resources that are used as labels in GMPLS signaling.  LMP also
provides mechanism to ensure proper configuration for span protection.