RFC 5976 on Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes

rfc-editor@rfc-editor.org Wed, 06 October 2010 19:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 065903A71EF; Wed, 6 Oct 2010 12:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.294
X-Spam-Level:
X-Spam-Status: No, score=-102.294 tagged_above=-999 required=5 tests=[AWL=-0.306, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, USER_IN_WHITELIST=-100]
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 Lr43461vdj8b; Wed, 6 Oct 2010 12:15:43 -0700 (PDT)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 08E193A71E8; Wed, 6 Oct 2010 12:15:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E89BAE070E; Wed, 6 Oct 2010 12:16:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5976 on Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes
From: rfc-editor@rfc-editor.org
Message-Id: <20101006191639.E89BAE070E@rfc-editor.org>
Date: Wed, 06 Oct 2010 12:16:39 -0700
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 19:15:44 -0000

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

        
        RFC 5976

        Title:      Y.1541-QOSM: Model for Networks Using 
                    Y.1541 Quality-of-Service Classes 
        Author:     G. Ash, A. Morton,
                    M. Dolly, P. Tarapore,
                    C. Dvorak, Y. El Mghazli
        Status:     Experimental
        Stream:     IETF
        Date:       October 2010
        Mailbox:    gash5107@yahoo.com, 
                    acmorton@att.com, 
                    mdolly@att.com,  tarapore@att.com, 
                    cdvorak@att.com,  yacine.el_mghazli@alcatel.fr
        Pages:      19
        Characters: 42215
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-y1541-qosm-10.txt

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

This document describes a QoS-NSLP Quality-of-Service model (QOSM)
based on ITU-T Recommendation Y.1541 Network QoS Classes and related
guidance on signaling.  Y.1541 specifies 8 classes of Network
Performance objectives, and the Y.1541-QOSM extensions include
additional QSPEC parameters and QOSM processing guidelines.  
This document defines an Experimental Protocol for the Internet
community.

This document is a product of the Next Steps in Signaling Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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