I feel like it's an entirely reasonable stance. The two valid approaches to solving a technical problem is either you try to solve all of it so that no one is concerned by it any more, or you solve as little of it as possible, but solve that part well, so there's a clear line on what's your job and what is not.

IP as a concept of 'digital PO box' falls short even if we upgrade to IPv6 - imagine talking to someone via voicechat on your phone, and moving from home Wifi to mobile data. They are two separate HW interfaces with their own identities and networking stacks, so moving your connection has to bypass the IP layer even on IPv6.

On the other hand if your job description is to shuttle packets between 'A' and 'B', where neither is guaranteed to be the actual sender or receiver, IP address becomes an implementation detail, and doing you job on IPv4 is much simpler, with the rube-goldberg stuff of actually figuring out how to connect the actual sender and recipient falling to higher level protocols.

So while I don't have strong feelings on the topic, this movement feels like a management reorg, where some business units get shuffled around, priorities change, but ultimately there's very little consistent motive or goal to the whole thing.