Subject: Fw: RFC 4203 on OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

From: Adrian Farrel <[email-masked]>
Date: Fri, 28 Oct 2005 11:06:52 +0100

Hi,

I think this announcement should have been shared on the OSPF list.

Adrian
----- Original Message ----- 
From: <[email-masked]>
To: <[email-masked]>
Cc: <[email-masked]>; <[email-masked]>
Sent: Friday, October 28, 2005 1:11 AM
Subject: RFC 4203 on OSPF Extensions in Support of Generalized
Multi-Protocol Label Switching (GMPLS)

>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 4203
>
>         Title:      OSPF 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:    [email-masked], [email-masked]
>         Pages:      11
>         Characters: 23130
>         Updates:    3630
>
>         I-D Tag:    draft-ietf-ccamp-ospf-gmpls-extensions-12.txt
>
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4203.txt
>
>
> This document specifies encoding of extensions to the OSPF routing
> protocol in support of Generalized Multi-Protocol Label Switching
> (GMPLS).
>
> 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 [email-masked].  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to [email-masked].
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to [email-masked] with the message body
> help: ways_to_get_rfcs.  For example:
>
>         To: [email-masked]
>         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 [email-masked].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> [email-masked].  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.
>