RFC 7570 on Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
rfc-editor@rfc-editor.org Thu, 09 July 2015 22:40 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FA31A1BB4; Thu, 9 Jul 2015 15:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3HGPk1xYVJC; Thu, 9 Jul 2015 15:40:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id EB1141A1BB5; Thu, 9 Jul 2015 15:40:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F18A180206; Thu, 9 Jul 2015 15:36:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7570 on Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150709223632.5F18A180206@rfc-editor.org>
Date: Thu, 09 Jul 2015 15:36:32 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/aEwGDU9Wj3OchHqKC7bUOmbUX9U>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 09 Jul 2015 22:40:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7570
Title: Label Switched Path (LSP) Attribute
in the Explicit Route Object (ERO)
Author: C. Margaria, Ed., G. Martinelli,
S. Balls, B. Wright
Status: Standards Track
Stream: IETF
Date: July 2015
Mailbox: cmargaria@juniper.net,
giomarti@cisco.com,
steve.balls@metaswitch.com,
ben.wright@metaswitch.com
Pages: 15
Characters: 34223
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-lsp-attribute-ro-05.txt
URL: https://www.rfc-editor.org/info/rfc7570
DOI: http://dx.doi.org/10.17487/RFC7570
RFC 5420 extends RSVP-TE to specify or record generic attributes that
apply to the whole of the path of a Label Switched Path (LSP). This
document defines an extension to the RSVP Explicit Route Object (ERO)
and Record Route Object (RRO) to allow them to specify or record
generic attributes that apply to a given hop.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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