[Teas] BCP 206, RFC 7926 on Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
rfc-editor@rfc-editor.org Wed, 27 July 2016 00:46 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B0512DA84; Tue, 26 Jul 2016 17:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, 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 krAxIzTPdOmf; Tue, 26 Jul 2016 17:46:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E238F12DA86; Tue, 26 Jul 2016 17:46:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DCE07B811BB; Tue, 26 Jul 2016 17:46:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160727004602.DCE07B811BB@rfc-editor.org>
Date: Tue, 26 Jul 2016 17:46:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/pCLBL2rtKg7WqtPPtAuMCgoMCWc>
Cc: teas@ietf.org, rfc-editor@rfc-editor.org
Subject: [Teas] BCP 206, RFC 7926 on Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2016 00:46:04 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 206
RFC 7926
Title: Problem Statement and Architecture for
Information Exchange between Interconnected
Traffic-Engineered Networks
Author: A. Farrel, Ed.,
J. Drake, N. Bitar,
G. Swallow, D. Ceccarelli,
X. Zhang
Status: Best Current Practice
Stream: IETF
Date: July 2016
Mailbox: adrian@olddog.co.uk,
jdrake@juniper.net,
nbitar40@gmail.com,
swallow@cisco.com,
daniele.ceccarelli@ericsson.com,
zhang.xian@huawei.com
Pages: 67
Characters: 159905
See Also: BCP 206
I-D Tag: draft-ietf-teas-interconnected-te-info-exchange-07.txt
URL: https://www.rfc-editor.org/info/rfc7926
DOI: http://dx.doi.org/10.17487/RFC7926
In Traffic-Engineered (TE) systems, it is sometimes desirable to
establish an end-to-end TE path with a set of constraints (such as
bandwidth) across one or more networks from a source to a
destination. TE information is the data relating to nodes and TE
links that is used in the process of selecting a TE path. TE
information is usually only available within a network. We call such
a zone of visibility of TE information a domain. An example of a
domain may be an IGP area or an Autonomous System.
In order to determine the potential to establish a TE path through a
series of connected networks, it is necessary to have available a
certain amount of TE information about each network. This need not
be the full set of TE information available within each network but
does need to express the potential of providing TE connectivity.
This subset of TE information is called TE reachability information.
This document sets out the problem statement for the exchange of TE
information between interconnected TE networks in support of
end-to-end TE path establishment and describes the best current
practice architecture to meet this problem statement. For reasons
that are explained in this document, this work is limited to simple
TE constraints and information that determine TE reachability.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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