RFC 6107 on Procedures for Dynamically Signaled Hierarchical Label Switched Paths

rfc-editor@rfc-editor.org Thu, 03 February 2011 04:01 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 []) by core3.amsl.com (Postfix) with ESMTP id A83E43A67EC; Wed, 2 Feb 2011 20:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.008
X-Spam-Status: No, score=-102.008 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4wnRte9C7Tq8; Wed, 2 Feb 2011 20:01:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 502D13A67EE; Wed, 2 Feb 2011 20:01:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E2F73E0749; Wed, 2 Feb 2011 20:04:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6107 on Procedures for Dynamically Signaled Hierarchical Label Switched Paths
From: rfc-editor@rfc-editor.org
Message-Id: <20110203040430.E2F73E0749@rfc-editor.org>
Date: Wed, 02 Feb 2011 20:04:30 -0800
Cc: ccamp@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: Thu, 03 Feb 2011 04:01:24 -0000

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

        RFC 6107

        Title:      Procedures for Dynamically Signaled Hierarchical 
                    Label Switched Paths 
        Author:     K. Shiomoto, Ed.,
                    A. Farrel, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2011
        Mailbox:    shiomoto.kohei@lab.ntt.co.jp, 
        Pages:      30
        Characters: 65363
        Updates:    RFC3477, RFC4206

        I-D Tag:    draft-ietf-ccamp-lsp-hierarchy-bis-08.txt

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

Label Switched Paths (LSPs) set up in Multiprotocol Label Switching
(MPLS) or Generalized MPLS (GMPLS) networks can be used to form links
to carry traffic in those networks or in other (client) networks.

Protocol mechanisms already exist to facilitate the establishment of
such LSPs and to bundle traffic engineering (TE) links to reduce the load on
routing protocols.  This document defines extensions to those mechanisms to
support identifying the use to which such LSPs are to be put and to
enable the TE link endpoints to be assigned addresses or unnumbered
identifiers during the signaling process.  [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

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