Re: [netmod] "input"/"output" in tree diagrams

2018-10-23 Thread Martin Bjorklund
Hi,

Jernej Tuljak  wrote:
> Hi,
> 
> am I reading RFC8340 correctly by assuming "input" and "output" nodes
> are not to be part of tree diagrams and that instead input/output
> parameters are now children to the "rpc" or "action" node,
> distinguished solely via -w/ro flags?

I hope not, or that was not the intention anyway.

>   rpcs:
>     +---x get-schema
>    +---w identifier! string
>    +---w version?    string
>    +---w format? identityref
>    +--ro data?

pyang outputs

+---x get-schema
   +---w input
   |  +---w identifierstring
   |  +---w version?  string
   |  +---w format?   identityref
   +--ro output
  +--ro data?   


> Only "input parameters" and "output parameters" are mentioned, which
> seems to suggest data node children of "input" and "output", but not
> themselves. It also says nothing about which flag they receive, if
> they are intended to appear.

Yes I can see how this could be clarified.


/martin

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


[netmod] "input"/"output" in tree diagrams

2018-10-23 Thread Jernej Tuljak

Hi,

am I reading RFC8340 correctly by assuming "input" and "output" nodes 
are not to be part of tree diagrams and that instead input/output 
parameters are now children to the "rpc" or "action" node, distinguished 
solely via -w/ro flags?


  rpcs:
    +---x get-schema
   +---w identifier! string
   +---w version?    string
   +---w format? identityref
   +--ro data?

Only "input parameters" and "output parameters" are mentioned, which 
seems to suggest data node children of "input" and "output", but not 
themselves. It also says nothing about which flag they receive, if they 
are intended to appear.


Jernej

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod