[Tsvwg] RFC 5127 on Aggregation of DiffServ Service Classes
rfc-editor@rfc-editor.org Sat, 23 February 2008 01:15 UTC
Return-Path: <tsvwg-bounces@ietf.org>
X-Original-To: ietfarch-tsvwg-archive@core3.amsl.com
Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 865DB28C663; Fri, 22 Feb 2008 17:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.737
X-Spam-Level:
X-Spam-Status: No, score=-16.737 tagged_above=-999 required=5 tests=[AWL=0.862, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLHfa+EITcCk; Fri, 22 Feb 2008 17:15:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01FE428C4BE; Fri, 22 Feb 2008 17:11:46 -0800 (PST)
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EB3628C4BE; Fri, 22 Feb 2008 17:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kOXb89Ngf1J; Fri, 22 Feb 2008 17:11:42 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 6622028C499; Fri, 22 Feb 2008 17:11:42 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 7AF871158DB; Fri, 22 Feb 2008 17:11:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080223011138.7AF871158DB@bosco.isi.edu>
Date: Fri, 22 Feb 2008 17:11:38 -0800
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] RFC 5127 on Aggregation of DiffServ Service Classes
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 5127 Title: Aggregation of DiffServ Service Classes Author: K. Chan, J. Babiarz, F. Baker Status: Informational Date: February 2008 Mailbox: khchan@nortel.com, babiarz@nortel.com, fred@cisco.com Pages: 19 Characters: 43751 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-diffserv-class-aggr-07.txt URL: http://www.rfc-editor.org/rfc/rfc5127.txt In the core of a high-capacity network, service differentiation may still be needed to support applications' utilization of the network. Applications with similar traffic characteristics and performance requirements are mapped into Diffserv service classes based on end- to-end behavior requirements of the applications. However, some network segments may be configured in such a way that a single forwarding treatment may satisfy the traffic characteristics and performance requirements of two or more service classes. In these cases, it may be desirable to aggregate two or more Diffserv service classes into a single forwarding treatment. This document provides guidelines for the aggregation of Diffserv service classes into forwarding treatments. This memo provides information for the Internet community. This document is a product of the Transport Area Working Group Working Group of the IETF. INFORMATIONAL: 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. 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. The RFC Editor Team USC/Information Sciences Institute ...