Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
RFC 7926
Document | Type |
RFC - Best Current Practice
(July 2016; No errata)
Also known as BCP 206
|
|
---|---|---|---|
Last updated | 2018-12-20 | ||
Replaces | draft-ietf-ccamp-interconnected-te-info-exchange | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Lou Berger | ||
Shepherd write-up | Show (last changed 2016-03-22) | ||
IESG | IESG state | RFC 7926 (Best Current Practice) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Deborah Brungard | ||
Send notices to | "Lou Berger" <lberger@labn.net> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) A. Farrel, Ed. Request for Comments: 7926 J. Drake BCP: 206 Juniper Networks Category: Best Current Practice N. Bitar ISSN: 2070-1721 Nokia G. Swallow Cisco Systems, Inc. D. Ceccarelli Ericsson X. Zhang Huawei July 2016 Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks Abstract 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. Farrel, et al. Best Current Practice [Page 1] RFC 7926 Information Exchange between TE Networks July 2016 Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7926. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Farrel, et al. Best Current Practice [Page 2] RFC 7926 Information Exchange between TE Networks July 2016 Table of Contents 1. Introduction ....................................................5 1.1. Terminology ................................................6 1.1.1. TE Paths and TE Connections .........................6 1.1.2. TE Metrics and TE Attributes ........................6 1.1.3. TE Reachability .....................................7 1.1.4. Domain ..............................................7 1.1.5. Server Network ......................................7 1.1.6. Client Network ......................................7 1.1.7. Aggregation .........................................7 1.1.8. Abstraction .........................................8 1.1.9. Abstract Link .......................................8 1.1.10. Abstract Node or Virtual Node ......................8 1.1.11. Abstraction Layer Network ..........................9 2. Overview of Use Cases ...........................................9Show full document text