[mpls] RFC 6511 on Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths

rfc-editor@rfc-editor.org Mon, 20 February 2012 22:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3615321E8033; Mon, 20 Feb 2012 14:58:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.799
X-Spam-Level:
X-Spam-Status: No, score=-103.799 tagged_above=-999 required=5 tests=[AWL=1.278, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uwmjo+TdZkV2; Mon, 20 Feb 2012 14:58:19 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 710E421E802D; Mon, 20 Feb 2012 14:58:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 05CC6B1E00C; Mon, 20 Feb 2012 14:53:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120220225315.05CC6B1E00C@rfc-editor.org>
Date: Mon, 20 Feb 2012 14:53:15 -0800
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6511 on Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 22:58:30 -0000

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

        
        RFC 6511

        Title:      Non-Penultimate Hop Popping Behavior and 
                    Out-of-Band Mapping for RSVP-TE Label Switched 
                    Paths 
        Author:     Z. Ali, G. Swallow,
                    R. Aggarwal
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2012
        Mailbox:    zali@cisco.com, 
                    swallow@cisco.com, 
                    raggarwa_1@yahoo.com
        Pages:      10
        Characters: 21767
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt

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

There are many deployment scenarios that require an egress Label
Switching Router (LSR) to receive binding of the Resource
Reservation Protocol - Traffic Engineering (RSVP-TE) Label Switched
Path (LSP) to an application and a payload identifier using
some "out-of-band" (OOB) mechanism.  This document defines
protocol mechanisms to address this requirement.  The procedures
described in this document are equally applicable for point-to-point (P2P)
and point-to-multipoint (P2MP) LSPs.  [STANDARDS-TRACK]

This document is a product of the Multiprotocol Label Switching 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