RFC 3260 on New Terminology and Clarifications for Diffserv
RFC Editor <rfc-ed@ISI.EDU> Wed, 17 April 2002 00:06 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08458; Tue, 16 Apr 2002 20:06:24 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA09429 for ietf-123-outbound.10@ietf.org; Tue, 16 Apr 2002 20:05: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 TAA09313 for <all-ietf@loki.ietf.org>; Tue, 16 Apr 2002 19:52:07 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06848; Tue, 16 Apr 2002 19:52:04 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g3GNq5m04408; Tue, 16 Apr 2002 16:52:05 -0700 (PDT)
Message-Id: <200204162352.g3GNq5m04408@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3260 on New Terminology and Clarifications for Diffserv
Cc: rfc-editor@rfc-editor.org, diffserv@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 16 Apr 2002 16:52:05 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3260 Title: New Terminology and Clarifications for Diffserv Author(s): D. Grossman Status: Informational Date: April 2002 Mailbox: dan@dma.isg.mot.com Pages: 10 Characters: 21900 Updates: 2474, 2475, 2597 I-D Tag: draft-ietf-diffserv-new-terms-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3260.txt This memo captures Diffserv working group agreements concerning new and improved terminology, and provides minor technical clarifications. It is intended to update RFC 2474, RFC 2475 and RFC 2597. When RFCs 2474 and 2597 advance on the standards track, and RFC 2475 is updated, it is intended that the revisions in this memo will be incorporated, and that this memo will be obsoleted by the new RFCs. This document is a product of the Differentiated Services 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.