idnits 2.17.1 draft-ietf-ccamp-tracereq-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3609 5 Title: Tracing Requirements for Generic Tunnels 6 Author(s): R. Bonica, K. Kompella, D. Meyer 7 Status: Informational 8 Date: September 2003 9 Mailbox: ronald.p.bonica@mci.com, kireeti@juniper.net, 10 dmm@maoz.com 11 Pages: 9 12 Characters: 17859 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-ccamp-tracereq-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3609.txt 19 This document specifies requirements for a generic route-tracing 20 application. It also specifies requirements for a protocol that will 21 support that application. Network operators will use the generic 22 route-tracing application to verify proper operation of the IP 23 forwarding plane. They will also use the application to discover 24 details regarding tunnels that support IP forwarding. 26 The generic route-tracing application, specified herein, supports a 27 superset of the functionality that "traceroute" currently offers. 28 Like traceroute, the generic route-tracing application can discover 29 the forwarding path between two interfaces that are contained by an 30 IP network. Unlike traceroute, this application can reveal details 31 regarding tunnels that support the IP forwarding path. 33 This document is a product of the Common Control and Measurement Plane 34 Working Group of the IETF. 36 This memo provides information for the Internet community. It does 37 not specify an Internet standard of any kind. Distribution of this 38 memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.