Re: [netmod] WG Last Call: draft-ietf-netmod-acl-model-15

[Mahesh Jethanandani <[e-mail]>]

> On Jan 20, 2018, at 7:21 AM, Kent Watsen <[e-mail]> wrote:
> 
> Hi Mahesh,
> 
> I'm okay not adding the ability to reference an external rulebase now, or are you saying that you'd also like to defer priming the YANG model now so that it can be added later in a backwards compatible manner?
> 
> If you plan to prime the YANG model so that the ability to reference an external rulebase can added later in a backwards compatible manner, can you please send a concrete proposal to the list so that we can better understand the impact?  
> 
> My expectation is that it merely adds a 'choice' statement around the existing rulebase container, thereby enabling something other than a rulebase container to exist some day in the future.  

That is correct. The proposal is to add a ‘choice’ statement in parts of the model that will allow an external rulebase to be added in the future as another case statement.

Here is the concrete proposal of what those changes will look like:

https://github.com/netmod-wg/acl-model/pull/23 <https://github.com/netmod-wg/acl-model/pull/23>

Thanks
 
> 
> If the addition is indeed just this, then I don't believe that it materially changes the ACL model and therefore can be added as a LC comment.  Of course, the WG will want to review the addition for correctness, but otherwise should be alright.
> 
> Thanks,
> Kent // co-chair and shepherd
> 
> 
> ===== original message =====
> 
> Kent,
> 
> I have not heard a strong requirement to have the open issue fixed in this version of the RFC. We would therefore like to defer it to a bis document.
> 
> I will wait for the LC to complete, and update the draft to address all the comments received during the LC.
> 
> Thanks.
> 
>> On Jan 17, 2018, at 3:33 PM, Kent Watsen <[e-mail]> wrote:
>> 
>> 
>> H Mahesh,
>> 
>>>> - There is an open issue in the document (section 8) - are we going
>>>> to resolve that during WG last call or is this a leftover?
>>> 
>>> This will be resolved in the next version of the module. It is
>>> documented under Issues tab in GitHub. Should we remove it from
>>> the draft?
>> 
>> Most of Juergen's comments are editorial in nature and can truly be handled as part of the LC process, but this open issue has me worried, as it may result in a significant technical change.  
>> 
>> What will it take to close this open issue?  Is it just a matter of the getting the WG to agree that it's not an issue, or do we already know that it is a real issue and only the solution is pending?
>> 
>> Thanks,
>> Kent
>> 
>> 
>> 
>> 
> 
> Mahesh Jethanandani
> [e-mail]
> 
> 
> 

Mahesh Jethanandani
[e-mail]