[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-ietf-policy-qos-device-info-model-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Policy Framework Working Group of the IETF.

	Title		: Information Model for Describing Network Device QoS 
                          Datapath Mechanisms
	Author(s)	: B. Moore, D. Durham, J. Halpern, 
                          J. Strassner, A. Westerinen, W. Weiss
	Filename	: draft-ietf-policy-qos-device-info-model-04.txt
	Pages		: 94
	Date		: 08-Jun-01
The purpose of this draft is to define an information model to
describe the quality of service (QoS) mechanisms inherent in
different network devices, including hosts.  Broadly speaking,
these mechanisms describe the attributes common to selecting and
conditioning traffic through the forwarding path (datapath) of a
network device.  This selection and conditioning of traffic in
the datapath spans both major QoS architectures: Differentiated
Services (see [R2475]) and Integrated Services (see [R1633]).

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-policy-qos-device-info-model-04.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-policy-qos-device-info-model-04.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Content-type: text/plain