The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Dec> msg00234



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

draft-ietf-mpls-lsp-ping-01.txt - ECMP considerations

  • From: "David Allan" <dallan@nortelnetworks.com>
  • Date: Tue, 10 Dec 2002 20:51:58 -0500

Hi Curtis:

I think what you are proposing illustrates the complexity of the problem,
and highlights that we need a different approach in order for detecting
problems to be tractable. IMHO such constructs cannot be reliably and
proactively tested from a single arbitrary upstream point and what you
describe illustrates the complexity of actually performing meaningful
testing. This is compounded exponentially as load spreading points are
cascaded between the ingress and any point of failure.

IMHO the correct answer is to proactively test from more than one point in
the network and depend on the aggregate effect of the whole, and not try to
produce a protocol that reverse engineers proprietary boxes.

Each load spreading point should behave as a set of ingresses (from the POV
of probe injection) for some low frequency of probes. You live with not
necessaraily exercising all aspects of the actual load spreader but that is
true for any approach that is not ICMP monotonically going through the IP
address plan. 

This will provide bounded error detection in the network. Ideally you need
some smarts to locate the probe source closest to and upstream of the point
of failure once somthing goes wrong.  

food for thought
Dave