The MPLS WG Archive

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



[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: "Dave Cooper" <dcooper@gblx.net>
  • Date: Tue, 10 Jul 2001 10:43:30 -0700
  • Cc: "mpls-list" <mpls@UU.NET>, "mpls-ops" <mpls-ops@mplsrc.com>
  • Importance: Normal

David,
I think its up to the operators to ascertain
usefulness and applicability.  We were motivated
to submit this draft because of the urgency in
detecting LSP integrity in MPLS TE networks.
No, it doesnt address all of the requirements
outlined in the OAM draft. But it attempts to
address one of the most significant issues we face in
today's MPLS networks.  Our goal is to keep it
as simple as possible but accomplish this objective.

Thanks,
Dave


-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of David Allan
Sent: Tuesday, July 10, 2001 9:30 AM
To: Ping Pan
Cc: mpls-list; mpls-ops
Subject: RE: [Fwd: I-D ACTION:draft-pan-lsp-ping-00.txt]


Ping:
I am specifically concerned that although this tool may be percieved as useful, it really has very limited applicability, it assumes
a specific MPLS payload and a specific control plane. How many of these mechanisms do we wish to support before we finally have a
comprehensive toolkit?
IMHO It would be a whole lot more useful if we just tackled the problem in its entirety instead of via the incremental approach we
have seen to date.
One group of authors (Neil Harrison and company) has a requirements draft posted already, and we'll be bringing forward a framework
to London that builds upon it (to be posted later this week), Perhaps we can start to put these problems to bed a bit more
systematically....
cheers
Dave