Re: [CCAMP] draft-ietf-ccamp-client-signal-yang references to bandwidth profiles, make it a leafref

Hi Roque,

I agree with you. It should be a leafref to allow for YANG auto validation.
Thanks for the catch.

Aihua

On Mon, Jun 15, 2020 at 1:02 PM Roque Gagliano (rogaglia) <rogaglia=
40cisco.com@dmarc.ietf.org> wrote:

> Hi,
>
>
>
> I implemented the draft and I think the bandwidth-profile should be a
> leaf-ref and not a string (for both directions symmetrical and
> asymmetrical):
>
>
>
>           |  +--rw (direction)?
>
>           |  |  +--:(symmetrical)
>
>           |  |  |  +--rw ingress-egress-bandwidth-profile
>
>           |  |  |     +--rw (style)?
>
>           |  |  |        +--:(named)
>
>           |  |  |        |  +--rw bandwidth-profile-name?
>
>           |  |  |        |          string                    We need a
> leafref to the definition of the bandwidth-profile
>
>           |  |  |        +--:(value)
>
>
>
> In particular, I believe it should be:
>
> type leafref {
>
>                    path "/ethtsvc:etht-svc/ethtsvc:globals/ethtsvc:named-bandwidth-profiles/ethtsvc:bandwidth-profile-name";
>
>                }
>
>
>
> Why is this important? As an implementor, I need to understand the
> relationship between these nodes in order to select the right order of
> RESTCONF commands.
>
>
>
> If the leafref is not present, I would assume that the nodes are not
> related and I could try to delete a “named-bandwidth-profile” that is
> actually used in a service. Also, when I am trying to delete both a
> “named-bandwidth profile” and all its associated services, I would need to
> delete the service first and the profile later (when there Is not instance
> that reference it).
>
>
>
> For all of this to happen, as both nodes belong to different trees, I need
> to reference them to make the association explicit for a compiler.
>
>
>
> Regards,
>
> Roque
>
>
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>