# Service/message ID alocation registry - initial thoughts

**URL:** <https://forum.opencyphal.org/t/service-message-id-alocation-registry-initial-thoughts/1470>\
**Category:** General\
**Created:** [September 30, 2021, 6:34pm UTC](https://forum.opencyphal.org/t/service-message-id-alocation-registry-initial-thoughts/1470 "2021-09-30T18:34:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![VadimZ](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/vadimz/32/434_2.png) [@VadimZ](https://forum.opencyphal.org/u/VadimZ)\
**Post date:** [September 30, 2021, 6:34pm UTC](https://forum.opencyphal.org/t/service-message-id-alocation-registry-initial-thoughts/1470/1 "2021-09-30T18:34:26Z")

</div>

Quick dump of my thoughts and previous discussion regarding the message ID allocation files.

1. There are several options to define split between instance # and message ID parts, for usages like message routing in the receiver and parsing in analyzers.

2. It is highly desirable to allow compiling this file to get all the information required to configure a system and parse logs. Therefore inclusion of URL where full message DSDL can be retrieved.

3. Picking option 4 for the instance\_ID range, the main content of the file would be a collection of triplets { service\_name, message\_type, port\_range }

4. @pavel.kirienko prefers to use YAML as a format, therefore the following example :

```auto
version: 1
uri:
    reg: https://github.com/UAVCAN/public_regulated_data_types/tree/udral/reg
reg.udral.srv.battery:
    status:
        type: reg.udral.service.battery.Status.0.2
        id: [100, 110]
    energy:
    ...

```