RFC 5543 on BGP Traffic Engineering Attribute
rfc-editor@rfc-editor.org Mon, 04 May 2009 23:49 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4081228C290; Mon, 4 May 2009 16:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.917
X-Spam-Level:
X-Spam-Status: No, score=-16.917 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70xc-hJhm2MY; Mon, 4 May 2009 16:49:09 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 770133A6B63; Mon, 4 May 2009 16:48:17 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 912B229B2BA; Mon, 4 May 2009 16:46:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5543 on BGP Traffic Engineering Attribute
From: rfc-editor@rfc-editor.org
Message-Id: <20090504234633.912B229B2BA@bosco.isi.edu>
Date: Mon, 04 May 2009 16:46:33 -0700
Cc: softwires@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: Mon, 04 May 2009 23:49:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5543
Title: BGP Traffic Engineering Attribute
Author: H. Ould-Brahim, D. Fedyk,
Y. Rekhter
Status: Standards Track
Date: May 2009
Mailbox: hbrahim@nortel.com,
donald.fedyk@alcatel-lucent.com,
yakov@juniper.com
Pages: 6
Characters: 11883
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-softwire-bgp-te-attribute-04.txt
URL: http://www.rfc-editor.org/rfc/rfc5543.txt
This document defines a new BGP attribute, the Traffic Engineering
attribute, that enables BGP to carry Traffic Engineering information.
The scope and applicability of this attribute currently excludes its
use for non-VPN reachability information. [STANDARDS TRACK]
This document is a product of the Softwires 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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
USC/Information Sciences Institute