[yang-tooling] Re: SID file issues

[Laurent Toutain <[e-mail]>]

Hi,

There is something I don't understand in the discussion about RPCs and
input/output. For me, SIDs are not here to represent a YANG module, but
rather a way to serialize information in a more compact way than JSON.

SIDs are just a way to point to leaves or sub-trees. If there is no RPC,
why impose SIDs for input and output? And if there are several RPCs,
several SIDs will be needed.

For instance, in the SID allocation I'm doing for SCHC, I don't allocate
SIDs for typedefs, since they do not appear in any serialization.

Am I wrong? What would be the consequences if some SIDs are not defined?

Thank you for your clarifications.


Laurent

On Mon, Feb 16, 2026 at 7:23 PM Andy Bierman <[e-mail]> wrote:

>
>
> On Mon, Feb 16, 2026 at 4:49 AM Carsten Bormann <[e-mail]> wrote:
>
>> On Feb 16, 2026, at 13:45, Vojtech Vilimek <vojtech.vilimek=
>> [e-mail]> wrote:
>> >
>> > Hi Laurent,
>> >
>> > I meant it more as an requirement of the RFC 9595,
>>
>> You mean
>>
>>    Note also that RPC or action "input" and "output" YANG items MUST
>>    always be assigned SIDs even if they don't contain further YANG
>>    items.  The reason for this requirement is that other modules can
>>    augment the given module and those SIDs might be necessary.
>>
>> (last para of Appendix B of RFC 9595 [1])?
>>
>>
>    The "rpc" statement defines an rpc node in the schema tree.  Under
>    the rpc node, a schema node with the name "input" and a schema node
>    with the name "output" are also defined.  The nodes "input" and
>    "output" are defined in the module's namespace.
>
>
> The input and output nodes are not like other schema nodes
>
> -  they are hard-wired to always be defined
> -  they are defined in the same namespace as the parent rpc-stmt
> -  it is not possible for another module to add its own 'input' or
> 'output' nodes
> -  the NIDs for these nodes are simply 'input' and 'output'
>
>
>
>
>> If the examples don’t meet this MUST, we’ll need to file an errata report.
>>
>
> I believe pyang 2.7.1 generates input and output nodes correctly.
>
>
>>
>> Grüße, Carsten
>>
>> [1]: https://www.rfc-editor.org/rfc/rfc9595#appendix-B-6
>>
>>
>
> Andy
>
>
>> _______________________________________________
>> yang-tooling mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>