2. Updates from the Last Meeting 1. Limited communication on list We strongly encourage the mailing list to be more actively used for all Working Group discussions Especially for open issues Chairs see progress on topics between I-D authors, but conclusions should be coped to the list Future meeting time will be scheduled relative to mailing list discussion 2. Lack examples of how SUPA will be used Where to document Applicability? Framework I-D looks like a good place Need to survey operators and identify use case affinities 3. OpenSource Hackathons Early implementations would help discussion, this only has to be the “model for the engine”, simple examples to include: inputs, outputs, events and conditions MEF OpenLSO See next slide 97th IETF SUPA Working Group 1

4. Known Implementations IETF 97 – I2NSF Hackathon Sue Hares SUPA policy - helped developed I2NSF capability information model The I2NSF capability information model helped us develop the I2NSF yang data model. Paul Jeong’s team took the I2NSF Yang data models. They modified the single data models into multiple to create logical pieces, and implemented this code between IETF 96 an IETF 97 for the Hackathon at this IETF (IETF 97). It supports filtering (firewall, DPI, forwarding) or bypass (DPI, forwarding). It supported a VoIP filtering. 97th IETF SUPA Working Group 2

4. Planned Implementations MEF John Strassner (Orchestration Area Co-Director of the MEF) & SUPA I-D(s) Author “We have the following uses of SUPA artefacts planned” Use the SUPA IM and DM as-is, and then add to both, to represent policies to manage MEF Third Network Services; use the above SUPA models and extensions in the MEF policy-driven orchestration project use the above SUPA models and extensions in the MEF OpenLSO project to develop open source tools and open source policy systems 97th IETF SUPA Working Group 3