# On Subject/Service ID ranges

**URL:** <https://forum.opencyphal.org/t/on-subject-service-id-ranges/195>\
**Category:** Development & Maintenance\
**Created:** [October 14, 2018, 2:47pm UTC](https://forum.opencyphal.org/t/on-subject-service-id-ranges/195 "2018-10-14T14:47:19Z")\
**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:** [October 19, 2018, 7:18am UTC](https://forum.opencyphal.org/t/on-subject-service-id-ranges/195/5 "2018-10-19T07:18:06Z")

</div>

> [@scottdixon](#):
>
> We’re talking about determining “dynamic” identifiers at system definition time, not (necessarily) runtime; correct?

Yes.

> [@scottdixon](#):
>
> e.g. we even have the dynamic node id assignment function

I am debating whether we should start saying “plug-and-play” instead.

> [@scottdixon](#):
>
> Perhaps static == regulated and dynamic == unregulated?

Makes sense to me.

---

_[View the full topic](https://forum.opencyphal.org/t/on-subject-service-id-ranges/195)._