You may have run in to this, but Hulu also limits (or they were before I canceled the service personally) the number of “homes” you can use it at, and they tracked this by IP. So, if your customer’s IP changes more than a few times a year they will not be able to use the service they’re paying for.  

Last time I was responsible for said problem I was looking at alternate solutions to do CGNAT on, and reducing the domains from an architecture perspective…obviously they both have big repercussions.

On Tue, Oct 8, 2024 at 7:10 PM Michael Thomas <mike@mtcc.com> wrote:

On 10/8/24 1:19 PM, Jon Lewis wrote:
> I'm not so sure about that.  Our customers are all offered dual-stack
> (DHCPv6, DHCPv6-PD).  Do any of the common streaming services support
> v6 yet?  Last I checked, Hulu did not.

I just checked and it looks like Youtube and Netflix do which is a
pretty good chunk. Not sure about Amazon Prime. I was actually thinking
about social media which i think it's pretty well supported.

Mike


>
> On Tue, 8 Oct 2024, Michael Thomas wrote:
>
>> Hi Jon,
>>
>> So is this easier than what the mobile carriers are doing -- 464xlat,
>> isn't it? Probably a sizeable portion of the traffic would be running
>> native v6, right? Obviously it wouldn't run into these sorts of
>> problems.
>>
>> Mike
>>
>> On 10/8/24 12:19 PM, Jon Lewis wrote:
>>>  We started rolling out CGNAT about 6 months ago.  It was smooth
>>> sailing
>>>  for the first few months, but we eventually did run into a number of
>>>  issues.
>
> ----------------------------------------------------------------------
>  Jon Lewis, MCP :)              |  I route
>  Blue Stream Fiber, Sr. Neteng  |  therefore you are
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________