TR-069 replacing CAPWAP - A thought

It appears that there are too many standards to manage devices remotely - We have our old friend SNMP, TR-069 and its associated data models from DSLForum, OMA Device Management from open mobile alliance and CAPWAP to manage access point devices from IETF.

I had one thought - Why not manage access points using TR-069.

Certainly CAPWAP is versatile in wireless world- It can provision and control Split-MAC and Local MAC based access points (Wireless Termination Points). If the requirement is only to provision and control LOCAL MAC based access points, then TR-069 can be used effectively by placing TR-069 Server (Auto Configuration Server) in wireless controller and TR-069 agent (client) in WTPs.

Like CAPWAP, TR-069 protocol also defines operations such as enrollment, mutual authentication, image synchronization and configuration update. It also has mechanism of 'Inform'ing central server on state changes (Parameter Value Changes). CAPWAP has additional advantage though i.e securing the traffic between WTPs and Wireless controller. I believe that this additional secuirty can be achieved by running IPsec tunnel between WTPs and Wireless controllers.

I believe that network security appliance/gateway vendors would be adding TR-069 based central mangement in their hub appliances to manage branch office boxes. I believe that wireless controller functionality is going to be included along with security gateways and appliances. Rather than having one more managment middleware, I believe that vendors would prefer to have one management middleware. CAPWAP is primarily focused on provisioning wireless devices. TR-069 is versatile. Hence, I feel that TR-069 has an advatange.

Srini