# About the allocation of dynamic nodes

**URL:** <https://forum.opencyphal.org/t/about-the-allocation-of-dynamic-nodes/1343>\
**Category:** Libcanard\
**Created:** [July 9, 2021, 7:47am UTC](https://forum.opencyphal.org/t/about-the-allocation-of-dynamic-nodes/1343 "2021-07-09T07:47:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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 9, 2021, 11:28am UTC](https://forum.opencyphal.org/t/about-the-allocation-of-dynamic-nodes/1343/2 "2021-07-09T11:28:06Z")

</div>

I think you are missing this bit of the Spec, where the fields of the data type are defined:

> <https://github.com/UAVCAN/public_regulated_data_types/blob/c043498eacfe90a56e3246d4c2e4ae81aad13082/uavcan/protocol/dynamic_node_id/1.Allocation.uavcan#L134-L146>

You can see from the above that the first byte contains the node-ID in the seven most significant bits (the bit order was [changed in v1](https://forum.opencyphal.org/t/big-endian-vs-little-endian-in-the-context-of-bit-level-encoding/428/21) btw) and the flag `first_part_of_unique_id` in the LSB.

The response is the same basically. Note that the last byte of every frame pertains to the transport layer (it’s called the “tail byte”), and the last two bytes of a multi-frame transfer payload contain the transfer-CRC.

---

_[View the full topic](https://forum.opencyphal.org/t/about-the-allocation-of-dynamic-nodes/1343)._
