Re: [netmod] Live meeting? and my opinion. [Re: moving forward with schema mount]

Chris +1 on the taking too long in pursuit of the perfect model. No service provider or enterprise wants to put their network evolution on hold waiting for the IETF. Instead they will seek what they need from other SDOs as you point out. The IETF needs to modernize their process and perhaps

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

I have reviewed this draft and it addresses my earlier concerns. On Fri, Jul 7, 2017 at 2:34 PM, Kent Watsen wrote: > > > This is a notice to start a three week NETMOD WG last call for the > document: > > Network Access Control List (ACL) YANG Data Model >

[netmod] Fwd: WG Last Call for draft-ietf-netmod-acl-model-09 (until Oct 27, 2016)

I was asked to resend this to the list. -- Forwarded message -- From: David Bannister <d...@netflix.com> Date: Sat, Dec 17, 2016 at 1:06 PM Subject: Re: [netmod] WG Last Call for draft-ietf-netmod-acl-model-09 (until Oct 27, 2016) To: Kent Watsen <kwat...@juniper.net&

Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-acl-model-10.txt

ink? Do you think we should put feature statements on the > two case statements, or even move these into other modules (in the same > draft) so that there is no specialness imparted on them? > > > > What about others? I'm concerned that we may not have sufficient domain > exper

Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-acl-model-10.txt

(second try) There were no changes to the model so my concerns remain the same. Augmentation is not a scalable solution when dealing with a mutli-vendor or in some instances a multi-business-unit environment. The 'newco' example in the draft illustrates this problem. The IETF produces a

Re: [netmod] Fwd: New Version Notification for draft-ietf-netmod-acl-model-10.txt

There were no changes to the model so my concerns remain the same. Augmentation is not a scalable solution when dealing with a mutli-vendor or in some instances a multi-business-unit environment. The 'newco' example in the draft illustrates this problem. The IETF produces a 'standard' for an ACL