RFC 2698 on A Two Rate Three Color Marker

RFC Editor <rfc-ed@ISI.EDU> Thu, 16 September 1999 23:50 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09561; Thu, 16 Sep 1999 19:50:58 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA01685 for ietf-123-outbound.10@ietf.org; Thu, 16 Sep 1999 19:45:01 -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 TAA01292 for <all-ietf@loki.ietf.org>; Thu, 16 Sep 1999 19:16:13 -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 TAA08317 for <all-ietf@ietf.org>; Thu, 16 Sep 1999 19:16:12 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA18701; Thu, 16 Sep 1999 16:16:13 -0700 (PDT)
Message-Id: <199909162316.QAA18701@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2698 on A Two Rate Three Color Marker
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 16 Sep 1999 16:16:13 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2698:

        Title:	    A Two Rate Three Color Marker
        Author(s):  J. Heinanen, R. Guerin
        Status:     Informational
	Date:       September 1999
        Mailbox:    jh@telia.fi, guerin@ee.upenn.edu
        Pages:      6
        Characters: 9368
	Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-heinanen-diffserv-trtcm-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2698.txt


This document defines a Two Rate Three Color Marker (trTCM), which
can be used as a component in a Diffserv traffic conditioner
[RFC2475, RFC2474].

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.
ftp://ftp.isi.edu/in-notes/rfc2698.txt"><ftp://ftp.isi.edu/in-notes/rfc2698.txt>