-----Original Message-----
From: Hamid Ould-Brahim [mailto:hbrahim@nortelnetworks.com]
Sent: Tuesday, June 03, 2003 9:38 AM
To: Ron Bonica; ccamp@ops.ietf.org
Subject: RE: I-D ACTION:draft-ietf-ccamp-tracereq-04.txtRon,
This is a good document. I just have one clarification/comment:
in the draft:
"7) Support the following tunneling technologies: GRE, MPLS, IPSEC,
GMPLS, IP-in-IP, L2TP. Be easily extensible to support new tunnel
technologies."and req. 8 on heterogeneous tunnels.
I assume the tracing doesn't preclude the case where the IP
tunnels are carrying MPLS-in-IP or MPLS-in-GRE encapsulation.Should that be explicitly mentioned (since it has implication
on the type)?.Hamid.
>
> Pleae review this version. It is the most recent.
>
> Ron
>
> > -----Original Message-----
> > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > Behalf Of Internet-Drafts@ietf.org
> > Sent: Tuesday, June 03, 2003 7:46 AM
> > To: IETF-Announce:
> > Cc: ccamp@ops.ietf.org
> > Subject: I-D ACTION:draft-ietf-ccamp-tracereq-04.txt
> >
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the Common Control and Measurement
> > Plane Working Group of the IETF.
> >
> > Title : Tracing Requirements for Generic Tunnels
> > Author(s) : R. Bonica, K. Kompella, D. Meyer
> > Filename : draft-ietf-ccamp-tracereq-04.txt
> > Pages : 9
> > Date : 2003-6-2
> >
> > This document specifies requirements for a generic route-tracing
> > application. It also specifies requirements for a protocol
> that will
> > support that application. Network operators will use the generic
> > route-tracing application to verify proper operation of the IP
> > forwarding plane. They will also use the application to discover
> > details regarding tunnels that support IP forwarding.
> > The generic route-tracing application, specified herein, supports a
> > superset of the functionality that 'traceroute' currently offers.
> > Like traceroute, the generic route-tracing application can discover
> > the forwarding path between two interfaces that are contained by an
> > IP network. Unlike traceroute, this application can reveal details
> > regarding tunnels that support the IP forwarding path.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-ccamp-tracereq-04.txt
> >
> > To remove yourself from the IETF Announcement list, send a
> message to
> > ietf-announce-request with the word unsubscribe in the body of
> > the message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with
> > the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > "get draft-ietf-ccamp-tracereq-04.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> > mailserv@ietf.org.
> > In the body type:
> > "FILE /internet-drafts/draft-ietf-ccamp-tracereq-04.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> > MIME-encoded form by using the "mpack" utility. To use this
> > feature, insert the command "ENCODING mime" before the "FILE"
> > command. To decode the response(s), you will need "munpack" or
> > a MIME-compliant mail reader. Different MIME-compliant
> mail readers
> > exhibit different behavior, especially when dealing with
> > "multipart" MIME messages (i.e. documents which have been split
> > up into multiple messages), so check your local documentation on
> > how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >
>