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

Hi,

Looking at a couple models (isis and ospf), they appear to add their own interface lists and then refer back to the routing instance list. If we have a list of interfaces in the routing instance does it make sense for routing protocols to augment the routing-instance list rather than create their own? If not then what other data will be added to the routing instance interface?

Thanks,
Chris.

> On Jan 12, 2015, at 8:11 PM, Acee Lindem (acee) <acee@cisco.com> wrote:
> 
> Hi,
> 
> Lada and I have been discussing this issue for some time and were hoping
> for some comments from the routing community. The question is basically
> whether to have a list of interfaces in routing-instance that reference
> the RFC 7223 interfaces:
> 
>        container interfaces {
>           description
>             "Configuration of the routing instance's interfaces.";
>           list interface {
>             key "name";
>             description
>               "List of network layer interfaces assigned to the routing
>                instance.";
>             leaf name {
>               type if:interface-ref;
>               description
>                 "A reference to the name of a configured network layer
>                  interface.";
>             }
>           }
>         }
> 
> 
> 
> Or to augment the RFC 7223 interfaces to point to the routing-instance.
> 
> 
> Thanks,
> Acee
> 
> On 11/25/14, 8:16 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> 
>> Hi,
>> 
>> this issue refers the YANG module "ietf-routing" contained in
>> 
>> http://tools.ietf.org/html/draft-ietf-netmod-routing-cfg-16
>> 
>> Please indicate your preference or add comments.
>> 
>> ***** :R03: assignment of interfaces to routing instances
>>     In -16 it is done by including a network-layer interface in the
>>     list rt:interface under rt:routing-instance. An advantage of
>>     this organization is that the rt:interface list should contain
>>     only network layer interfaces for which the assignment makes
>>     sense. A drawback is that the assignment is detached from the
>>     specification of IP addresses in if:interface.
>> 
>> ****** Solution R03-1
>>      No change.
>> 
>> ****** Solution R03-2
>>      Do the assignment of an interface to a routing instance inside
>>      the if:interface entry.
>> 
>> --
>> Ladislav Lhotka, CZ.NIC Labs
>> PGP Key ID: E74E8C0C
>> 
>> _______________________________________________
>> Rtg-yang-coord mailing list
>> Rtg-yang-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
> 
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord

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

Attachment: signature.asc