Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 67
- 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.
- Publication Date
- 2016-07-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC7926- Link
- https://doi.org/10.17487/RFC7926
- Author(s)
- Adrian FarrelJohn DrakeNabil BitarGeorge SwallowDaniele CeccarelliXian Zhang
- Keyword(s)
- Abstract Link, Abstract Node, Virtual Node, Virtual Link
Latest version of IETF RFC 7926
Document Versions — IETF RFC 7926
-
▶ IETF RFC 7926 (2016-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF draft-beeram-ccamp-gmpls-enni-03 [Active*]
- IETF.draft-ietf-teas-lsp-diversity-05 — RSVP-TE-EXCL EXTERNAL
- IETF.draft-ietf-teas-rsvp-te-srlg-collect-06 — RSVP-TE-EXT EXTERNAL
- IETF.draft-ietf-teas-te-metric-recording-04 — RSVP-TE-METRIC EXTERNAL
- IETF RFC 2702 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3473 [Active*]
- IETF RFC 3630 [Active*]
- IETF RFC 3945 [Active*]
- IETF RFC 4105 [Active*]
- IETF RFC 4202 [Active*]
- IETF RFC 4206 [Active*]
- IETF RFC 4208 [Active*]
- IETF RFC 4216 [Active*]
- IETF RFC 4271 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 4726 [Active*]
- IETF RFC 4847 [Active*]
- IETF RFC 4874 [Active*]
- IETF RFC 4920 [Active*]
- IETF RFC 5150 [Active*]
- IETF RFC 5152 [Active*]
- IETF RFC 5195 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5251 [Active*]
- IETF RFC 5252 [Active*]
- IETF RFC 5305 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5441 [Active*]
- IETF RFC 5523 [Active*]
- IETF RFC 5553 [Active*]
- IETF RFC 5623 [Active*]
- IETF RFC 5920 [Active*]
- IETF RFC 5925 [Active*]
- IETF RFC 6005 [Active*]
- IETF RFC 6071 [Active*]
- IETF RFC 6107 [Active*]
- IETF RFC 6805 [Active*]
- IETF RFC 6827 [Active*]
- IETF RFC 6996 [Active*]
- IETF RFC 7399 [Active*]
- IETF RFC 7579 [Active*]
- IETF RFC 7580 [Active*]
- IETF RFC 7752 [Superseded*]
- T-REC-G.8080.2012 — G.8080 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7926.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7926, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks. Available at https://doi.org/10.17487/RFC7926
Snippet:
IETF RFC 7926, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks. Available at https://doi.org/10.17487/RFC7926
HTML (ISO 690 compliant)
Preview:
IETF RFC 7926, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks. Available at https://doi.org/10.17487/RFC7926
Snippet:
<span class="citation"><cite>IETF RFC 7926</cite>, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks. Available at <a href="https://doi.org/10.17487/RFC7926" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7926</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7926, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
doi: 10.17487/RFC7926
url: https://doi.org/10.17487/RFC7926
doi: 10.17487/RFC7926
url: https://doi.org/10.17487/RFC7926
Snippet:
<li> <cite id="bib-rfc7926">IETF RFC 7926</cite>, Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks <span class="doi">10.17487/RFC7926</span> </li>
Referenced By
- IETF RFC 8453 [Active*]
- IETF RFC 8795 [Active*]
- IETF RFC 9522 [Active*]