I was expecting to be able to ding this general idea just based on the inability to route it in a scalable fashion. But there are provisions for a location and

I was expecting to be able to ding this general idea just based on the inability to route it in a scalable fashion. But there are provisions for a location and a provider id, which would allow for decent aggregation if set up properly. So I'm left being generally concerned with larding up layer 3 with all kinds of additional semantics, but really the draft is so thin its difficult to really determine how feasible it would be to implement and deploy.