-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RT / RD autoasigment by controller Flag #20
Comments
As discussed offline, this discussion goes beyond RD/RTs and may be applicable to other parameters like VLANs,... |
That's why VLAN, interface-id are optional parameters in L3NM model, so does RD. I think it has no harm to keep them since we need to accommodate various different implementation choices, e.g, multiple domain under the same administrative domain. If they are not filled, it can be computed by controller using VPN-ID and other information. |
The behavior that non-mandatory parameters and are config true are expanded by the server which hosts the yang module (either by a template or whatever mechanism is used) is perfectly compliant with NMDA architecture. |
I think the proposal you offered in opsawg session is perfectly fine since it only focus on who provide RD, RT rather than how RD RT is allocated or provided or computed or derived. With this proposal, it does cover all the cases. But if explicitly indicate RD or RT is needed, we may have face, in some case, RT is needed, in some cases RD is needed, in some case both RT and RD are needed, in some case both RT and RD are not needed. So I perfer your original proposal to address this issue. |
Martin suggestion in netmod mailing list question: |
Agreement on the Group:
|
Here is the example of empty leaf in RFC7950, is this what you are looking for? With the following leaf:
the following is an example of a valid encoding if the leaf exists:
|
Implemented in 3b74db5 with Qin's proposal: grouping rt-rd { |
Now, only the explanatory text in the draft is needed |
we close this one and maintain issue #114 |
We need to indicate wether the RT and RDs are provided by the Network Operator / service orchestrator or they are automatically asigned by the controller which has the l3nm module
The text was updated successfully, but these errors were encountered: