RFC 5786 on Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions

rfc-editor@rfc-editor.org Wed, 10 March 2010 19:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 338C43A6A11; Wed, 10 Mar 2010 11:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id UkENO9FPyTe2; Wed, 10 Mar 2010 11:21:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id D938E3A6C44; Wed, 10 Mar 2010 11:18:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 55415E0740; Wed, 10 Mar 2010 11:18:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5786 on Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions
From: rfc-editor@rfc-editor.org
Message-Id: <20100310191841.55415E0740@rfc-editor.org>
Date: Wed, 10 Mar 2010 11:18:41 -0800
Cc: ospf@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 19:21:13 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5786

        Title:      Advertising a Router's Local Addresses 
                    in OSPF Traffic Engineering (TE) Extensions 
        Author:     R. Aggarwal, K. Kompella
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    rahul@juniper.net, 
        Pages:      7
        Characters: 15541
        Updates:    RFC3630

        I-D Tag:    draft-ietf-ospf-te-node-addr-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5786.txt

OSPF Traffic Engineering (TE) extensions are used to advertise TE
Link State Advertisements (LSAs) containing information about TE-enabled
links.  The only addresses belonging to a router that are
advertised in TE LSAs are the local addresses corresponding to TE-enabled
links, and the local address corresponding to the Router ID.

In order to allow other routers in a network to compute Multiprotocol
Label Switching (MPLS) Traffic Engineered Label Switched Paths (TE
LSPs) to a given router's local addresses, those addresses must also
be advertised by OSPF TE.

This document describes procedures that enhance OSPF TE to advertise
a router's local addresses.  [STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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
Association Management Solutions, LLC