RE: draft-bonica-tunneltrace-02

[Ron Bonica <Ronald.P.Bonica@wcom.com>]

Sharam,

Section 7 of this document enumerates a some minimal protocol requirements.
Specifically, it states that:

o a traceResponse will carry information regarding a section of the traced
path
o a traceProbe will elicit a traceResponse
o UDP will carry traceProbes and traceResponses
o the protocol will be stateless
o each device within the trace path need not maintain an IP route back to
the device that hosts that tracing application

Although these broad brushstrokes do not specify a protocol, they provide
direction to protocol developers. We are looking for an IP based protocol
that can probe network elements about whatever tunnels they maintain,
regardless of the tunnel type. We are not looking to extend the capabilities
of any particular tunneling technology.

                                      Ron

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> Behalf Of Shahram Davari
> Sent: Tuesday, February 19, 2002 5:29 PM
> To: ccamp@ops.ietf.org
> Subject: RE: draft-bonica-tunneltrace-02
>
>
> Hi,
>
> Although this document is a generic requirement for tunnel
> tracing, I find many protocol specific requirements that are not
> actually a requirement, rather they are suggesting a specific solution.
>
> For example:
>
> "The protocol elicits a series of traceResponse messages."
> "Each traceResponse message represents a hop that connects the
> head-end of the traced path to the tail-end of the traced path"
> "Each traceProbe message elicits exactly one traceResponse message."
> "UDP carries traceProbe and traceResponse messages to their destinations."
>
>
> Thanks,
> -Shahram
>
>