RFC 5146 on Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
rfc-editor@rfc-editor.org Fri, 21 March 2008 23:44 UTC
Return-Path: <owner-ccamp@ops.ietf.org>
X-Original-To: ietfarch-ccamp-archive@core3.amsl.com
Delivered-To: ietfarch-ccamp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 981923A6E11 for <ietfarch-ccamp-archive@core3.amsl.com>; Fri, 21 Mar 2008 16:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.977
X-Spam-Level:
X-Spam-Status: No, score=-0.977 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
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 erX1miRxTkXo for <ietfarch-ccamp-archive@core3.amsl.com>; Fri, 21 Mar 2008 16:44:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id BDF783A6E1B for <ccamp-archive@ietf.org>; Fri, 21 Mar 2008 16:41:40 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1Jcqjo-000N8x-8q for ccamp-data@psg.com; Fri, 21 Mar 2008 23:33:28 +0000
Received: from [128.9.168.207] (helo=bosco.isi.edu) by psg.com with esmtp (Exim 4.68 (FreeBSD)) (envelope-from <rfc-editor@rfc-editor.org>) id 1Jcqjl-000N8M-RD for ccamp@ops.ietf.org; Fri, 21 Mar 2008 23:33:26 +0000
Received: by bosco.isi.edu (Postfix, from userid 70) id AD37A120688; Fri, 21 Mar 2008 16:33:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5146 on Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ccamp@ops.ietf.org
Message-Id: <20080321233325.AD37A120688@bosco.isi.edu>
Date: Fri, 21 Mar 2008 16:33:25 -0700
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries.
RFC 5146
Title: Interworking Requirements to Support Operation
of MPLS-TE over GMPLS Networks
Author: K. Kumaki, Ed.
Status: Informational
Date: March 2008
Mailbox: ke-kumaki@kddi.com
Pages: 15
Characters: 31624
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ccamp-mpls-gmpls-interwork-reqts-04.txt
URL: http://www.rfc-editor.org/rfc/rfc5146.txt
Operation of a Multiprotocol Label Switching (MPLS) traffic
engineering (TE) network as a client network to a Generalized MPLS
(GMPLS) network has enhanced operational capabilities compared to
those provided by a coexistent protocol model (i.e., operation of
MPLS-TE over an independently managed transport layer).
The GMPLS network may be a packet or a non-packet network, and may
itself be a multi-layer network supporting both packet and non-packet
technologies. An MPLS-TE Label Switched Path (LSP) originates and
terminates on an MPLS Label Switching Router (LSR). The GMPLS network
provides transparent transport for the end-to-end MPLS-TE LSP.
This document describes a framework and Service Provider requirements
for operating MPLS-TE networks over GMPLS networks. 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
...