RFC 6401 on RSVP Extensions for Admission Priority

rfc-editor@rfc-editor.org Tue, 01 November 2011 04:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 20F7621F8EF7; Mon, 31 Oct 2011 21:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.646
X-Spam-Status: No, score=-103.646 tagged_above=-999 required=5 tests=[AWL=1.431, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id gcib5PWeR9jE; Mon, 31 Oct 2011 21:57:00 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3868521F8EFE; Mon, 31 Oct 2011 21:57:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 068A0B1E00D; Mon, 31 Oct 2011 21:52:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6401 on RSVP Extensions for Admission Priority
From: rfc-editor@rfc-editor.org
Message-Id: <20111101045242.068A0B1E00D@rfc-editor.org>
Date: Mon, 31 Oct 2011 21:52:42 -0700
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 01 Nov 2011 04:57:02 -0000

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

        RFC 6401

        Title:      RSVP Extensions for Admission Priority 
        Author:     F. Le Faucheur, J. Polk,
                    K. Carlberg
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2011
        Mailbox:    flefauch@cisco.com, 
        Pages:      32
        Characters: 72343
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-emergency-rsvp-15.txt

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

Some applications require the ability to provide an elevated
probability of session establishment to specific sessions in times of
network congestion.  When supported over the Internet Protocol suite,
this may be facilitated through a network-layer admission control
solution that supports prioritized access to resources (e.g.,
bandwidth).  These resources may be explicitly set aside for
prioritized sessions, or may be shared with other sessions.  This
document specifies extensions to the Resource reSerVation Protocol
(RSVP) that can be used to support such an admission priority
capability at the network layer.

Based on current security concerns, these extensions are intended for
use in a single administrative domain.  [STANDARDS-TRACK]

This document is a product of the Transport Area Working Group 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

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