time tracing utility

[Tom Scott <telecomtom@vedatel.com>]

In a thread on the CCAMP list regarding draft-ietf-ccamp-tracereq-00.txt,
the authors indicated that a time-tracing application was beyond the
scope of the draft. Is there any interest in the TE WG for such a utility,
as applied to the delay-based metric suggested in section 2 of
draft-ietf-tewg-te-metric-igp-01.txt:

  In current MPLS TE deployments, network administrators often want
  Constraint Based Routing of TE LSPs carrying data traffic to be
  based on the same metric as the metric used for Shortest Path
  Routing. Where this is the case, this practice allows the Constraint
  Based Routing algorithm running on the Head-End LSR to use the IGP
  metric advertised in the IGP to compute paths for data TE LSPs
  instead of the advertised TE metric. The TE metric can then be used
  to convey another metric (e.g. a delay-based metric) which can be
  used by the Constraint Based Routing algorithm on the Head-End LSR
  to compute path for the TE LSPs with different requirements (e.g.
  Voice TE LSP).

The management model in RFC 3290/89 describes ten "datapath elements" and
"traffic conditioning blocks" that are constructed from the elements. Is
it possible to use these elements (and TCBs?), along with the metric
recommendations of the IPPM WG, to define a time-tracing utility that
measures not only where traffic travels but also the time that packets
take to travel from A to B, where the endpoints of interest are nodes or
"functional groupings" on any layer or components such as the datapath
elements in any of those nodes?

If this is out of scope for the TE WG, I would be grateful to anyone who
could refer me to publications on this topic.

-- TIA, TT