Re: [Rtg-yang-coord] issue :R03: assignment of interfaces to routing instances

[Ladislav Lhotka <[e-mail]>]

Russ White <[e-mail]> writes:

>> > > 2. Add an attribute routing-instance-ref (type leafref) in interface to point
>> to the name attribute (key) of routing-instance.
>> >
>> > This is IMO a good idea, we would then have links in both directions.
>
> How often would we traverse the link from the interface to the routing
> instance? I'm trying to think of a use case where you'd be looking at
> an interface configuration or state, and need to find out which

The link from an interface to routing instance(s) would be only in state data.

> routing instance it's being "included" in, and -- given a single
> interface can be included in multiple routing instances, how would I
> know which one I'm actually looking for?

It will be a leaf-list so you will be able to see all routing instances
in which the interface is included, and hopefully find the one you are
looking for.

>
> What specific question would I be asking that would cause me to look
> at this list -- in other words, when would I ask, "what routing
> instances is this interface included in?"

For example: Which VPN is this interface part of?

Lada

>
> :-)
>
> Russ
>
>

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C