# Cyphal-Config food for thought

**URL:** <https://forum.opencyphal.org/t/cyphal-config-food-for-thought/1848>\
**Category:** Specification\
**Created:** [March 13, 2023, 5:17pm UTC](https://forum.opencyphal.org/t/cyphal-config-food-for-thought/1848 "2023-03-13T17:17:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![scottdixon](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/scottdixon/32/39_2.png) [@scottdixon](https://forum.opencyphal.org/u/scottdixon)\
**Post date:** [March 13, 2023, 5:17pm UTC](https://forum.opencyphal.org/t/cyphal-config-food-for-thought/1848/1 "2023-03-13T17:17:45Z")

</div>

This next in my “v1.x food-for-thought” series: I wonder if standardizing on [YANG models](https://datatracker.ietf.org/doc/html/rfc6020) as a way to configure Cyphal networks would make sense. This is especially pertinent given my desire to develop Cyphal/TSN as part of a v1.x and TSN networks use YANG models to configure network equipment properly.

Anyway, just putting this out there to give people time to read and think about [RFC6020](https://datatracker.ietf.org/doc/html/rfc6020) and related material before we get into the next version design discussions.