RFC 5212 on Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
rfc-editor@rfc-editor.org Wed, 09 July 2008 23:42 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 DD73F3A684B for <ietfarch-ccamp-archive@core3.amsl.com>; Wed, 9 Jul 2008 16:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level:
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[AWL=-0.597, 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 cB5jrbw85UvI for <ietfarch-ccamp-archive@core3.amsl.com>; Wed, 9 Jul 2008 16:42:53 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id E429B3A6822 for <ccamp-archive@ietf.org>; Wed, 9 Jul 2008 16:42:52 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1KGjE4-0007Rn-Qr for ccamp-data@psg.com; Wed, 09 Jul 2008 23:37:32 +0000
Received: from [128.9.168.207] (helo=bosco.isi.edu) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <rfc-editor@rfc-editor.org>) id 1KGjDl-0007Pp-Fj for ccamp@ops.ietf.org; Wed, 09 Jul 2008 23:37:23 +0000
Received: by bosco.isi.edu (Postfix, from userid 70) id E5F6F141CF8; Wed, 9 Jul 2008 16:37:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5212 on Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ccamp@ops.ietf.org
Message-Id: <20080709233712.E5F6F141CF8@bosco.isi.edu>
Date: Wed, 09 Jul 2008 16:37:12 -0700
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
List-ID: <ccamp.ops.ietf.org>
A new Request for Comments is now available in online RFC libraries. RFC 5212 Title: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) Author: K. Shiomoto, D. Papadimitriou, JL. Le Roux, M. Vigoureux, D. Brungard Status: Informational Date: July 2008 Mailbox: shiomoto.kohei@lab.ntt.co.jp, dimitri.papadimitriou@alcatel-lucent.be, jeanlouis.leroux@orange-ftgroup.com, martin.vigoureux@alcatel-lucent.fr, dbrungard@att.com Pages: 28 Characters: 70286 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-mln-reqs-11.txt URL: http://www.rfc-editor.org/rfc/rfc5212.txt Most of the initial efforts to utilize Generalized MPLS (GMPLS) have been related to environments hosting devices with a single switching capability. The complexity raised by the control of such data planes is similar to that seen in classical IP/MPLS networks. By extending MPLS to support multiple switching technologies, GMPLS provides a comprehensive framework for the control of a multi-layered network of either a single switching technology or multiple switching technologies. In GMPLS, a switching technology domain defines a region, and a network of multiple switching types is referred to in this document as a multi-region network (MRN). When referring in general to a layered network, which may consist of either single or multiple regions, this document uses the term multi-layer network (MLN). This document defines a framework for GMPLS based multi-region / multi-layer networks and lists a set of functional requirements. 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-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 USC/Information Sciences Institute