[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fw: [Isis-wg] RFC 4205 on Intermediate System to Intermediate System(IS-IS) Extensions in Support of Generalized Multi-ProtocolLabel Switching (GMPLS)
- To: <ccamp@ops.ietf.org>
- Subject: Fw: [Isis-wg] RFC 4205 on Intermediate System to Intermediate System(IS-IS) Extensions in Support of Generalized Multi-ProtocolLabel Switching (GMPLS)
- From: "Adrian Farrel" <adrian@olddog.co.uk>
- Date: Sun, 6 Nov 2005 06:37:15 -0000
- Reply-to: "Adrian Farrel" <adrian@olddog.co.uk>
I think we missed seeing this announcement on the CCAMP list.
Adrian
----- Original Message -----
From: <rfc-editor@rfc-editor.org>
To: <ietf-announce@ietf.org>
Cc: <isis-wg@ietf.org>; <rfc-editor@rfc-editor.org>
Sent: Friday, October 28, 2005 12:14 AM
Subject: [Isis-wg] RFC 4205 on Intermediate System to Intermediate
System(IS-IS) Extensions in Support of Generalized Multi-ProtocolLabel
Switching (GMPLS)
>
> A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4205
>
> Title: Intermediate System to Intermediate System (IS-IS)
> Extensions in Support of Generalized
> Multi-Protocol Label Switching (GMPLS)
> Author(s): K. Kompella, Ed., Y. Rekhter, Ed.
> Status: Informational
> Date: October 2005
> Mailbox: kireeti@juniper.net, yakov@juniper.net
> Pages: 11
> Characters: 22323
> Updates: 3784
>
> I-D Tag: draft-ietf-isis-gmpls-extensions-19.txt
>
> URL: ftp://ftp.rfc-editor.org/in-notes/rfc4205.txt
>
>
> This document specifies encoding of extensions to the IS-IS routing
> protocol in support of Generalized Multi-Protocol Label Switching
> (GMPLS).
>
> This document is a product of the IS-IS for IP Internets Working Group
> of the IETF.
>
> 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.
>
>
> 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.
>
--------------------------------------------------------------------------
------
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
>