It seems that there is some confusion on what HDCP actually is.
Its not confusion on what HDCP is ... but exactly how dish will implement and block content based on HDCP "requirements" to *any* analog outputs that are *not* digitally protected by HDCP.
This is not stuff from the HDCP Specifications documents ... but from the LICENSING documents which specify no Analog Output.
http://www.digital-cp.com/licensing
http://www.digital-cp.com/files/static_page_files/26D315BF-1A4B-B294-D04BB484EE81591E/HDCP License Agreement0831_2011_clean _2_.pdf
Exhibit C - Compliance Rules (starts at PDF page 37 of 51)
3.3 / 3.3.1 - Digital Outputs (starts on pdf page 38 of 51) .. shall not permit the output of Audiovisual Content to digital outputs except ... only digital outputs (audio) that further comply to approved no-copy options (or are approved Audiovisual repeaters, which again are spec'd to comply with HDCP, at Exhibit C section 5 "Repeaters")
3.4 Analog Outputs (starts on page 39 of 51 and continues to pg 40 of 51)
3.4 Analog Outputs. No output of Decrypted HDCP Content is permitted except as follows:
3.4.1 Audiovisiual Content. Except as otherwise expressly provided in Section 3.3.1 of these Compliance Rules, A Presentation Device shall not permit the output of Audiovisual Content Decrypted HDCP Content in any analog representation.
(that section there <3.4.1> should be enough to quash the "we're not talking coax", because the coax on dish receivers *IS* analog)
5
Compliance Rules for Repeaters.
5.4 (pdf page 41 of 51)
5.4 No Analog Outputs. A Repeater shall not permit the output of Decrypted HDCP Content in any analog representation.
Now ... given the explicit statements of HDCP License compliance.. while a Coax output is analog, and is very low quality .. at NO TIME did I read ANY mention in the license documentation where it exempts Coax ... its analog, its getting *ITS* signal from Dish as a transcoded HDCP protected digital signal to an analog unprotected signal. If the digital signal comes from Dish with HDCP ... then by definition allowing HDCP *decrypted* content on the coax is in violation of the license.
Now maybe there is an addendum where it mentions such things.. but I didn't see it (that website has an addendum, the addedum mentions Exhibit C sections 3.5 and 5.3 but *not* 3.3.1 nor 3.4 or 5.4)
The simple fact is that Dish is the one required to implement such restrictions on the output .... and if the content is encrypted with HDCP from Dish Uplink .. and not at the disgression of the reciever.. then dish will fall into non-compliance and risk a law suit ...
IF however, dish is turning on HDCP as a requirement for HDMI Port as the source *ON* the box..
then they should be allowed to leave the Component & Coaxial cables alone, in their natives.. because you're not moving HDCP from uplink to satellite, and down/into dish receiver.
So again.. what's needed is for **DISH** to clarify what its position is in the box and source position of the HDCP requirements. Is dish putting HDCP on from the uplink? OR Is dish merely enforcing HDCP from the Box as source of the HDCP to protect a digital output (HDMI).
And if its the latter ... dish should *not* be disabling the Coax, and certainly should
*not* be disabling the Component outputs as they would not be from an HDCP protected device, they are from Dish's decrypted DISH signal before protection of HDCP is added to the HDMI output and HDMI output alone.
There have been folks complaining that their Component Outputs have been effected to their Sling Boxes (not sling adapters, the full slingbox) and if that is a result of Dish's HDCP then they need to re-evaluate what they are doing.