]> Ericsson AB

Lindholmspiren 11 Goteborg 417 56 Sweden jonas.ahlberg@ericsson.com

Ericsson Inc

scott.mansfield@ericsson.com

Huawei Technologies

No.1899, Xiyuan Avenue Chengdu 611731 China amy.yemin@huawei.com

Huawei Technologies

italo.busi@huawei.com

NEC Laboratories Europe

Kurfursten-Anlage 36 Heidelberg 69115 Germany Xi.Li@neclab.eu

Nokia - IT

Via Energy Park, 14 Vimercate (MI) 20871 Italy daniela.spreafico@nokia.com

Routing CCAMP Working Group Internet-Draft This document defines a YANG data model to provide a reference from a termination point in a topology model to interface management information. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the CCAMP Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction This document defines a YANG data model to provide a reference from a termination point in a topology model to interface management information. It introduces a way to reference the information in a YANG data model for interface management that could be useful for all types of termination points. The model augments "YANG Data Model for Traffic Engineering (TE) Topologies" defined in , which is based on "A YANG Data Model for Network Topologies" defined in . The interface reference model is expected to be used between a Provisioning Network Controller (PNC) and a Multi Domain Service Coordinator(MDSC) . Different use cases require access to different attributes and in order not to restrict what use cases can be supported, all attributes supported by the interface management model is with this model made accessible from the topology model.

Terminology and Definitions The following acronyms are used in this document: PNC Provisioning Network Controller MDSC Multi Domain Service Coordinator

Tree Structure A simplified graphical representation of the data model is used in chapter 3.1 of this document. The meaning of the symbols in these diagrams is defined in .

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Termination Point to Interface Reference YANG Data Model

YANG Tree /if:interfaces/interface/name ]]>

Termination Point to Interface Reference YANG Data Module Editor: Jonas Ahlberg Editor: Scott Mansfield Editor: Min Ye Editor: Italo Busi Editor: Xi Li Editor: Daniela Spreafico "; description "This is a module for defining a reference from a termination point in a te topology to a list element in interfaces as defined in RFC 8343. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://tools.ietf.org/html/rfcXXXX); see the RFC itself for full legal notices."; revision 2023-02-15 { description "First rough draft."; reference ""; } /* * Groupings */ grouping tp-to-interface-ref { description "Grouping used for reference between a termination point and an interface."; leaf tp-to-interface-path { type leafref { path '/if:interfaces/if:interface/if:name'; } description "Leafref expression referencing a list element, identified by its name, in interfaces as defined in RFC 8343."; } } /* * Data nodes */ augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te" { description "Augmentation to add possibility to reference an element in the list of interfaces as defined by RFC 8343."; uses tp-to-interface-ref; } } ]]>

Security Considerations The YANG modules specified in this document define schemas for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The NETCONF access control model provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. The YANG module specified in this document imports and augments the ietf-network and ietf-network-topology models defined in . The security considerations from are applicable to the module in this document. There is a data node defined in this YANG module that is writable/creatable/deletable (i.e., config true, which is the default). This data node may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to this data node without proper protection can have a negative effect on network operations. This is the subtrees and data node and its sensitivity/vulnerability:

• tp-to-interface-path: A malicious client could set an arbitrary path that could allow a client to retrieve incorrect information. Troubleshooting would be difficult because the bad path would not be detectable until the client tries to use the leaf to identify to radio link terminal.

IANA Considerations IANA is asked to assign a new URI from the "IETF XML Registry" as follows: It is proposed that IANA should record YANG module names in the "YANG Module Names" registry as follows:

References Normative References This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics). The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342. This document obsoletes RFC 7223. This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment. This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] Informative References Traffic Engineered (TE) networks have a variety of mechanisms to facilitate the separation of the data plane and control plane. They also have a range of management and provisioning protocols to configure and activate network resources. These mechanisms represent key technologies for enabling flexible and dynamic networking. The term "Traffic Engineered network" refers to a network that uses any connection-oriented technology under the control of a distributed or centralized control plane to support dynamic provisioning of end-to- end connectivity. Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network that is under the control of a network operator or the customer of the operator that actually owns the network resources. This document provides a framework for Abstraction and Control of TE Networks (ACTN) to support virtual network services and connectivity services. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.

Examples of the Interface Reference Topology Model This appendix provides some examples and illustrations of how the Interface Reference Topology Model can be used. There is one extended tree to illustrate the Model and a JSON based instantiation of the Interface Reference Model for a small network example.

A tree for a complete Interface Reference Topology Model The tree below shows the leafs for extending a Network Topology Model defined in , Traffic Engineering (TE) Topologies model defined in with a possibility to reference interface management information. /if:interfaces/interface/name ]]>

A JSON example

Acknowledgments This document was prepared using kramdown The authors would like to thank ...