Hi all, This version implements the following changes to address some pending issues: * Define the notion of parent AC to manage ACs that involve many peer SAPs but for which some specific information is required for each peer SAP. * Add support of BGP import policies. * Include a data node for feasibility check purposes. This is similar to test-only in NETCONF, but some protocols may no support natively that function. * Add support for bandwidth management which mirror what is already supported in the ACaaS model. * Add support for QoS and ACL profiles. * Add missing narrative text and subtrees. Many of this text is "brought" from RFC9182 and RFC9291. * Add an example.
We do still have 3 pending issues that we plan to fix in the next iteration: https://github.com/boucadair/attachment-circuit-model/issues?q=is%3Aissue+is%3Aopen+label%3Aac-ntw. Reviews and comments are highly appreciated. Thanks. Cheers, Med > -----Message d'origine----- > De : I-D-Announce <i-d-announce-boun...@ietf.org> De la part de > internet-dra...@ietf.org > Envoyé : mardi 28 novembre 2023 14:20 > À : i-d-annou...@ietf.org > Cc : opsawg@ietf.org > Objet : I-D Action: draft-ietf-opsawg-ntw-attachment-circuit-02.txt > > Internet-Draft draft-ietf-opsawg-ntw-attachment-circuit-02.txt is now > available. It is a work item of the Operations and Management Area > Working Group (OPSAWG) WG of the IETF. > > Title: A Network YANG Data Model for Attachment Circuits > Authors: Mohamed Boucadair > Richard Roberts > Oscar Gonzalez de Dios > Samier Barguil Giraldo > Bo Wu > Name: draft-ietf-opsawg-ntw-attachment-circuit-02.txt > Pages: 92 > Dates: 2023-11-28 > > Abstract: > > This document specifies a network model for attachment circuits. > The > model can be used for the provisioning of attachment circuits prior > or during service provisioning (e.g., Network Slice Service). A > companion service model is specified in I-D.ietf-opsawg-teas- > attachment-circuit. > > The module augments the Service Attachment Point (SAP) model with > the > detailed information for the provisioning of attachment circuits in > Provider Edges (PEs). > > The IETF datatracker status page for this Internet-Draft is: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata > tracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-ntw-attachment- > circuit%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C605a5381d76 > c4e67089408dbf014d224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638 > 367744433166598%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 > luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TIsawVPInd3 > Kj4QbRNH%2Bj9kuMgoS2GSL70LhKYYhTu0%3D&reserved=0 > > There is also an HTML version available at: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ietf.org%2Farchive%2Fid%2Fdraft-ietf-opsawg-ntw-attachment-circuit- > 02.html&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C605a5381d76c4e > 67089408dbf014d224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638367 > 744433173861%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM > zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xDaSXdw%2BUSlT > U6cAjpBzMsOE%2FhMbbVAeiUGEiX%2BVWqo%3D&reserved=0 > > A diff from the previous version is available at: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauth > or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-ntw-attachment- > circuit- > 02&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C605a5381d76c4e67089 > 408dbf014d224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63836774443 > 3177780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC > JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=h%2FRqjASIMK18lHZsA > rk6BokqyhGwXzgAxKGHDPtUpZ0%3D&reserved=0 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > I-D-Announce mailing list > i-d-annou...@ietf.org > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ietf.org%2Fmailman%2Flistinfo%2Fi-d- > announce&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C605a5381d76c4 > e67089408dbf014d224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63836 > 7744433181938%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu > MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fWDec0lUjHD07 > btYNeFnRynJSRkh3ysDnv%2BcTD6QdHY%3D&reserved=0 ____________________________________________________________________________________________________________ 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 OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
