The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Jul> msg00116



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

[Fwd: I-D ACTION:draft-pan-lsp-ping-00.txt]

  • From: Eric Rosen <erosen@cisco.com>
  • Date: Tue, 10 Jul 2001 16:34:22 -0400
  • cc: "David Allan" <dallan@nortelnetworks.com>, "Ping Pan" <pingpan@juniper.net>, "mpls-list" <mpls@UU.NET>, "mpls-ops" <mpls-ops@mplsrc.com>
  • User-Agent: EMH/1.10.0 WEMI/1.13.2 (Mochimune) FLIM/1.12.1(Nishinokyō) Emacs/20.6 (sparc-sun-solaris2.5.1)MULE/4.0 (HANANOEN)

I'm still trying to  be sure I understand just what this  mechanism is to be
used for.  

If a given LSP is working, and  was set up with RSVP-TE, this mechanism will
allow you to verify that it is working.

If a given LSP is not working,  this mechanism does not provide you with any
diagnostic information. 

So you can use it for two purposes:

- to test regularly whether an LSP is working

- to  eliminate  "LSP data  plane  outage" as  the  source  of a  particular
  problem. 

This does seem useful.

I think though that draft-bonica-icmp-mpls is also an attempt to provide the
testing  function, along  with  some diagnostic  capability,  but without  a
dependence on a particular control  plane.  Do you see draft-pan-lsp-ping as
being superior in some respect?