I don't think so. There are a number of documents online that detail naming standards for infrastructure like servers, but I think this is slightly different than what you mean. Those are things like, "If you have a server, you should name it foo-123-bar" according to some scheme. That is, naming instances of infrastructure. I think you're after naming the infrastructure components themselves (server, gateway, load balancer, etc)
The closest thing I know of is the AWS architectural standards / reference architectures you can find here:
They tend to use a standardized (but AWS specific) language for describing a large variety of resources.
I think the extreme difficulty in this area is that at the architectural level you can refer to components abstractly by what feature they provide to the architecture (a term like this would be "load balancer" which describes something it does for the wider architecture). Then again, it might matter for you that it's nginx, or F5, or HAProxy. They might conceptually all do the same thing but they're implemented quite differently.
So it depends on what you're doing, how vendor-specific you need to be, and so on. Overall, naming and data standards are a really tough area. There's an old saying: "Data standards are like toothbrushes. Everybody's got one, and nobody wants to use yours". :)