Change:
view of the provider network topology containing the points from which its services can be attached (e.g., basic connectivity, VPN, network slices).  The data model augments the 'ietf-network' data <del> model by adding the concept of service attachment points (SAPs).  The service attachment points are the points to which network services (such as L3VPN or L2VPN) can be attached.  The customer endpoint of an attachment circuits are not covered in the SAP network topology. </del> <ins> model by adding the concept of Service Attachment Points (SAPs).  The Service Attachment Points are the points to which network services (such as Layer 3 Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network (L2VPN)) can be attached. The customer endpoints of an attachment circuit (Customer Edges (CEs), topically) are not covered in the SAP network topology. </ins> 1. <del> The service attachment point (SAP) is an important architectural </del> <ins> The Service Attachment Point (SAP) is an important architectural </ins> concept in many implementations and deployments of services such as <del> VPNs, SDWAN, or managed VoIP services.  It has already been used to decide where to attach and, thus, deliver the service in the L3SM RFC8299 and the L2SM RFC8466. </del> <ins> Virtual Private Networks (VPNs), Software-Defined Wide Area Network (SDWAN), or managed Voice over IP (VoIP) services.  It is used to decide where to attach and, thus, deliver the service in the Layer 3 VPN Service Model (L3SM) RFC8299 and the Layer 2 VPN Service Model (L2SM) RFC8466.  It can also be used to retrieve where services, such as the Layer 3 VPN Network Model (L3NM) I-D.ietf-opsawg-l3sm-l3nm, and the Layer 2 VPN Network Model (L2NM) I-D.ietf-opsawg-l2nm, are delivered. </ins> This document defines a YANG network model for representing, <del> managing, and controlling the service attachment points (SAPs).  The data model augments the 'ietf-network' module RFC8345 by adding the concept of service attachment points.  The service attachment points are abstraction of the points where network services such as L3VPNs or L2VPNs can be attached. </del> <ins> managing, and controlling the Service Attachment Points.  The data model augments the 'ietf-network' module RFC8345 by adding the concept of Service Attachment Points.  The Service Attachment Points are abstraction of the points where network services can be attached. </ins> <del> This document does not make any assumption about the service provided by the network to the users.  VPN services are used for illustration purposes.  This concept can also be used to decide network slice SAPs I-D.ietf-teas-ietf-network-slices. </del> <ins> This document does not make any assumption about the service(s) provided by the network to the users.  VPN services (such as Layer 3 Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network (L2VPN)) are used for illustration purposes.  The SAP concept can be used to decide network slice SAPs I-D.ietf-teas-ietf-network-slices. </ins> In the context of Software-Defined Networking (SDN) RFC7426, the defined YANG data model in this document can be used to exchange

Discussion:
Check if we need to expose SAPs per servcie-type and if so, how we can easily add support for it OLD: NEW: