Igmp Proxy

Video streaming is usually going to use HTTPS. Mirroring will use RDP or also HTTPS. Multicast is kind of like signing up for a email group list. The same thing is being sent to everyone, but only those that send a request to be part of the thread can see it. It's used a lot by some cable boxes(IPTV), but nothing Cox uses. 

Tecknowhelp said:

Video streaming is usually going to use HTTPS. Mirroring will use RDP or also HTTPS. Multicast is kind of like signing up for a email group list. The same thing is being sent to everyone, but only those that send a request to be part of the thread can see it. It's used a lot by some cable boxes(IPTV), but nothing Cox uses. 

Most likely not.

Are there performance or security concerns about enabling it?

Since you don't need it, then don't enable it. It is difficult to discuss security vulnerabilities of something as ornate as IGMP in layman's terms. If you are still curious, feel free to look up more about it online or see this article here.

You can be as technical as you want 

Omoeba said:
You can be as technical as you want 

I don't have a running knowledge of IGMP, just general practice based on messing around in wireshark. I was digging with google to try to help answer your specific question, but I really don't "want" to or have the ability to carry a entire thread on the subject.

AFAIK the need for a IGMP proxy is rare, and I have left it disabled on my router and haven't had issue with anything streaming video(up or down), IPv6, or anything else I know of to use multicast traffic. Gaming is fine. VOIP(Google Voice) is fine.

However if your question is what the security vulnerabilities are of leaving IGMP proxy enabled, I just don't know. Please feel free to bump the thread and hopefully someone else can comment who has more experience on the security side of things.