[Dime] RFC 5777 on Traffic Classification and Quality of Service (QoS) Attributes for Diameter

rfc-editor@rfc-editor.org Fri, 12 February 2010 20:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20D3D28C22F; Fri, 12 Feb 2010 12:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level:
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[AWL=-0.347, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6]
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 26LTIN1susBs; Fri, 12 Feb 2010 12:42:31 -0800 (PST)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 6F26728C22E; Fri, 12 Feb 2010 12:42:31 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 799E9130007; Fri, 12 Feb 2010 12:43:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100212204351.799E9130007@rfc-editor.org>
Date: Fri, 12 Feb 2010 12:43:51 -0800
Cc: dime@ietf.org, rfc-editor@rfc-editor.org
Subject: [Dime] RFC 5777 on Traffic Classification and Quality of Service (QoS) Attributes for Diameter
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2010 20:42:32 -0000

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

        
        RFC 5777

        Title:      Traffic Classification and Quality of 
                    Service (QoS) Attributes for Diameter 
        Author:     J. Korhonen, H. Tschofenig,
                    M. Arumaithurai, M. Jones,
                      Ed., A. Lior
        Status:     Standards Track
        Date:       February 2010
        Mailbox:    jouni.korhonen@nsn.com, 
                    Hannes.Tschofenig@gmx.net, 
                    mayutan.arumaithurai@gmail.com,  
                    mark.jones@bridgewatersystems.com, 
                    avi@bridgewatersystems.com
        Pages:      43
        Characters: 91305
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dime-qos-attributes-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5777.txt

This document defines a number of Diameter attribute-value pairs
(AVPs) for traffic classification with actions for filtering and
Quality of Service (QoS) treatment.  These AVPs can be used in
existing and future Diameter applications where permitted by the
Augmented Backus-Naur Form (ABNF) specification of the respective
Diameter command extension policy.  [STANDARDS TRACK]

This document is a product of the Diameter Maintanence and Extensions Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC