Open APIs

I understand TMF641 will now support Intent-based orchestration on specs 5.0.  With this direction what is the use for TMF921?  Will these coexist or will TMF921 be retired?

You see intent also in the draft version of TMF645. So you could do service and intent qualification using TMF645. 

TR29x would be supported by both TMF633, TMF641 and TMF645 and TMF921. 

At least for now TMF921 would offer more functionality on reporting, probe, best, Judge etc. 

I assume they could work side by side. However TMF641 would now offer a easy start to managed intents. 

The challenges here are the realisation within the resource layer and how this is achieved. The Intent concept has existed for approximately a decade within various networking standard bodies. ONFs SDN Architecture (TR-521) provided a ONF Common Information Model (TR-512) that was structured around providing Intent as a Business outcome with dynamic network APIs and tooling required to enable this capability. ONF T-API is utilised by groups such as TIP to enable Optical Transport and uses a RESTConf interface with YANG data models. At the resource layer the challenge is how to address the various technology domains and the different interfaces in a coherent manner such that you can manage to abstract the service and operations. IETF approached this as well in RFC8453 (Framework for Abstraction and Control of TE Networks) and the information model (8454). This fundamentally aligns with the ONF SDN Controller architecture that was centred around intent and Intent Based Networking (IETF RFC9315,6 and 9417). 

TMF ODA Production is examining the options and use cases surrounding this to enable adoption.