RFC 4202 on Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
rfc-editor@rfc-editor.org Fri, 28 October 2005 00:15 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVHuM-0001Na-17 for ccamp-archive@megatron.ietf.org; Thu, 27 Oct 2005 20:15:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29405 for <ccamp-archive@ietf.org>; Thu, 27 Oct 2005 20:15:28 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVI7o-0006qI-UD for ccamp-archive@ietf.org; Thu, 27 Oct 2005 20:29:41 -0400
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD)) id 1EVHpq-0003PC-R5 for ccamp-data@psg.com; Fri, 28 Oct 2005 00:11:06 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00, MIME_BOUND_NEXTPART,NO_REAL_NAME autolearn=no version=3.1.0
Received: from [128.9.160.161] (helo=boreas.isi.edu) by psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1EVHpq-0003P1-51 for ccamp@ops.ietf.org; Fri, 28 Oct 2005 00:11:06 +0000
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j9S0AWL16553; Thu, 27 Oct 2005 17:10:32 -0700 (PDT)
Message-Id: <200510280010.j9S0AWL16553@boreas.isi.edu>
To: ietf-announce@ietf.org
Subject: RFC 4202 on Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Cc: rfc-editor@rfc-editor.org, ccamp@ops.ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 27 Oct 2005 17:10:32 -0700
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
A new Request for Comments is now available in online RFC libraries. RFC 4202 Title: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) Author(s): K. Kompella, Ed., Y. Rekhter, Ed. Status: Standards Track Date: October 2005 Mailbox: kireeti@juniper.net, yakov@juniper.net Pages: 27 Characters: 57333 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-routing-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4202.txt This document specifies routing extensions in support of carrying link state information for Generalized Multi-Protocol Label Switching (GMPLS). This document enhances the routing extensions required to support MPLS Traffic Engineering (TE). This document is a product of the Common Control and Measurement Plane Working Group of the IETF. This is now a Proposed Standard Protocol. 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 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.