# Fixing remaining deficiences in UAVCANv1 infrastructure

**URL:** <https://forum.opencyphal.org/t/fixing-remaining-deficiences-in-uavcanv1-infrastructure/1344>\
**Category:** Development & Maintenance\
**Created:** [July 14, 2021, 6:56pm UTC](https://forum.opencyphal.org/t/fixing-remaining-deficiences-in-uavcanv1-infrastructure/1344 "2021-07-14T18:56:31Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**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:** [July 15, 2021, 11:16am UTC](https://forum.opencyphal.org/t/fixing-remaining-deficiences-in-uavcanv1-infrastructure/1344/5 "2021-07-15T11:16:39Z")

</div>

Here is one extra item that I believe should be on this list:

- Formation of a new SIG dedicated to the physical layer connectivity standard.

This is expressly out of the scope of UDRAL because it is focused on the application layer. It is also out of the scope of v1 because [reasons](https://forum.opencyphal.org/t/removal-of-the-physical-layer-specification/895). I imagine that it should be mostly a no-brainer because we can just move the existing [v0 hardware specifications](https://legacy.uavcan.org/Specification/8._Hardware_design_recommendations/) over to the new standard as-is, amended with CAN FD support.

Should I go ahead and set up the SIG?

I think I should invite @PetervdPerk into this thread.

---

_[View the full topic](https://forum.opencyphal.org/t/fixing-remaining-deficiences-in-uavcanv1-infrastructure/1344)._
