RFC 6510 on Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects
rfc-editor@rfc-editor.org Mon, 20 February 2012 22:58 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F4921E8025; Mon, 20 Feb 2012 14:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.279
X-Spam-Level:
X-Spam-Status: No, score=-102.279 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbrRNs8K5-Pt; Mon, 20 Feb 2012 14:58:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id C3A2321E8026; Mon, 20 Feb 2012 14:58:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5ED02B1E004; Mon, 20 Feb 2012 14:53:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6510 on Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects
From: rfc-editor@rfc-editor.org
Message-Id: <20120220225304.5ED02B1E004@rfc-editor.org>
Date: Mon, 20 Feb 2012 14:53:04 -0800
Cc: ccamp@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: Mon, 20 Feb 2012 22:58:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6510
Title: Resource Reservation Protocol (RSVP) Message
Formats for Label Switched Path (LSP)
Attributes Objects
Author: L. Berger, G. Swallow
Status: Standards Track
Stream: IETF
Date: February 2012
Mailbox: lberger@labn.net,
swallow@cisco.com
Pages: 8
Characters: 16650
Updates: RFC4875, RFC5420
I-D Tag: draft-ietf-ccamp-attribute-bnf-02.txt
URL: http://www.rfc-editor.org/rfc/rfc6510.txt
Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
established using the Resource Reservation Protocol Traffic
Engineering (RSVP-TE) extensions may be signaled with a set of LSP-specific
attributes. These attributes may be carried in both Path
and Resv messages. This document specifies how LSP attributes are
to be carried in RSVP Path and Resv messages using the Routing
Backus-Naur Form and clarifies related Resv message formats.
This document updates RFC 4875 and RFC 5420. [STANDARDS-TRACK]
This document is a product of the Common Control and Measurement Plane 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