White contribution COM 16-C8-E on Questions
okubo at MXZ.MESH.NE.JP
Wed Nov 26 00:13:16 EST 2003
For your information.
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org]
Sent: 18 November 2003 22:47
Cc: rfc-editor at rfc-editor.org; policy at ietf.org
Subject: RFC 3644 on Policy Quality of Service (QoS) Information Model
A new Request for Comments is now available in online RFC libraries.
Title: Policy Quality of Service (QoS) Information Model
Author(s): Y. Snir, Y. Ramberg, J. Strassner, R. Cohen,
Status: Standards Track
Date: November 2003
Mailbox: yramberg at cisco.com, ysnir at cisco.com,
john.strassner at intelliden.com,
ronc at lyciumnetworks.com, remoore at us.ibm.com
I-D Tag: draft-ietf-policy-qos-info-model-05.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
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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at 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.
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Date: Wed, 19 Nov 2003 10:24:19 +0100
More information about the sg16-avd