[Supa] Time to close SUPA

[Benoit Claise <[e-mail]>]

Dear all,

The SUPA charter was created with one goal in mind:

    The working group will have succeeded when the SUPA policy constructs are
    re-used in future IETF specifications (and ideally specifications from other
    SDOs), in a manner that saves development time and avoid inconsistencies
    between data models developed by different working groups.

At charter time, the IESG limited the scope of work, the deliverables, 
and the related milestones dates for a phase approach in this world of 
policy and data modeling: event-condition-action, a single management 
domains, etc.

All the SUPA documents should have been published a year ago. Delays are 
actually common at the IETF, but what concerns me is that the SUPA data 
model is not being reused 
<https://yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-supa-policy&recurse=0&rfcs=1>, 
while all the data models are being standardized, including ones 
containing policies.
The SUPA reuse success is not there, and I regret it. As I mentioned 
before, the window of opportunity has been closing rapidly.
Note: using the SUPA data model as a way to encode polices between two 
controllers is nice, but not that reuse metric.

The WG received some early warnings, one of them at IETF 98 
<https://www.ietf.org/mail-archive/web/supa/current/msg01612.html>.
After reviewing the facts during this week, and discussing them with the 
IESG and the IAB this Friday afternoon, I concluded to close the SUPA WG.

I invite the authors who want to pursue publication to pursue the 
Independent Submission 
<https://https://www.rfc-editor.org/about/independent/www.rfc-editor.org/about/independent/> 
road.

Let me thanks the SUPA chairs Nevil and Daniel, who have been trying hard.

Regards, Benoit (responsible AD).