Re: [netmod] Tree diagrams

Hi Tom, Med, Authors

Tom, thanks for flagging these.

Med, authors, please can you check if the tree diagrams in draft-ietf-opsawg-vpn-common-12 or draft-ietf-opsawg-l3sm-l3nm-18 need to be updated.  If they do, then given that these documents are in the RFC editor queue then we will need to coordinate any corrections with the RFC editor.

Regards,
Rob

> -----Original Message-----
> From: netmod <netmod-bounces@ietf.org> On Behalf Of tom petch
> Sent: 15 October 2021 11:03
> To: netmod@ietf.org
> Subject: [netmod] Tree diagrams
> 
> I do not understand tree diagrams.  My expectation is that the same YANG
> should produce the same tree diagram but apparently not.  I look at
> RFC8519 and see
> 
>         |        |  |  +--:(tcp)
>         |        |  |  |  +--rw tcp {match-on-tcp}?
> ............
>         |  |  |     +--rw source-port
>         |        |  |  |     |  +--rw (source-port)?
>         |        |  |  |     |     +--:(range-or-operator)
>         |        |  |  |     |        +--rw (port-range-or-operator)?
> 
> but when imported into 'draft-ietf-opsawg-vpn-common-12' this becomes
>           |  |     +--:(tcp)
>           |  |     |  +-- tcp
> ......
>           |  |     |     +-- (source-port)?
>           |  |     |     |  +--:(source-port-range-or-operator)
>           |  |     |     |     +-- source-port-range-or-operator
> ie the identifiers have gained a 'source'  (or 'destination').
> 
> Also, the structure changes.  Moving on, vpn-common has
> 
>           |  |     +--:(tcp)
>           |  |     |  +-- tcp
> .....
>           |  |     |     +-- (source-port)?
>           |  |     |     |  +--:(source-port-range-or-operator)
>           |  |     |     |     +-- source-port-range-or-operator
> .......
>           |  |     |     +-- (destination-port)?
>           |  |     |        +--:(destination-port-range-or-operator)
>           |  |     |           +-- destination-port-range-or-operator
> which looks fine until this is imported into
> 'draft-ietf-opsawg-l3sm-l3nm-18' when it becomes
> 
>    |  |     |  |     +--:(tcp)
>    |  |     |  |     |  +--rw tcp
> ...................
>    |  |     |  |     |     +--rw (source-port)?
>    |  |     |  |     |     |  +--:(source-port-range-or-operator)
>    |  |     |  |     |     |     +--rw source-port-range-or-operator
>    |  |     |  |     |     |                      inet:port-number
> 
>    |  |     |  |     |     +--rw (destination-port)?
>    |  |     |  |     +--:(destination-port-range-or-operator)
>    |  |     |  |     |          +--rw destination-port-range-or-operator
>    |  |     |  |     |             +--rw (port-range-or-operator)?
> 
> 'destination-port-range-or-operator' has moved and we now have
>    |  |     |  |     +--:(tcp)
>    |  |     |  |     +--:(destination-port-range-or-operator)
> which does not look fine to me; how can this be?
> 
> Earlier drafts of l3nm did not have this feature.
> 
> Tom Petch
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod