Maybe because people aren’t looking for super_CAS_id or CA_subsystem_id? It’s not like AFN/DigitalGlue gets to trash ETSI/DVB because they feel like it.
Many things you do not understand.
Powervu as a company does not have to follow DVB specs,it only describe their irds as DVB compliant,and they can do what they want appart from that.
DSS and Digicypher are proof that not all streams are DVB compliant,so is powervu,Tandberg and the rest.
All receivers can be made to be DVB compliant,and at the same time work differently altogether.
Beside,whatever is sent in the stream can be seen,there is no way to hide information,even when there is not descriptor for it.If a PID has information anyone can find it,but they are not doing that.
So,basically,if they ordered customers to hook up to internet,then there is only one reason for it : to update firmware that change internal keys (no,not ECM keys) and insert new unknown hashes and who knows what else.
Everybody think they have an idea about what's going on,but the truth comes only looking at the stream.
You can see those funny ECM packets,now imagine how much packetry handling has changed in new firmware in order to be able to understand there are more than one table in each packet (which is not a DVB practice,unless you show me other services past and present that has both ecm tables in one packet),then see if you can explain how to the PSI can be set for this to happen.
All this is weird and different,have not seen this before myself,after 25+ years of "looking" at the stream.
But I see the rationale of it : updating firmware out of sight,then make things change in ways not seen before.
You have to remember the CA handling has little DVB guidelines,just an outline.
Anyway,we will know more with time.