%% You should probably cite rfc7926 instead of this I-D. @techreport{ietf-teas-interconnected-te-info-exchange-04, number = {draft-ietf-teas-interconnected-te-info-exchange-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-teas-interconnected-te-info-exchange/04/}, author = {Adrian Farrel and John Drake and Nabil Bitar and George Swallow and Daniele Ceccarelli and Xian Zhang}, title = {{Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks}}, pagetotal = 60, year = 2016, month = mar, day = 20, 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 network 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 and architecture for the exchange of TE information between interconnected TE networks in support of end-to-end TE path establishment. For reasons that are explained in the document, this work is limited to simple TE constraints and information that determine TE reachability.}, }