There are actually reasons behind this. I've got a
In the days of old, customers were assigned their statics in WAN-side way as you describe. My parents used to have a static assigned to them from a WAN block on their CMTS. This was great because whatever allocation assigned was very efficiently used. Granted, this was back when nodes were combined 4:1 or greater on the small CMTS that was being used. A uBR7246 with 1x6 cards in the day could easily route traffic for over 48 cable nodes, at 2:1 combining on the upstreams, and 12:1 on the downstreams. (A whopping 150mbps for 48 nodes
It wasn't all that long ago I remember some towns sharing a single downstream port. Now, enter node splits, and combining gets down to 1:1 in many cases. Even with a much larger CMTS (uBR10012 vs. uBR7246), it can't handle the same number of nodes. With redundancy failover switchboxes, there are only 35 downstreams per box (assuming 5x20 cards).
Now a problem exists as soon as the box's capacity is reached. If I need to split your node and move it to another CMTS to increase your available bandwidth, I need to coordinate with everyone who is moving who has a WAN side IP and tell them that their IP address is going to change on whatever date. This turns into an incredible shitstorm when one person stammers their feet and cries up the escalation chain and then delays necessary work because they bitch. Then capacity continues to be in hell until the move is finally approved. Then, there are the customers who ignore your voicemail and phone calls and then cry for a credit because they didn't pay attention until the move date.
So now what everyone is doing in order to make this easier is to assign you a
Seems wasteful, but that's the sense behind it.
They cradle my balls, stroke the shaft, work the pipe, and drink the gravy.
For God's sake, stop researching for a while and begin to think!