RFC 2859 on TSWTCM
RFC Editor <rfc-ed@ISI.EDU> Tue, 27 June 2000 23:44 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26708; Tue, 27 Jun 2000 19:44:55 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA13608 for ietf-123-outbound.10@ietf.org; Tue, 27 Jun 2000 19:35:03 -0400 (EDT)
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 TAA13513 for <all-ietf@loki.ietf.org>; Tue, 27 Jun 2000 19:17:52 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26315 for <all-ietf@ietf.org>; Tue, 27 Jun 2000 19:17:51 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA19176; Tue, 27 Jun 2000 16:17:51 -0700 (PDT)
Message-Id: <200006272317.QAA19176@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2859 on TSWTCM
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 27 Jun 2000 16:17:51 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2859 Title: A Time Sliding Window Three Colour Marker (TSWTCM) Author(s): W. Fang, N. Seddigh, B. Nandy Status: Experimental Date: June 2000 Mailbox: wfang@cs.princeton.edu, nseddigh@nortelnetworks.com, bnandy@nortelnetworks.com Pages: 9 Characters: 19203 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-fang-diffserv-tc-tswtcm-01.txt URL: ftp://ftp.isi.edu/in-notes/rfc2859.txt This memo defines a Time Sliding Window Three Colour Marker (TSWTCM), which can be used as a component in a Diff-Serv traffic conditioner [RFC2475, RFC2474]. The marker is intended to mark packets that will be treated by the Assured Forwarding (AF) Per Hop Behaviour (PHB) [AFPHB] in downstream routers. The TSWTCM meters a traffic stream and marks packets to be either green, yellow or red based on the measured throughput relative to two specified rates: Committed Target Rate (CTR) and Peak Target Rate (PTR). This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 2859 on TSWTCM RFC Editor