Skip to main content

A YANG Network Data Model for Service Attachment Points (SAPs)
draft-ietf-opsawg-sap-15

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, adrian@olddog.co.uk, draft-ietf-opsawg-sap@ietf.org, opsawg-chairs@ietf.org, opsawg@ietf.org, rfc-editor@rfc-editor.org, rwilton@cisco.com
Subject: Protocol Action: 'A YANG Network Model for Service Attachment Points (SAPs)' to Proposed Standard (draft-ietf-opsawg-sap-15.txt)

The IESG has approved the following document:
- 'A YANG Network Model for Service Attachment Points (SAPs)'
  (draft-ietf-opsawg-sap-15.txt) as Proposed Standard

This document is the product of the Operations and Management Area Working
Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/


Ballot Text

Technical Summary

   This document defines a YANG data model for representing an abstract
   view of the provider network topology that contains the points from
   which its services can be attached (e.g., basic connectivity, VPN,
   network slices).  Also, the model can be used to retrieve the points
   where the services are actually being delivered to customers
   (including peer networks).

   This document augments the 'ietf-network' data model by adding the
   concept of Service Attachment Points (SAPs).  The SAPs are the
   network reference points to which network services, such as Layer 3
   Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network
   (L2VPN), can be attached.  One or multiple services can be bound to
   the same SAP.  Both User-Network Interface (UNI) and Network-to-
   Network Interface (NNI) are supported in the SAP data model.

Working Group Summary

   Went pretty smoothly.  No controversy. Some detailed debate
   during WGLC, but this seemed to reach consensus.

Document Quality

No one has reported any implementations.
Note that this document is referenced by a TEAS document
(draft-ietf-teas-actn-poi-applicability) which discusses a topic that is
likely to lead to implementation, and by the TEAS network slicing
framework (draft-ietf-teas-ietf-network-slices) which is likely to mean
that YANG models for the network slice service interface (such as
draft-ietf-teas-ietf-network-slice-nbi-yang) may come to use it in time.

Personnel
   Adrian Farrel was the Doc Shepherd.
   Rob Wilton is the responsible AD.

RFC Editor Note