RFC 5145 on Framework for MPLS-TE to GMPLS Migration

rfc-editor@rfc-editor.org Fri, 21 March 2008 23:37 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C73728C6FA; Fri, 21 Mar 2008 16:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.693
X-Spam-Level:
X-Spam-Status: No, score=-100.693 tagged_above=-999 required=5 tests=[AWL=-0.256, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Llh2xFrd8qL; Fri, 21 Mar 2008 16:37:16 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAE9328C3F5; Fri, 21 Mar 2008 16:35:22 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 226AD28C3F5 for <ietf-announce@core3.amsl.com>; Fri, 21 Mar 2008 16:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uk9NZP1CyCW0 for <ietf-announce@core3.amsl.com>; Fri, 21 Mar 2008 16:35:21 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id A13823A6DED for <ietf-announce@ietf.org>; Fri, 21 Mar 2008 16:35:17 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 155F8120686; Fri, 21 Mar 2008 16:33:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5145 on Framework for MPLS-TE to GMPLS Migration
From: rfc-editor@rfc-editor.org
Message-Id: <20080321233300.155F8120686@bosco.isi.edu>
Date: Fri, 21 Mar 2008 16:33:00 -0700
Cc: ccamp@ops.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5145

        Title:      Framework for MPLS-TE to GMPLS 
                    Migration 
        Author:     K. Shiomoto, Ed.
        Status:     Informational
        Date:       March 2008
        Mailbox:    shiomoto.kohei@lab.ntt.co.jp
        Pages:      19
        Characters: 44646
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-05.txt

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

The migration from Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) to Generalized MPLS (GMPLS) is the process of
evolving an MPLS-TE control plane to a GMPLS control plane.  An
appropriate migration strategy will be selected based on various
factors including the service provider's network deployment plan,
customer demand, and operational policy.

This document presents several migration models and strategies for
migrating from MPLS-TE to GMPLS.  In the course of migration, MPLS-TE
and GMPLS devices, or networks, may coexist that may require
interworking between MPLS-TE and GMPLS protocols.  Aspects of the
required interworking are discussed as it will influence the choice
of a migration strategy.  This framework document provides a migration
toolkit to aid the operator in selection of an appropriate strategy.

This framework document also lists a set of solutions that may aid in
interworking, and highlights a set of potential issues.  This memo provides information for the Internet community.

This document is a product of the Common Control and Measurement Plane Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce