Hi all, 

We updated the uni draft to address some of the comments we received in the 
past. For better clarity, we abandoned the uni terminology and went with 
service attachment points that is more generic. It can be used to build a 
network topology to be consumed by an orchestrator to handle a service request. 
SAPs can be the PE endpoint facing a CE or a peer PE (for services such as 
inter-AS VPN). 

Comments, questions, and suggestions are more than welcome.

Cheers,
Oscar, Samier, Qin, Victor, & Med

-----Message d'origine-----
De : [email protected] <[email protected]> 
Envoyé : vendredi 22 octobre 2021 13:57
À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; Oscar Gonzalez 
de Dios <[email protected]>; Oscar de Dios 
<[email protected]>; Qin WU <[email protected]>; Qin Wu 
<[email protected]>; Samier Barguil 
<[email protected]>; Victor Lopez 
<[email protected]>; samier barguil 
<[email protected]>
Objet : New Version Notification for draft-dbwb-opsawg-sap-00.txt


A new version of I-D, draft-dbwb-opsawg-sap-00.txt has been successfully 
submitted by Mohamed Boucadair and posted to the IETF repository.

Name:           draft-dbwb-opsawg-sap
Revision:       00
Title:          A Network YANG Model for Service Attachment Points
Document date:  2021-10-22
Group:          Individual Submission
Pages:          21
URL:            https://www.ietf.org/archive/id/draft-dbwb-opsawg-sap-00.txt
Status:         https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dbwb-opsawg-sap


Abstract:
   This document defines a YANG data model for representing an abstract
   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
   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.

                                                                                
  


The IETF Secretariat



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to