RFC 4874 on Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
rfc-editor@rfc-editor.org Tue, 10 April 2007 18:21 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HbKxu-00006X-40; Tue, 10 Apr 2007 14:21:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HbKxr-00006Q-So for ietf-announce@ietf.org; Tue, 10 Apr 2007 14:21:11 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbKxq-0007FT-Ga for ietf-announce@ietf.org; Tue, 10 Apr 2007 14:21:11 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l3AILAuC023100; Tue, 10 Apr 2007 11:21:10 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l3AIL9gX023099; Tue, 10 Apr 2007 11:21:09 -0700
Date: Tue, 10 Apr 2007 11:21:09 -0700
Message-Id: <200704101821.l3AIL9gX023099@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: ccamp@ops.ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4874 on Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4874
Title: Exclude Routes - Extension to
Resource ReserVation Protocol-Traffic Engineering
(RSVP-TE)
Author: CY. Lee, A. Farrel,
S. De Cnodder
Status: Standards Track
Date: April 2007
Mailbox: c.yin.lee@gmail.com,
adrian@olddog.co.uk,
stefaan.de_cnodder@alcatel-lucent.be
Pages: 27
Characters: 59569
Updates: RFC3209, RFC3473
See-Also:
I-D Tag: draft-ietf-ccamp-rsvp-te-exclude-route-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4874.txt
This document specifies ways to communicate route exclusions during
path setup using Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE).
The RSVP-TE specification, "RSVP-TE: Extensions to RSVP for LSP
Tunnels" (RFC 3209) and GMPLS extensions to RSVP-TE, "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE) Extensions" (RFC 3473) allow
abstract nodes and resources to be explicitly included in a path
setup, but not to be explicitly excluded.
In some networkto 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
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce