As of Q3 2022, customers can assign the "Interconnection Name" to a connection, but that applies to the whole connection, which could include multiple "circuits" or paths.
Customers often want to provide context data such as circuit IDs, active / redundant role names, A-side information etc to these resources for obvious reasons.
If the ports behind a connection we're "taggable", then customers could assign any context information they need to the A/B side of a connection via it's ports.
Customers could also then continue to add context information into the virtual circuits above the ports with the virtual circuit name field.