From d5ad593519aa7d72d7662c9ba02fc3dd95efc290 Mon Sep 17 00:00:00 2001 From: italobusi Date: Mon, 15 Jan 2024 10:49:12 +0100 Subject: [PATCH] Addressed comments form IETF 118 Removed geolocation example --- .../draft-busi-teas-te-topology-profiles.md | 47 +-- .../draft-busi-teas-te-topology-profiles.txt | 202 ++++------- .../draft-busi-teas-te-topology-profiles.xml | 343 ++++++++---------- 3 files changed, 224 insertions(+), 368 deletions(-) diff --git a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.md b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.md index ff25e54..c031b9c 100644 --- a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.md +++ b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.md @@ -6,7 +6,7 @@ title: > Applicability to non-TE Use Cases abbrev: TE Topology Profiles -docname: draft-busi-teas-te-topology-profiles-06 +docname: draft-busi-teas-te-topology-profiles-07 submissiontype: IETF workgroup: TEAS Working Group category: info @@ -243,51 +243,6 @@ contributor: administrative and operational state and administrative names for nodes, termination points and links. -{: #geolocation} - -## Geolocation - - The TE Topology model supports the management of geolocation - coordinates for nodes and termination points. This solution is - generic and does not necessarily require the network to be a TE - network. - - The TE topology data model profile shown in {{geolocation-tree}} - can be used to - model geolocation data for networks. - -~~~~ - module: ietf-te-topology - augment /nw:networks/nw:network/nw:network-types: - +--rw te-topology! - augment /nw:networks/nw:network/nw:node/nt:termination-point: - +--rw te-tp-id? te-types:te-tp-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree - augment /nw:networks/nw:network/nw:node: - +--rw te-node-id? te-types:te-node-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree - augment /nw:networks/nw:network/nw:node/nt:termination-point: - +--rw te-tp-id? te-types:te-tp-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree -~~~~ -{: #geolocation-tree title="Generic Topology with geolocation information"} - - This profile is applicable to any network technology (TE or non-TE) - that requires management of the geolocation information for its nodes - and termination points. - {: #overlay-underlay} ## Overlay and Underlay non-TE Topologies diff --git a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.txt b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.txt index ecf9e3b..182524e 100644 --- a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.txt +++ b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.txt @@ -5,19 +5,19 @@ TEAS Working Group I. Busi Internet-Draft Huawei Intended status: Informational X. Liu -Expires: 10 February 2024 Alef Edge +Expires: 18 July 2024 Alef Edge I. Bryskin Individual T. Saad Cisco Systems Inc O. Gonzalez de Dios Telefonica - 9 August 2023 + 15 January 2024 Profiles for Traffic Engineering (TE) Topology Data Model and Applicability to non-TE Use Cases - draft-busi-teas-te-topology-profiles-06 + draft-busi-teas-te-topology-profiles-07 Abstract @@ -40,11 +40,11 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 10 February 2024. + This Internet-Draft will expire on 18 July 2024. Copyright Notice - Copyright (c) 2023 IETF Trust and the persons identified as the + Copyright (c) 2024 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 @@ -53,9 +53,9 @@ Copyright Notice -Busi, et al. Expires 10 February 2024 [Page 1] +Busi, et al. Expires 18 July 2024 [Page 1] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 Please review these documents carefully, as they describe your rights @@ -70,21 +70,20 @@ Table of Contents 2. Examples of non-TE scenarios . . . . . . . . . . . . . . . . 3 2.1. UNI Topology Discovery . . . . . . . . . . . . . . . . . 3 2.2. Administrative and Operational status management . . . . 5 - 2.3. Geolocation . . . . . . . . . . . . . . . . . . . . . . . 6 - 2.4. Overlay and Underlay non-TE Topologies . . . . . . . . . 7 - 2.5. Nodes with switching limitations . . . . . . . . . . . . 8 - 3. Technology-specific augmentations . . . . . . . . . . . . . . 9 - 3.1. Multi-inheritance . . . . . . . . . . . . . . . . . . . . 11 - 3.2. Example (Link augmentation) . . . . . . . . . . . . . . . 12 - 4. Implemented profiles . . . . . . . . . . . . . . . . . . . . 13 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 - 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 - Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 14 - References . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - Normative References . . . . . . . . . . . . . . . . . . . . . 14 - Informative References . . . . . . . . . . . . . . . . . . . . 15 - Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 16 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 + 2.3. Overlay and Underlay non-TE Topologies . . . . . . . . . 6 + 2.4. Nodes with switching limitations . . . . . . . . . . . . 7 + 3. Technology-specific augmentations . . . . . . . . . . . . . . 8 + 3.1. Multi-inheritance . . . . . . . . . . . . . . . . . . . . 10 + 3.2. Example (Link augmentation) . . . . . . . . . . . . . . . 11 + 4. Implemented profiles . . . . . . . . . . . . . . . . . . . . 12 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 + Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 13 + References . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 + Normative References . . . . . . . . . . . . . . . . . . . . . 13 + Informative References . . . . . . . . . . . . . . . . . . . . 14 + Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 15 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 1. Introduction @@ -109,9 +108,10 @@ Table of Contents -Busi, et al. Expires 10 February 2024 [Page 2] + +Busi, et al. Expires 18 July 2024 [Page 2] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 Examples of such features that are applicable to both TE and non-TE @@ -165,9 +165,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 3] +Busi, et al. Expires 18 July 2024 [Page 3] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 The profile data model shown in Figure 1 can be used to discover TE @@ -221,9 +221,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 4] +Busi, et al. Expires 18 July 2024 [Page 4] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 * modelling non TE UNIs such as Ethernet, and TE UNIs such as OTN, @@ -277,9 +277,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 5] +Busi, et al. Expires 18 July 2024 [Page 5] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 The TE topology data model profile shown in Figure 2 is applicable to @@ -287,58 +287,7 @@ Internet-Draft TE Topology Profiles August 2023 administrative and operational state and administrative names for nodes, termination points and links. -2.3. Geolocation - - The TE Topology model supports the management of geolocation - coordinates for nodes and termination points. This solution is - generic and does not necessarily require the network to be a TE - network. - - The TE topology data model profile shown in Figure 3 can be used to - model geolocation data for networks. - - module: ietf-te-topology - augment /nw:networks/nw:network/nw:network-types: - +--rw te-topology! - augment /nw:networks/nw:network/nw:node/nt:termination-point: - +--rw te-tp-id? te-types:te-tp-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree - augment /nw:networks/nw:network/nw:node: - +--rw te-node-id? te-types:te-node-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree - augment /nw:networks/nw:network/nw:node/nt:termination-point: - +--rw te-tp-id? te-types:te-tp-id - +--rw te! - +--ro geolocation - +--ro altitude? int64 - +--ro latitude? geographic-coordinate-degree - +--ro longitude? geographic-coordinate-degree - - Figure 3: Generic Topology with geolocation information - - This profile is applicable to any network technology (TE or non-TE) - that requires management of the geolocation information for its nodes - and termination points. - - - - - - -Busi, et al. Expires 10 February 2024 [Page 6] - -Internet-Draft TE Topology Profiles August 2023 - - -2.4. Overlay and Underlay non-TE Topologies +2.3. Overlay and Underlay non-TE Topologies The TE Topology model supports the management of overlay/underlay relationship for nodes and links, as described in section 5.8 of @@ -380,18 +329,13 @@ Internet-Draft TE Topology Profiles August 2023 +--rw hop-type? te-hop-type +--rw direction? te-link-direction - Figure 4: Generic Topology with overlay/underlay information - - - - - + Figure 3: Generic Topology with overlay/underlay information -Busi, et al. Expires 10 February 2024 [Page 7] +Busi, et al. Expires 18 July 2024 [Page 6] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 This profile is applicable to any technology (TE or non-TE) when it @@ -400,7 +344,7 @@ Internet-Draft TE Topology Profiles August 2023 vice versa, a non-TE underlay network to support a TE overlay network. -2.5. Nodes with switching limitations +2.4. Nodes with switching limitations A node can have some switching limitations where connectivity is not possible between all its TP pairs, for example when: @@ -438,19 +382,19 @@ Internet-Draft TE Topology Profiles August 2023 | +--rw tp-ref? leafref +--rw is-allowed? boolean - Figure 5: Generic Topology with connectivity constraints + Figure 4: Generic Topology with connectivity constraints -Busi, et al. Expires 10 February 2024 [Page 8] +Busi, et al. Expires 18 July 2024 [Page 7] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 - The TE topology data model profile shown in Figure 5 is applicable to + The TE topology data model profile shown in Figure 4 is applicable to any technology (TE or non-TE) networks that requires managing nodes with certain connectivity constraints. When used with TE technologies, additional TE attributes, as defined in [RFC8795], can @@ -466,7 +410,7 @@ Internet-Draft TE Topology Profiles August 2023 Topology Model, such as those defined in Section 2. The first option is to define a technology-specific TE Topology Model - which augments the TE Topology Model, as shown in Figure 6: + which augments the TE Topology Model, as shown in Figure 5: +-------------------+ | Network Topology | @@ -488,7 +432,7 @@ Internet-Draft TE Topology Profiles August 2023 | TE Topology | +---------------------+ - Figure 6: Augmenting the TE Topology Model + Figure 5: Augmenting the TE Topology Model This approach is more suitable for cases when the technology-specific TE topology model provides augmentations to the TE Topology @@ -501,9 +445,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 9] +Busi, et al. Expires 18 July 2024 [Page 8] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 This is the approach currently used in @@ -534,7 +478,7 @@ Internet-Draft TE Topology Profiles August 2023 | (profile) | | Network Topology | +-------------+ +---------------------+ - Figure 7: Augmenting the Network Topology Model with multi- + Figure 6: Augmenting the Network Topology Model with multi- inheritance This approach is more suitable in cases where the technology-specific @@ -550,16 +494,16 @@ Internet-Draft TE Topology Profiles August 2023 specific TE Topology Model which augments the TE Topology Model, and a technology-specific Network Topology Model which augments the Network Topology Model and to rely on the multiple inheritance - capability, as shown in Figure 8: + capability, as shown in Figure 7: -Busi, et al. Expires 10 February 2024 [Page 10] +Busi, et al. Expires 18 July 2024 [Page 9] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 +-----------------------+ @@ -582,10 +526,10 @@ Internet-Draft TE Topology Profiles August 2023 | TE Topology | +---------------------+ - Figure 8: Augmenting both the Network and TE Topology Models + Figure 7: Augmenting both the Network and TE Topology Models This option does not provide any technical advantage with respect to - the first option, shown in Figure 6, but could be useful to add + the first option, shown in Figure 5, but could be useful to add augmentations to the TE Topology constructs and to re-use an already existing technology-specific Network Topology Model. @@ -601,7 +545,7 @@ Internet-Draft TE Topology Profiles August 2023 network subtypes. The hierachy of netwok subtypes can be single hierarchy, as shown in - Figure 6. In this case, each presence container contains at most one + Figure 5. In this case, each presence container contains at most one child presence container, as shows in the JSON code below: @@ -613,9 +557,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 11] +Busi, et al. Expires 18 July 2024 [Page 10] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 { @@ -627,7 +571,7 @@ Internet-Draft TE Topology Profiles August 2023 } The hierachy of netwok subtypes can also be multi-hierarchy, as shown - in Figure 7 and Figure 8. In this case, one presence container can + in Figure 6 and Figure 7. In this case, one presence container can contain more than one child presence containers, as show in the JSON codes below: @@ -669,9 +613,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 12] +Busi, et al. Expires 18 July 2024 [Page 11] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 +--rw link* [link-id] @@ -701,7 +645,7 @@ Internet-Draft TE Topology Profiles August 2023 +--:(example) +--rw example? example-bandwidth - Figure 9: Augmenting the Link with technology-specific attributes + Figure 8: Augmenting the Link with technology-specific attributes The technology-specific attributes within the example-link-attributes container can be defined either in the technology-specific TE @@ -725,9 +669,9 @@ Internet-Draft TE Topology Profiles August 2023 -Busi, et al. Expires 10 February 2024 [Page 13] +Busi, et al. Expires 18 July 2024 [Page 12] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 It is also worth noting that the supported profile may also depend on @@ -781,9 +725,9 @@ Normative References -Busi, et al. Expires 10 February 2024 [Page 14] +Busi, et al. Expires 18 July 2024 [Page 13] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and @@ -795,12 +739,12 @@ Internet-Draft TE Topology Profiles August 2023 Informative References [I-D.ietf-ccamp-eth-client-te-topo-yang] - Zheng, H., Guo, A., Busi, I., Xu, Y., Zhao, Y., and X. - Liu, "A YANG Data Model for Ethernet TE Topology", Work in - Progress, Internet-Draft, draft-ietf-ccamp-eth-client-te- - topo-yang-04, 6 March 2023, + Yu, C., Zheng, H., Guo, A., Busi, I., Xu, Y., Zhao, Y., + and X. Liu, "A YANG Data Model for Ethernet TE Topology", + Work in Progress, Internet-Draft, draft-ietf-ccamp-eth- + client-te-topo-yang-05, 9 October 2023, . + eth-client-te-topo-yang-05>. [I-D.ietf-ccamp-otn-topo-yang] Zheng, H., Busi, I., Liu, X., Belotti, S., and O. G. de @@ -813,17 +757,17 @@ Informative References [I-D.ietf-teas-rfc3272bis] Farrel, A., "Overview and Principles of Internet Traffic Engineering", Work in Progress, Internet-Draft, draft- - ietf-teas-rfc3272bis-26, 4 August 2023, + ietf-teas-rfc3272bis-27, 12 August 2023, . + rfc3272bis-27>. [I-D.ietf-teas-yang-sr-te-topo] Liu, X., Bryskin, I., Beeram, V. P., Saad, T., Shah, H. C., and S. Litkowski, "YANG Data Model for SR and SR TE Topologies on MPLS Data Plane", Work in Progress, - Internet-Draft, draft-ietf-teas-yang-sr-te-topo-17, 13 - March 2023, . + Internet-Draft, draft-ietf-teas-yang-sr-te-topo-18, 21 + October 2023, . [I-D.ogondio-opsawg-uni-topology] de Dios, O. G., Barguil, S., Wu, Q., and M. Boucadair, "A @@ -837,9 +781,9 @@ Informative References -Busi, et al. Expires 10 February 2024 [Page 15] +Busi, et al. Expires 18 July 2024 [Page 14] -Internet-Draft TE Topology Profiles August 2023 +Internet-Draft TE Topology Profiles January 2024 Contributors @@ -893,4 +837,4 @@ Authors' Addresses -Busi, et al. Expires 10 February 2024 [Page 16] +Busi, et al. Expires 18 July 2024 [Page 15] diff --git a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.xml b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.xml index f76a7f0..aae834c 100644 --- a/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.xml +++ b/drafts/te-topo-profile/draft-busi-teas-te-topology-profiles.xml @@ -13,7 +13,7 @@ - + Profiles for Traffic Engineering (TE) Topology Data Model and Applicability to non-TE Use Cases @@ -48,7 +48,7 @@ - + TEAS Working Group @@ -236,49 +236,6 @@ configured as either Ethernet or OTN UNI). administrative and operational state and administrative names for nodes, termination points and links. - -
Geolocation - -The TE Topology model supports the management of geolocation - coordinates for nodes and termination points. This solution is - generic and does not necessarily require the network to be a TE - network. - -The TE topology data model profile shown in - can be used to - model geolocation data for networks. - -
- -This profile is applicable to any network technology (TE or non-TE) - that requires management of the geolocation information for its nodes - and termination points. -
Overlay and Underlay non-TE Topologies @@ -706,13 +663,13 @@ in section 5.3 of . - + Overview and Principles of Internet Traffic Engineering Old Dog Consulting - + This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better @@ -731,14 +688,17 @@ in section 5.3 of . - + - + A YANG Data Model for Ethernet TE Topology + + Huawei Technologies + Huawei Technologies @@ -755,18 +715,19 @@ in section 5.3 of . China Mobile - Volta Networks + Alef Edge - + - A transport network is a server-layer network to provide connectivity - services to its client. In this draft the topology of Ethernet with - TE is described with YANG data model. + This document describes a YANG data model for Ethernet networks when + used either as a client-layer network of an underlay transport + network (e.g., an Optical Transport Network (OTN)) or as a transport + network itself. - + @@ -841,11 +802,11 @@ in section 5.3 of . - + YANG Data Model for SR and SR TE Topologies on MPLS Data Plane - IBM Corporation + Alef Edge Individual @@ -862,7 +823,7 @@ in section 5.3 of . Cisco - + This document defines a YANG data model for Segment Routing (SR) topology and Segment Routing (SR) traffic engineering (TE) topology, @@ -871,7 +832,7 @@ in section 5.3 of . - + @@ -912,140 +873,136 @@ in section 5.3 of .