RFC 2745 on RSVP Diagnostic Messages
RFC Editor <rfc-ed@ISI.EDU> Tue, 01 February 2000 20:12 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01143; Tue, 1 Feb 2000 15:12:23 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA27774 for ietf-123-outbound.10@ietf.org; Tue, 1 Feb 2000 15:05:05 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA27727 for <all-ietf@loki.ietf.org>; Tue, 1 Feb 2000 14:55:47 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00737 for <all-ietf@ietf.org>; Tue, 1 Feb 2000 14:55:44 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA19785; Tue, 1 Feb 2000 11:55:44 -0800 (PST)
Message-Id: <200002011955.LAA19785@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2745 on RSVP Diagnostic Messages
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 01 Feb 2000 11:55:44 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2745 Title: RSVP Diagnostic Messages Author(s): A. Terzis, B. Braden, S. Vincent, L. Zhang Status: Standards Track Date: January 2000 Mailbox: terzis@cs.ucla.edu, braden@isi.edu, svincent@cisco.com, lixia@cs.ucla.edu Pages: 23 Characters: 52256 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rsvp-diagnostic-msgs-08.txt URL: ftp://ftp.isi.edu/in-notes/rfc2745.txt This document specifies the RSVP diagnostic facility, which allows a user to collect information about the RSVP state along a path. This specification describes the functionality, diagnostic message formats, and processing rules. This document is a product of the Resource Reservation Setup Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2745 on RSVP Diagnostic Messages RFC Editor