I read the kermit paper, and it is a home use tool, it can only tell the user what they are using, not what exactly the ISP routers are doing.
http://www.cc.gatech.edu/~marshini/files/kermit.pdfIt is also important to distinguish a speed cap from a usage cap.
And it seems they have a convoluted method - a router flashed with DD-WRT for firmware and then using a packet flow plugin.
Why re-invent the wheel? Badly.
Nah, what we need is for the ISPs to open up the customer-side SNMP ports on the DOCSIS 2 and 3 modems. (Motorola Surfboards ideally). Then we can watch it all ourselves locally. The monitoring and control apps would proliferate quickly.
The new modems already have all of this built-in. No need to use a custom router firmware, run a local server with MySQL, php and a flash front-end webapp... just have the ISPs open certain portions of the SNMP monitoring and modem controls to the customer side. Some business accounts already do this, though most ISP techs are not familiar with these "advanced" concepts. (old, 90s stuff, been on the hardware for years, only starting to get used now...)
My quick and dirty solution for minimal control is wintc.
SNMP is on all the DOCSIS2+ modems, and QoS in all the OS network stacks now... so... why would one need anything else? A single app and peer negotiation on the lan would cover it all.
No need for kermit. It's not easy being green.
Besides, kermit, as I recall it was an old network service right? Kermit, Gopher... Bad name to pick for a new network application.