[Policy] RFC 3644 on Policy Quality of Service (QoS) Information Model

rfc-editor@rfc-editor.org Thu, 20 November 2003 21:26 UTC

Message-Id: <200311182146.hAILkWs26504@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, policy@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 18 Nov 2003 13:46:32 -0800
Subject: [Policy] RFC 3644 on Policy Quality of Service (QoS) Information Model
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
Precedence: bulk

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


        RFC 3644

        Title:      Policy Quality of Service (QoS) Information Model
        Author(s):  Y. Snir, Y. Ramberg, J. Strassner, R. Cohen,
                    B. Moore
        Status:     Standards Track
        Date:       November 2003
        Mailbox:    yramberg@cisco.com, ysnir@cisco.com,
                    john.strassner@intelliden.com,
                    ronc@lyciumnetworks.com, remoore@us.ibm.com
        Pages:      73
        Characters: 170150
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-policy-qos-info-model-05.txt

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


This document presents an object-oriented information model for
representing Quality of Service (QoS) network management policies.
This document is based on the IETF Policy Core Information Model and
its extensions.  It defines an information model for QoS enforcement
for differentiated and integrated services using policy.  It is
important to note that this document defines an information model,
which by definition is independent of any particular data storage
mechanism and access protocol.

This document is a product of the Policy Framework 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.

ftp://ftp.isi.edu/in-notes/rfc3644.txt"><ftp://ftp.isi.edu/in-notes/rfc3644.txt>

[Policy] RFC 3644 on Policy Quality of Service (Q… rfc-editor