Hi all, I'm forwarding this announcement to OPSAWG as there might be some implications on the maintenance of some of the work we have done here. So far, the following is identified for OPSAWG:
== Relationship with Existing WGs OPSAWG * Offload AC/SAP/LxNM to ONIONS * Future relevant work on abstractions will be directed to ONIONS == This is consistent with the latest OPSAWG charter. Furthermore, this would help refocus opsawg on "occasional proposals" and perform its dispatch function for the area. Feel free to raise any other items that need to be clarified in reference to OPSAWG. Of course, consider joining ONIONS list if you are interested in this work. Thanks. Cheers, Med -----Message d'origine----- De : IETF Secretariat <ietf-secretar...@ietf.org> Envoyé : mardi 13 mai 2025 20:26 À : IETF Announcement List <ietf-annou...@ietf.org> Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; oni...@ietf.org Objet : New Non-WG Mailing List: Operationalizing Network & service abstractIONS (ONIONS) A new IETF non-working group email list has been created. List address: oni...@ietf.org Archive: https://mailarchive.ietf.org/arch/browse/onions/ To subscribe: https://mailman3.ietf.org/mailman3/lists/onions.ietf.org/ Purpose: This list is intended to discuss operational considerations related to the network and service abstractions in the IETF. The list will be used to discuss a WG charter that will cover the following initial scope: -Reference for network/service abstractions modelling in the IETF -Build and provide a big picture of the operational needs and motivations for these abstractions -Structure the effort on Service and Network models (and their maintenance) together with glues with underlying devices models -Define models for network and service abstractions with support from operators -Maintain network and service models (L3SM, L2SM, L2NM, L3NM, ACaaS, SAP, Slicing, VN, and ACTN, in particular) based on operational feedback -Explore approaches for mapping between various abstraction layers -Provide recommendations on operationalizing YANG APIs (YANG2API) -Investigate required components so that YANG modules can be easily consumed -These components are meant to programmatically transform YANG models into key open APIs specifications -Assess the applicability of these abstractions to accommodate specific operational use cases and deployments -Assess the realization of the intended abstractions and identify gaps, if any -Typically, assess interactions with required control and data plane features to implement an intended service in a network -Coordinate with the routing area for evaluating OPS needs of proposed solutions that are motivated by a given abstraction need (e.g., slicing) More details can found at: https://github.com/boucadair/WG-Charters/blob/main/onions.md This list belongs to IETF area: OPS For additional information, please contact the list administrators. ____________________________________________________________________________________________________________ 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 To unsubscribe send an email to opsawg-le...@ietf.org
