Profiles for Traffic Engineering (TE) Topology Data Model
draft-busi-teas-te-topology-profiles-00
TEAS Working Group Italo Busi
Internet Draft Huawei
Intended status: Informational Xufeng Liu
Volta Networks
Igor Bryskin
Individual
Vishnu Pavan Beeram
Tarek Saad
Juniper Networks
Oscar Gonzalez de Dios
Telefonica
Expires: July 2021 January 11, 2021
Profiles for Traffic Engineering (TE) Topology Data Model
draft-busi-teas-te-topology-profiles-00
Abstract
This document describes how profiles of the Traffic Engineering (TE)
Topology Model, defined in RFC8795, can be used to address
applications beyond "Traffic Engineering".
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Busi, et al. Expires July 11, 2021 [Page 1]
Internet-Draft TE Topology Profiles January 2021
This Internet-Draft will expire on July 11, 2021.
Copyright Notice
Copyright (c) 2021 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.
Table of Contents
1. Introduction...................................................2
2. Examples of non-TE scenarios...................................3
2.1. UNI Topology Discovery....................................3
2.2. Administrative and Operational status management..........5
2.3. Geolocation...............................................7
2.4. Overlay and Underlay non-TE Topologies....................8
2.5. Nodes with switching limitations.........................10
3. Technology-specific augmentations.............................11
4. Security Considerations.......................................13
5. IANA Considerations...........................................13
6. References....................................................14
6.1. Normative References.....................................14
6.2. Informative References...................................14
Acknowledgments..................................................14
Contributors.....................................................14
Authors' Addresses...............................................15
1. Introduction
There are many network scenarios being discussed in various IETF
Working Groups (WGs) that are not classified as "Traffic Engineering"
but can be addressed by a sub-set (profile) of the Traffic
Engineering (TE) Topology YANG data model, defined in [RFC8795].
Traffic Engineering (TE) is defined in [RFC3272bis] as aspects of
Internet network engineering that deal with the issues of performance
evaluation and performance optimization of operational IP networks.
Busi, et al. Expires July 11, 2021 [Page 2]
Internet-Draft TE Topology Profiles January 2021
TE encompasses the application of technology and scientific
principles to the measurement, characterization, modeling, and
control of Internet traffic.
The TE Topology Model is augmenting the Network Topology Model
defined in [RFC8345] with generic and technology-agnostic features
Show full document text