RFC 7752 on North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
rfc-editor@rfc-editor.org Wed, 16 March 2016 22:57 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A2A12D71F; Wed, 16 Mar 2016 15:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OTEOV66Ev6nP; Wed, 16 Mar 2016 15:57:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D7B012D591; Wed, 16 Mar 2016 15:57:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AF4CD180094; Wed, 16 Mar 2016 15:56:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7752 on North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160316225656.AF4CD180094@rfc-editor.org>
Date: Wed, 16 Mar 2016 15:56:56 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/kd9zfb7sFEP-Fwyb0HixCXgJ84w>
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 16 Mar 2016 22:57:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7752
Title: North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP
Author: H. Gredler, Ed.,
J. Medved, S. Previdi,
A. Farrel, S. Ray
Status: Standards Track
Stream: IETF
Date: March 2016
Mailbox: hannes@gredler.at,
jmedved@cisco.com,
sprevidi@cisco.com,
adrian@olddog.co.uk,
raysaikat@gmail.com
Pages: 48
Characters: 113130
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-ls-distribution-13.txt
URL: https://www.rfc-editor.org/info/rfc7752
DOI: http://dx.doi.org/10.17487/RFC7752
In a number of environments, a component external to a network is
called upon to perform computations based on the network topology and
current state of the connections within the network, including
Traffic Engineering (TE) information. This is information typically
distributed by IGP routing protocols within the network.
This document describes a mechanism by which link-state and TE
information can be collected from networks and shared with external
components using the BGP routing protocol. This is achieved using a
new BGP Network Layer Reachability Information (NLRI) encoding
format. The mechanism is applicable to physical and virtual IGP
links. The mechanism described is subject to policy control.
Applications of this technique include Application-Layer Traffic
Optimization (ALTO) servers and Path Computation Elements (PCEs).
This document is a product of the Inter-Domain Routing Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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