Hi Alex,
in earlier revisions of the ietf-routing module (up to
draft-ietf-netmod-routing-cfg-17), we had a configuration item
("recipient-ribs") that allowed for assigning RIBs to routing protocol
instances. The reason for removing it is summarized in my presentation from
IETF 92, slides 10 a
Module pedigree seems good. Other alternatives might be "module ownership"
or "module origin"
On Tue, Jun 6, 2017 at 9:30 PM, Alia Atlas wrote:
> Alia Atlas has entered the following ballot position for
> draft-ietf-netmod-yang-model-classification-07: Yes
>
> When responding, please keep the s
Hi,
I noticed that the ietf-routing YANG (published in RFC 8022) allows for
multiple instances of each control plane protocol, as well as multiple RIBs per
address family.
However I don't see any way to associate one with the other. Without additional
configuration, protocols will only place th
Adam Roach has entered the following ballot position for
draft-ietf-netmod-yang-model-classification-07: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Pl
Alia Atlas has entered the following ballot position for
draft-ietf-netmod-yang-model-classification-07: Yes
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refe
On Tue, Jun 6, 2017 at 8:02 AM, Rohit R Ranade
wrote:
> Hi All,
>
>
>
> In RFC 6022 :
>
>
>
> *2.1.3. The /netconf-state/schemas Subtree*
>
>
>
>The list of *supported schema* for the NETCONF server.
>
this usage is general meaning all modules used by the server -- not the
same as YANG
Hi All,
In RFC 6022 :
2.1.3. The /netconf-state/schemas Subtree
The list of supported schema for the NETCONF server.
In RFC 7950:
Section 5.6.4 Announcing Conformance Information in NETCONF
With this mechanism, a client can cache the supported modules for a
server and only upda
