# Port Configuration Error **URL:** \ **Category:** PyCyphal\ **Created:** [April 23, 2024, 3:23am UTC](https://forum.opencyphal.org/t/port-configuration-error/2114 "2024-04-23T03:23:31Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\ **Post date:** [May 6, 2024, 8:32am UTC](https://forum.opencyphal.org/t/port-configuration-error/2114/5 "2024-05-06T08:32:09Z")
To use a client you need to export `UAVCAN __CLN__...`. This design where you need to specify the direction of the port explicitly is actually a deficient one. I am considering to discard it in favor of omnidirectional names when this change is implemented: > [@Consider the implications of renaming the "uavcan" namespace into "cyphal"](https://forum.opencyphal.org/t/consider-the-implications-of-renaming-the-uavcan-namespace-into-cyphal/1975/9): > > There are two aspects: renaming the DSDL namespace itself and renaming the registers. The DSDL renaming can be done by copying all non-deprecated definitions from the uavcan namespace into cyphal with the appropriate changes to the documentation where the original namespace is referenced. All uavcan.\* definitions will be made @deprecated immediately, with their complete removal deadline set somewhere in the future. The standard register names will be updated from uavcan.\* to cyphal.\*. Nodes w… The scheme I am envisioning is a much simpler one: `cyphal.sub.id.PORT_NAME` for subjects (both subscriptions and publications), `cyphal.rpc.id.PORT_NAME` for RPC-services (both clients and servers). This will have certain positive implications on orchestration (where a multitude of topics needs to be configured at once in a config file) and for the eventual [named topic support](https://github.com/OpenCyphal-Garage/cyraft). --- _[View the full topic](https://forum.opencyphal.org/t/port-configuration-error/2114)._