[Diffserv] RFC 3317 on Differentiated Services Quality of Service Policy Information Base

rfc-editor@rfc-editor.org Fri, 07 March 2003 23:18 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13640 for <diffserv-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:18:55 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h27NUbl24787 for diffserv-archive@odin.ietf.org; Fri, 7 Mar 2003 18:30:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NKtO24096; Fri, 7 Mar 2003 18:20:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27N80O23674 for <diffserv@optimus.ietf.org>; Fri, 7 Mar 2003 18:08:00 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11918; Fri, 7 Mar 2003 17:55:46 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h27MvoZ19024; Fri, 7 Mar 2003 14:57:50 -0800 (PST)
Message-Id: <200303072257.h27MvoZ19024@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, diffserv@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 07 Mar 2003 14:57:50 -0800
Subject: [Diffserv] RFC 3317 on Differentiated Services Quality of Service Policy Information Base
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-BeenThere: diffserv@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=unsubscribe>
List-Id: Diffserv Discussion List <diffserv.ietf.org>
List-Post: <mailto:diffserv@ietf.org>
List-Help: <mailto:diffserv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=subscribe>

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


        RFC 3317

        Title:      Differentiated Services Quality of Service Policy
                    Information Base
        Author(s):  K. Chan, R. Sahita, S. Hahn, K. McCloghrie
        Status:     Informational
        Date:       March 2003
        Mailbox:    khchan@nortelnetworks.com, ravi.sahita@intel.com,
                    scott.hahn@intel.com, kzm@cisco.com
        Pages:      96
        Characters: 188553
        Updates/Obsoletes/See Also:   None

        I-D Tag:    draft-ietf-diffserv-pib-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3317.txt


This document describes a Policy Information Base (PIB) for a device
implementing the Differentiated Services Architecture.  The
provisioning classes defined here provide policy control over
resources implementing the Differentiated Services Architecture.
These provisioning classes can be used with other none Differentiated
Services provisioning classes (defined in other PIBs) to provide for a
comprehensive policy controlled mapping of service requirement to
device resource capability and usage.

This document is a product of the Differentiated Services (DIFFSERV)
Working Group of the IETF.

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.